-
Notifications
You must be signed in to change notification settings - Fork 82
[Collaboration] Added doc for latest changes #2965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 5 commits
307050f
c2ffbc7
83da25f
2b31cda
4e18cd7
e6ae7e6
58e8739
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -23,7 +23,7 @@ The system automatically tracks changes, allowing seamless collaboration within | |||||
|
|
||||||
| Collaborative editing is an opt-in available as an LTS update starting with the v4.6.24 in all [[= product_name =]] editions. | ||||||
| To start using Collaborative editing, you must first install the required packages and perform initial configuration. | ||||||
| To use Real-time editing feature, you must make arrangements with [[= product_name_base =]], and accept Terms & Conditions and Service Level Agreement in the Support Portal. | ||||||
| To use Real-time editing feature, you must make arrangements with [[= product_name_base =]], and accept Terms & Conditions and Service Level Agreement in the Service Portal. | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| ## Prerequisites | ||||||
|
|
||||||
|
|
@@ -51,13 +51,17 @@ Collaboration session begins when first invited user accepts the invitation and | |||||
|
|
||||||
| To start collaborative editing, you need to invite collaborators using the **Share** button. | ||||||
|
|
||||||
| You can invite other users to join the session, both internal and external: | ||||||
| The owner of the draft can invite other users to join the session, both internal and external: | ||||||
|
|
||||||
| - **Internal** - by searching their name or email address. These users can either edit the content item or preview it, depending on your choice. | ||||||
| - **External** - by providing their email address in the field. They can only preview the content item. | ||||||
|
|
||||||
| Once they accept the invitation, they are able to join you in editing content item or reviewing it. | ||||||
|
|
||||||
| Once the invitation is accepted, internal users can invite further users if their permissions allow for it. | ||||||
| To do so, they must be a part of an active collaboration session. | ||||||
| Gaining access to the draft through other means, for example by [workflow](workflow.md), doesn't allow inviting other users. | ||||||
|
||||||
| Gaining access to the draft through other means, for example by [workflow](workflow.md), doesn't allow inviting other users. | |
| Gaining access to the draft through other methods, for example by [workflow](workflow.md), doesn't allow to invite other users. |
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -166,8 +166,60 @@ | |||||
|
|
||||||
| The following setting is available: | ||||||
|
|
||||||
| - `content_type_groups` – defines groups of content types for which the **Share** button is displayed (it can still be disabled for specific content types within these groups) | ||||||
| - `content_type_groups` – defines groups of content types for which the **Share** button is displayed (it can still be disabled for specific content types within these groups by using the `excluded_content_types` setting) | ||||||
|
|
||||||
| In the example confugiration above, the **Share** button is displayed for any content that belongs to the `Content` group, except for `tag` and `product_category_tag` content types. | ||||||
| In the example configuration above, the **Share** button is displayed for any content that belongs to the `Content` group, except for `tag` and `product_category_tag` content types. | ||||||
|
|
||||||
| You can also control which user content types can use the feature by using the `ibexa.share.permission_check_context.content.user_content_type_identifiers` container parameter. | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| It accepts an array of content type identifiers and the default value is `['editor']`. | ||||||
mnocon marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
| You can now restart you application and start [working with the Collaborative editing feature]([[= user_doc =]]/content_management/collaborative_editing/work_with_collaborative_editing/). | ||||||
| To add the real-time editing capabilities, continue with the instruction below. | ||||||
|
|
||||||
| ## Configure real-time editing | ||||||
|
|
||||||
| You must have an arrangment with Ibexa before configuring the real-time editing. | ||||||
|
Check failure on line 181 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| If you haven't already, you must also accept the Terms of Service in the [Service portal](https://support.ibexa.co/). | ||||||
|
|
||||||
| Only then you can create a new collaborative editing environment. | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| To do it, go to your Service Portal and select **Create environment** (this requires the **Portal administrator** access level). | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| With the environment created, you can continue the configuration in [[= product_name =]]. | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| Use the generated values to set the `environment_id`, `environment_secret`, and `web_socket_url` for your [repositories](repository_configuration.md) as in the example below: | ||||||
|
|
||||||
| ``` yaml | ||||||
| ibexa: | ||||||
| repositories: | ||||||
| default: | ||||||
| fieldtype_richtext_rte: | ||||||
| environment_id: '%env(CKEDITOR_ENVIRONMENT_ID)%' | ||||||
| environment_secret: '%env(CKEDITOR_ENVIRONMENT_SECRET)%' | ||||||
| web_socket_url: '%env(CKEDITOR_WEB_SOCKET_URL)%' | ||||||
| ``` | ||||||
|
|
||||||
| Then, enable real-time editing for specific [SiteAccesses](siteaccess.md). | ||||||
|
Check failure on line 201 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
| The following example enables it for the back office: | ||||||
|
|
||||||
| ``` yaml | ||||||
| ibexa: | ||||||
| system: | ||||||
| admin_group: | ||||||
| fieldtype_richtext_rte: | ||||||
| enabled: true | ||||||
| ``` | ||||||
|
|
||||||
| Finish the configuration by running: | ||||||
|
|
||||||
| ``` bash | ||||||
| composer run post-install-cmd | ||||||
| ``` | ||||||
|
|
||||||
| ## Accepting new Terms of Service | ||||||
|
|
||||||
| Real-Time Collaboration service is only available after accepting its Terms and Conditions. | ||||||
| When Ibexa releases a new version of this document, the new version must be accepted before the appointed deadline. | ||||||
|
Check failure on line 221 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| The **Portal administrator** for your [Service portal](https://support.ibexa.co) can accept it in Service portal's service details. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd keep it here, as there can be multiple service portals |
||||||
|
|
||||||
| If not done in time, the Real-Time Collaboration service will be disabled until the latest Terms and Conditions are accepted. | ||||||
|
Check warning on line 225 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -63,6 +63,46 @@ | |||||
| |------|------|------| | ||||||
| |`1`|"Forbid"|The user cannot change owner of a content item| | ||||||
|
|
||||||
| ## Collaborative editing limitations [[% include 'snippets/lts-update_badge.md' %]] | ||||||
|
|
||||||
| The collaborative editing limitations specify how the user can use the [collaborative editing](collaborative_editing.md) feature. | ||||||
|
||||||
| The collaborative editing limitations specify how the user can use the [collaborative editing](collaborative_editing.md) feature. | |
| The Collaborative editing limitations specify how the user can use the [Collaborative editing](collaborative_editing.md) feature. |
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Check failure on line 75 in docs/permissions/limitation_reference.md
GitHub Actions / vale
[vale] docs/permissions/limitation_reference.md#L75
[Ibexa.Gender] Use they/their instead of 'his'.
Raw output
{"message": "[Ibexa.Gender] Use they/their instead of 'his'.", "location": {"path": "docs/permissions/limitation_reference.md", "range": {"start": {"line": 75, "column": 3}}}, "severity": "ERROR"}
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -133,6 +133,8 @@ For example, to enable the user to edit only content in the "Design" stage and t | |||||
| - `content/edit` with `WorkflowStageLimitation` set to "Design". | ||||||
| - `workflow/change_stage` with `WorkflowTransitionLimitation` set to `to_proofreading` | ||||||
|
|
||||||
| When using the [Collaborative editing LTS Update](collaborative_editing.md), see the [collaborative editing policies](policies.md#content-collaborative-editing) for collaborative editing without defining a strict workflow. | ||||||
mnocon marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| When using the [Collaborative editing LTS Update](collaborative_editing.md), see the [collaborative editing policies](policies.md#content-collaborative-editing) for collaborative editing without defining a strict workflow. | |
| When using the [Collaborative editing LTS Update](collaborative_editing.md), see the [Collaborative editing policies](policies.md#content-collaborative-editing) for collaborative editing without defining a strict workflow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: feature or LTS update aa it is for 4.6?
Also, for the consistency: