diff --git a/code_samples/ibexa_engage/config/packages/ibexa_connector_qualifio.yaml b/code_samples/qualifio/config/packages/ibexa_connector_qualifio.yaml similarity index 100% rename from code_samples/ibexa_engage/config/packages/ibexa_connector_qualifio.yaml rename to code_samples/qualifio/config/packages/ibexa_connector_qualifio.yaml diff --git a/code_samples/cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php b/code_samples/raptor_cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php similarity index 100% rename from code_samples/cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php rename to code_samples/raptor_cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php diff --git a/docs/administration/admin_panel/admin_panel.md b/docs/administration/admin_panel/admin_panel.md index dc5c18cad13..5b4f0abe15c 100644 --- a/docs/administration/admin_panel/admin_panel.md +++ b/docs/administration/admin_panel/admin_panel.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP back office contains managements options for permissions, users, languages, content types, and system information. +description: Cohesivo back office contains managements options for permissions, users, languages, content types, and system information. page_type: landing_page --- diff --git a/docs/administration/admin_panel/languages_admin_panel.md b/docs/administration/admin_panel/languages_admin_panel.md index fd6842bf400..5395bbbd807 100644 --- a/docs/administration/admin_panel/languages_admin_panel.md +++ b/docs/administration/admin_panel/languages_admin_panel.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP offers the ability to create multiple translations of your website. +description: Cohesivo offers the ability to create multiple translations of your website. --- # Languages diff --git a/docs/administration/administration.md b/docs/administration/administration.md index 6a333d4feab..b371a4788a6 100644 --- a/docs/administration/administration.md +++ b/docs/administration/administration.md @@ -1,5 +1,5 @@ --- -description: Administer and configure your Ibexa DXP installation. +description: Administer and configure your Cohesivo installation. page_type: landing_page --- diff --git a/docs/administration/back_office/product_tour.md b/docs/administration/back_office/product_tour.md index 1fa5f5cb3ee..ec8df708c5c 100644 --- a/docs/administration/back_office/product_tour.md +++ b/docs/administration/back_office/product_tour.md @@ -1,5 +1,5 @@ --- -description: Product tours provide interactive guided walkthroughs to help users learn Ibexa DXP features. +description: Product tours provide interactive guided walkthroughs to help users learn Cohesivo features. edition: lts-update month_change: false --- diff --git a/docs/administration/configuration/configuration.md b/docs/administration/configuration/configuration.md index 5ff421bebb7..2d9b8c9900d 100644 --- a/docs/administration/configuration/configuration.md +++ b/docs/administration/configuration/configuration.md @@ -1,5 +1,5 @@ --- -description: In Ibexa DXP you store and manage configuration in project files, typically in YAML format. +description: In Cohesivo you store and manage configuration in project files, typically in YAML format. --- # Configuration diff --git a/docs/administration/project_organization/architecture.md b/docs/administration/project_organization/architecture.md index ae9519f1b28..b2169989302 100644 --- a/docs/administration/project_organization/architecture.md +++ b/docs/administration/project_organization/architecture.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP architecture is structured in multiple layers connected by APIs. +description: Cohesivo architecture is structured in multiple layers connected by APIs. --- # Architecture @@ -7,7 +7,7 @@ description: Ibexa DXP architecture is structured in multiple layers connected b [[= product_name =]] architecture is based on the philosophy to **use APIs** that is maintained in the long term. This **makes upgrades easier and provides lossless couplings** between all parts of the architecture, at the same time improving the migration capabilities of the system. -The structure of an [[= product_name =]] app is based on the Symfony framework but content management functions rely on the public PHP API. +The structure of a [[= product_name =]] app is based on the Symfony framework but content management functions rely on the public PHP API. Other applications integrate with [[= product_name =]] via REST API, which also relies on the public PHP API. ![Architecture](architecture.png "Architecture") @@ -16,11 +16,11 @@ The architecture of [[= product_name =]] is layered and uses clearly defined API | Layer | Description | |-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Back office](back_office_configuration.md) | Back office contains all the necessary parts to run the [[= product_name =]] back office interface. | +| [Back office](back_office_configuration.md) | Back office contains all the necessary parts to run the [[= product_name =]]'s back office interface. | | [HTTP Cache](http_cache.md) | Symfony HTTP cache is used to manage content "view" cache with an expiration model. In addition it is extended by using FOSHttpCache to add several advanced features. | | [Controllers](controllers.md) | Controllers created by you to read information from a Request object, create and return a Response objects. | | [Twig templates](twig_function_reference.md) | Set of custom and built-in Twig templates. User interfaces are developed with the Twig template engine and query the public PHP API directly. | -| [REST API v2](rest_api_usage.md) | The REST API v2 enables you to interact with an [[= product_name =]] installation through the HTTP protocol, following a REST interaction model. | +| [REST API v2](rest_api_usage.md) | The REST API v2 enables you to interact with a [[= product_name =]] installation through the HTTP protocol, following a REST interaction model. | | [GraphQL](graphql.md) | GraphQL for [[= product_name =]] exposes the domain model using the repository, based on content type groups, content types and field definitions. | | [Public PHP API](php_api.md) | Public PHP API exposes the repository which enables you to create, read, update, manage and delete all objects available in [[= product_name =]]. | | Business Logic | The business logic is defined in the kernel. This business logic is exposed to applications via an API. It is used to organize development of the user interface layer. | diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md index 581d388dbcd..b374e70b85a 100644 --- a/docs/administration/project_organization/bundles.md +++ b/docs/administration/project_organization/bundles.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP is composed of bundles containing different parts of the application. +description: Cohesivo is composed of bundles containing different parts of the application. page_type: reference --- @@ -113,7 +113,7 @@ To remove a bundle (either one you created yourself, or an out-of-the-box one th |ibexa/permissions|Additional permission functionalities| |ibexa/segmentation|Segment functionality for profiling the content displayed to specific users| |ibexa/site-factory|Enables configuration of sites from UI| -|ibexa/engage|Enables integration with [Qualifio Engage platform](https://developers.qualifio.com/docs/engage/)| +|ibexa/engage|Enables integration with [[[= product_name_engage =]]](https://developers.qualifio.com/docs/engage/)| ## [[= product_name_com =]] packages @@ -138,7 +138,7 @@ The following packages are optional and can be installed independently. |Bundle|Description| |---------|-----------| |[ibexa/automated-translation](https://github.com/ibexa/automated-translation)|Automated translation of content using [Google Translate or DeepL](automated_translations.md)| -|ibexa/cdp|Integration with the [Customer Data Platform](cdp.md)| +|ibexa/cdp|Integration with [[[= product_name_cdp =]]](../../raptor_cdp/raptor_cdp.md)| |[ibexa/cloud](https://github.com/ibexa/cloud)|Integration with [[[= product_name_cloud =]]](/ibexa_cloud/ibexa_cloud.md)| In addition, you can extend the capabilities of your project by installing additional [LTS Updates](editions.md#lts-updates). diff --git a/docs/administration/project_organization/project_organization.md b/docs/administration/project_organization/project_organization.md index 5803cea48de..6a40afc6513 100644 --- a/docs/administration/project_organization/project_organization.md +++ b/docs/administration/project_organization/project_organization.md @@ -1,5 +1,5 @@ --- -description: An Ibexa DXP project follows Symfony's directory structure to organize files in the project. +description: A Cohesivo project follows Symfony's directory structure to organize files in the project. --- # Project organization diff --git a/docs/administration/recent_activity/recent_activity.md b/docs/administration/recent_activity/recent_activity.md index eb39877f93f..59a00dd93bc 100644 --- a/docs/administration/recent_activity/recent_activity.md +++ b/docs/administration/recent_activity/recent_activity.md @@ -34,7 +34,7 @@ ibexa: To automate a regular truncation, you must schedule the command `ibexa:activity-log:truncate`. To minimize the number of entries to delete, it's recommended that you execute the command more than one time a day. -For more information, see [Additional scheduled tasks and advanced usage](install_ibexa_dxp.md#additional-scheduled-tasks-and-advanced-usage). +For more information, see [Additional scheduled tasks and advanced usage](install_cohesivo.md#additional-scheduled-tasks-and-advanced-usage). ### Display limit diff --git a/docs/ai/ai.md b/docs/ai/ai.md index 846866e5de9..775b6e4b6ef 100644 --- a/docs/ai/ai.md +++ b/docs/ai/ai.md @@ -1,5 +1,5 @@ --- -description: AI interactions with [[= product_name =]] +description: AI interactions with Cohesivo page_type: landing_page month_change: false --- diff --git a/docs/ai/ai_actions/ai_actions_guide.md b/docs/ai/ai_actions/ai_actions_guide.md index 33be6a9056b..0bf5abc073d 100644 --- a/docs/ai/ai_actions/ai_actions_guide.md +++ b/docs/ai/ai_actions/ai_actions_guide.md @@ -140,7 +140,7 @@ For example, if this is your organization's requirement, a developer could write ## Use cases -Out of the box, after you configure access to the OpenAI service, the [[= product_name_base =]] AI Actions come with two action types that can help your organization with the following tasks. +Out of the box, after you configure access to the OpenAI service, AI Actions come with two action types that can help your organization with the following tasks. ### Refining text diff --git a/docs/ai/mcp/img/diagram_source/mcp-com-diagram.drawio b/docs/ai/mcp/img/diagram_source/mcp-com-diagram.drawio index 5e1b2ba3267..385a73213ae 100644 --- a/docs/ai/mcp/img/diagram_source/mcp-com-diagram.drawio +++ b/docs/ai/mcp/img/diagram_source/mcp-com-diagram.drawio @@ -4,7 +4,7 @@ - + diff --git a/docs/ai/mcp/img/mcp-com-diagram.png b/docs/ai/mcp/img/mcp-com-diagram.png index 993d078ffc3..9a38d468493 100644 Binary files a/docs/ai/mcp/img/mcp-com-diagram.png and b/docs/ai/mcp/img/mcp-com-diagram.png differ diff --git a/docs/ai/mcp/mcp.md b/docs/ai/mcp/mcp.md index aa23e201396..d6f7df2b662 100644 --- a/docs/ai/mcp/mcp.md +++ b/docs/ai/mcp/mcp.md @@ -1,5 +1,5 @@ --- -description: Overview of MCP resources in [[= product_name =]] +description: Overview of MCP resources in Cohesivo page_type: landing_page edition: lts-update month_change: false diff --git a/docs/ai/mcp/mcp_guide.md b/docs/ai/mcp/mcp_guide.md index 4aa1977b436..12ad3ee266c 100644 --- a/docs/ai/mcp/mcp_guide.md +++ b/docs/ai/mcp/mcp_guide.md @@ -27,7 +27,7 @@ An MCP server allows the agent to discover available tools, inspect their parame ## Availability -MCP Servers feature is an [LTS Update package](editions.md#lts-updates) available starting with the v5.0.8 in all Ibexa DXP editions. +MCP Servers feature is an [LTS Update package](editions.md#lts-updates) available starting with the v5.0.8 in all [[= product_name =]] editions. ## Capabilities diff --git a/docs/ai/mcp/mcp_usage.md b/docs/ai/mcp/mcp_usage.md index 9741037921c..fe82fa47218 100644 --- a/docs/ai/mcp/mcp_usage.md +++ b/docs/ai/mcp/mcp_usage.md @@ -91,10 +91,10 @@ The server: !!! note "Storage choice recommendations" Filesystem storage is convenient for the sake of this example and for testing. - For production, it is recommended that you use Redis or Valkey to share cache among the cluster and improve performance. + For production, it's recommended that you use Redis or Valkey to share cache among the cluster and improve performance. - For development, you can set `discovery_cache: ~` to avoid clearing the cache after each change. - This example uses the filesystem storage to illustrate that you have to clear the cache pool to refresh the available capabilities, exactly as when deploying into production. + For development, you can set `discovery_cache: ~` to avoid clearing the cache after each change. + This example uses the filesystem storage to illustrate that you have to clear the cache pool to refresh the available capabilities, exactly as when deploying into production. In a new `config/packages/mcp.yaml` file, define a new MCP server for the `default` repository and assign it to all SiteAccesses: diff --git a/docs/api/api.md b/docs/api/api.md index 7d3cf2ede9d..b7f13972d57 100644 --- a/docs/api/api.md +++ b/docs/api/api.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP is an API-first product and provides APIs to handle content and repository information. +description: Cohesivo is an API-first product and provides APIs to handle content and repository information. page_type: landing_page --- diff --git a/docs/api/event_reference/event_reference.md b/docs/api/event_reference/event_reference.md index 6cc5792d698..99bab1fa3a3 100644 --- a/docs/api/event_reference/event_reference.md +++ b/docs/api/event_reference/event_reference.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP dispatches events before and after you perform different operations in the back office and on the Repository. +description: Cohesivo dispatches events before and after you perform different operations in the back office and on the Repository. page_type: reference --- diff --git a/docs/api/graphql/graphql.md b/docs/api/graphql/graphql.md index 6268c09a635..8693f353c57 100644 --- a/docs/api/graphql/graphql.md +++ b/docs/api/graphql/graphql.md @@ -1,5 +1,5 @@ --- -description: GraphQL enables making concise, readable requests to Ibexa DXP APIs. +description: GraphQL enables making concise, readable requests to Cohesivo APIs. --- # GraphQL diff --git a/docs/api/php_api/php_api_reference/index.html b/docs/api/php_api/php_api_reference/index.html index 3fe85b168ea..8027292b89c 100644 --- a/docs/api/php_api/php_api_reference/index.html +++ b/docs/api/php_api/php_api_reference/index.html @@ -49669,7 +49669,7 @@

PHP API Reference

- Ibexa DXP's public PHP API is defined in the + Cohesivo's public PHP API is defined in the Ibexa\Contracts namespace. Ibexa promises backward compatibility to API consumers.

diff --git a/docs/api/rest_api/rest_api_authentication.md b/docs/api/rest_api/rest_api_authentication.md index ceb782304c1..3e87258701d 100644 --- a/docs/api/rest_api/rest_api_authentication.md +++ b/docs/api/rest_api/rest_api_authentication.md @@ -343,7 +343,7 @@ security: ibexa_rest: host: ^api\.example\.com$ http_basic: - realm: Ibexa DXP REST API + realm: Cohesivo REST API #ibexa_front: # ... ``` diff --git a/docs/api/rest_api/rest_api_usage/rest_api_usage.md b/docs/api/rest_api/rest_api_usage/rest_api_usage.md index db775828fee..222f825b7bf 100644 --- a/docs/api/rest_api/rest_api_usage/rest_api_usage.md +++ b/docs/api/rest_api/rest_api_usage/rest_api_usage.md @@ -1,10 +1,10 @@ --- -description: The REST API covers objects in the Ibexa DXP Repository with regular and custom HTTP methods, such as GET or PUBLISH, and HTTP headers. +description: The REST API covers objects in the Cohesivo Repository with regular and custom HTTP methods, such as GET or PUBLISH, and HTTP headers. --- # REST API usage -The REST API in [[= product_name =]] allows you to interact with an [[= product_name =]] installation by using the HTTP protocol, following a [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) interaction model. +The REST API in [[= product_name =]] allows you to interact with the [[= product_name =]] installation by using the HTTP protocol, following a [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) interaction model. Each resource (URI) interacts with a part of the system (like content, users or search). Every interaction with the repository than you can do from back office or by using the [Public PHP API](php_api.md) can also be done with the REST API. diff --git a/docs/cdp/cdp_activation/cdp_activation.md b/docs/cdp/cdp_activation/cdp_activation.md deleted file mode 100644 index f93aa9a94c8..00000000000 --- a/docs/cdp/cdp_activation/cdp_activation.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -description: Step-by-step activation procedure of Ibexa CDP. -page_type: landing_page -edition: experience ---- - -# CDP Activation - -Follow a step-by-step procedure that allows you to activate [[= product_name_cdp =]]. - -Activation includes configuration, data export and adding tracking. - -[[= cards([ - "cdp/cdp_activation/cdp_configuration", - "cdp/cdp_activation/cdp_data_export", - "cdp/cdp_activation/cdp_add_tracking", -], columns=3) =]] diff --git a/docs/cdp/img/cdp_how_works.png b/docs/cdp/img/cdp_how_works.png deleted file mode 100644 index 2bbbc01215f..00000000000 Binary files a/docs/cdp/img/cdp_how_works.png and /dev/null differ diff --git a/docs/commerce/commerce.md b/docs/commerce/commerce.md index 773bdb8f99c..9e84ecfb728 100644 --- a/docs/commerce/commerce.md +++ b/docs/commerce/commerce.md @@ -1,5 +1,5 @@ --- -description: The commerce component of Ibexa DXP covers various steps of making a transaction from listing available products, through adding products to a cart, to checkout and confirmation. +description: The commerce component of Cohesivo covers various steps of making a transaction from listing available products, through adding products to a cart, to checkout and confirmation. edition: commerce page_type: landing_page --- diff --git a/docs/content_management/content_management.md b/docs/content_management/content_management.md index d83dda32712..02d6abe4efd 100644 --- a/docs/content_management/content_management.md +++ b/docs/content_management/content_management.md @@ -1,5 +1,5 @@ --- -description: Manage content in Ibexa DXP by learning about the content model, field types, pages, forms, workflows, and more. +description: Manage content in Cohesivo by learning about the content model, field types, pages, forms, workflows, and more. page_type: landing_page --- diff --git a/docs/content_management/content_model.md b/docs/content_management/content_model.md index 272c76fedf8..7a80c06ca4d 100644 --- a/docs/content_management/content_model.md +++ b/docs/content_management/content_model.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP's content model relies on content items that are instances of content types and contain content fields. +description: Cohesivo's content model relies on content items that are instances of content types and contain content fields. --- # Content model diff --git a/docs/content_management/data_migration/data_migration.md b/docs/content_management/data_migration/data_migration.md index d3230cc111d..55e256cc0ab 100644 --- a/docs/content_management/data_migration/data_migration.md +++ b/docs/content_management/data_migration/data_migration.md @@ -5,7 +5,7 @@ page_type: landing_page # Data migration -Data migration allows exporting and importing selected data from an [[= product_name =]] installation. +Data migration allows exporting and importing selected data from a [[= product_name =]] installation. [*Exporting*](exporting_data.md) data consists in saving selected repository information in YAML format. [*Importing*](importing_data.md) reads migration YAML files and creates or modifies repository content based on them. diff --git a/docs/content_management/field_types/field_type_reference/field_type_reference.md b/docs/content_management/field_types/field_type_reference/field_type_reference.md index 275a3527bea..a39315f7e70 100644 --- a/docs/content_management/field_types/field_type_reference/field_type_reference.md +++ b/docs/content_management/field_types/field_type_reference/field_type_reference.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP offers a range of built-in field types that cover most common needs when creating content. +description: Cohesivo offers a range of built-in field types that cover most common needs when creating content. page_type: reference month_change: false --- diff --git a/docs/content_management/images/fastly_io.md b/docs/content_management/images/fastly_io.md index bd3eab6c35e..d092b69519d 100644 --- a/docs/content_management/images/fastly_io.md +++ b/docs/content_management/images/fastly_io.md @@ -11,7 +11,7 @@ To be able to configure this feature, you need [Fastly IO subscription](https:// ## Enable shielding -To use Fastly Image Optimizer, you first need a [working setup of Ibexa DXP and Fastly](reverse_proxy.md#using-varnish-or-fastly) +To use Fastly Image Optimizer, you first need a [working setup of [[= product_name =]] and Fastly](../../infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md#using-varnish-or-fastly) with shielding enabled. To enable shielding, follow the steps in [Fastly Developer Documentation](https://www.fastly.com/documentation/guides/concepts/shielding/#enabling-and-disabling-shielding). Remember to choose a shield location from the **Shielding** menu, as described in [Fastly User Documentation](https://www.fastly.com/documentation/guides/getting-started/hosts/shielding/#enabling-shielding). diff --git a/docs/content_management/pages/page_builder_guide.md b/docs/content_management/pages/page_builder_guide.md index 4dc104396d8..c788655ffc6 100644 --- a/docs/content_management/pages/page_builder_guide.md +++ b/docs/content_management/pages/page_builder_guide.md @@ -1,5 +1,5 @@ --- -description: Read about the Page Builder - a powerful tool for creating and modifying pages in Ibexa DXP. +description: Read about the Page Builder - a powerful tool for creating and modifying pages in Cohesivo. edition: experience month_change: false --- diff --git a/docs/content_management/rich_text/online_editor_guide.md b/docs/content_management/rich_text/online_editor_guide.md index 72471f2ef48..a2a641e7b09 100644 --- a/docs/content_management/rich_text/online_editor_guide.md +++ b/docs/content_management/rich_text/online_editor_guide.md @@ -1,5 +1,5 @@ --- -description: Learn how to use the Online Editor, a tool that allows you to edit RichText Fields in any content item in Ibexa DXP. +description: Learn how to use the Online Editor, a tool that allows you to edit RichText Fields in any content item in Cohesivo. --- # Online Editor product guide diff --git a/docs/content_management/rich_text/rich_text.md b/docs/content_management/rich_text/rich_text.md index 5921b7017f0..60013a8700c 100644 --- a/docs/content_management/rich_text/rich_text.md +++ b/docs/content_management/rich_text/rich_text.md @@ -1,5 +1,5 @@ --- -description: RichText is a type of field that you add in any content item in Ibexa DXP and edit in Online Editor. +description: RichText is a type of field that you add in any content item in Cohesivo and edit in Online Editor. page_type: landing_page --- diff --git a/docs/content_management/url_management/url_management.md b/docs/content_management/url_management/url_management.md index 8fdb19956f5..6d109ae0b55 100644 --- a/docs/content_management/url_management/url_management.md +++ b/docs/content_management/url_management/url_management.md @@ -37,7 +37,7 @@ The following protocols are currently supported: To enable automatic URL validation, set up a scheduled task to run the `ibexa:check-urls` command periodically. -For more information, see [Additional scheduled tasks and advanced usage](install_ibexa_dxp.md#additional-scheduled-tasks-and-advanced-usage). +For more information, see [Additional scheduled tasks and advanced usage](install_cohesivo.md#additional-scheduled-tasks-and-advanced-usage). ### Configuration diff --git a/docs/customer_management/customer_portal_guide.md b/docs/customer_management/customer_portal_guide.md index b3a41e7d39b..b81e830a90d 100644 --- a/docs/customer_management/customer_portal_guide.md +++ b/docs/customer_management/customer_portal_guide.md @@ -15,7 +15,7 @@ With this feature, your customers can self-register, edit their organization inf ## Availability -Customer Portal is available in [[= product_name_exp =]]. It's also compatible with PIM, Commerce and [[= product_name_connect =]]. +Customer Portal is available in [[= product_name_exp =]]. It's also compatible with Product catalog, Commerce and [[= product_name_connect =]]. ## How does Customer Portal work? diff --git a/docs/discounts/configure_discounts.md b/docs/discounts/configure_discounts.md index 425915e4b8a..00868134f2e 100644 --- a/docs/discounts/configure_discounts.md +++ b/docs/discounts/configure_discounts.md @@ -55,7 +55,7 @@ php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenge php bin/console ibexa:discounts:reindex ``` -For more information about command scheduling, see [Additional scheduled tasks and advanced usage](install_ibexa_dxp.md#additional-scheduled-tasks-and-advanced-usage). +For more information about command scheduling, see [Additional scheduled tasks and advanced usage](install_cohesivo.md#additional-scheduled-tasks-and-advanced-usage). !!! note "Deploying Symfony Messenger" diff --git a/docs/getting_started/first_steps.md b/docs/getting_started/first_steps.md index 9f9ffbb916d..2cdbb1df347 100644 --- a/docs/getting_started/first_steps.md +++ b/docs/getting_started/first_steps.md @@ -1,5 +1,5 @@ --- -description: Start off working with Ibexa DXP by doing initial configuration and testing system capabilities. +description: Start off working with Cohesivo by doing initial configuration and testing system capabilities. --- # First steps diff --git a/docs/getting_started/getting_started.md b/docs/getting_started/getting_started.md index 67e89c4cd3e..84eace2204c 100644 --- a/docs/getting_started/getting_started.md +++ b/docs/getting_started/getting_started.md @@ -1,5 +1,5 @@ --- -description: Get started working with Ibexa DXP by learning about the requirements and installing the platform. +description: Get started working with Cohesivo by learning about the requirements and installing the platform. page_type: landing_page --- @@ -9,6 +9,6 @@ To get started working with [[= product_name =]], see how you can get an install [[= cards([ "getting_started/requirements", - "getting_started/install_ibexa_dxp", + "getting_started/install_cohesivo", "getting_started/first_steps", ], columns=3) =]] diff --git a/docs/getting_started/install_ibexa_dxp.md b/docs/getting_started/install_cohesivo.md similarity index 94% rename from docs/getting_started/install_ibexa_dxp.md rename to docs/getting_started/install_cohesivo.md index 4d51637bb12..d9a319d839b 100644 --- a/docs/getting_started/install_ibexa_dxp.md +++ b/docs/getting_started/install_cohesivo.md @@ -1,9 +1,9 @@ --- -description: Install Ibexa DXP on a Linux system and prepare your installation for production. +description: Install Cohesivo on a Linux system and prepare your installation for production. month_change: false --- -# Install Ibexa DXP +# Install [[= product_name =]] !!! note @@ -436,7 +436,7 @@ Use [`cron`](https://en.wikipedia.org/wiki/Cron) to run it every minute. The following example creates a temporary crontab entry file and appends it to the existing crontab for the web server user (`www-data`): ```bash -echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod' > ibexa_cron.txt +echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod' > ibexa_cron.txt crontab -u www-data -l | cat - ibexa_cron.txt | crontab -u www-data - rm ibexa_cron.txt ``` @@ -444,7 +444,7 @@ rm ibexa_cron.txt For [Scheduled content publications]([[= user_doc =]]/content_management/schedule_publishing/), the `ibexa:scheduled:run` command is tagged with `ibexa.cron.job` and runs every minute (`* * * * *`) by default. You can redefine this service to change the frequency. -The [CDP data export schedule](cdp_data_export_schedule.md) dynamically creates services tagged with `ibexa.cron.job`. +The [[[= product_name_cdp =]] data export schedule](/raptor_cdp/raptor_cdp_data_export_schedule.md) dynamically creates services tagged with `ibexa.cron.job`. You can add other commands to scheduled tasks in one of two ways: @@ -474,10 +474,10 @@ The following example schedules these commands separately: This shell script creates a temporary file with the job lines, then replaces the existing crontab for the web server user: ```bash -echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod' > ibexa_cron.txt -echo '0 0 * * 0 cd ; php bin/console ibexa:check-urls --quiet --env=prod' >> ibexa_cron.txt -echo '0 * * * * cd ; php bin/console ibexa:activity-log:truncate --quiet --env=prod' >> ibexa_cron.txt -echo '0 0 * * * cd ; php bin/console ibexa:discounts:reindex --quiet --env=prod' >> ibexa_cron.txt +echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod' > ibexa_cron.txt +echo '0 0 * * 0 cd ; php bin/console ibexa:check-urls --quiet --env=prod' >> ibexa_cron.txt +echo '0 * * * * cd ; php bin/console ibexa:activity-log:truncate --quiet --env=prod' >> ibexa_cron.txt +echo '0 0 * * * cd ; php bin/console ibexa:discounts:reindex --quiet --env=prod' >> ibexa_cron.txt crontab -u www-data ibexa_cron.txt rm ibexa_cron.txt ``` @@ -531,7 +531,7 @@ The following example shows how to set up a different schedule for a specific Si This command schedules `ibexa:cron:run` for the SiteAccess `minor_website` and the job category `minor_website`: ```bash -(crontab -u www-data -l; echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod --siteaccess=minor_website --category=minor_website') | crontab -u www-data - +(crontab -u www-data -l; echo '* * * * * cd ; php bin/console ibexa:cron:run --quiet --env=prod --siteaccess=minor_website --category=minor_website') | crontab -u www-data - ``` Then, run `ibexa:scheduled:run` on this SiteAccess at a different frequency from the default: @@ -552,7 +552,7 @@ Make sure that its [worker starts with the server](background_tasks.md#start-wor A list of processes that use [[= product_name_base =]] Messenger includes at least these two: -- [CDP data export](cdp_data_export.md#ibexa-messenger-support-for-large-batches-of-data) +- [[[= product_name_cdp =]] data export](/raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md#ibexa-messenger-support-for-large-batches-of-data) - [Discount re-indexing](configure_discounts.md#discount-re-indexing) ## [[= product_name_cloud =]] diff --git a/docs/getting_started/install_on_mac_os_and_windows.md b/docs/getting_started/install_on_mac_os_and_windows.md index ac25171b4db..ea89f0a07b8 100644 --- a/docs/getting_started/install_on_mac_os_and_windows.md +++ b/docs/getting_started/install_on_mac_os_and_windows.md @@ -1,5 +1,5 @@ --- -description: Install Ibexa DXP on a macOS or Windows system to use it for development. +description: Install Cohesivo on a macOS or Windows system to use it for development. --- # Install [[= product_name =]] on macOS or Windows @@ -11,7 +11,7 @@ This page explains how to install [[= product_name =]] on macOS or Windows. This procedure is **for development purposes only**. Installing [[= product_name =]] for production purposes is supported only on Linux. - For information about installing the product on Linux, see [Install [[= product_name =]]](install_ibexa_dxp.md). + For information about installing the product on Linux, see [Install [[= product_name =]]](install_cohesivo.md). ## Prepare work environment @@ -74,7 +74,7 @@ The instructions below assume that you're using Apache. ## Install [[= product_name =]] At this point the installation procedure is the same as when installing on Linux. -Follow the steps from the main [Install [[= product_name =]]](install_ibexa_dxp.md#install-ibexa-dxp) page. +Follow the steps from the main [Install [[= product_name =]]](install_cohesivo.md#install-cohesivo) page. ## Set up virtual host diff --git a/docs/getting_started/install_with_ddev.md b/docs/getting_started/install_with_ddev.md index 0fc4a9e2df6..95ff254877a 100644 --- a/docs/getting_started/install_with_ddev.md +++ b/docs/getting_started/install_with_ddev.md @@ -1,5 +1,5 @@ --- -description: Install Ibexa DXP with Docker and DDEV to use it for development. +description: Install Cohesivo with Docker and DDEV to use it for development. month_change: false --- @@ -63,7 +63,7 @@ Depending on your database of choice (MySQL or PostgreSQL), use the appropriate !!! note - Those commands set a `DATABASE_URL` environment variable inside the container which overrides [the variable from `.env`](install_ibexa_dxp.md#change-installation-parameters). + Those commands set a `DATABASE_URL` environment variable inside the container which overrides [the variable from `.env`](install_cohesivo.md#change-installation-parameters). To use `.env.local` file instead of server-level environment variables, see [Using dotenv](#using-dotenv). @@ -99,7 +99,7 @@ ddev config --web-environment-add MAILER_DSN=smtp://localhost:1025 #### Configure scheduled tasks (optional) -You can [schedule tasks](install_ibexa_dxp.md#schedule-tasks) using [DDEV Cron add-on](https://addons.ddev.com/addons/ddev/ddev-cron). +You can [schedule tasks](install_cohesivo.md#schedule-tasks) using [DDEV Cron add-on](https://addons.ddev.com/addons/ddev/ddev-cron). ```bash ddev add-on get ddev/ddev-cron @@ -108,7 +108,7 @@ echo "* * * * * cd $basedir && php bin/console ibexa:cron:run --quiet --env=prod ddev restart ``` -For more schedulable tasks and ways to schedule them, see [Additional scheduled tasks and advanced usage](install_ibexa_dxp.md#additional-scheduled-tasks-and-advanced-usage). +For more schedulable tasks and ways to schedule them, see [Additional scheduled tasks and advanced usage](install_cohesivo.md#additional-scheduled-tasks-and-advanced-usage). You can run the following command to check Cron: @@ -169,7 +169,7 @@ ddev start ### 4. Composer authentication -Next, you need to [set up authentication tokens](install_ibexa_dxp.md#set-up-authentication-tokens) by modifying the Composer configuration. +Next, you need to [set up authentication tokens](install_cohesivo.md#set-up-authentication-tokens) by modifying the Composer configuration. You must run the following command **after** executing `ddev start`, because the command runs inside the container. Replace `` and `` with your actual installation key and token password. @@ -425,7 +425,7 @@ To run an existing project, you need to: - getting a clean database with `ddev php bin/console ibexa:install` and adding some data with [Ibexa data migration](importing_data.md), or - injecting a dump with [`ddev import-db`](https://docs.ddev.com/en/stable/users/usage/commands/#import-db) and copying related binary files into `public/var`. -The following examples run an already [version-controlled project](install_ibexa_dxp.md#add-project-to-version-control) and have the right content structure (but no content): +The following examples run an already [version-controlled project](install_cohesivo.md#add-project-to-version-control) and have the right content structure (but no content): ```bash # Clone the version-controlled project and enter its local directory @@ -455,7 +455,7 @@ Some DDEV configs can be shared among developers. For example, a common `.ddev/c Compared to running a clean install like described in [Installation steps](#installation), you can proceed as follows: -- In [1. Create a DDEV project directory](#1-create-a-ddev-project-directory), you can use an existing directory that contains an [[= product_name =]] project instead of creating an empty directory. +- In [1. Create a DDEV project directory](#1-create-a-ddev-project-directory), you can use an existing directory that contains a [[= product_name =]] project instead of creating an empty directory. - In [5. Create [[= product_name =]] project](#5-create-project), use only `ddev composer install` instead of `ddev composer create-project`. - Populate the database with [Ibexa data migration](importing_data.md) or [`ddev import-db`](https://docs.ddev.com/en/stable/users/usage/commands/#import-db). @@ -472,7 +472,7 @@ If the local project needs to answer to real production domains (for example, to You can use DDEV to locally simulate a production cluster. - See [Clustering with DDEV](clustering_with_ddev.md) to add Elasticsearch, Solr, or Redis to your DDEV installation. -- See [DDEV and Ibexa Cloud](ddev_and_ibexa_cloud.md) to locally run an [[= product_name =]] project by using DDEV. +- See [DDEV and Ibexa Cloud](ddev_and_ibexa_cloud.md) to locally run a [[= product_name =]] project by using DDEV. ## Stop or remove the project diff --git a/docs/getting_started/requirements.md b/docs/getting_started/requirements.md index b6a9d9545f6..311ad4e4a1e 100644 --- a/docs/getting_started/requirements.md +++ b/docs/getting_started/requirements.md @@ -1,5 +1,5 @@ --- -description: System, component and package requirements for running Ibexa DXP. +description: System, component and package requirements for running Cohesivo. month_change: false --- diff --git a/docs/getting_started/troubleshooting.md b/docs/getting_started/troubleshooting.md index 0561268afe4..3c7fcb37a3c 100644 --- a/docs/getting_started/troubleshooting.md +++ b/docs/getting_started/troubleshooting.md @@ -1,5 +1,5 @@ --- -description: See what issues you can encounter when installing Ibexa DXP and how to resolve them. +description: See what issues you can encounter when installing Cohesivo and how to resolve them. --- # Troubleshooting diff --git a/docs/ibexa_cloud/ibexa_cloud_guide.md b/docs/ibexa_cloud/ibexa_cloud_guide.md index baa3536bfad..4468974dab7 100644 --- a/docs/ibexa_cloud/ibexa_cloud_guide.md +++ b/docs/ibexa_cloud/ibexa_cloud_guide.md @@ -11,13 +11,13 @@ month_change: false It also establishes the framework for the potential growth and improves project delivery. As a diverse Platform as a Service (PaaS), it's designed to allow you to focus on the crucial things. -[[= product_name_cloud =]] is a part of [[= product_name =]] - a software that is designed to provide your business with all the features, functionality, and support your need to transform your business for the digital age. +[[= product_name_cloud =]] complements the capabilities of [[= product_name =]] - a software that is designed to provide your business with all the features, functionality, and support your need to transform your business for the digital age. -![Ibexa Cloud - part of Ibexa DXP](ibexa_cloud_dxp.png) +![Ibexa Cloud - part of [[= product_name =]]](../getting_started/img/ibexa_cloud_dxp.png) ## Availability -[[= product_name_cloud =]] is available in all [[= product_name =]] editions. +[[= product_name_cloud =]] is available for all [[= product_name =]] editions. ## How does [[= product_name_cloud =]] work diff --git a/docs/ibexa_cloud/install_on_ibexa_cloud.md b/docs/ibexa_cloud/install_on_ibexa_cloud.md index 793fe9d5a42..c41b94cf8e6 100644 --- a/docs/ibexa_cloud/install_on_ibexa_cloud.md +++ b/docs/ibexa_cloud/install_on_ibexa_cloud.md @@ -1,5 +1,5 @@ --- -description: Install and configure Ibexa DXP to run in cloud using [[= product_name_cloud =]]. +description: Install and configure Cohesivo to run in cloud using [[= product_name_cloud =]]. month_change: false --- @@ -104,7 +104,7 @@ You can also use the [[[= product_name_cloud =]] CLI](https://cli.ibexa.cloud/) ibexa_cloud push main ``` -The [database installer](install_ibexa_dxp.md#create-a-database) runs in non-interactive mode and keeps the default password for the `admin` user. +The [database installer](install_cohesivo.md#create-a-database) runs in non-interactive mode and keeps the default password for the `admin` user. Modify this password after the installation, for example, by using [data migrations](importing_data.md#users) or the [user management command](update_basic_user_data.md#change-password). !!! note diff --git a/docs/ibexa_products/editions.md b/docs/ibexa_products/editions.md index c9df1b14e5d..9c1842a134f 100644 --- a/docs/ibexa_products/editions.md +++ b/docs/ibexa_products/editions.md @@ -1,5 +1,5 @@ --- -description: Learn more about various Ibexa DXP editions' features to help yourself choose the right one for your project. +description: Learn more about various Cohesivo editions' features to help yourself choose the right one for your project. page_type: landing_page --- @@ -48,8 +48,8 @@ Compare all features available in [[= product_name_headless =]], [[= product_nam | [Customer Portal](customer_portal_guide.md) | | ✔ | ✔ | | [Segments](segments_admin_panel.md) | | ✔ | ✔ | | [Recent activity](recent_activity.md) | | ✔ | ✔ | -| [[[= product_name_engage =]] add-on]([[= user_doc =]]/ibexa_engage/ibexa_engage/) | | ✔ | ✔ | -| [Customer Data Platform (CDP) add-on](cdp_guide.md) | | ✔ | ✔ | +| [[[= product_name_engage =]] add-on]([[= user_doc =]]/qualifio/qualifio/) | | ✔ | ✔ | +| [[[= product_name_cdp =]] (Customer Data Platform) add-on](/raptor_cdp/raptor_cdp_guide.md) | | ✔ | ✔ | | [Order management](order_management.md) | | | ✔ | | [Payment management](payment.md) | | | ✔ | | [Shipping management](shipping_management.md) | | | ✔ | diff --git a/docs/ibexa_products/ibexa_commerce.md b/docs/ibexa_products/ibexa_commerce.md index 67392155bfd..64cdbfbe2d0 100644 --- a/docs/ibexa_products/ibexa_commerce.md +++ b/docs/ibexa_products/ibexa_commerce.md @@ -1,5 +1,5 @@ --- -description: Explore all of the key features, functionalities, and advantages of Ibexa Commerce, the most powerful edition that Ibexa DXP has to offer. +description: Explore all of the key features, functionalities, and advantages of Ibexa Commerce, the most powerful edition that Cohesivo has to offer. month_change: false --- @@ -27,7 +27,7 @@ You can also [contact us](https://www.ibexa.co/about-ibexa/contact-us) or [one o ### Technical backstage -With an active license, you can start the [installation process](install_ibexa_dxp.md) that uses the Composer. +With an active license, you can start the [installation process](install_cohesivo.md) that uses the Composer. [[= product_name_com =]] is based on [Symfony]([[= symfony_doc =]]). With a help of documentation and trainings, any developer familiar with Symfony or even PHP alone can learn how to use available extension points and extend the platform. diff --git a/docs/ibexa_products/ibexa_experience.md b/docs/ibexa_products/ibexa_experience.md index cd0db3f0f8a..73d1e0a7149 100644 --- a/docs/ibexa_products/ibexa_experience.md +++ b/docs/ibexa_products/ibexa_experience.md @@ -7,7 +7,7 @@ month_change: false ## What is [[= product_name_exp =]] -[[= product_name_exp =]] is an [[= product_name =]] edition that focuses on the customer. +[[= product_name_exp =]] is a [[= product_name =]] edition that focuses on the customer. It offers smooth consumer journey and great online experience. In everything you do, it places your clients first. With Experience edition you can empower Editors to quickly create new pages or personalized content, and improve their daily work. It also provides tools for using segmentation and targeting, and it can be widely used in B2B thanks its features and integrations. @@ -25,7 +25,7 @@ You can also [contact us](https://www.ibexa.co/about-ibexa/contact-us) or [one o ### Technical backstage -With an active license, you can start the [installation process](install_ibexa_dxp.md) that uses the Composer. +With an active license, you can start the [installation process](install_cohesivo.md) that uses the Composer. [[= product_name_exp =]] is based on [Symfony]([[= symfony_doc =]]). With a help of documentation and trainings, any developer familiar with Symfony or simply PHP may learn how to use available extension points and extend the platform. @@ -100,9 +100,9 @@ You can assign users to different recommendation groups and create advanced logi ![Segments](segments.png) -#### Customer Data Platform (CDP) +#### [[= product_name_cdp =]] (Customer Data Platform) -[Ibexa CDP](cdp_guide.md) is an add-on available for both Experience and [Commerce](ibexa_commerce.md) editions of [[= product_name =]]. +[[[= product_name_cdp =]]](/raptor_cdp/raptor_cdp_guide.md) is an add-on available for both Experience and [Commerce](ibexa_commerce.md) editions of [[= product_name =]]. To use it, you must make arrangements with [[= product_name_base =]] to define the initial configuration. Once you activate [[= product_name_cdp =]], you can create complete customer profiles, including their interactions, behavior, and preferences. It helps you improve user engagement, conversion rates, and return on investment by segmenting your audience and delivering tailored campaigns and experiences. @@ -110,17 +110,17 @@ Additionally, you can manage and analyze campaigns, evaluate customer data, and By using [[= product_name_cdp =]] you can store and manage large volumes of customer data in a structured manner. This central data storage supports business growth with a scalable infrastructure, helping to futureproof your business. -![CDP](cdp.png) +![CDP](../raptor_cdp/img/cdp.png) #### [[= product_name_engage =]] -Another add-on available for Experience and [Commerce](ibexa_commerce.md) edition is [Ibexa Engage](ibexa_engage.md). +Another add-on available for Experience and [Commerce](ibexa_commerce.md) edition is [[[= product_name_engage =]]](/qualifio/qualifio.md). To use it, you must make arrangements with [[= product_name_base =]] to define the initial configuration, and then get and set up a user account. [[= product_name_engage =]] is a data collection tool. It gives you the ability to use the [Qualifio](https://qualifio.com/) tools to engage your audiences. You can use Qualifio's existing templates and interactive elements, such as quizzes, pools, and forms, to create visually appealing, customized campaigns and collect important data. To promote your campaign, you can add a Campaign block to a page in Page Builder or embed a campaign within the Rich Text field by using a Campaign custom tag. -![Ibexa Engage](ibexa_engage.png) +![Qualifio](qualifio.png) ### Use cases diff --git a/docs/ibexa_products/ibexa_headless.md b/docs/ibexa_products/ibexa_headless.md index ebeb6a86db3..0149c5e053a 100644 --- a/docs/ibexa_products/ibexa_headless.md +++ b/docs/ibexa_products/ibexa_headless.md @@ -104,9 +104,9 @@ There are many paths to access the content in many shapes: On top of this strong core, [[= product_name_headless =]] brings tools to increase user experience, from final front users to back office contributors. -#### Complete DXP +#### Complete platform -[[= product_name_headless =]] is a complete Digital Experience Platform (DXP), which comes with the following components to enhance user's journey: +[[= product_name_headless =]] is a complete platform, which comes with the following components to enhance user's journey: - [Recommendations](raptor_connector_guide.md) connector, which allows you to recommend content to end users according to their behavior, or, when authenticated, by matching with their segment/group. @@ -150,7 +150,7 @@ Several features help end users collaborate on the content, such as: - [[= product_name_connect =]]'s role is to create application interconnections with low code and drag-and-drop, in a compelling visual interface. Complex data flows can be easily implemented with a huge library of connectors and actions for famous to specific applications. For more information, see [[[= product_name_connect =]] product guide]([[= connect_doc =]]/general/ibexa_connect/). -- An OAuth 2 server offers the possibility to use the DXP as the authentication service for other applications. +- An OAuth 2 server offers the possibility to use the platform as the authentication service for other applications. - An OAuth 2 client supports authentication with a third-party OAuth 2 server. - A DAM Connector, previously mentioned, helps to access any image repository when needing to illustrate a content. - [[= product_name_headless =]] supports Elasticsearch and Solr. diff --git a/docs/ibexa_products/img/cdp.png b/docs/ibexa_products/img/cdp.png deleted file mode 100644 index 2bbbc01215f..00000000000 Binary files a/docs/ibexa_products/img/cdp.png and /dev/null differ diff --git a/docs/ibexa_products/img/customizable_dashboard.drawio b/docs/ibexa_products/img/customizable_dashboard.drawio index ba4995167e3..2766db435ca 100644 --- a/docs/ibexa_products/img/customizable_dashboard.drawio +++ b/docs/ibexa_products/img/customizable_dashboard.drawio @@ -22,7 +22,7 @@ - + @@ -298,7 +298,7 @@ - + diff --git a/docs/ibexa_products/img/form_builder.drawio b/docs/ibexa_products/img/form_builder.drawio index dedbb29ca89..4df1ac76b1c 100644 --- a/docs/ibexa_products/img/form_builder.drawio +++ b/docs/ibexa_products/img/form_builder.drawio @@ -22,7 +22,7 @@ - + @@ -298,7 +298,7 @@ - + diff --git a/docs/ibexa_products/img/ibexa_engage.drawio b/docs/ibexa_products/img/qualifio.drawio similarity index 99% rename from docs/ibexa_products/img/ibexa_engage.drawio rename to docs/ibexa_products/img/qualifio.drawio index 8f484a2c884..84ddcf03496 100644 --- a/docs/ibexa_products/img/ibexa_engage.drawio +++ b/docs/ibexa_products/img/qualifio.drawio @@ -22,7 +22,7 @@ - + @@ -298,7 +298,7 @@ - + diff --git a/docs/ibexa_products/img/ibexa_engage.png b/docs/ibexa_products/img/qualifio.png similarity index 100% rename from docs/ibexa_products/img/ibexa_engage.png rename to docs/ibexa_products/img/qualifio.png diff --git a/docs/ibexa_products/img/segments.drawio b/docs/ibexa_products/img/segments.drawio index fe8e5d6d334..fbb4904bc88 100644 --- a/docs/ibexa_products/img/segments.drawio +++ b/docs/ibexa_products/img/segments.drawio @@ -22,7 +22,7 @@ - + @@ -298,7 +298,7 @@ - + diff --git a/docs/index.md b/docs/index.md index 05f88a5ecc0..325f88191dc 100644 --- a/docs/index.md +++ b/docs/index.md @@ -33,7 +33,7 @@
- Install Ibexa DXP + Install Cohesivo
@@ -75,7 +75,7 @@
-

The latest Ibexa DXP is v5.0 LTS

+

The latest Cohesivo is v5.0 LTS

The latest v5.0 LTS release is [[= latest_tag_5_0 =]]. You can now update your application.
@@ -90,7 +90,7 @@

The newest LTS Update is MCP Servers

-
Set up MCP servers to help AI agents interact with Ibexa DXP.
+
Set up MCP servers to help AI agents interact with Cohesivo.
Learn more about this LTS Update @@ -162,7 +162,7 @@
-

Manage your DXP

+

Manage your Cohesivo

@@ -192,7 +192,7 @@ diff --git a/docs/infrastructure_and_maintenance/backup.md b/docs/infrastructure_and_maintenance/backup.md index 0e710ea36a1..c5586274c48 100644 --- a/docs/infrastructure_and_maintenance/backup.md +++ b/docs/infrastructure_and_maintenance/backup.md @@ -6,7 +6,7 @@ description: Periodically back up your Repository information by making a databa You should always make sure that your solution is properly backed up. The following example shows you how to do this on a Linux-UNIX-based system. -You should shut down the DXP if it's running before making a backup. +You should shut down [[= product_name =]] if it's running before making a backup. !!! note "Externally stored assets" diff --git a/docs/infrastructure_and_maintenance/cache/cache.md b/docs/infrastructure_and_maintenance/cache/cache.md index 0ca8bf13cd8..2b34058271a 100644 --- a/docs/infrastructure_and_maintenance/cache/cache.md +++ b/docs/infrastructure_and_maintenance/cache/cache.md @@ -1,5 +1,5 @@ --- -description: For caching, Ibexa DXP offers both HTTP cache for content views, and persistence cache. +description: For caching, Cohesivo offers both HTTP cache for content views, and persistence cache. page_type: landing_page --- diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md b/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md index fc009185ac1..426c880e9eb 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md @@ -1,5 +1,5 @@ --- -description: Configure Fastly for use with Ibexa DXP. +description: Configure Fastly for use with Cohesivo. month_change: false --- diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/http_cache.md b/docs/infrastructure_and_maintenance/cache/http_cache/http_cache.md index 56d010379c0..0f2e21a17eb 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/http_cache.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/http_cache.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP's HTTP cache functionalities enable using reverse proxies - Symfony HttpCache Proxy, Varnish or Fastly. +description: Cohesivo's HTTP cache functionalities enable using reverse proxies - Symfony HttpCache Proxy, Varnish or Fastly. --- # HTTP cache diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/http_cache_configuration.md b/docs/infrastructure_and_maintenance/cache/http_cache/http_cache_configuration.md index 44373504cdb..5e5fa35ae0b 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/http_cache_configuration.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/http_cache_configuration.md @@ -1,5 +1,5 @@ --- -description: Configure HTTP cache for Ibexa DXP, including cache header rules and time-to-live. HTTP cache configuration is SiteAccess-aware. +description: Configure HTTP cache for Cohesivo, including cache header rules and time-to-live. HTTP cache configuration is SiteAccess-aware. --- # HTTP cache configuration @@ -36,7 +36,7 @@ To avoid this, the installation ships with configuration to match these specific fos_http_cache: cache_control: rules: - # Make sure cacheable (fresh) responses from Ibexa DXP which are errors/redirects get lower TTL than default_ttl + # Make sure cacheable (fresh) responses from Cohesivo which are errors/redirects get lower TTL than default_ttl - match: match_response: 'response.isFresh() && ( response.isServerError() || response.isClientError() || response.isRedirect() )' diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md index e0badab7b1e..e3a85faef6b 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md @@ -1,5 +1,5 @@ --- -description: You can use Symfony HttpCache Proxy, Varnish or Fastly as reverse proxies with Ibexa DXP. +description: You can use Symfony HttpCache Proxy, Varnish or Fastly as reverse proxies with Cohesivo. month_change: false --- diff --git a/docs/infrastructure_and_maintenance/clustering/clustering.md b/docs/infrastructure_and_maintenance/clustering/clustering.md index dff879be1b1..475500bee46 100644 --- a/docs/infrastructure_and_maintenance/clustering/clustering.md +++ b/docs/infrastructure_and_maintenance/clustering/clustering.md @@ -1,5 +1,5 @@ --- -description: Clustering enables you to host one installation of Ibexa DXP on multiple servers. +description: Clustering enables you to host one installation of Cohesivo on multiple servers. --- # Clustering diff --git a/docs/infrastructure_and_maintenance/databases.md b/docs/infrastructure_and_maintenance/databases.md index 0ad31fe7884..eba92e555ed 100644 --- a/docs/infrastructure_and_maintenance/databases.md +++ b/docs/infrastructure_and_maintenance/databases.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP can use MySQL, PostgreSQL or MariaDB as its database. +description: Cohesivo can use MySQL, PostgreSQL or MariaDB as its database. --- # Databases @@ -14,7 +14,7 @@ To use PostgreSQL, you need to have the `pdo_pgsql` PHP extension installed. ### Provide parameters -When you run `composer install`, you're asked to [provide installation parameters](install_ibexa_dxp.md#change-installation-parameters). +When you run `composer install`, you're asked to [provide installation parameters](install_cohesivo.md#change-installation-parameters). !!! tip diff --git a/docs/infrastructure_and_maintenance/devops.md b/docs/infrastructure_and_maintenance/devops.md index 2fb47269b5b..b1d830f3a79 100644 --- a/docs/infrastructure_and_maintenance/devops.md +++ b/docs/infrastructure_and_maintenance/devops.md @@ -1,5 +1,5 @@ --- -description: See various tools that can help you debug your Ibexa DXP installation. +description: See various tools that can help you debug your Cohesivo installation. --- # DevOps @@ -86,7 +86,7 @@ composer require --dev symfony/debug-pack After you have installed Symfony Web Debug Toolbar, it's available when running [[= product_name =]] in the `dev` environment. It's extended with some [[= product_name =]]-specific information: -![Ibexa DXP info in Web Debug Toolbar](web_debug_toolbar.png "Ibexa DXP info in Web Debug Toolbar") +![[[= product_name =]] info in Web Debug Toolbar](img/web_debug_toolbar.png "Cohesivo info in Web Debug Toolbar") ### SPI (persistence) diff --git a/docs/infrastructure_and_maintenance/environments.md b/docs/infrastructure_and_maintenance/environments.md index 752011d68fd..91287a9d803 100644 --- a/docs/infrastructure_and_maintenance/environments.md +++ b/docs/infrastructure_and_maintenance/environments.md @@ -1,5 +1,5 @@ --- -description: In Ibexa DXP you can use environment provided by Symfony in virtual host configuration, and to create custom environments. +description: In Cohesivo you can use environment provided by Symfony in virtual host configuration, and to create custom environments. --- # Environments diff --git a/docs/infrastructure_and_maintenance/performance.md b/docs/infrastructure_and_maintenance/performance.md index b3886d3625e..4f033dcf474 100644 --- a/docs/infrastructure_and_maintenance/performance.md +++ b/docs/infrastructure_and_maintenance/performance.md @@ -1,5 +1,5 @@ --- -description: Ensure that your Ibexa DXP installation performs well by following our set of recommendations. +description: Ensure that your Cohesivo installation performs well by following our set of recommendations. --- # Performance diff --git a/docs/infrastructure_and_maintenance/request_lifecycle.md b/docs/infrastructure_and_maintenance/request_lifecycle.md index bd403c5ae24..5977c30c946 100644 --- a/docs/infrastructure_and_maintenance/request_lifecycle.md +++ b/docs/infrastructure_and_maintenance/request_lifecycle.md @@ -1,5 +1,5 @@ --- -description: See the lifecycle of an HTTP request in Ibexa DXP, from request to response. +description: See the lifecycle of an HTTP request in Cohesivo, from request to response. --- # Request lifecycle: from request to response diff --git a/docs/infrastructure_and_maintenance/security/development_security.md b/docs/infrastructure_and_maintenance/security/development_security.md index 61f5c08b0eb..5c2ecfefcdc 100644 --- a/docs/infrastructure_and_maintenance/security/development_security.md +++ b/docs/infrastructure_and_maintenance/security/development_security.md @@ -1,5 +1,5 @@ --- -description: Ensure the security of your Ibexa DXP installation by using one of the available authentication methods. +description: Ensure the security of your Cohesivo installation by using one of the available authentication methods. --- # Development security diff --git a/docs/infrastructure_and_maintenance/security/reporting_issues.md b/docs/infrastructure_and_maintenance/security/reporting_issues.md index aad919e18fd..043d7ba33d5 100644 --- a/docs/infrastructure_and_maintenance/security/reporting_issues.md +++ b/docs/infrastructure_and_maintenance/security/reporting_issues.md @@ -1,5 +1,5 @@ --- -description: Learn how to report security issues in Ibexa DXP. +description: Learn how to report security issues in Cohesivo. --- # Reporting security issues in Ibexa products diff --git a/docs/infrastructure_and_maintenance/security/security_checklist.md b/docs/infrastructure_and_maintenance/security/security_checklist.md index 174ace2a370..bba7e1c09dd 100644 --- a/docs/infrastructure_and_maintenance/security/security_checklist.md +++ b/docs/infrastructure_and_maintenance/security/security_checklist.md @@ -1,5 +1,5 @@ --- -description: Ensure that your Ibexa DXP installation is secure by following our set of recommendations. +description: Ensure that your Cohesivo installation is secure by following our set of recommendations. --- # Security checklist @@ -117,7 +117,7 @@ Reduce your attack surface by exposing only what you must. - If possible, make the back office unavailable on the open internet. - [Symfony FOSJsRoutingBundle](https://github.com/FriendsOfSymfony/FOSJsRoutingBundle) is required in those releases where it's included, to expose routes to JavaScript. It exposes only the required routes, nothing more. It's only required in the back office SiteAccess though, so you can consider blocking it in other SiteAccesses. You should also go through your own custom routes, and decide for each if you need to expose them or not. See the documentation on [YAML route definitions for exposure](https://github.com/FriendsOfSymfony/FOSJsRoutingBundle/blob/master/Resources/doc/usage.rst#generating-uris). -- By default, a [Powered-By header](update_db_to_2.5.md#powered-by-header) is set. It specifies what version of the DXP is running. For example, `x-powered-by: [[= product_name_exp =]] v4`. This doesn't expose anything that couldn't be detected through other means. But if you wish to obscure this, you can either omit the version number, or disable the header entirely by setting `enabled: false`. +- By default, a [Powered-By header](update_db_to_2.5.md#powered-by-header) is set. It specifies what version of [[= product_name =]] is running. For example, `x-powered-by: [[= product_name_exp =]] v4`. This doesn't expose anything that couldn't be detected through other means. But if you wish to obscure this, you can either omit the version number, or disable the header entirely by setting `enabled: false`. ```yaml ibexa_system_info: @@ -223,7 +223,7 @@ For more information, see [PHP's own security manual](https://www.php.net/manual ### Block execution of scripts in `var` directory Make sure that the web server blocks the execution of PHP files and other scripts in the `var` directory. -See the line below `# Disable .php(3) and other executable extensions in the var directory` in the example virtual host files for Apache and Nginx, provided in the [installation documentation](install_ibexa_dxp.md#set-up-virtual-host). +See the line below `# Disable .php(3) and other executable extensions in the var directory` in the example virtual host files for Apache and Nginx, provided in the [installation documentation](install_cohesivo.md#set-up-virtual-host). ### Security headers diff --git a/docs/infrastructure_and_maintenance/sessions.md b/docs/infrastructure_and_maintenance/sessions.md index 697fcc04222..b93f7afc145 100644 --- a/docs/infrastructure_and_maintenance/sessions.md +++ b/docs/infrastructure_and_maintenance/sessions.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP uses Symfony to handle user sessions, with support for SiteAccess-aware session cookie configuration. +description: Cohesivo uses Symfony to handle user sessions, with support for SiteAccess-aware session cookie configuration. --- # Sessions @@ -60,7 +60,7 @@ Symfony can be configured to use custom handlers, or fall back to what is confi framework: session: # handler_id can be set to null (~) like default in Symfony, if it so will use default session handler from php.ini - # But in order to use %ibexa.session.save_path%, default Ibexa DXP instead sets %ibexa.session.handler_id% to: + # But in order to use %ibexa.session.save_path%, default Cohesivo instead sets %ibexa.session.handler_id% to: # - session.handler.native_file (default) # - Ibexa\Bundle\Core\Session\Handler\NativeSessionHandler (recommended value for Cluster usage, using php-redis session handler ) handler_id: '%ibexa.session.handler_id%' diff --git a/docs/infrastructure_and_maintenance/support_and_maintenance_faq.md b/docs/infrastructure_and_maintenance/support_and_maintenance_faq.md index ed2a13e3fae..6f0fd8eb664 100644 --- a/docs/infrastructure_and_maintenance/support_and_maintenance_faq.md +++ b/docs/infrastructure_and_maintenance/support_and_maintenance_faq.md @@ -71,7 +71,7 @@ imports: - { resource: ../landing_page_blocks.yaml } ``` -## How can I implement authentication in an [[= product_name =]]-based project? +## How can I implement authentication in a [[= product_name =]]-based project? The best approach is to use Symfony authentication. Check [development security](development_security.md) page for more detailed instructions. diff --git a/docs/product_catalog/add_remote_pim_support.md b/docs/product_catalog/add_remote_pim_support.md index 994234c4ec7..bdfc39d7b38 100644 --- a/docs/product_catalog/add_remote_pim_support.md +++ b/docs/product_catalog/add_remote_pim_support.md @@ -5,7 +5,7 @@ description: Install and configure the Remote PIM example package. # Add Remote PIM support [[= product_name =]] provides flexible product catalog infrastructure that works with external Product Information Management (PIM) systems. -For advanced product data management without custom development, you can use the readily available [[[= pim_product_name =]] PIM integration](quable/quable.md) with [[= product_name =]]. +For advanced product data management without custom development, you can use the readily available [[[= pim_product_name =]] integration](quable/quable.md) with [[= product_name =]]. To implement [Remote PIM support](product_catalog_guide.md#remote-pim-support) for a custom integration, you can build upon a foundation provided by [[= product_name_base =]]. diff --git a/docs/product_catalog/catalogs.md b/docs/product_catalog/catalogs.md index 032c6ed4ba7..7ed7e7d3c03 100644 --- a/docs/product_catalog/catalogs.md +++ b/docs/product_catalog/catalogs.md @@ -1,5 +1,5 @@ --- -description: Catalogs enable filtering our a selection of products from the PIM. +description: Catalogs enable filtering out a selection of products from the Product catalog. --- # Catalogs diff --git a/docs/product_catalog/create_custom_catalog_filter.md b/docs/product_catalog/create_custom_catalog_filter.md index 367871505e8..5e56631c902 100644 --- a/docs/product_catalog/create_custom_catalog_filter.md +++ b/docs/product_catalog/create_custom_catalog_filter.md @@ -1,10 +1,10 @@ --- -description: Fine-tune product catalogs by adding a custom catalog filter for selecting products from the PIM. +description: Fine-tune catalogs by adding a custom catalog filter for selecting products from the Product catalog. --- # Create custom catalog filter -Catalog filters let you narrow down the products from the PIM that are available in the given [catalog](catalogs.md). +Catalog filters let you narrow down the products from the Product catalog that are available in the given [catalog](catalogs.md). Besides the built-in catalog filters, you can also create custom ones. The following example shows how to create a filter that selects products with the entered name. diff --git a/docs/product_catalog/customize_product_attribute_templates.md b/docs/product_catalog/customize_product_attribute_templates.md index ab1e36dbdb3..4d71933f299 100644 --- a/docs/product_catalog/customize_product_attribute_templates.md +++ b/docs/product_catalog/customize_product_attribute_templates.md @@ -29,7 +29,7 @@ If none is found, it falls back to the first `generic_attribute` block available ### [[= pim_product_name =]] attribute types -When using [[[= pim_product_name =]] PIM](/product_catalog/quable/quable.md), use the following identifiers to override the templates for [[[= pim_product_name =]]'s attribute types](https://docs.quable.com/v5-EN/docs/objects-and-attributes#attribute-types): +When using [[[= pim_product_name =]]](/product_catalog/quable/quable.md), use the following identifiers to override the templates for [[[= pim_product_name =]]'s attribute types](https://docs.quable.com/v5-EN/docs/objects-and-attributes#attribute-types): | Attribute name | Identifier | |---|---| diff --git a/docs/product_catalog/img/diagrams_source/remote_pim_support.xml b/docs/product_catalog/img/diagrams_source/remote_pim_support.xml index f52a0c42076..1fb74108db8 100644 --- a/docs/product_catalog/img/diagrams_source/remote_pim_support.xml +++ b/docs/product_catalog/img/diagrams_source/remote_pim_support.xml @@ -35,7 +35,7 @@ - + @@ -47,7 +47,7 @@ - + @@ -92,7 +92,7 @@ - + diff --git a/docs/product_catalog/img/remote_pim_support.png b/docs/product_catalog/img/remote_pim_support.png index 7bc95d41e69..9cef5c5194a 100644 Binary files a/docs/product_catalog/img/remote_pim_support.png and b/docs/product_catalog/img/remote_pim_support.png differ diff --git a/docs/product_catalog/product_api.md b/docs/product_catalog/product_api.md index d5ffb771dbc..da43f935339 100644 --- a/docs/product_catalog/product_api.md +++ b/docs/product_catalog/product_api.md @@ -1,5 +1,5 @@ --- -description: Use PHP API to manage products in PIM, their attributes, availability, and prices. +description: Use PHP API to manage products, their attributes, availability, and prices. month_change: false --- diff --git a/docs/product_catalog/product_catalog.md b/docs/product_catalog/product_catalog.md index 86348d466db..be02c6b51c0 100644 --- a/docs/product_catalog/product_catalog.md +++ b/docs/product_catalog/product_catalog.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. +description: Cohesivo provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. page_type: landing_page month_change: false --- @@ -10,7 +10,7 @@ The Product Catalog provides comprehensive capabilities for managing products of [[= product_name =]] offers robust product catalog infrastructure that can be used standalone. -You can also use [[[= pim_product_name =]] Product Information Management (PIM)](/product_catalog/quable/quable.md) add-on that fully integrates into the [[= product_name_base =]] ecosystem, or the [Remote PIM](add_remote_pim_support.md) to add integration with any external PIM system. +You can also use [[[= pim_product_name =]]](/product_catalog/quable/quable.md) add-on that fully integrates into the [[= product_name_base =]] ecosystem, or the [Remote PIM](add_remote_pim_support.md) to add integration with any external PIM system. [[= cards([ "product_catalog/product_catalog_guide", diff --git a/docs/product_catalog/product_catalog_configuration.md b/docs/product_catalog/product_catalog_configuration.md index 6bab65e630c..17a145f6464 100644 --- a/docs/product_catalog/product_catalog_configuration.md +++ b/docs/product_catalog/product_catalog_configuration.md @@ -33,7 +33,7 @@ ibexa_product_catalog: ``` The `local` type is the built-in type of catalog based on the content repository. -With [[[= pim_product_name =]] PIM integration](/product_catalog/quable/quable_guide.md) add-on installed and configured, by using the `quable` type you can retrieve product data coming from [[= pim_product_name =]]. +With [[[= pim_product_name =]] integration](/product_catalog/quable/quable_guide.md) add-on installed and configured, by using the `quable` type you can retrieve product data coming from [[= pim_product_name =]]. You can use a single engine across all repositories, or assign different ones per repository. Each repository can use only one product catalog engine. diff --git a/docs/product_catalog/product_catalog_guide.md b/docs/product_catalog/product_catalog_guide.md index 7c33fe00145..fe00bfd7778 100644 --- a/docs/product_catalog/product_catalog_guide.md +++ b/docs/product_catalog/product_catalog_guide.md @@ -161,7 +161,7 @@ Besides, the built-in catalog filters, you can also [create custom ones](create_ In [[= product_name =]], products are created and maintained by using the REST API or the back office, and their data is stored in a local database. However, in your project or organization, you might have an existing product database, or be specifically concerned about product information security. To address such needs, [[= product_name =]] provides remote PIM support. -You can install and configure a readily available [[[= pim_product_name =]] PIM integration](/product_catalog/quable/quable.md) add-on, or build a custom one to connect to a remote PIM or ERP system, pull product data and present it on your website. +You can install and configure a readily available [[[= pim_product_name =]] integration](/product_catalog/quable/quable.md) add-on, or build a custom one to connect to a remote PIM or ERP system, pull product data and present it on your website. ![Remote PIM](img/remote_pim_support.png) @@ -192,7 +192,7 @@ In your specific scenario, you can implement the support for availability and pr The limitation of remote PIM depend on implementation details of specific integration and may arise in areas relying on [content model](content_model.md). -To see the limitations of the [[= pim_product_name =]] PIM integration add-on, see [[[= pim_product_name =]] PIM known limitations](/product_catalog/quable/quable_guide.md#known-limitations). +To see the limitations of the [[= pim_product_name =]] integration add-on, see [[[= pim_product_name =]] known limitations](/product_catalog/quable/quable_guide.md#known-limitations). ##### Searching diff --git a/docs/product_catalog/quable/configure_quable_connector.md b/docs/product_catalog/quable/configure_quable_connector.md index dd0d3400c7d..80c9c3d7a49 100644 --- a/docs/product_catalog/quable/configure_quable_connector.md +++ b/docs/product_catalog/quable/configure_quable_connector.md @@ -1,10 +1,10 @@ --- -description: Quable PIM connector configuration reference for Ibexa DXP +description: Quable connector configuration reference for Cohesivo page_type: reference month_change: false --- -# Configure Quable connector +# Configure [[= pim_product_name =]] connector You can customize the behavior of the [[= pim_product_name =]] integration add-on by using the following [configuration](configuration.md). diff --git a/docs/product_catalog/quable/install_quable.md b/docs/product_catalog/quable/install_quable.md index bbacf5b0ee4..8607059948f 100644 --- a/docs/product_catalog/quable/install_quable.md +++ b/docs/product_catalog/quable/install_quable.md @@ -1,15 +1,15 @@ --- -description: Install and configure Quable PIM connector for Ibexa DXP +description: Install and configure Quable connector for Cohesivo month_change: false --- -# Install Quable connector +# Install [[= pim_product_name =]] connector -To integrate [[= product_name =]] with [[= pim_product_name =]] PIM, you need to install the [[= pim_product_name =]] connector packages, configure the connection, and set up synchronization. +To integrate [[= product_name =]] with [[= pim_product_name =]], you need to install the [[= pim_product_name =]] connector packages, configure the connection, and set up synchronization. ## Create [[= pim_product_name =]] instance -Before installing the [[= pim_product_name =]] connector, ensure you have access to a [[[= pim_product_name =]] PIM instance](https://www.quable.com). +Before installing the [[= pim_product_name =]] connector, ensure you have access to a [[[= pim_product_name =]] instance](https://www.quable.com). ## Install package @@ -19,11 +19,11 @@ Run the following command to install the required package: composer require ibexa/connector-quable ``` -The command adds the [[= pim_product_name =]] connector code, including services that enable communication with [[= pim_product_name =]] PIM. +The command adds the [[= pim_product_name =]] connector code, including services that enable communication with [[= pim_product_name =]]. ## Get API credentials -To connect to [[= pim_product_name =]] PIM, you need an API token: +To connect to [[= pim_product_name =]], you need an API token: 1. Log in to your [[= pim_product_name =]] instance, for example, `https://example.quable.com`. 2. Navigate to the [API Tokens](https://docs.quable.com/v5-EN/docs/api-tokens) section. @@ -130,22 +130,22 @@ Run the following command to synchronize classifications: php bin/console ibexa:quable:classification:sync ``` -This command imports the product classification structure from [[= pim_product_name =]] PIM into [[= product_name =]], ensuring that product categories are aligned. +This command imports the product classification structure from [[= pim_product_name =]] into [[= product_name =]], ensuring that product categories are aligned. !!! tip - To keep the classifications aligned, we recommend running the `ibexa:quable:classification:sync` command every night, even when using synchronization with webhooks. + To keep the classifications aligned, it's recommended that you run the `ibexa:quable:classification:sync` command every night, even when using synchronization with webhooks. ## Set up real-time synchronization -[[= pim_product_name =]] PIM can notify [[= product_name =]] about product data and classification changes in real-time by using webhooks. +[[= pim_product_name =]] can notify [[= product_name =]] about product data and classification changes in real-time by using webhooks. This invalidates the cache kept in [[= product_name =]], ensuring that product information stays up to date. -Webhook configuration must be set up in both Quable PIM and [[= product_name =]]. +Webhook configuration must be set up in both [[= pim_product_name =]] and [[= product_name =]]. ### Create webhook in [[= pim_product_name =]] -1. Create a new [webhook in Quable](https://docs.quable.com/v5-EN/docs/webhook). +1. Create a new [webhook in [[= pim_product_name =]]](https://docs.quable.com/v5-EN/docs/webhook). 2. Set the webhook code (used as the webhook name). 3. Provide the URL to your [[= product_name =]] instance suffixed by `/webhook/quable`, for example: `https://example.com/webhook/quable`. 4. Mark it as **Activated**. @@ -174,11 +174,11 @@ ibexa_connector_quable: !!! caution - [Quable uses dynamic IP addresses](https://faq.quable.com/en/articles/8250056-what-are-the-ip-addresses-of-quable-to-add-to-the-whitelist) to connect to [[= product_name =]]. - If your DXP instance is protected by a firewall, make sure your configuration allows connections from changing IP addresses. + [[[= pim_product_name =]] uses dynamic IP addresses](https://faq.quable.com/en/articles/8250056-what-are-the-ip-addresses-of-quable-to-add-to-the-whitelist) to connect to [[= product_name =]]. + If your [[= product_name =]] instance is protected by a firewall, make sure your configuration allows connections from changing IP addresses. ### Configure background task -[[= product_name =]]'s webhook processes Quable's classification change events and queues them to be processed in the background. +[[= product_name =]] webhook processes [[= pim_product_name =]]'s classification change events and queues them to be processed in the background. To process them, [configure Ibexa Messenger](background_tasks.md) and make sure the `messenger:consume` command is run periodically. diff --git a/docs/product_catalog/quable/quable.md b/docs/product_catalog/quable/quable.md index 02282290aa7..f516745d93f 100644 --- a/docs/product_catalog/quable/quable.md +++ b/docs/product_catalog/quable/quable.md @@ -1,10 +1,10 @@ --- -description: Quable PIM integration with Ibexa DXP +description: Quable integration with Cohesivo page_type: landing_page month_change: false --- -# Quable PIM Integration +# [[= pim_product_name =]] Integration [[= product_name =]] integrates with [[[= pim_product_name =]]](https://www.quable.com/en) to provide product information management as part of the [[= product_name_base =]] orchestration platform. @@ -18,7 +18,7 @@ Products can be viewed, selected, and embedded in [[= product_name =]], while al "product_catalog/quable/quable_guide", ("https://doc.ibexa.co/projects/userguide/en/5.0/product_catalog/quable_pim_integration/"), ("https://www.quable.com/en", "Quable - PIM solution for product data management", "Manage your product data and accelerate sales with Quable. Discover the new PIM platform that revolutionizes the product experience"), - ("https://docs.quable.com/", "Quable resources", "Find all Quable PIM, DAM, and Portal resources: user guides, training content, product documentation, technical documentation, and the PIM API for developers."), + ("https://docs.quable.com/", "Quable resources", "Find all PIM, DAM, and Portal resources: user guides, training content, product documentation, technical documentation, and the PIM API for developers."), ]) =]] ## Development diff --git a/docs/product_catalog/quable/quable_api.md b/docs/product_catalog/quable/quable_api.md index de0dc06e167..ed05d9c35d7 100644 --- a/docs/product_catalog/quable/quable_api.md +++ b/docs/product_catalog/quable/quable_api.md @@ -4,7 +4,7 @@ month_change: false --- -# Quable API +# [[= pim_product_name =]] API As [[= pim_product_name =]] products are represented as [[= product_name =]] products, you can use the existing [Product APIs](product_api.md) to retrieve the product information. diff --git a/docs/product_catalog/quable/quable_guide.md b/docs/product_catalog/quable/quable_guide.md index eecef45aa43..e4af8d6f06c 100644 --- a/docs/product_catalog/quable/quable_guide.md +++ b/docs/product_catalog/quable/quable_guide.md @@ -1,13 +1,13 @@ --- -description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. +description: The Quable product guide describes how you can use the product data from Quable in Cohesivo to create marketing campaigns built around your products. month_change: false --- -# Quable product guide +# [[= pim_product_name =]] product guide ## Overview -[[= pim_product_name =]] integration connects [[= product_name =]] with [[[= pim_product_name =]] Product Information Management (PIM)](https://www.quable.com/en), making [[= pim_product_name =]] the authoritative source of product information for every website powered by [[= product_name =]]. +[[= pim_product_name =]] integration connects [[= product_name =]] with [[[= pim_product_name =]]](https://www.quable.com/en), making [[= pim_product_name =]] the authoritative source of product information for every website powered by [[= product_name =]]. [[= pim_product_name =]] serves as the single source of truth for all product data, including attributes, classifications, variants, and translations. [[= product_name =]] consumes this data and makes it available for use in content and digital experiences. @@ -16,9 +16,9 @@ This approach eliminates the need to manage product data in multiple systems, wh ## Availability -The integration with [[= pim_product_name =]] PIM is available as an add-on for all [[= product_name =]] editions, starting with [[= product_name =]] v5.0.7. +The integration with [[= pim_product_name =]] is available as an add-on for all [[= product_name =]] editions. -Before installing and enabling the add-on, ensure that you have an active [[= pim_product_name =]] PIM instance with defined products, classifications, and channels. +Before installing and enabling the add-on, ensure that you have an active [[= pim_product_name =]] instance with defined products, classifications, and channels. Then, [perform the initial configuration](install_quable.md). @@ -28,7 +28,7 @@ The integration is built on [[= product_name =]]'s [Remote PIM framework](add_re Once configured, the system performs: -- an initial synchronization of product data from Quable +- an initial synchronization of product data from [[= pim_product_name =]] - ongoing updates via webhooks (near real-time) Product data is mapped to the [[= product_name =]]'s product data model, including variants, attributes and [product categories](product_catalog_guide.md#product-taxonomy). diff --git a/docs/product_guides/product_guides.md b/docs/product_guides/product_guides.md index c6a70510e41..3f0a53f5030 100644 --- a/docs/product_guides/product_guides.md +++ b/docs/product_guides/product_guides.md @@ -1,5 +1,5 @@ --- -description: Discover various Ibexa DXP features. +description: Discover various Cohesivo features. page_type: landing_page month_change: false --- @@ -22,7 +22,7 @@ Discover the primary ones with the help of product guides. Condensed content all "product_catalog/quable/quable_guide", "commerce/shopping_list/shopping_list_guide", "ibexa_cloud/ibexa_cloud_guide", - "cdp/cdp_guide", + "raptor_cdp/raptor_cdp_guide", "recommendations/raptor_integration/raptor_connector_guide", "ai/ai_actions/ai_actions_guide", "ai/mcp/mcp_guide", diff --git a/docs/ibexa_engage/create_campaign.md b/docs/qualifio/create_campaign.md similarity index 88% rename from docs/ibexa_engage/create_campaign.md rename to docs/qualifio/create_campaign.md index dd789be337a..3f36c838a61 100644 --- a/docs/ibexa_engage/create_campaign.md +++ b/docs/qualifio/create_campaign.md @@ -1,11 +1,11 @@ --- -description: Create campaign with Ibexa Engage. +description: Create a campaign with Qualifio. edition: experience --- -# Create campaign +# Create [[= product_name_engage =]] campaign -[Campaign]([[= user_doc =]]/ibexa_engage/ibexa_engage/#campaign) is a set of concepts, divided into steps, that the user can configure. +[Campaign]([[= user_doc =]]/qualifio/qualifio/#campaign) is a set of concepts, divided into steps, that the user can configure. It can contain, for example, a welcome screen, an interaction element, a form step, and an exit screen. To create new campaign, you need to use Qualifio Manager. You can use Qualifio's existing templates and interactive elements, such as quizzes, pools, and forms, to create visually appealing, customized campaigns. @@ -18,7 +18,7 @@ For more information about creating and managing campaigns, see [Qualifio docume ## Publication channels Each campaign includes a minimum of one publication channel that you can choose from the three options the platform provides for publishing a campaign. -For more information about publication channels, see [Publication channel]([[= user_doc =]]/ibexa_engage/ibexa_engage/#publication-channel) in User Documentation. +For more information about publication channels, see [Publication channel]([[= user_doc =]]/qualifio/qualifio/#publication-channel) in User Documentation. ## Use Campaign block in Page Builder diff --git a/docs/ibexa_engage/img/campaign_block.png b/docs/qualifio/img/campaign_block.png similarity index 100% rename from docs/ibexa_engage/img/campaign_block.png rename to docs/qualifio/img/campaign_block.png diff --git a/docs/ibexa_engage/img/campaign_custom_tag.png b/docs/qualifio/img/campaign_custom_tag.png similarity index 100% rename from docs/ibexa_engage/img/campaign_custom_tag.png rename to docs/qualifio/img/campaign_custom_tag.png diff --git a/docs/ibexa_engage/img/configure_ibexa_engage.png b/docs/qualifio/img/configure_qualifio.png similarity index 100% rename from docs/ibexa_engage/img/configure_ibexa_engage.png rename to docs/qualifio/img/configure_qualifio.png diff --git a/docs/ibexa_engage/img/create_scenario.png b/docs/qualifio/img/create_scenario.png similarity index 100% rename from docs/ibexa_engage/img/create_scenario.png rename to docs/qualifio/img/create_scenario.png diff --git a/docs/ibexa_engage/img/create_webhook.png b/docs/qualifio/img/create_webhook.png similarity index 100% rename from docs/ibexa_engage/img/create_webhook.png rename to docs/qualifio/img/create_webhook.png diff --git a/docs/ibexa_engage/install_ibexa_engage.md b/docs/qualifio/install_qualifio.md similarity index 88% rename from docs/ibexa_engage/install_ibexa_engage.md rename to docs/qualifio/install_qualifio.md index 8f4177890f4..2c87bb23838 100644 --- a/docs/ibexa_engage/install_ibexa_engage.md +++ b/docs/qualifio/install_qualifio.md @@ -1,9 +1,9 @@ --- -description: Install and configure [[= product_name_engage =]]. +description: Install and configure Qualifio. edition: experience --- -# [[= product_name_engage =]] +# Install [[= product_name_engage =]] [[= product_name_engage =]] is a data collection tool. It enables you to engage your audiences by using the [Qualifio](https://qualifio.com/) tools. You can use interactive content to gather valuable data, for example, customer data or recent orders list, and create connections. @@ -16,7 +16,7 @@ To use [[= product_name_engage =]], you must make arrangements with [[= product_ [[= product_name_base =]] team creates and provides user account. An invitation link is sent during the setup process. -For more information, see [[[= product_name_engage =]] in User Documentation]([[= user_doc =]]/ibexa_engage/ibexa_engage/#request-access). +For more information, see [[[= product_name_engage =]] in User Documentation]([[= user_doc =]]/qualifio/qualifio/#request-access). ## Install [[= product_name_engage =]] @@ -40,7 +40,7 @@ This command adds to your project configuration files required for using [[= pro In `config/packages` directory add the following `ibexa_connector_qualifio.yaml` [YAML configuration](configuration.md#configuration-files): ``` yaml -[[= include_file('code_samples/ibexa_engage/config/packages/ibexa_connector_qualifio.yaml') =]] +[[= include_file('code_samples/qualifio/config/packages/ibexa_connector_qualifio.yaml') =]] ``` - `client_id` - an identifier of the user. diff --git a/docs/ibexa_engage/integrate_ibexa_connect.md b/docs/qualifio/integrate_ibexa_connect.md similarity index 90% rename from docs/ibexa_engage/integrate_ibexa_connect.md rename to docs/qualifio/integrate_ibexa_connect.md index 560a5d31e41..302d59db7df 100644 --- a/docs/ibexa_engage/integrate_ibexa_connect.md +++ b/docs/qualifio/integrate_ibexa_connect.md @@ -1,9 +1,9 @@ --- -description: Integrate Ibexa Engage with Ibexa Connect. +description: Integrate Qualifio with Ibexa Connect. edition: experience --- -# Use Ibexa Connect +# Integrate with [[= product_name_connect =]] You can use [[[= product_name_connect =]]]([[= connect_doc =]]/general/ibexa_connect/) to create workflows. [[= product_name_engage =]] collects user data and passes it directly to [[= product_name_connect =]]. @@ -11,7 +11,7 @@ With this data, you can create scenarios, for example, to add a user to newslett For more information, see [[[= product_name_connect =]] documentation]([[= connect_doc =]]/). -## Integrate [[= product_name_engage =]] with [[= product_name_connect =]] +## Use [[= product_name_connect =]] Webhooks provide a powerful way to transfer data between applications in real-time. You can use webhooks to connect [[= product_name_engage =]] with [[= product_name_connect =]] - integration platform (iPaaS). @@ -52,7 +52,7 @@ To do it, perform the following actions:: 3\. Paste the URL from the clipboard into **Webhook Host** field and click **Save**. -![Configure Ibexa Engage](configure_ibexa_engage.png "Configure Ibexa Engage") +![Configure Qualifio](configure_qualifio.png "Configure Qualifio") 4\. Then, go to **Engage** -> **Integrations** -> **Push rules** to define the default or specific rules for new campaign or website. Select the created webhook. diff --git a/docs/ibexa_engage/ibexa_engage.md b/docs/qualifio/qualifio.md similarity index 67% rename from docs/ibexa_engage/ibexa_engage.md rename to docs/qualifio/qualifio.md index 5fc2515d68d..94316de59be 100644 --- a/docs/ibexa_engage/ibexa_engage.md +++ b/docs/qualifio/qualifio.md @@ -1,10 +1,10 @@ --- -description: Use Ibexa Engage to collect customer data by creating interactive content. +description: Use Qualifio to collect customer data by creating interactive content. edition: experience month_change: false --- -# [[= product_name_engage =]] +# [[= product_name_engage =]] integration [[= product_name_engage =]] is a data collection tool. It gives you the ability to use the [Qualifio](https://qualifio.com/) tools to engage your audiences. @@ -12,7 +12,7 @@ You can use interactive content to build relationships and collect important dat You can also integrate [[= product_name_engage =]] with [[= product_name_connect =]] to create workflows. [[= cards([ - "ibexa_engage/install_ibexa_engage", - "ibexa_engage/create_campaign", - "ibexa_engage/integrate_ibexa_connect", + "qualifio/install_qualifio", + "qualifio/create_campaign", + "qualifio/integrate_ibexa_connect", ], columns=3) =]] diff --git a/docs/cdp/img/audience_builder.png b/docs/raptor_cdp/img/audience_builder.png similarity index 100% rename from docs/cdp/img/audience_builder.png rename to docs/raptor_cdp/img/audience_builder.png diff --git a/docs/ibexa_products/img/cdp.drawio b/docs/raptor_cdp/img/cdp.drawio similarity index 99% rename from docs/ibexa_products/img/cdp.drawio rename to docs/raptor_cdp/img/cdp.drawio index 16df86642a3..37ce6cecc4f 100644 --- a/docs/ibexa_products/img/cdp.drawio +++ b/docs/raptor_cdp/img/cdp.drawio @@ -22,7 +22,7 @@ - + @@ -298,7 +298,7 @@ - + @@ -563,7 +563,7 @@ - + diff --git a/docs/raptor_cdp/img/cdp.png b/docs/raptor_cdp/img/cdp.png new file mode 100644 index 00000000000..b2d6633ec80 Binary files /dev/null and b/docs/raptor_cdp/img/cdp.png differ diff --git a/docs/cdp/img/customer_profile.png b/docs/raptor_cdp/img/customer_profile.png similarity index 100% rename from docs/cdp/img/customer_profile.png rename to docs/raptor_cdp/img/customer_profile.png diff --git a/docs/cdp/img/cdp_account_number.png b/docs/raptor_cdp/img/raptor_cdp_account_number.png similarity index 100% rename from docs/cdp/img/cdp_account_number.png rename to docs/raptor_cdp/img/raptor_cdp_account_number.png diff --git a/docs/cdp/img/cdp_accounts.png b/docs/raptor_cdp/img/raptor_cdp_accounts.png similarity index 100% rename from docs/cdp/img/cdp_accounts.png rename to docs/raptor_cdp/img/raptor_cdp_accounts.png diff --git a/docs/cdp/img/cdp_activation_general_info.png b/docs/raptor_cdp/img/raptor_cdp_activation_general_info.png similarity index 100% rename from docs/cdp/img/cdp_activation_general_info.png rename to docs/raptor_cdp/img/raptor_cdp_activation_general_info.png diff --git a/docs/cdp/img/cdp_activation_ibexa_info.png b/docs/raptor_cdp/img/raptor_cdp_activation_ibexa_info.png similarity index 100% rename from docs/cdp/img/cdp_activation_ibexa_info.png rename to docs/raptor_cdp/img/raptor_cdp_activation_ibexa_info.png diff --git a/docs/cdp/img/cdp_control_panel.png b/docs/raptor_cdp/img/raptor_cdp_control_panel.png similarity index 100% rename from docs/cdp/img/cdp_control_panel.png rename to docs/raptor_cdp/img/raptor_cdp_control_panel.png diff --git a/docs/cdp/img/cdp_create_new_schema.png b/docs/raptor_cdp/img/raptor_cdp_create_new_schema.png similarity index 100% rename from docs/cdp/img/cdp_create_new_schema.png rename to docs/raptor_cdp/img/raptor_cdp_create_new_schema.png diff --git a/docs/cdp/img/cdp_create_segment_group.png b/docs/raptor_cdp/img/raptor_cdp_create_segment_group.png similarity index 100% rename from docs/cdp/img/cdp_create_segment_group.png rename to docs/raptor_cdp/img/raptor_cdp_create_segment_group.png diff --git a/docs/cdp/img/cdp_person_identifier.png b/docs/raptor_cdp/img/raptor_cdp_person_identifier.png similarity index 100% rename from docs/cdp/img/cdp_person_identifier.png rename to docs/raptor_cdp/img/raptor_cdp_person_identifier.png diff --git a/docs/cdp/img/cdp_userid_mapid.png b/docs/raptor_cdp/img/raptor_cdp_userid_mapid.png similarity index 100% rename from docs/cdp/img/cdp_userid_mapid.png rename to docs/raptor_cdp/img/raptor_cdp_userid_mapid.png diff --git a/docs/cdp/cdp.md b/docs/raptor_cdp/raptor_cdp.md similarity index 61% rename from docs/cdp/cdp.md rename to docs/raptor_cdp/raptor_cdp.md index 51259b70bb0..918ebbdf9d3 100644 --- a/docs/cdp/cdp.md +++ b/docs/raptor_cdp/raptor_cdp.md @@ -1,17 +1,17 @@ --- -description: Ibexa CDP is a software system designed to collect and organize customer data from multiple sources to build comprehensive customer profiles. +description: Raptor CDP is a software system designed to collect and organize customer data from multiple sources to build comprehensive customer profiles. edition: experience --- -# Customer Data Platform (CDP) +# [[= product_name_cdp =]] integration ## What is [[= product_name_cdp =]] -[[= product_name_cdp =]] helps you solve one of the hardest challenges facing business world today: building unique experiences for your customers. +[[= product_name_cdp =]] (Customer Data Platform) helps you solve one of the hardest challenges facing business world today: building unique experiences for your customers. With [[= product_name_cdp =]] you're able to track and aggregate data of your customers' activity on multiple channels. It allows you to create individual customer profiles that enable you to personalize their experience on your platform. -![Ibexa CDP control panel](img/cdp_control_panel.png) +![[[= product_name_cdp =]] control panel](img/raptor_cdp_control_panel.png) ## How it works @@ -19,4 +19,4 @@ It allows you to create individual customer profiles that enable you to personal With defined audiences you can target your user segments at the right time, through the most used channel, with the relevant message, content, or products. The customer data are collected through the system of trackers embedded in different parts of your page. -For more information on activation and trackers, see [CDP activation documentation](cdp_activation.md). +For more information on activation and trackers, see [CDP activation documentation](raptor_cdp_activation.md). diff --git a/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_activation.md b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_activation.md new file mode 100644 index 00000000000..d436a15a1c7 --- /dev/null +++ b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_activation.md @@ -0,0 +1,17 @@ +--- +description: Step-by-step activation procedure of Raptor CDP. +page_type: landing_page +edition: experience +--- + +# Activate [[= product_name_cdp =]] + +Follow a step-by-step procedure that allows you to activate [[= product_name_cdp =]]. + +Activation includes configuration, data export and adding tracking. + +[[= cards([ + "raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration", + "raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export", + "raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking", +], columns=3) =]] diff --git a/docs/cdp/cdp_activation/cdp_add_tracking.md b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md similarity index 91% rename from docs/cdp/cdp_activation/cdp_add_tracking.md rename to docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md index 097f6d5ab83..81ee5236537 100644 --- a/docs/cdp/cdp_activation/cdp_add_tracking.md +++ b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md @@ -1,9 +1,9 @@ --- -description: Adding tracking in [[= product_name_cdp =]]. +description: Adding tracking in Raptor CDP. edition: experience --- -# Add tracking +# Track with [[= product_name_cdp =]] The final step is setting up a tracking script that identifies visitors and records their interactions. You can set it up in two ways: @@ -14,7 +14,7 @@ You can set it up in two ways: ## Set up tracking with built-in Raptor tracking functions If your project uses the [Raptor connector](raptor_connector.md), use the built-in [Raptor tracking functions](tracking_functions.md). -This recommended approach supports both client-side and server-side tracking, handles cookie consent, and sets the tracking cookie required for [anonymous user segmentation](cdp_configuration.md#anonymous-user-segmentation). +This recommended approach supports both client-side and server-side tracking, handles cookie consent, and sets the tracking cookie required for [anonymous user segmentation](raptor_cdp_configuration.md#anonymous-user-segmentation). For setup instructions, see [Raptor tracking functions](tracking_functions.md). diff --git a/docs/cdp/cdp_activation/cdp_configuration.md b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration.md similarity index 92% rename from docs/cdp/cdp_activation/cdp_configuration.md rename to docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration.md index 39a13c8eb5e..3723fdc21cf 100644 --- a/docs/cdp/cdp_activation/cdp_configuration.md +++ b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration.md @@ -1,9 +1,9 @@ --- -description: Step-by-step configuration procedure of Ibexa CDP. +description: Step-by-step configuration procedure of Raptor CDP. edition: experience --- -# Configuration +# Configure [[= product_name_cdp =]] To configure [[= product_name_cdp =]], use the `ibexa.system..cdp` [configuration key](configuration.md#configuration-files): @@ -53,11 +53,11 @@ ibexa: Now, fill in the account number. Log in to [[= product_name_cdp =]] and in the top right corner, select available accounts. -![List of available accounts](cdp_accounts.png) +![List of available accounts](../img/raptor_cdp_accounts.png) A pop-up window displays a list of all available accounts and their numbers. -![Account number](cdp_account_number.png) +![Account number](../img/raptor_cdp_account_number.png) ## Segment group @@ -71,13 +71,13 @@ Choose wisely, as once connected to CDP segment group cannot be changed. After you create the segment group in the back office and connect it to [[= product_name_cdp =]], you cannot change it in any way, including edit its name. -![Creating a new segment group](cdp_create_segment_group.png) +![Creating a new segment group](../img/raptor_cdp_create_segment_group.png) Next, add a segment group identifier to the configuration. ## Anonymous user segmentation -To set up [segmentation for anonymous users](cdp_guide.md#anonymous-user-segmentation), take the following steps: +To set up [segmentation for anonymous users](raptor_cdp_guide.md#anonymous-user-segmentation), take the following steps: ### Set up CDP API activation diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md similarity index 91% rename from docs/cdp/cdp_activation/cdp_data_export.md rename to docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md index dc845accbb6..81b3bf46a72 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md @@ -1,9 +1,9 @@ --- -description: Step-by-step data export procedure in Ibexa CDP. +description: Step-by-step data export procedure in Raptor CDP. edition: experience --- -# Data export +# Export [[= product_name_cdp =]] data You need to specify a source of the user data that [[= product_name_cdp =]] connects to. To do so, go to **Data Manager** in **Tools** section and select **Create new dataflow**. @@ -46,7 +46,7 @@ The first one is used to send the test user data to the Data Manager. If it passes a validation test in the **Activation** section, use the latter one to send a full version. You can extend exported user data with custom fields from your user content, such as date of birth, preferences, or other profile information. -For more information, see [Data customization](cdp_data_customization.md#export-additional-user-data). +For more information, see [Data customization](raptor_cdp_data_customization.md#export-additional-user-data). Next, go back to [[= product_name_cdp =]] and select **Validate & download**. If the file passes, you can see a confirmation message. @@ -66,18 +66,18 @@ If you make any alterations, select the **Parse File** to generate columns with In the **Transform & Map** section you transform data and map it to a schema. At this point, you can map **email** to **email** and **id** to **integer** fields to get custom columns. -If you have [extended user data export with custom fields](cdp_data_customization.md#export-additional-user-data), those fields appear as additional columns in this section. +If you have [extended user data export with custom fields](raptor_cdp_data_customization.md#export-additional-user-data), those fields appear as additional columns in this section. Make sure to add them to your schema in Raptor so they can be used for segmentation and recommendations. Next, select **Create schema based on the downloaded columns**. It moves you to Schema Creator. There, choose **PersonalData** as a parent and name the schema. -![Create new schema](cdp_create_new_schema.png) +![Create new schema](../img/raptor_cdp_create_new_schema.png) Next, select all the columns and set Person Identifier as **userid**. -![Person Identifier](cdp_person_identifier.png) +![Person Identifier](../img/raptor_cdp_person_identifier.png) If you used PersonData or Catalog type schemas, the system requires specifying the Write Mode that is applied to them. @@ -88,7 +88,7 @@ For example, if a customer unsubscribes a newsletter, their email remains in the Next, select **userid** from a **Schema columns section** on the right and map it to **id**. -![Map userid to id](cdp_userid_mapid.png) +![Map userid to id](../img/raptor_cdp_userid_mapid.png) ## Activation @@ -114,14 +114,14 @@ In the Audience Builder, you can also connect created audiences to the activatio ## Activation -Activation synchronises data from [[= product_name_cdp =]] to the [[= product_name =]]. +Activation synchronises data from [[= product_name_cdp =]] to [[= product_name =]]. When you specify a segment, you can activate it on multiple communication channels, such as newsletters or commercials. You can configure multiple activations based data flows. First, from the menu bar, select **Activations** and create a new **Ibexa** activation. Specify name of your activation, select `userid` as **Person Identifier** and click **Next**. -![General Information - Activation](cdp_activation_general_info.png) +![General Information - Activation](../img/raptor_cdp_activation_general_info.png) Next, you can fill in **Ibexa information** they must match the ones provided in the YAML configuration: @@ -133,7 +133,7 @@ It points to a segment group where all the CDP audiences are stored. - **Base URL** - URL of your instance with added `/cdp/webhook` at the end. -![Ibexa Information - Activation](cdp_activation_ibexa_info.png) +![Ibexa Information - Activation](../img/raptor_cdp_activation_ibexa_info.png) Finally, you can specify the audiences you wish to include. diff --git a/docs/cdp/cdp_data_customization.md b/docs/raptor_cdp/raptor_cdp_data_customization.md similarity index 96% rename from docs/cdp/cdp_data_customization.md rename to docs/raptor_cdp/raptor_cdp_data_customization.md index 5d29bf815bc..c4755bc5ee9 100644 --- a/docs/cdp/cdp_data_customization.md +++ b/docs/raptor_cdp/raptor_cdp_data_customization.md @@ -1,9 +1,9 @@ --- -description: Data customization in Ibexa CDP. +description: Data customization in Raptor CDP. edition: experience --- -# Data customization +# Customize [[= product_name_cdp =]] data You can customize user, content, and product data exported to CDP and you can control what field type information you want to export. By default, custom field types have basic export functionality. @@ -20,7 +20,7 @@ The base class handles user field validation and provides helper methods for wor The following example adds a custom date of birth field to the exported data: ``` php -[[= include_code('code_samples/cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php') =]] +[[= include_code('code_samples/raptor_cdp/date_of_birth_export/src/Export/User/DateOfBirthUserItemProcessor.php') =]] ``` Register your processor as a Symfony service and tag it with `ibexa.cdp.export.user.item_processor`: diff --git a/docs/cdp/cdp_data_export_schedule.md b/docs/raptor_cdp/raptor_cdp_data_export_schedule.md similarity index 93% rename from docs/cdp/cdp_data_export_schedule.md rename to docs/raptor_cdp/raptor_cdp_data_export_schedule.md index 56451196205..5986ac9c7ff 100644 --- a/docs/cdp/cdp_data_export_schedule.md +++ b/docs/raptor_cdp/raptor_cdp_data_export_schedule.md @@ -1,10 +1,10 @@ --- -description: Data export schedule in Ibexa CDP. +description: Data export schedule in Raptor CDP. edition: experience month_change: true --- -# CDP data export schedule +# Schedule [[= product_name_cdp =]] data export ## Configuration key @@ -70,4 +70,4 @@ php bin/console ibexa:cdp:stream-content-data --help The configuration is executed by `ibexa:cron:run` command which must be configured as a cron job. -For more information, see [Schedule tasks](install_ibexa_dxp.md#schedule-tasks). +For more information, see [Schedule tasks](install_cohesivo.md#schedule-tasks). diff --git a/docs/cdp/cdp_guide.md b/docs/raptor_cdp/raptor_cdp_guide.md similarity index 83% rename from docs/cdp/cdp_guide.md rename to docs/raptor_cdp/raptor_cdp_guide.md index 477624e3aab..cbd14615898 100644 --- a/docs/cdp/cdp_guide.md +++ b/docs/raptor_cdp/raptor_cdp_guide.md @@ -1,13 +1,13 @@ --- -description: The [[= product_name_cdp =]] product guide describes all the possibilities that the Customer Data Platform offers to help you build great customer experiences. +description: The Raptor CDP product guide describes all the possibilities that the Customer Data Platform offers to help you build great customer experiences. edition: experience --- -# Ibexa Customer Data Platform (CDP) product guide +# [[= product_name_cdp =]] product guide ## What is [[= product_name_cdp =]] -[[= product_name_cdp =]] is a Customer Data Platform module that helps you build unique and memorable experiences for your customers. +[[= product_name_cdp =]] (Customer Data Platform) module helps you build unique and memorable experiences for your customers. By using [[= product_name_cdp =]] you can monitor and compile data about your customers' activity on multiple channels. It also allows you to create individual customer profiles so you can customize their experience on your platform. @@ -27,15 +27,15 @@ It helps you activate your users and give them real-time interaction. You can target certain user segments with the appropriate message, content, or products at the right time through the most used channels by using specified audiences. Customer data is gathered through a system of trackers embedded in various areas of your website. -![CDP - how does it work](img/cdp_how_works.png) +![CDP - how does it work](img/cdp.png) ### Installation and configuration -To start using [[= product_name_cdp =]], first you need to contact your sales representative, who provides you with a link to [register your [[= product_name_cdp =]] account](/cdp/cdp_installation.md#register-in-ibexa-cdp-dashboard). +To start using [[= product_name_cdp =]], first you need to contact your sales representative, who provides you with a link to [register your [[= product_name_cdp =]] account](/raptor_cdp/raptor_cdp_installation.md#register-in-raptor-cdp-dashboard). When you're done with registration process, you're able to access a separate instance with the data needed to configure, activate, and use this feature. -After your account is created, you can [download and install the [[= product_name_cdp =]] package](/cdp/cdp_installation.md#install-cdp-package) that is opt-in and needs to be downloaded separately. -Last step is to go through the [configuration process](cdp_configuration.md). +After your account is created, you can [download and install the [[= product_name_cdp =]] package](/raptor_cdp/raptor_cdp_installation.md#install-package) that is opt-in and needs to be downloaded separately. +Last step is to go through the [configuration process](raptor_cdp_configuration.md). ### Customer profile @@ -65,7 +65,7 @@ Remember to add a segment group identifier to the configuration, under the `segm ### Data export Configuration in [[= product_name_cdp =]] allows you to automate the process of exporting content, users, and products. -An `ibexa_cdp.data_export` [configuration key](cdp_data_export_schedule.md#configuration-key) includes the `schedule` setting where you can find separate sections for exporting user, content, and product. +An `ibexa_cdp.data_export` [configuration key](raptor_cdp_data_export_schedule.md#configuration-key) includes the `schedule` setting where you can find separate sections for exporting user, content, and product. Structure of each section is exactly the same and includes `interval` and `options` elements: - `interval` - sets the frequency at which the command is invoked, uses cron expressions, for example, '*/30 * * * *' means "every 30 minutes", '0 */12 * * *' means "every 12th hour" @@ -77,7 +77,7 @@ It's important, because all the types of content/product must have their own par Regarding data export, currently, only Stream File transport is supported and can be initialized from the configuration. -For more information, see [CDP data export](cdp_data_export.md). +For more information, see [CDP data export](raptor_cdp_data_export.md). ### Data customization @@ -85,12 +85,12 @@ For more information, see [CDP data export](cdp_data_export.md). With [[= product_name_cdp =]], you can export field types and field type values. They're exported with metadata and attributes, for example, ID, field definition name, type, or value. -For more information, see [data customization](cdp_data_customization.md#data-customization) documentation in Developer Documentation. +For more information, see [data customization](raptor_cdp_data_customization.md) documentation in Developer Documentation. ### Client-side Tracking The final step is setting up a tracking script. -For more information, see [CDP add client-side tracking](cdp_add_tracking.md) and [Introduction to tracking in Raptor documentation](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation). +For more information, see [CDP add client-side tracking](raptor_cdp_add_tracking.md) and [Introduction to tracking in Raptor documentation](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation). ### Audience Builder diff --git a/docs/cdp/cdp_installation.md b/docs/raptor_cdp/raptor_cdp_installation.md similarity index 84% rename from docs/cdp/cdp_installation.md rename to docs/raptor_cdp/raptor_cdp_installation.md index 45f98359ae8..5b4c954c02f 100644 --- a/docs/cdp/cdp_installation.md +++ b/docs/raptor_cdp/raptor_cdp_installation.md @@ -1,9 +1,9 @@ --- -description: Installation of standalone [[= product_name_cdp =]] package. +description: Installation of standalone Raptor CDP package. edition: experience --- -# [[= product_name_cdp =]] installation +# Install [[= product_name_cdp =]] There are three steps required to install [[= product_name_cdp =]]. First, you need to register your [[= product_name_cdp =]] account, then you can download a CDP package and update the configuration. @@ -13,7 +13,7 @@ First, you need to register your [[= product_name_cdp =]] account, then you can If you decide to acquire [[= product_name_cdp =]], contact your sales representative to receive a registration link to [[= product_name_cdp =]]. After registration, you get access to a separate instance where you can find data required for configuring, activating, and using this feature. -## Install CDP package +## Install package [[= product_name_cdp =]] comes in an additional package that is opt-in and needs to be downloaded separately. @@ -38,4 +38,4 @@ security: ``` Now, you can configure [[= product_name_cdp =]]. -Go to [the activation documentation](cdp_activation.md) and follow the steps. +Go to [the activation documentation](raptor_cdp_activation.md) and follow the steps. diff --git a/docs/recommendations/raptor_integration/connector_installation_configuration.md b/docs/recommendations/raptor_integration/connector_installation_configuration.md index 75e626a5164..3e2df68d3c5 100644 --- a/docs/recommendations/raptor_integration/connector_installation_configuration.md +++ b/docs/recommendations/raptor_integration/connector_installation_configuration.md @@ -3,13 +3,13 @@ description: To configure the Raptor integration, follow the step-by-step proced month_change: true --- -# Configuration procedure +# Install and configure [[= product_name_cdp_base =]] -To configure the [Raptor](https://www.raptorservices.com/) integration add-on, follow the step-by-step procedure below. +To configure the [[[= product_name_cdp_base =]]](https://www.raptorservices.com/) integration add-on, follow the step-by-step procedure below. -## Install Raptor connector +## Install [[= product_name_cdp_base =]] connector -Before you can proceed to configuring the integration with Raptor, install the Raptor connector. +Before you can proceed to configuring the integration with [[= product_name_cdp_base =]], install the [[= product_name_cdp_base =]] connector. To do it, run the following command: ``` bash @@ -23,24 +23,24 @@ composer require ibexa/connector-raptor ## SiteAccess-aware configuration -To configure the Raptor connector, use the `ibexa.system..connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file: +To configure the [[= product_name_cdp_base =]] connector, use the `ibexa.system..connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file: ``` yaml [[= include_file('code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml', 0, 17) =]] ``` - `enabled` - enables or disables the connector for a given scope. Default value: `true`. If set to `false`, no tracking or recommendation requests are executed. -- `customer_id` - an identifier used to authenticate requests to the recommendation engine. You can find this value as ["Account number"](connector_installation_configuration.md#customer-id) in Raptor Control Panel. +- `customer_id` - an identifier used to authenticate requests to the recommendation engine. You can find this value as ["Account number"](connector_installation_configuration.md#customer-id) in [[= product_name_cdp_base =]] Control Panel. - `tracking_type` - defines how user events are sent to the tracking API. Default value: `client`. Possible values: - `client` - tracking is executed in the browser using JavaScript snippets generated by the [Twig functions](recommendations_twig_functions.md) and included in the templates. This approach may be blocked by ad blockers. - `server` - tracking is handled on the backend, with events sent directly to the tracking API. It's not affected by ad blockers. - - `hybrid` - tracking is executed in the browser by a first-party JavaScript provided by the DXP instead of Raptor and then forwarded by the DXP server to the Raptor SaaS. For more information, see [Hybrid tracking](hybrid_tracking.md). -- `recommendations_api_key` - an API key used to authenticate requests to the Recommendations API. This key allows the connector to retrieve personalized recommendations from the recommendation engine. You can find this value as ["API key"](connector_installation_configuration.md#recommendations-api-key) in Raptor Control Panel. -- `recommendations_api_uri` (optional) - overrides the default Raptor address, do not set it unless a custom endpoint is required. + - `hybrid` - tracking is executed in the browser by a first-party JavaScript provided by [[= product_name =]] instead of [[= product_name_cdp_base =]] and then forwarded by the [[= product_name =]] server to the [[= product_name_cdp_base =]] SaaS. For more information, see [Hybrid tracking](hybrid_tracking.md). +- `recommendations_api_key` - an API key used to authenticate requests to the Recommendations API. This key allows the connector to retrieve personalized recommendations from the recommendation engine. You can find this value as ["API key"](connector_installation_configuration.md#recommendations-api-key) in [[= product_name_cdp_base =]] Control Panel. +- `recommendations_api_uri` (optional) - overrides the default [[= product_name_cdp_base =]] address, do not set it unless a custom endpoint is required. - `cookie_id_lifetime_days` (optional) - the lifetime in days of the server-side tracking identifier cookies. Default value: `365` days. Minimum value: `1` day. -By default, `tracking_type` is set to `client` as client-side tracking is the standard Raptor mode. -To understand the differences between client and server tracking types, including their advantages and disadvantages, refer to the [Raptor documentation](https://content.raptorservices.com/help-center/client-side-vs.-server-side-tracking). +By default, `tracking_type` is set to `client` as client-side tracking is the standard [[= product_name_cdp_base =]] mode. +To understand the differences between client and server tracking types, including their advantages and disadvantages, refer to the [[[= product_name_cdp_base =]] documentation](https://content.raptorservices.com/help-center/client-side-vs.-server-side-tracking). !!! note @@ -49,7 +49,7 @@ To understand the differences between client and server tracking types, includin ### Customer ID -To find the value for the `customer_id` identifier, log in to Raptor Control Panel, and look for "Account number": +To find the value for the `customer_id` identifier, log in to [[= product_name_cdp_base =]] Control Panel, and look for "Account number": A. In the top-left corner, above the account name, you can find the account number for the currently active account. B. Click the arrow icon in the top-left corner to expand the window. There you can see a list of all your accounts, with their numbers shown in the “Account number” column on the right. This way, if you have multiple accounts, you can locate and copy the number of any of your accounts, not just the active one. @@ -58,7 +58,7 @@ B. Click the arrow icon in the top-left corner to expand the window. There you c ### Recommendations API key -To find the value for the `recommendations_api_key`, log in to Raptor Control Panel, and look for "API key". +To find the value for the `recommendations_api_key`, log in to [[= product_name_cdp_base =]] Control Panel, and look for "API key". To do it, in the left panel, open the **Recommendations** section, and select **Website**. Next, click on the Web module you’re interested in. In the top-right corner, click the three-dot icon and select **API information**. @@ -73,7 +73,7 @@ The following settings are global and apply to the entire application (they are - `strict_exceptions` – when enabled, tracking exceptions are thrown instead of being silently handled. Default value: `%kernel.debug%`. -- `hybrid_tracking_proxy_path` - by default, it's set to `/raptor/track`. The client-side shim sends tracking events to this same-origin endpoint, which forwards them to Raptor asynchronously. +- `hybrid_tracking_proxy_path` - by default, it's set to `/raptor/track`. The client-side shim sends tracking events to this same-origin endpoint, which forwards them to [[= product_name_cdp_base =]] asynchronously. This value can be overridden in `config/packages/ibexa_connector_raptor.yaml` file, for example: diff --git a/docs/recommendations/raptor_integration/custom_recommendation_rendering.md b/docs/recommendations/raptor_integration/custom_recommendation_rendering.md index fb79746e695..3ff45a2abcf 100644 --- a/docs/recommendations/raptor_integration/custom_recommendation_rendering.md +++ b/docs/recommendations/raptor_integration/custom_recommendation_rendering.md @@ -3,7 +3,7 @@ description: Use existing controllers to render recommendations outside the Page month_change: true --- -# Custom recommendation rendering +# Render recommendations You can use existing controllers to render [recommendations](recommendation_blocks.md) outside the Page Builder. The controllers responsible for rendering block recommendations on the front-end are independent and can be used to render recommendations for specific strategies. diff --git a/docs/recommendations/raptor_integration/hybrid_tracking.md b/docs/recommendations/raptor_integration/hybrid_tracking.md index 6a9a75f2240..b838c10b55b 100644 --- a/docs/recommendations/raptor_integration/hybrid_tracking.md +++ b/docs/recommendations/raptor_integration/hybrid_tracking.md @@ -3,20 +3,20 @@ description: Enable hybrid tracking to avoid ad blockers and proxy events throug month_change: true --- -# Raptor hybrid tracking +# Hybrid tracking Hybrid tracking mode is an additional tracking mode available alongside [`client` and `server`](tracking_functions.md). -In hybrid mode, the bundle includes a client-side [shim](https://en.wikipedia.org/wiki/Shim_(computing)) that captures Raptor tracking events and sends them to a same-origin endpoint instead of communicating directly with Raptor SaaS. -The server enriches each event with identifiers resolved from request cookies (`cookieId`, `sessionId`, and `userId`) and forwards it to Raptor asynchronously through [Ibexa Messenger](background_tasks.md). -Since the browser never connects to the Raptor domain, ad blockers cannot block the requests. +In hybrid mode, the bundle includes a client-side [shim](https://en.wikipedia.org/wiki/Shim_(computing)) that captures [[= product_name_cdp_base =]] tracking events and sends them to a same-origin endpoint instead of communicating directly with [[= product_name_cdp_base =]] servers. +The server enriches each event with identifiers resolved from request cookies (`cookieId`, `sessionId`, and `userId`) and forwards it to [[= product_name_cdp_base =]] asynchronously through [Ibexa Messenger](background_tasks.md). +Since the browser never connects to the [[= product_name_cdp_base =]] domain, ad blockers cannot block the requests. ## Hybrid vs server or client-side tracking Both `server` and `hybrid` tracking modes deliver pageviews and events server-side, so tracking requests are not affected by ad blockers. -The main difference is that `hybrid` mode loads a first-party tracking JavaScript (`raptor-proxy.js`) provided by the DXP instance, instead of the Raptor SaaS JavaScript. -The Raptor script itself (`//deliver.raptorstatic.com/script/raptor-3.0.min.js`) is loaded only in `client` mode. +The main difference is that `hybrid` mode loads a first-party tracking JavaScript (`raptor-proxy.js`) provided by the [[= product_name =]] instance, instead of the [[= product_name_cdp_base =]] SaaS JavaScript. +The [[= product_name_cdp_base =]] script itself (`//deliver.raptorstatic.com/script/raptor-3.0.min.js`) is loaded only in `client` mode. -The browser script only forwards captured tracking events to the same-origin proxy endpoint on your DXP instance. First-party visitor cookies are created and refreshed server-side, which is what helps them survive Safari [Intelligent Tracking Prevention](https://webkit.org/blog/7675/intelligent-tracking-prevention/). +The browser script only forwards captured tracking events to the same-origin proxy endpoint on your [[= product_name =]] instance. First-party visitor cookies are created and refreshed server-side, which is what helps them survive Safari [Intelligent Tracking Prevention](https://webkit.org/blog/7675/intelligent-tracking-prevention/). Event tracking still happens on the server, so ad blockers cannot block it. The main advantage of `hybrid` mode over `server` mode is its ability to capture client-side tracking events. @@ -35,11 +35,11 @@ Check the table below to compare the behavior of different tracking modes: When hybrid tracking is enabled, `TrackingScriptExtension` renders the proxy bootstrap template and loads the `raptor-proxy.js` shim, which replaces the `window.raptor.push` function and sends out the events queued before the tracking consent was given. The shim sends each captured event to the proxy endpoint as a separate POST request. The `TrackingProxyController::track` action validates the `EventPayloadParser` payload, enriches each event with identifiers resolved from cookies, and dispatches one `TrackProxiedEventMessage` for every event. -Messages are then processed asynchronously via Ibexa Messenger and `TrackProxiedEventMessageHandler` ultimately forwards them to Raptor through `TrackingService::trackRawParameters`. +Messages are then processed asynchronously via Ibexa Messenger and `TrackProxiedEventMessageHandler` ultimately forwards them to [[= product_name_cdp_base =]] through `TrackingService::trackRawParameters`. ### Hybrid tracking configuration -To configure the Raptor hybrid tracking, use the `ibexa.system..connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file: +To configure the [[= product_name_cdp_base =]] hybrid tracking, use the `ibexa.system..connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file: ``` yaml ibexa_connector_raptor: @@ -75,7 +75,7 @@ Without it, the proxy endpoint returns 404 responses and tracking events are not You can configure the proxy endpoint path globally. By default, it's set to `/raptor/track`. -The client-side shim sends tracking events to this same-origin endpoint, which forwards them to Raptor asynchronously. +The client-side shim sends tracking events to this same-origin endpoint, which forwards them to [[= product_name_cdp_base =]] asynchronously. ``` yaml ibexa_connector_raptor: diff --git a/docs/recommendations/raptor_integration/raptor_connector.md b/docs/recommendations/raptor_integration/raptor_connector.md index c266a2b4ce8..8b2a4cfb303 100644 --- a/docs/recommendations/raptor_integration/raptor_connector.md +++ b/docs/recommendations/raptor_integration/raptor_connector.md @@ -4,9 +4,9 @@ page_type: landing_page month_change: false --- -# Raptor connector +# [[= product_name_cdp_base =]] integration -The [Raptor](https://www.raptorservices.com/) connector is an add-on that provides a seamless integration between [[= product_name =]] and Raptor recommendation engine. +The [[[= product_name_cdp_base =]]](https://www.raptorservices.com/) integration is an add-on that provides a seamless integration between [[= product_name =]] and [[= product_name_cdp_base =]] recommendation engine. Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps increase conversion rates, drive sales, and improve user engagement. @@ -20,10 +20,10 @@ The connector ensures a smooth and unified integration layer, enabling: This approach reduces integration complexity while providing a scalable foundation for personalization use cases across multiple sites and markets. -To configure the integration with Raptor, follow a step-by-step procedure that allows you to activate the Raptor connector. +To configure the integration with [[= product_name_cdp_base =]], follow a step-by-step procedure that allows you to activate the [[= product_name_cdp_base =]] connector. Activation includes [configuration](connector_installation_configuration.md), adding tracking scripts and events, and using [Page Builder](page_builder_guide.md) blocks. -For more information about tracking, check the Raptor documentation: [Implementing tracking](https://content.raptorservices.com/help-center/data-management#implementing-tracking). +For more information about tracking, check the [[= product_name_cdp_base =]] documentation: [Implementing tracking](https://content.raptorservices.com/help-center/data-management#implementing-tracking). [[= cards([ "recommendations/raptor_integration/connector_installation_configuration", diff --git a/docs/recommendations/raptor_integration/raptor_connector_guide.md b/docs/recommendations/raptor_integration/raptor_connector_guide.md index 3814914e758..ec6d17aedd1 100644 --- a/docs/recommendations/raptor_integration/raptor_connector_guide.md +++ b/docs/recommendations/raptor_integration/raptor_connector_guide.md @@ -3,14 +3,14 @@ description: Discover Raptor integration - an add-on focused on recommendations month_change: true --- -# Raptor integration guide +# [[= product_name_cdp_base =]] integration product guide -Discover [Raptor](https://www.raptorservices.com/) integration - an add-on that is focused on recommendations and tracking customer behaviors. -It includes Raptor connector with tracking scripts and events, used to track and analyze customer behaviors, and a set of Recommendation blocks. +Discover [[[= product_name_cdp_base =]]](https://www.raptorservices.com/) integration - an add-on that is focused on recommendations and tracking customer behaviors. +It includes the connector with tracking scripts and events that are used to track and analyze customer behaviors, and a set of Recommendation blocks. -## What is Raptor connector +## What is [[= product_name_cdp_base =]] integration -The [Raptor connector](raptor_connector.md) provides a seamless integration between [[= product_name =]] and Raptor recommendation engine. +The [[[= product_name_cdp_base =]] integration](raptor_connector.md) provides a seamless integration between [[= product_name =]] and the [[= product_name_cdp_base =]] recommendation engine. Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement. @@ -26,11 +26,11 @@ This approach simplifies integration while supporting personalization across dif ## Availability -Raptor integration elements, such as tracking, Twig functions, and public API, are available in all supported [[= product_name =]] editions starting from v5.0.7 version. +[[= product_name_cdp_base =]] integration elements, such as tracking, Twig functions, and public API, are available in all supported [[= product_name =]] editions starting from v5.0.7 version. Recommendation blocks provided in Page Builder, are available in [[= product_name_exp =]] and [[= product_name_com =]] editions. -## How does Raptor tracking work +## How does [[= product_name_cdp_base =]] tracking work To start [tracking](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation) user interactions, the tracking script needs to be added to the website’s layout. Tracking can be set up either on the client-side, server-side, or using hybrid mode, depending on how you want to capture and process the events. @@ -38,7 +38,7 @@ Tracking can be set up either on the client-side, server-side, or using hybrid m The tracking works differently depending on the mode you choose. In server-side mode, tracking happens on the server, handling all events without loading scripts in the browser. In client-side mode, it inserts script tags so tracking runs directly in the browser. -In hybrid mode, the browser loads a first-party [shim](https://en.wikipedia.org/wiki/Shim_(computing)) that forwards tracking events to a same-origin proxy endpoint instead of the Raptor SaaS script, helping prevent ad blockers from blocking tracking. +In hybrid mode, the browser loads a first-party [shim](https://en.wikipedia.org/wiki/Shim_(computing)) that forwards tracking events to a same-origin proxy endpoint instead of the [[= product_name_cdp_base =]] SaaS script, helping prevent ad blockers from blocking tracking. For more information, see [Hybrid tracking](hybrid_tracking.md). You can switch between tracking modes at any time by changing the tracking type to fit your setup and needs. @@ -47,7 +47,7 @@ You can switch between tracking modes at any time by changing the tracking type ### Tracking -Raptor [tracking functions](tracking_functions.md) allow you to collect data about how users interact with your products and content. +[[= product_name_cdp_base =]] [tracking functions](tracking_functions.md) allow you to collect data about how users interact with your products and content. You can track product visits to better understand what users are viewing. Provided [Twig functions](../../templating/twig_function_reference/recommendations_twig_functions.md) simplify the implementation, allowing developers to quickly add tracking to templates without complex setup. @@ -56,7 +56,7 @@ This gives you the data you need to better understand user behavior, improve rec ### Recommendation blocks -The Raptor Integration add-on provides a set of ready-to-use recommendation blocks that can be added directly in the [Page Builder](page_builder_guide.md). +The [[= product_name_cdp_base =]] integration add-on provides a set of ready-to-use recommendation blocks that can be added directly in the [Page Builder](page_builder_guide.md). These blocks can be configured to adjust how they work and what they display. Content, Product, and Commerce recommendations can be placed on landing pages using these components. @@ -124,7 +124,7 @@ Start building predictions of their behaviors and suggest products your visitors ### Track performance and increase conversions -Use the Raptor service in your Commerce shop and see how recommendations drive sales. +Use the [[= product_name_cdp_base =]] service in your Commerce shop and see how recommendations drive sales. Keep track of which recommendations are shown to visitors and measure conversion rates to evaluate their effectiveness against your goals. ### Flexible tracking with PHP API diff --git a/docs/recommendations/raptor_integration/recommendation_blocks.md b/docs/recommendations/raptor_integration/recommendation_blocks.md index 5c6c9673424..2a728dbf990 100644 --- a/docs/recommendations/raptor_integration/recommendation_blocks.md +++ b/docs/recommendations/raptor_integration/recommendation_blocks.md @@ -6,7 +6,7 @@ month_change: true # Recommendation blocks in Page Builder -One of the Raptor Integration elements is the introduction of recommendation blocks available in the [Page Builder](page_builder_guide.md). +One of the [[= product_name_cdp_base =]] Integration elements is the introduction of recommendation blocks available in the [Page Builder](page_builder_guide.md). Content, Product, and Commerce recommendations can be added to a landing page using the blocks. @@ -41,7 +41,7 @@ In the toolbar, corresponding categories for recommendation blocks are available ![Recommendation blocks](img/recommendation_blocks.png) After opening the settings of a recommendation block, a link is available at the bottom of the window. -It leads to the [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/) (opens in a separate tab), where you can configure advanced settings and fine-tune the recommendation strategy. +It leads to the [[[= product_name_cdp_base =]] Control Panel](https://controlpanel.raptorsmartadvisor.com/) (opens in a separate tab), where you can configure advanced settings and fine-tune the recommendation strategy. ![Advanced settings](img/advanced_settings.png) diff --git a/docs/recommendations/raptor_integration/tracking_functions.md b/docs/recommendations/raptor_integration/tracking_functions.md index 4fc378fef8b..98454d7a473 100644 --- a/docs/recommendations/raptor_integration/tracking_functions.md +++ b/docs/recommendations/raptor_integration/tracking_functions.md @@ -3,12 +3,12 @@ description: Integrate the tracking script to collect user interactions. month_change: true --- -# Raptor tracking functions +# Tracking functions -[Raptor connector](raptor_connector.md) introduces [visit tracking functionality](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation) for collecting user interactions with products and content. +[[[= product_name_cdp_base =]] connector](raptor_connector.md) introduces [visit tracking functionality](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation) for collecting user interactions with products and content. The implementation includes product visit tracking with mapping to tracking parameters, and Twig functions for straightforward integration. -Raptor integration introduces two Twig functions: +[[= product_name_cdp_base =]] integration introduces two Twig functions: - [`ibexa_tracking_script()`](../../templating/twig_function_reference/recommendations_twig_functions.md#ibexa_tracking_script-function) - allows you to embed main tracking script into the website. - [`ibexa_tracking_track_event()`](../../templating/twig_function_reference/recommendations_twig_functions.md#ibexa_tracking_track_event-function) - is responsible for sending event data to the service, enabling tracking of user interactions and behaviors. @@ -45,7 +45,7 @@ connector_raptor: - **server** - doesn't return anything in the `prod` environment, while returns HTML comments in the `dev` environment or any environment where `kernel.debug` Symfony container parameter is set to `true`. Tracking is performed server-side. - **client** - returns `script` tags to load the tracking script in the browser. -- **hybrid** - returns script tags like `client`, but they load a first-party shim (`raptor-proxy.js`) that forwards events to a same-origin proxy endpoint instead of the Raptor SaaS script. The server then delivers them to Raptor, preventing ad blockers from blocking tracking. +- **hybrid** - returns script tags like `client`, but they load a first-party shim (`raptor-proxy.js`) that forwards events to a same-origin proxy endpoint instead of the [[= product_name_cdp_base =]] SaaS script. The server then delivers them to [[= product_name_cdp_base =]], preventing ad blockers from blocking tracking. You can switch tracking mode anytime by changing the `tracking_type` parameter. @@ -58,7 +58,7 @@ For more information on Tracking modes, see documentation: ## Complex integration -For more complex integrations, the [[= product_name_base =]] Design Engine can be used to override parts or entire templates that render the tracking script. +For more complex integrations, the [Design Engine](design_engine.md) can be used to override parts or entire templates that render the tracking script. |Template|Description|Example project path| |--------|-----------|--------------------| @@ -67,7 +67,7 @@ For more complex integrations, the [[= product_name_base =]] Design Engine can b Available variables are: -- **customer_id** - type: string, Raptor account ID used for tracking +- **customer_id** - type: string, [[= product_name_cdp_base =]] account ID used for tracking - **script_url** - type: string, URL of the tracking script, by default `//deliver.raptorstatic.com/script/raptor-3.0.min.js`, configurable through `ibexa.connector.raptor.tracking_script.url` Symfony Dependency Injection container parameter (not SiteAccess-aware) - **has_consented** - type: boolean, indicates whether the user has given consent, default value: `false` (unless explicitly passed as function argument) - **debug** - type: boolean, `kernel.debug` Symfony dependency injection container parameter, typically `true` in development environments and `false` in production @@ -79,7 +79,7 @@ You can override the default templates, either individually or both at the same ## Extending default templates -It's possible to extend `script.html.twig` by combining the [[= product_name_base =]] Design Engine with standard Symfony template reference in `templates/themes/standard/ibexa/tracking/script.html.twig`: +It's possible to extend `script.html.twig` by combining the Design Engine with standard Symfony template reference in `templates/themes/standard/ibexa/tracking/script.html.twig`: ``` html+twig [[= include_file('code_samples/recommendations/templates/themes/standard/ibexa/tracking/script.html.twig') =]] diff --git a/docs/recommendations/raptor_integration/tracking_php_api.md b/docs/recommendations/raptor_integration/tracking_php_api.md index 6b9cabe1cb8..1cd07227f42 100644 --- a/docs/recommendations/raptor_integration/tracking_php_api.md +++ b/docs/recommendations/raptor_integration/tracking_php_api.md @@ -5,7 +5,7 @@ month_change: false # Tracking with PHP API -You can interact directly with the [Raptor connector](raptor_connector.md)'s service using the [PHP API](/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking.html) for advanced tracking usage. +You can interact directly with the [[[= product_name_cdp_base =]] connector](raptor_connector.md)'s service using the [PHP API](/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking.html) for advanced tracking usage. ## Advanced usage – direct interaction with the service @@ -41,7 +41,7 @@ Check the following example: ### Category parameter for product events In [[= product_name =]], products can be assigned to multiple categories. -However, Raptor accepts only a single category value in tracking events. +However, [[= product_name_cdp_base =]] accepts only a single category value in tracking events. By default, the connector uses the first category from the list of categories assigned to the product. You can override this behavior and define which category is sent in tracking events. diff --git a/docs/release_notes/ibexa_dxp_v3.2.md b/docs/release_notes/ibexa_dxp_v3.2.md index f9699b36b6d..d517efb0af7 100644 --- a/docs/release_notes/ibexa_dxp_v3.2.md +++ b/docs/release_notes/ibexa_dxp_v3.2.md @@ -110,6 +110,6 @@ to [get object states and object state groups](https://doc.ibexa.co/en/3.2/api/p ## Full changelog -| Ibexa Platform | [[= product_name =]] | [[= product_name_com =]] | +| Ibexa Platform | Ibexa DXP | [[= product_name_com =]] | |--------------|------------|------------| -| [Ibexa Platform v3.2.0](https://github.com/ezsystems/ezplatform/releases/tag/v3.2.0) | [[[= product_name =]] v3.2.0](https://github.com/ezsystems/ezplatform-ee/releases/tag/v3.2.0) | [[[= product_name_com =]] v3.2.0](https://github.com/ezsystems/ezcommerce/releases/tag/v3.2.0) | +| [Ibexa Platform v3.2.0](https://github.com/ezsystems/ezplatform/releases/tag/v3.2.0) | [Ibexa DXP v3.2.0](https://github.com/ezsystems/ezplatform-ee/releases/tag/v3.2.0) | [[[= product_name_com =]] v3.2.0](https://github.com/ezsystems/ezcommerce/releases/tag/v3.2.0) | diff --git a/docs/release_notes/ibexa_dxp_v3.3.md b/docs/release_notes/ibexa_dxp_v3.3.md index e495095174d..45189f5027c 100644 --- a/docs/release_notes/ibexa_dxp_v3.3.md +++ b/docs/release_notes/ibexa_dxp_v3.3.md @@ -20,7 +20,7 @@ This release brings a completely reconstructed user interface of the Personaliza ### Symfony Flex -[[= product_name =]] is now installed using [Symfony Flex]([[= symfony_doc =]]/quick_tour/flex_recipes.html). +Ibexa DXP is now installed using [Symfony Flex]([[= symfony_doc =]]/quick_tour/flex_recipes.html). See [the updated installation instruction](https://doc.ibexa.co/en/3.3/getting_started/install_ez_platform/) for a new guide to installing the product. @@ -89,6 +89,6 @@ See [list of changes in Symfony 5.2](https://symfony.com/blog/symfony-5-2-curate ### Symfony 5.4 -The version v3.3.15 moves [[= product_name =]] to Symfony 5.4. +The version v3.3.15 moves Ibexa DXP to Symfony 5.4. For more information, see [Symfony 5.4 documentation](https://symfony.com/releases/5.4) and [update documentation](update_from_3.3.md#v3315). diff --git a/docs/release_notes/ibexa_dxp_v4.0.md b/docs/release_notes/ibexa_dxp_v4.0.md index aaae03cf62e..d524a669b02 100644 --- a/docs/release_notes/ibexa_dxp_v4.0.md +++ b/docs/release_notes/ibexa_dxp_v4.0.md @@ -109,7 +109,7 @@ Personalization service has been enhanced with a feature which allows to exclude v4.0 sees significant code cleanup, including renaming of namespaces, services, REST API endpoints and many other internal names. -Refer to [[[= product_name =]] v4.0 deprecations and backwards compatibility breaks](ibexa_dxp_v4.0_deprecations.md) +Refer to [Ibexa DXP v4.0 deprecations and backwards compatibility breaks](ibexa_dxp_v4.0_deprecations.md) for full details of changes and how they influence your project. ## Full changelog diff --git a/docs/release_notes/ibexa_dxp_v4.0_deprecations.md b/docs/release_notes/ibexa_dxp_v4.0_deprecations.md index 7feaee9df8e..aaefd0814aa 100644 --- a/docs/release_notes/ibexa_dxp_v4.0_deprecations.md +++ b/docs/release_notes/ibexa_dxp_v4.0_deprecations.md @@ -2,7 +2,7 @@ # Ibexa DXP v4.0 deprecations and backwards compatibility breaks -[[= product_name =]] v4.0 introduces changes to significant parts of the code +Ibexa DXP v4.0 introduces changes to significant parts of the code to align with the product name change from earlier eZ Platform. These changes include changing repository names, namespaces, filenames, function names, and others. diff --git a/docs/release_notes/ibexa_dxp_v4.2.md b/docs/release_notes/ibexa_dxp_v4.2.md index 614a391f773..df5cd8f3e82 100644 --- a/docs/release_notes/ibexa_dxp_v4.2.md +++ b/docs/release_notes/ibexa_dxp_v4.2.md @@ -209,7 +209,7 @@ You can now hide and reveal content items in data migrations by using the [`hide ### Fastly shielding -[[= product_name =]] now supports Fastly shielding. +Ibexa DXP now supports Fastly shielding. ## Deprecations diff --git a/docs/release_notes/ibexa_dxp_v4.4.md b/docs/release_notes/ibexa_dxp_v4.4.md index 5a9f845a2f5..a459605c600 100644 --- a/docs/release_notes/ibexa_dxp_v4.4.md +++ b/docs/release_notes/ibexa_dxp_v4.4.md @@ -50,7 +50,7 @@ You can now use Fastly IO to serve optimized versions of your images in real tim Fastly can perform multiple transformations on your image, for example, cropping, resizing, and trimming before serving it to end user. Fastly is an external service that requires a separate subscription, to learn more see, [Fastly Image Optimizer website](https://www.fastly.com/documentation/guides/full-site-delivery/image-optimization/about-fastly-image-optimizer/). -If you already have Fastly IO subscription, you can move to [Fastly IO configuration in [[= product_name =]]](https://doc.ibexa.co/en/4.4/content_management/images/fastly_io/). +If you already have Fastly IO subscription, you can move to [Fastly IO configuration in Ibexa DXP](https://doc.ibexa.co/en/4.4/content_management/images/fastly_io/). #### Fastly VCL upload @@ -84,7 +84,7 @@ provide the best recommendations. ## [[= product_name_connect =]] You can now take advantage of [[[= product_name_connect =]]](https://www.ibexa.co/products/features/integration-and-automation), -an iPaaS (integration platform-as-a-service) which allows you to connect [[= product_name =]] with third-party applications. +an iPaaS (integration platform-as-a-service) which allows you to connect Ibexa DXP with third-party applications. [[= product_name_connect =]] features a low-code drag-and-drop interface and hundreds of connectors to different services that help you automate business processes. See [[[= product_name_connect =]] documentation]([[= connect_doc =]]/). diff --git a/docs/release_notes/ibexa_dxp_v4.5.md b/docs/release_notes/ibexa_dxp_v4.5.md index 91274541164..98efacf7da5 100644 --- a/docs/release_notes/ibexa_dxp_v4.5.md +++ b/docs/release_notes/ibexa_dxp_v4.5.md @@ -31,7 +31,7 @@ Modules can interact with each other, for example, to decrease stock as a result With order management in place, it's now possible to create orders, configure and customize the order processing workflow, and manage orders by using the APIs. -New screens added to the back office user interface let [[= product_name =]] users search for orders and filter search results. +New screens added to the back office user interface let Ibexa DXP users search for orders and filter search results. Users can also review order details and completion status, and cancel orders. ![The order list screen](img/4.5_order_list.png "The order list screen") @@ -122,7 +122,7 @@ In this release, the CDP configuration becomes more generic and allows supporting other transport types accepted by CDP. Currently, only `stream_file` transport is supported and can be initialized from the configuration. -[[= product_name =]] v4.5 adds the abstraction that allows you to implement other transport types from third parties. +Ibexa DXP v4.5 adds the abstraction that allows you to implement other transport types from third parties. For more information, see [CDP configuration](https://doc.ibexa.co/en/4.5/cdp/cdp_activation/#configuration). diff --git a/docs/release_notes/ibexa_dxp_v4.6.md b/docs/release_notes/ibexa_dxp_v4.6.md index 894d2d768c9..b614571f86a 100644 --- a/docs/release_notes/ibexa_dxp_v4.6.md +++ b/docs/release_notes/ibexa_dxp_v4.6.md @@ -83,7 +83,7 @@ For more information, see [Workflow API](https://doc.ibexa.co/en/5.0/content_man ### Product tour -The product tour is a new Integrated help feature that helps back office contributors to discover [[= product_name =]]. +The product tour is a new Integrated help feature that helps back office contributors to discover Ibexa DXP. With product tours, you can create customized onboarding journeys. This accelerates user adoption, reduces training time, and helps users confidently navigate the platform. @@ -270,7 +270,7 @@ The PHP API has been enhanced with the following classes and interfaces: [[= release_note_entry_begin("Integrated help " + version, '2025-12-10', ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature', 'First release']) =]] -Integrated help, a new [LTS Update](https://doc.ibexa.co/en/4.6/ibexa_products/editions/#lts-updates), brings contextual documentation, guidance, and partner-specific resources right into the user interface of [[= product_name =]]. +Integrated help, a new [LTS Update](https://doc.ibexa.co/en/4.6/ibexa_products/editions/#lts-updates), brings contextual documentation, guidance, and partner-specific resources right into the user interface of Ibexa DXP. It helps editors, store managers, and developers to quickly access relevant content, training and resources without leaving the UI, narrowing the gap between product and documentation. The default help menu can be modified to include links to internal editorial guidelines, custom tutorials, or support pages. @@ -290,7 +290,7 @@ Real-time editing is now part of the [Collaborative editing](https://doc.ibexa.c By using it, users can edit and review content in real time, making teamwork faster, more efficient, and streamlining the content review process. The system automatically tracks changes, allowing seamless collaboration within a single content item. -This extends the already existing capabilities allowing editors to work on the same content created in [[= product_name =]] simultaneously, streamlining the content creation and review process. +This extends the already existing capabilities allowing editors to work on the same content created in Ibexa DXP simultaneously, streamlining the content creation and review process. ![Participants list](img/participants_list.png) @@ -428,7 +428,7 @@ With improved reasoning and greater accuracy in mind, the AI Connector package h #### Discount indexing Discounts now allow scheduling a re-indexing of discounted product catalog prices at the most convenient time by using the Ibexa Messenger package. -Ibexa Messenger is a customization of the Symfony Messenger package, created to adjust it to [[= product_name =]]'s needs. +Ibexa Messenger is a customization of the Symfony Messenger package, created to adjust it to Ibexa DXP's needs. Once properly configured, it uses a background queue to trigger price re-indexing, ensuring efficient use of system resources without causing performance disruptions. @@ -461,7 +461,7 @@ Developers can now create and configure their own notification types, while user ##### New packages -The only package that has been introduced in [[= product_name =]] v4.6.24 is ibexa/messenger. +The only package that has been introduced in Ibexa DXP v4.6.24 is ibexa/messenger. ##### New version of PHP Storm Plugin @@ -576,7 +576,7 @@ It uses the [special characters plugin](https://ckeditor.com/docs/ckeditor5/late #### Support for Solr 9 -With this release, [[= product_name =]] starts supporting [Solr 9](https://doc.ibexa.co/en/4.6/getting_started/requirements/#search). +With this release, Ibexa DXP starts supporting [Solr 9](https://doc.ibexa.co/en/4.6/getting_started/requirements/#search). Solr 9 comes with support for [Dense Vector Search](https://solr.apache.org/guide/solr/latest/query-guide/dense-vector-search.html), paving the way for incoming improvements to the [AI Actions](https://doc.ibexa.co/en/4.6/ai_actions/ai_actions/) feature. @@ -697,7 +697,7 @@ To update to the latest version, see the [update instructions](https://doc.ibexa #### Twig Components -- The new [Twig Components](https://doc.ibexa.co/en/4.6/templating/components/) feature allow you to effortlessly build customizable and reusable Twig templates in [[= product_name =]] +- The new [Twig Components](https://doc.ibexa.co/en/4.6/templating/components/) feature allow you to effortlessly build customizable and reusable Twig templates in Ibexa DXP #### Extending Sub-items view @@ -1454,16 +1454,16 @@ For more information, see [Ibexa DAM](https://doc.ibexa.co/projects/userguide/en ##### Remote PIM support -This release introduces a foundation for connecting [[= product_name =]]'s product catalog capabilities to external Product Information Management (PIM) systems. +This release introduces a foundation for connecting Ibexa DXP's product catalog capabilities to external Product Information Management (PIM) systems. You can use it to implement a custom solution and connect to external PIM or ERP systems, import product data, and present it side-by-side with your organization's existing content, while managing product data in a remote system of your choice. Here are the most important benefits of Remote PIM support: -- Integration with external data sources: your organization can utilize [[= product_name =]]'s features, without having to migrate data to a new environment. -- Increased accessibility of product information: customers and users can access product data through different channels, including [[= product_name =]]. +- Integration with external data sources: your organization can utilize Ibexa DXP's features, without having to migrate data to a new environment. +- Increased accessibility of product information: customers and users can access product data through different channels, including Ibexa DXP. - Centralized product data management: product information can be maintained and edited in one place, which then serves as a single source of truth for different applications. -Among other things, the Remote PIM support feature allows [[= product_name =]] customers to: +Among other things, the Remote PIM support feature allows Ibexa DXP customers to: - let their users purchase products by following a regular or quick order path, - manage certain aspects of product data, @@ -1565,7 +1565,7 @@ For more information, see [Define cancel order](https://doc.ibexa.co/en/5.0/comm ##### Integrate with payment gateways -[[= product_name =]] can now be configured to integrate with various payment gateways, like Stripe and PayPal, by using the solution provided by [Payum](https://github.com/Payum). +Ibexa DXP can now be configured to integrate with various payment gateways, like Stripe and PayPal, by using the solution provided by [Payum](https://github.com/Payum). ##### Shipments @@ -1726,9 +1726,9 @@ For more information, see [[[= product_name_connect =]] scenario block](https:// #### DDEV -[[[= product_name =]] can officially be run on DDEV](https://docs.ddev.com/en/stable/users/quickstart/#ibexa-dxp). +[Ibexa DXP can officially be run on DDEV](https://docs.ddev.com/en/stable/users/quickstart/#ibexa-dxp). -For more information, see the [DDEV guide](https://doc.ibexa.co/en/5.0/getting_started/install_with_ddev/), which offers a step-by-step walkthrough for installing [[= product_name =]]. +For more information, see the [DDEV guide](https://doc.ibexa.co/en/5.0/getting_started/install_with_ddev/), which offers a step-by-step walkthrough for installing Ibexa DXP. #### Customer Data Platform (CDP) @@ -1741,7 +1741,7 @@ For more information, see [CDP Activation](https://doc.ibexa.co/en/5.0/cdp/cdp_a #### New packages -The following packages have been introduced in [[= product_name =]] v4.6.0: +The following packages have been introduced in Ibexa DXP v4.6.0: - [ibexa/oauth2-server](https://doc.ibexa.co/en/4.6/users/oauth_server/) (optional) - ibexa/site-context @@ -1762,7 +1762,7 @@ The following packages have been introduced in [[= product_name =]] v4.6.0: #### REST APIs -[[= product_name =]] v4.6.0 adds REST API coverage for the following features: +Ibexa DXP v4.6.0 adds REST API coverage for the following features: - Price engine - Shipping @@ -1927,7 +1927,7 @@ The following events have been added in the v4.6.0 release (39 events in total): #### View matchers -The following view matchers have been introduced in [[= product_name =]] v4.6.0: +The following view matchers have been introduced in Ibexa DXP v4.6.0: - `\Ibexa\Core\MVC\Symfony\Matcher\ContentBased\IsPreview` - `\Ibexa\Taxonomy\View\Matcher\TaxonomyEntryBased\Id` diff --git a/docs/release_notes/ibexa_dxp_v5.0.md b/docs/release_notes/ibexa_dxp_v5.0.md index a7602fe2e2d..636a1cf358f 100644 --- a/docs/release_notes/ibexa_dxp_v5.0.md +++ b/docs/release_notes/ibexa_dxp_v5.0.md @@ -102,7 +102,7 @@ The following additions were made to the PHP API: ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature', 'First release'] ) =]] -MCP servers make it easier for AI agents to discover the available interactions with [[= product_name =]]. +MCP servers make it easier for AI agents to discover the available interactions with Ibexa DXP. With the MCP Servers feature, you can configure multiple MCP servers with their specific sets of tools. For more information, see [MCP Servers product guide](https://doc.ibexa.co/en/5.0/ai/mcp/mcp_guide/). @@ -151,7 +151,7 @@ For more information, see [connector installation and configuration](https://doc ### Anonymous user segmentation in [[= product_name_cdp =]] [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] [[= product_name_cdp =]] can now build audiences for anonymous visitors. -Use them in [[= product_name =]] to deliver personalized experiences even before users log in. +Use them in Ibexa DXP to deliver personalized experiences even before users log in. For more information, see [Anonymous user segmentation](https://doc.ibexa.co/en/5.0/cdp/cdp_activation/cdp_configuration/#anonymous-user-segmentation). @@ -237,7 +237,7 @@ For more information, see how to [install and configure the Google Gemini connec ### Product tour -The product tour is a new Integrated help feature that helps back office contributors to discover [[= product_name =]]. +The product tour is a new Integrated help feature that helps back office contributors to discover Ibexa DXP. With product tours, you can create customized onboarding journeys. This accelerates user adoption, reduces training time, and helps users confidently navigate the platform. @@ -259,7 +259,7 @@ To learn more, see the [corresponding security advisory](https://developers.ibex ### Raptor connector -The Raptor connector provides a seamless integration between [[= product_name =]] and [Raptor Recommendation Engine](https://www.raptorservices.com/website-recommendations/). +The Raptor connector provides a seamless integration between Ibexa DXP and [Raptor Recommendation Engine](https://www.raptorservices.com/website-recommendations/). For more information, see [Raptor connector](https://doc.ibexa.co/en/5.0/recommendations/raptor_integration/raptor_connector/). @@ -278,14 +278,14 @@ This add-on introduces a set of recommendation blocks available in the [Page Bui For more information about Recommendation blocks in Page Builder, see the relevant [Developer Documentation](https://doc.ibexa.co/en/5.0/recommendations/raptor_integration/recommendation_blocks/) and [User Documentation](https://doc.ibexa.co/projects/userguide/en/5.0/recommendations/raptor_integration/raptor_recommendation_blocks/). -### [[= pim_product_name =]] PIM +### [[= pim_product_name =]] -The [[= pim_product_name =]] integration add-on allows you to connect [[= product_name =]] with [[[= pim_product_name =]] Product Information Management (PIM)](https://www.quable.com/en), making [[= pim_product_name =]] the authoritative source of product information for every website powered by [[= product_name =]]. +The [[= pim_product_name =]] integration add-on allows you to connect Ibexa DXP with [[[= pim_product_name =]]](https://www.quable.com/en), making [[= pim_product_name =]] the authoritative source of product information for every website powered by Ibexa DXP. [[= pim_product_name =]] can serve as the single source of truth for all product data, including attributes, classifications, variants, and translations. -[[= product_name =]] consumes this data and makes it available for use in content and digital experiences. +Ibexa DXP consumes this data and makes it available for use in content and digital experiences. -For more information, see [Quable PIM Integration](https://doc.ibexa.co/en/5.0/product_catalog/quable/quable/). +For more information, see [[[= pim_product_name =]] Integration](https://doc.ibexa.co/en/5.0/product_catalog/quable/quable/). ### AI Actions in Page Builder blocks [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] @@ -297,7 +297,7 @@ You can now use the [refining text AI Actions](https://doc.ibexa.co/en/5.0/ai/ai Symfony is upgraded from 7.3 to 7.4. It's the latest [LTS release](https://symfony.com/releases#long-term-support-release), maintained till November 2029. -See [what's new in Symfony 7.4](https://symfony.com/blog/category/living-on-the-edge/8.0-7.4) and [how to update Symfony within [[= product_name =]]](https://doc.ibexa.co/en/5.0/update_and_migration/from_5.0/update_from_5.0/#update-symfony-from-73-to-74). +See [what's new in Symfony 7.4](https://symfony.com/blog/category/living-on-the-edge/8.0-7.4) and [how to update Symfony within Ibexa DXP](https://doc.ibexa.co/en/5.0/update_and_migration/from_5.0/update_from_5.0/#update-symfony-from-73-to-74). #### Taxonomy search @@ -540,7 +540,7 @@ The [Collaborative editing](https://doc.ibexa.co/en/5.0/content_management/colla [[= release_note_entry_begin("Integrated help " + version, '2025-12-10', ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature', 'First release']) =]] -Integrated help brings contextual documentation, guidance, and partner-specific resources right into the user interface of [[= product_name =]]. +Integrated help brings contextual documentation, guidance, and partner-specific resources right into the user interface of Ibexa DXP. It helps editors, store managers, and developers to quickly access relevant content, training and resources without leaving the UI, narrowing the gap between product and documentation. The default help menu can be modified to include links to internal editorial guidelines, custom tutorials, or support pages. @@ -573,7 +573,7 @@ Real-time editing is now part of the [Collaborative editing](https://doc.ibexa.c By using it, users can edit and review content in real time, making teamwork faster, more efficient, and streamlining the content review process. The system automatically tracks changes, allowing seamless collaboration within a single content item. -This extends the already existing capabilities allowing editors to work on the same content created in [[= product_name =]] simultaneously, streamlining the content creation and review process. +This extends the already existing capabilities allowing editors to work on the same content created in Ibexa DXP simultaneously, streamlining the content creation and review process. ![Participants list](img/participants_list.png) @@ -727,7 +727,7 @@ Additionally, shared drafts can be accessed and managed through new dashboard ta ### Discount indexing Discounts now allow scheduling a re-indexing of discounted product catalog prices at the most convenient time by using the Ibexa Messenger package. -Ibexa Messenger is a customization of the Symfony Messenger package, created to adjust it to [[= product_name =]]'s needs. +Ibexa Messenger is a customization of the Symfony Messenger package, created to adjust it to Ibexa DXP's needs. Once properly configured, it uses a background queue to trigger price re-indexing, ensuring efficient use of system resources without causing performance disruptions. @@ -858,7 +858,7 @@ It uses the [special characters plugin](https://ckeditor.com/docs/ckeditor5/late ### Support for Solr 9 -With this release, [[= product_name =]] starts supporting [Solr 9](https://doc.ibexa.co/en/5.0/getting_started/requirements/#search). +With this release, Ibexa DXP starts supporting [Solr 9](https://doc.ibexa.co/en/5.0/getting_started/requirements/#search). Solr 9 comes with support for [Dense Vector Search](https://solr.apache.org/guide/solr/latest/query-guide/dense-vector-search.html), paving the way for incoming improvements to the [AI Actions](https://doc.ibexa.co/en/5.0/ai/ai_actions/ai_actions/) feature. @@ -904,7 +904,7 @@ This version incorporates into the product numerous features brought by LTS Upda #### AI Actions -The AI Actions feature enhances the usability and flexibility of [[= product_name =]] by harnessing the potential of artificial intelligence to automate time-consuming editorial tasks. +The AI Actions feature enhances the usability and flexibility of Ibexa DXP by harnessing the potential of artificial intelligence to automate time-consuming editorial tasks. By default, the AI Actions feature can help users with their work in following scenarios: - Refining text: when editing a content item, users can request that a passage selected in online editor is modified, for example, by adjusting the length of the text, changing its tone, or correcting linguistic errors @@ -957,17 +957,17 @@ For a full list of updated system requirements, see [Requirements](https://doc.i #### Symfony 7.3 -With this release, [[= product_name =]] moves to Symfony 7.3 from the previously used versions of Symfony. +With this release, Ibexa DXP moves to Symfony 7.3 from the previously used versions of Symfony. For details, see [Symfony 7.3](https://symfony.com/blog/symfony-7-3-curated-new-features). #### Doctrine DBAL 3.9 -By moving to Doctrine DBAL 3.9, [[= product_name =]] brings developers better performance, cleaner code, and stronger foundation for a more modern and maintainable application. +By moving to Doctrine DBAL 3.9, Ibexa DXP brings developers better performance, cleaner code, and stronger foundation for a more modern and maintainable application. #### PHP 8.3 -With performance, coding safety and security in mind, with this version, [[= product_name =]] moves to [PHP 8.3](https://www.php.net/releases/8.3/en.php) and drops support for lower versions of the language. +With performance, coding safety and security in mind, with this version, Ibexa DXP moves to [PHP 8.3](https://www.php.net/releases/8.3/en.php) and drops support for lower versions of the language. #### OpenAPI support @@ -979,14 +979,14 @@ Support for serialization and deserialization of REST payloads with the [Symfony #### React 19 -[[= product_name =]]'s Back Office now uses [React 19](https://react.dev/blog/2024/12/05/react-19). +Ibexa DXP's Back Office now uses [React 19](https://react.dev/blog/2024/12/05/react-19). This upgrade enhances maintainability, unlocks new UI capabilities, and simplifies future feature development. ### Developer experience #### New packages -The following packages have been introduced in [[= product_name =]] v5.0.0: +The following packages have been introduced in Ibexa DXP v5.0.0: - ibexa/collaboration - ibexa/connector-ai @@ -999,7 +999,7 @@ The following packages have been introduced in [[= product_name =]] v5.0.0: #### REST APIs -[[= product_name =]] v5.0.0 adds REST API coverage for the following features: +Ibexa DXP v5.0.0 adds REST API coverage for the following features: - AI Actions: - Action Configurations @@ -1225,7 +1225,7 @@ The following Twig functions have been added in the v5.0 release: This release brings other minor upgrades intended to improve the developer's experience: - To improve code clarity, reliability, and error detection, type hint declarations that specify the expected data type have been added in multiple places throughout the product -- In anticipation of [changes coming with PHP 8.4](https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated), implicit nullable type declarations have been replaced with nullable type declarations throughout the product code. It is recommended that you update your custom code in the same way +- In anticipation of [changes coming with PHP 8.4](https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated), implicit nullable type declarations have been replaced with nullable type declarations throughout the product code. It's recommended that you update your custom code in the same way - Developer experience has improved with capabilities offered by PHP in version 8.3. For example, the `AsTwigComponent` attribute [facilitates autoconfiguration](https://doc.ibexa.co/en/5.0/templating/components/#php-code) of Twig components - With protection against breaking changes and easier refactoring in mind, [TypeScript](https://www.typescriptlang.org/) can now be used to extend the Back Office - [[[= product_name_base =]] Rector package](https://github.com/ibexa/rector) has been introduced that is based on [Rector](https://github.com/rectorphp) and comes with additional rules for working with Ibexa code. You can use it to get rid of PHP code deprecations diff --git a/docs/release_notes/ibexa_dxp_v5.0_deprecations.md b/docs/release_notes/ibexa_dxp_v5.0_deprecations.md index bbee6902841..6180edd97e0 100644 --- a/docs/release_notes/ibexa_dxp_v5.0_deprecations.md +++ b/docs/release_notes/ibexa_dxp_v5.0_deprecations.md @@ -2,20 +2,20 @@ # Ibexa DXP v5.0 renames, deprecations and removals -This page lists backwards compatibility breaks and deprecations introduced in [[= product_name =]] v5.0. +This page lists backwards compatibility breaks and deprecations introduced in Ibexa DXP v5.0. !!! tip "Upgrade to v5" For a guide on moving your project to v5.0, see [Update and migration instructions](../update_and_migration/from_4.6/update_to_5.0.md). -[[= product_name =]] v5.0 introduces further modifications to significant parts of the code to align with the ones introduced in previous versions. +Ibexa DXP v5.0 introduces further modifications to significant parts of the code to align with the ones introduced in previous versions. These changes include dropped packages, changing database table and column names, field identifiers, namespaces, function names, and others. ## Dropped packages -[[= product_name =]] v5.0 no longer includes legacy Commerce packages. +Ibexa DXP v5.0 no longer includes legacy Commerce packages. The solution has been replaced with [Commerce](commerce.md) that is included as standard and has been continuously developed since v4.4. Also, packages `compatibility-layer` and `icons` have been dropped. diff --git a/docs/release_notes/release_notes.md b/docs/release_notes/release_notes.md index c27d5359f00..c8991814274 100644 --- a/docs/release_notes/release_notes.md +++ b/docs/release_notes/release_notes.md @@ -1,11 +1,11 @@ --- -description: Learn about the latest releases on Ibexa DXP. +description: Learn about the latest releases of Cohesivo. page_type: landing_page --- # Release notes -The latest stable and LTS (Long Term Support) version of [[= product_name =]] is [[[= product_name =]] v5.0](ibexa_dxp_v5.0.md). +The latest stable and LTS (Long Term Support) version of [[= product_name =]] is [Ibexa DXP v5.0](ibexa_dxp_v5.0.md). [[= cards([ "release_notes/ibexa_dxp_v5.0", diff --git a/docs/resources/contributing/contribute_translations.md b/docs/resources/contributing/contribute_translations.md index 656474ace78..5102ec50b45 100644 --- a/docs/resources/contributing/contribute_translations.md +++ b/docs/resources/contributing/contribute_translations.md @@ -1,5 +1,5 @@ --- -description: You can contribute back office translations to Ibexa DXP by using Crowdin. +description: You can contribute back office translations to Cohesivo by using Crowdin. month_change: false --- diff --git a/docs/resources/contributing/package_structure.md b/docs/resources/contributing/package_structure.md index 392610ed4bd..75ef6dc899c 100644 --- a/docs/resources/contributing/package_structure.md +++ b/docs/resources/contributing/package_structure.md @@ -1,12 +1,12 @@ --- -description: All code contributions to Ibexa DXP must follow package and bundle structure and namespace standards. +description: All code contributions to Cohesivo must follow package and bundle structure and namespace standards. --- # Package and bundle structure and namespaces If you wish to contribute to [[= product_name =]] development, you need to adhere to the package and bundle structure and namespace standards. -The following conventions apply to contributions to [[= product_name_base =]] core code, not to third party packages. +The following conventions apply to contributions to [[= product_name =]] core code, not to third party packages. !!! note @@ -21,7 +21,7 @@ Define [[= product_name =]] core PHP code in a namespace with the following pref namespace Ibexa; ``` -A package which groups some DXP features can use an additional prefix, for example: +A package which groups some [[= product_name =]] features can use an additional prefix, for example: ``` php {skip-validation} namespace Ibexa\Commerce; diff --git a/docs/resources/contributing/report_and_follow_issues.md b/docs/resources/contributing/report_and_follow_issues.md index f576aa04442..0bcdd0005dc 100644 --- a/docs/resources/contributing/report_and_follow_issues.md +++ b/docs/resources/contributing/report_and_follow_issues.md @@ -4,7 +4,7 @@ description: You can report encountered issues to Service Portal # Report and follow issues -If you have an [[= product_name =]] subscription, report your issues through the [Service portal](https://support.ibexa.co). +If you have a [[= product_name =]] subscription, report your issues through the [Service portal](https://support.ibexa.co). To do it, log in to your Service portal at , click "New Ticket", and report the issue as you would report a normal support request. [[= product_name_base =]] Product Support will respond, take care of the report, and keep you informed of the developments. This ensures the issue can be quickly prioritized according to its impact. diff --git a/docs/resources/new_in_doc.md b/docs/resources/new_in_doc.md index a59e50cf9ed..b60394b0869 100644 --- a/docs/resources/new_in_doc.md +++ b/docs/resources/new_in_doc.md @@ -1,11 +1,11 @@ --- -description: Overview of major recent additions to Ibexa DXP documentation. +description: Overview of major recent additions to Ibexa DXP and Cohesivo documentation. month_change: true --- # New in documentation -This page contains recent highlights and notable changes in [[= product_name =]] documentation. +This page contains recent highlights and notable changes in Ibexa DXP and [[= product_name =]] documentation. ## June 2026 @@ -21,7 +21,7 @@ This page contains recent highlights and notable changes in [[= product_name =]] ### Background tasks and scheduled tasks -- Reworked documentation about [scheduled tasks](install_ibexa_dxp.md#schedule-tasks) +- Reworked documentation about [scheduled tasks](install_cohesivo.md#schedule-tasks) - Described [Ibexa Messenger configuration for production](background_tasks.md#configure-for-production-environment) ## May 2026 @@ -111,9 +111,9 @@ This page contains recent highlights and notable changes in [[= product_name =]] ### CDP -- Illustrated how to [export additional user data](cdp_data_customization.md#export-additional-user-data) -- Detailed [Ibexa Messenger support for large batches of data](cdp_data_export.md#ibexa-messenger-support-for-large-batches-of-data) -- Introduced the [CDP Monolog channel](cdp_data_export.md#cdp-monolog-channel) +- Illustrated how to [export additional user data](raptor_cdp_data_customization.md#export-additional-user-data) +- Detailed [Ibexa Messenger support for large batches of data](raptor_cdp_data_export.md#ibexa-messenger-support-for-large-batches-of-data) +- Introduced the [CDP Monolog channel](raptor_cdp_data_export.md#cdp-monolog-channel) - Added [`Ibexa\Contracts\Cdp` PHP API reference](/api/php_api/php_api_reference/namespaces/ibexa-contracts-cdp.html) ### Infrastructure @@ -140,7 +140,7 @@ This promotes skipping the rebuild of the Symfony container when environment var ### Getting started -- Added a description of password constraints in [Install Ibexa DXP](install_ibexa_dxp.md#create-a-database) and [Install with DDEV](install_with_ddev.md#6-install-the-platform-and-its-database) +- Added a description of password constraints in [Install Ibexa DXP](install_cohesivo.md#create-a-database) and [Install with DDEV](install_with_ddev.md#6-install-the-platform-and-its-database) ### Administration @@ -148,7 +148,7 @@ This promotes skipping the rebuild of the Symfony container when environment var ### Discounts -- Added Ibexa Messenger instructions for [[= product_name =]] 4.6 +- Added Ibexa Messenger instructions for Ibexa DXP 4.6 - Modified [discounts configuration](https://doc.ibexa.co/en/4.6/discounts/configure_discounts/#discount-re-indexing) - Added [installation instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#installation) @@ -183,7 +183,7 @@ This promotes skipping the rebuild of the Symfony container when environment var ### Infrastructure -- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/) for [[= product_name =]] 4.6 and 5.0: PostgreSQL 18 is now officially supported +- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/) for Ibexa DXP 4.6 and 5.0: PostgreSQL 18 is now officially supported ### Ibexa Cloud @@ -232,7 +232,7 @@ This promotes skipping the rebuild of the Symfony container when environment var ### PHP API -- Enhanced the PHP API reference with the following new classes for [[= product_name =]] 4.6 and 5.0: +- Enhanced the PHP API reference with the following new classes for Ibexa DXP 4.6 and 5.0: - [`Ibexa\Contracts\Elasticsearch\Query\EmbeddingVisitor`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Elasticsearch-Query-EmbeddingVisitor.html) - [`Ibexa\Contracts\AdminUi\ContentType\ContentTypeFieldsByExpressionServiceInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-ContentType-ContentTypeFieldsByExpressionServiceInterface.html) @@ -304,7 +304,7 @@ We want to thank ### Trainings -- The [Advanced Developer training](https://learn.ibexa.co) for [[= product_name =]] v5 is now available +- The [Advanced Developer training](https://learn.ibexa.co) for Ibexa DXP v5 is now available ### Documentation improvements @@ -342,7 +342,7 @@ We want to thank ### Collaborative editing - Added the [Collaborative editing product guide](collaborative_editing_guide.md), describing the high-level overview of this feature -- Described collaborative editing endpoints to the [REST API reference](https://doc.ibexa.co/en/4.6/api/rest_api/rest_api_reference/rest_api_reference.html#collaborative-editing) for [[= product_name =]] v4.6 +- Described collaborative editing endpoints to the [REST API reference](https://doc.ibexa.co/en/4.6/api/rest_api/rest_api_reference/rest_api_reference.html#collaborative-editing) for Ibexa DXP v4.6 ### Infrastructure @@ -350,7 +350,7 @@ We want to thank ### PHP API -- Enhanced the PHP API reference with the following new classes for [[= product_name =]] 4.6 and 5.0: +- Enhanced the PHP API reference with the following new classes for Ibexa DXP 4.6 and 5.0: - [`Ibexa\Contracts\AdminUi\Event\ResolveVersionPreviewUrlEvent`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-Event-ResolveVersionPreviewUrlEvent.html) - [`Ibexa\Contracts\AdminUi\Exception\UnresolvedPreviewUrlException`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-Exception-UnresolvedPreviewUrlException.html) - [`Ibexa\Contracts\AdminUi\PreviewUrlResolver\VersionPreviewUrlResolverInterface`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-AdminUi-PreviewUrlResolver-VersionPreviewUrlResolverInterface.html) @@ -490,7 +490,7 @@ Discounts documentation includes: ### Twig Components -- Documented new [Twig Components](https://doc.ibexa.co/en/4.6/templating/components/) feature that allows you to effortlessly build customizable and reusable Twig templates in [[= product_name =]] +- Documented new [Twig Components](https://doc.ibexa.co/en/4.6/templating/components/) feature that allows you to effortlessly build customizable and reusable Twig templates in Ibexa DXP ### Extending Sub-items view @@ -509,7 +509,7 @@ Discounts documentation includes: ### Requirements update -- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/) for [[= product_name =]] 4.6: MySQL 8.4, Node 20 and Node 22 are now officially supported +- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/) for Ibexa DXP 4.6: MySQL 8.4, Node 20 and Node 22 are now officially supported ### AI Actions Connect handler @@ -546,11 +546,11 @@ We want to thank [todomagichere](https://github.com/todomagichere) and [hgieseno ### Requirements update -- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/#operating-system) for [[= product_name =]]: RHEL 9.5 and CentOS Stream 9 are now supported for v4.6 +- Updated [requirements](https://doc.ibexa.co/en/4.6/getting_started/requirements/#operating-system) for Ibexa DXP: RHEL 9.5 and CentOS Stream 9 are now supported for v4.6 ### AI Actions -- Specified minimum [[= product_name =]] version supported while working with AI Actions +- Specified minimum Ibexa DXP version supported while working with AI Actions - AI Actions product guide: [Availability](https://doc.ibexa.co/en/4.6/ai_actions/ai_actions_guide/#availability) - AI Actions section: [Install AI Actions](https://doc.ibexa.co/en/4.6/ai_actions/install_ai_actions/) @@ -792,7 +792,7 @@ Enhanced the PHP API with the following new classes and interfaces: - Updated configuration details (including endpoint addresses and code examples) in multiple how-to articles -### PIM +### Product catalog - Updated the [Product API](https://doc.ibexa.co/en/4.6/pim/product_api/) article by fixing method signatures and adding links to the PHP API reference @@ -851,7 +851,7 @@ Enhanced the PHP API with the following new classes and interfaces: ### Getting started -- Added instructions in [Install [[= product_name =]]](https://doc.ibexa.co/en/4.6/getting_started/install_ibexa_dxp/#create-project) about using PHP 8.3 to create a project +- Added instructions in [Install Ibexa DXP](https://doc.ibexa.co/en/4.6/getting_started/install_ibexa_dxp/#create-project) about using PHP 8.3 to create a project - Updated the [requirements for running v3.3.x on PHP 8.3](https://doc.ibexa.co/en/4.6/getting_started/requirements/#php) ### Infrastructure and maintenance @@ -980,7 +980,7 @@ Enhanced the PHP API with the following new classes and interfaces: - [Ibexa DAM](https://doc.ibexa.co/projects/userguide/en/4.6/dam/ibexa_dam/) -### PIM +### Product catalog - [Price engine REST API](https://doc.ibexa.co/en/4.6/api/rest_api/rest_api_reference/rest_api_reference.html#product-catalog-load-the-list-of-product-prices) @@ -1028,7 +1028,7 @@ Enhanced the PHP API with the following new classes and interfaces: - Customize recommendation request with segment parameters -### PIM +### Product catalog - Product search Aggregations: - [BasePriceStatsAggregation](https://doc.ibexa.co/en/4.6/search/aggregation_reference/basepricestats_aggregation/) @@ -1042,7 +1042,7 @@ Enhanced the PHP API with the following new classes and interfaces: - [Checkbox page block attribute type](https://doc.ibexa.co/en/4.6/content_management/pages/page_block_attributes/#block-attribute-types) - [Updated Create Form Builder Form attribute procedure](https://doc.ibexa.co/en/4.6/content_management/forms/create_form_attribute/#create-form-builder-form-attribute) -### PIM +### Product catalog - [Reorganized and updated information in User Documentation](https://doc.ibexa.co/projects/userguide/en/4.6/pim/pim/) @@ -1094,7 +1094,7 @@ Enhanced the PHP API with the following new classes and interfaces: - Post visit and price drop triggers - Wishlist and Deletefromwishlist events -### PIM +### Product catalog - [VAT category configuration update](https://doc.ibexa.co/en/4.6/pim/pim_configuration/#vat-rates) - [Payment Method Name Criterion](https://doc.ibexa.co/en/4.6/search/criteria_reference/payment_method_name_criterion/) @@ -1127,7 +1127,7 @@ Enhanced the PHP API with the following new classes and interfaces: - Send messages with recommendations - Email triggers in User Documentation -### PIM +### Product catalog - [Product availability Twig extension](https://doc.ibexa.co/en/4.6/templating/twig_function_reference/product_twig_functions/#ibexa_has_product_availability) - [PriceQuery with its criteria](https://doc.ibexa.co/en/4.6/search/criteria_reference/price_search_criteria/) @@ -1153,7 +1153,7 @@ Enhanced the PHP API with the following new classes and interfaces: - [Form Builder](https://doc.ibexa.co/en/4.6/content_management/forms/form_builder_guide/) - [Online editor](https://doc.ibexa.co/en/4.6/content_management/rich_text/online_editor_guide/) - Personalization - - [PIM](https://doc.ibexa.co/en/4.6/pim/pim_guide/) + - [Product catalog](https://doc.ibexa.co/en/4.6/pim/pim_guide/) - [Updated bundles list](https://doc.ibexa.co/en/4.6/administration/project_organization/bundles/) @@ -1165,7 +1165,7 @@ Enhanced the PHP API with the following new classes and interfaces: ### Administration -- [Install [[= product_name =]] with DDEV](https://doc.ibexa.co/en/4.6/getting_started/install_with_ddev/) +- [Install Ibexa DXP with DDEV](https://doc.ibexa.co/en/4.6/getting_started/install_with_ddev/) - [Update from v3.3.x to v3.3.latest](https://doc.ibexa.co/en/4.6/update_and_migration/from_3.3/update_from_3.3/) ### Commerce @@ -1186,7 +1186,7 @@ Enhanced the PHP API with the following new classes and interfaces: - [Add CKEditor plugins](https://doc.ibexa.co/en/4.6/content_management/rich_text/extend_online_editor/#add-ckeditor-plugins) -### PIM +### Product catalog - [Custom name schema strategy](https://doc.ibexa.co/en/4.6/pim/create_custom_name_schema_strategy/) - [IsVirtual Search Criterion](https://doc.ibexa.co/en/4.6/search/criteria_reference/isvirtual_criterion/) @@ -1224,7 +1224,7 @@ Enhanced the PHP API with the following new classes and interfaces: - Multiple attributes in submodel computation - Multiple attributes in submodel computation in User Documentation -### PIM +### Product catalog - Updated [Enable purchasing products](https://doc.ibexa.co/en/4.6/pim/enable_purchasing_products/#region-and-currency) - [Virtual products](https://doc.ibexa.co/en/4.6/pim/products/#product-types) diff --git a/docs/resources/phpstorm_plugin.md b/docs/resources/phpstorm_plugin.md index 527f412b3d3..78e0bc10eaa 100644 --- a/docs/resources/phpstorm_plugin.md +++ b/docs/resources/phpstorm_plugin.md @@ -2,9 +2,9 @@ description: The Ibexa DXP PhpStorm plugin helps you speed up your development by providing file templates, autocompletion, a quick installation wizard, and more. --- -# Ibexa DXP plugin for PhpStorm +# Ibexa plugin for PhpStorm -[[= product_name =]] plugin for PhpStorm helps you to work with [[= product_name =]] by speeding up installation and providing file templates, intentions, autocompletion, and other features. +Ibexa plugin for PhpStorm helps you to work with [[= product_name =]] by speeding up installation and providing file templates, intentions, autocompletion, and other features. ## Requirements @@ -13,13 +13,13 @@ description: The Ibexa DXP PhpStorm plugin helps you speed up your development b ## Install PhpStorm plugin -You can install the [[= product_name =]] plugin for PhpStorm from the JetBrains Marketplace, or manually, from a downloaded .jar file. +You can install the Ibexa plugin for PhpStorm from the JetBrains Marketplace, or manually, from a downloaded .jar file. ### Install from JetBrains Marketplace To install plugin from JetBrains marketplace: -Look for "[[= product_name =]]" in the plugin browser and click **Install**. +Look for "Ibexa DXP" in the plugin browser and click **Install**. ### Install from file @@ -31,7 +31,7 @@ You can also install the plugin manually from a `.jar` file: ## Configuration -Plugin configuration is available in PhpStorm settings/preferences (depending on your system), under **PHP** > **Frameworks** > **[[= product_name =]]**. +Plugin configuration is available in PhpStorm settings/preferences (depending on your system), under **PHP** > **Frameworks** > **Ibexa DXP**. You can use it to: @@ -46,16 +46,16 @@ You can use it to: For example, "deprecated namespaces usage" inspection is enabled only if the project uses v4.x. Plugin configuration is automatically resolved when opening [[= product_name =]] project for the first time. -If detection is successful, a notification appears with an "Enable [[= product_name =]] support for this project" link. +If detection is successful, a notification appears with an "Enable Ibexa DXP support for this project" link. -If you created your project by using [[= product_name =]] project wizard, the plugin is automatically enabled and configured based on wizard data. +If you created your project by using Ibexa DXP project wizard, the plugin is automatically enabled and configured based on wizard data. ## Features ### Project wizard The plugin enables creating a new [[= product_name =]] project directly from PhpStorm. -To do it, select **File** > **New Project...** > **[[= product_name =]]**. +To do it, select **File** > **New Project...** > **Ibexa DXP**. In project settings form you can choose: @@ -99,7 +99,7 @@ The plugin provides the following built-in file templates: | Value object visitor | REST value visitor class based on `Ibexa\Contracts\Rest\Output\ValueObjectVisitor` | | Workflow action listener | Workflow action listener class based on `Ibexa\Contracts\Workflow\Event\Action\AbstractTransitionWorkflowActionListener` | -The templates are available in, for example, the context menu in **Project window** > **New** > **[[= product_name =]]**. +The templates are available in, for example, the context menu in **Project window** > **New** > **Ibexa DXP**. The list of available file templates depends on the [[= product_name =]] edition used by the project. diff --git a/docs/resources/release_process_and_roadmap.md b/docs/resources/release_process_and_roadmap.md index 0357090395e..3696fc34c04 100644 --- a/docs/resources/release_process_and_roadmap.md +++ b/docs/resources/release_process_and_roadmap.md @@ -1,5 +1,5 @@ --- -description: "Ibexa DXP releases new versions periodically in different flavors: Ibexa Headless, Ibexa Experience and Ibexa Commerce, plus open-source Ibexa OSS." +description: Cohesivo releases new versions periodically in different flavors - Headless, Experience and Commerce, plus open-source OSS. --- # [[= product_name =]] release process and roadmap @@ -12,7 +12,7 @@ description: "Ibexa DXP releases new versions periodically in different flavors: - [[= product_name_headless =]] is a multichannel and headless content management system. - [[= product_name_exp =]] is a modern modular Digital Experience Platform to build outstanding customer experiences -- [[= product_name_com =]] is a commerce-ready B2B DXP designed to digitalize your business from customer awareness to purchase and beyond. +- [[= product_name_com =]] is a commerce-ready B2B platform designed to digitalize your business from customer awareness to purchase and beyond. Additionally, [[= product_name =]] also has an open-source version called [[= product_name_oss =]]. [[= product_name_oss =]] is developed by [[= product_name_base =]] together with the open source community. diff --git a/docs/resources/resources.md b/docs/resources/resources.md index c93d0b86dee..720d17daf16 100644 --- a/docs/resources/resources.md +++ b/docs/resources/resources.md @@ -1,5 +1,5 @@ --- -description: See additional information about Ibexa DXP development process, helpful tools, and learn how you can contribute to the creation of the platform. +description: See additional information about Cohesivo development process, helpful tools, and learn how you can contribute to the creation of the platform. page_type: landing_page --- diff --git a/docs/search/criteria_reference/product_search_criteria.md b/docs/search/criteria_reference/product_search_criteria.md index 79b9f21cac4..e1bff9f7cd2 100644 --- a/docs/search/criteria_reference/product_search_criteria.md +++ b/docs/search/criteria_reference/product_search_criteria.md @@ -16,9 +16,9 @@ Search Criterion let you filter product by specific attributes, for example, col ## Product Search Criteria -To query for products coming from [[= pim_product_name =]] PIM, see [[[= pim_product_name =]] Search API](/product_catalog/quable/quable_api.md#search-for-products) for details about the integration. +To query for products coming from [[= pim_product_name =]], see [[[= pim_product_name =]] Search API](/product_catalog/quable/quable_api.md#search-for-products) for details about the integration. -|Search Criterion|Search based on|Local product catalog|[[= pim_product_name =]] PIM| +|Search Criterion|Search based on|Local product catalog|[[= pim_product_name =]]| |-----|-----|-----|-----| |[AttributeGroupIdentifier](attributegroupidentifier_criterion.md)|Value of product's attribute group identifier| ✔| | |[AttributeName](attributename_criterion.md)|Value of product's attribute name| ✔| | diff --git a/docs/search/search.md b/docs/search/search.md index c1aa69d006a..1b4d7bf5f9b 100644 --- a/docs/search/search.md +++ b/docs/search/search.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP search functionalities allow working with three search engines and using search API to run complex and precise queries about content and products. +description: Cohesivo search functionalities allow working with three search engines and using search API to run complex and precise queries about content and products. page_type: landing_page --- diff --git a/docs/search/search_engines/elasticsearch/configure_elasticsearch.md b/docs/search/search_engines/elasticsearch/configure_elasticsearch.md index 79b64326288..04626e1b145 100644 --- a/docs/search/search_engines/elasticsearch/configure_elasticsearch.md +++ b/docs/search/search_engines/elasticsearch/configure_elasticsearch.md @@ -1,6 +1,6 @@ --- month_change: false -description: Configure Elasticsearch to use it with Ibexa DXP. +description: Configure Elasticsearch to use it with Cohesivo. --- # Configure Elasticsearch @@ -365,7 +365,7 @@ Index names use the following pattern: `___` - By default, repository name is set to `default`, however, in the context of an [[= product_name =]] instance, there can be [several repositories with different names](repository_configuration.md#defining-custom-connection). + By default, repository name is set to `default`, however, in the context of a [[= product_name =]] instance, there can be [several repositories with different names](repository_configuration.md#defining-custom-connection). Document type can be either `content` or `location`. In a language code, hyphens are replaced with underscores, and all characters must be lowercase. An index name can therefore look like this: diff --git a/docs/search/search_engines/elasticsearch/install_elasticsearch.md b/docs/search/search_engines/elasticsearch/install_elasticsearch.md index 69a3cf5f48f..9c56aba55a9 100644 --- a/docs/search/search_engines/elasticsearch/install_elasticsearch.md +++ b/docs/search/search_engines/elasticsearch/install_elasticsearch.md @@ -1,6 +1,6 @@ --- month_change: false -description: Install Elasticsearch to use it with Ibexa DXP. +description: Install Elasticsearch to use it with Cohesivo. --- # Install Elasticsearch diff --git a/docs/search/search_engines/legacy_search_engine/configure_repository.md b/docs/search/search_engines/legacy_search_engine/configure_repository.md index b2c9cef2f07..34dfc8ea2bc 100644 --- a/docs/search/search_engines/legacy_search_engine/configure_repository.md +++ b/docs/search/search_engines/legacy_search_engine/configure_repository.md @@ -1,5 +1,5 @@ --- -description: Configure Legacy search engine to use it with Ibexa DXP. +description: Configure Legacy search engine to use it with Cohesivo. --- # Configure repository with Legacy search engine diff --git a/docs/search/search_engines/search_engines.md b/docs/search/search_engines/search_engines.md index d1fdfdac827..f8013fae474 100644 --- a/docs/search/search_engines/search_engines.md +++ b/docs/search/search_engines/search_engines.md @@ -1,5 +1,5 @@ --- -description: Learn about different search engines that are supported by Ibexa DXP. +description: Learn about different search engines that are supported by Cohesivo. --- # Search engines diff --git a/docs/search/search_engines/solr_search_engine/configure_solr.md b/docs/search/search_engines/solr_search_engine/configure_solr.md index f8e835577ee..c0c15955e9d 100644 --- a/docs/search/search_engines/solr_search_engine/configure_solr.md +++ b/docs/search/search_engines/solr_search_engine/configure_solr.md @@ -1,5 +1,5 @@ --- -description: Configure Solr search engine to use it with Ibexa DXP. +description: Configure Solr search engine to use it with Cohesivo. --- # Configure Solr @@ -226,7 +226,7 @@ Connect to the Solr slave interface (http://localhost:8983/solr), go to your cor ## Configure HTTP Client for Solr queries -[[= product_name_base =]] Solr Bundle uses Symfony HTTP Client to fetch and update Solr index. +[[= product_name =]] Solr Bundle uses Symfony HTTP Client to fetch and update Solr index. You can configure timeout and maximum number of retries for that client using Solr Bundle's Semantic configuration: ```yaml diff --git a/docs/search/search_engines/solr_search_engine/install_solr.md b/docs/search/search_engines/solr_search_engine/install_solr.md index 46f9b0e4bf4..1c31adcfdfb 100644 --- a/docs/search/search_engines/solr_search_engine/install_solr.md +++ b/docs/search/search_engines/solr_search_engine/install_solr.md @@ -1,5 +1,5 @@ --- -description: Install Solr search engine to use it with Ibexa DXP. +description: Install Solr search engine to use it with Cohesivo. --- # Install Solr search engine @@ -22,7 +22,7 @@ Download and extract Solr: - [solr-9.8.1.tgz](https://archive.apache.org/dist/solr/solr/9.8.1/solr-9.8.1.tgz) Copy the necessary configuration files. -The examples below copy from the root of your DXP project to the place you've extracted Solr: +The examples below copy from the root of your [[= product_name =]] project to the place you've extracted Solr: === "Solr 9" diff --git a/docs/search/sort_clause_reference/product_sort_clauses.md b/docs/search/sort_clause_reference/product_sort_clauses.md index 5b567401f8f..e4d146f0bc8 100644 --- a/docs/search/sort_clause_reference/product_sort_clauses.md +++ b/docs/search/sort_clause_reference/product_sort_clauses.md @@ -9,9 +9,9 @@ Product Sort Clauses are only supported by [Product Search (`ProductServiceInter By using Sort Clause you can filter product by specific attributes, for example: price, code, or availability. -To sort products coming from [[= pim_product_name =]] PIM, see [[[= pim_product_name =]] Search API](../../product_catalog/quable/quable_api.md#search-for-products) for details about the add-on. +To sort products coming from [[= pim_product_name =]], see [[[= pim_product_name =]] Search API](../../product_catalog/quable/quable_api.md#search-for-products) for details about the add-on. -| Sort Clause | Sorting based on | Local product catalog | [[= pim_product_name =]] PIM | +| Sort Clause | Sorting based on | Local product catalog | [[= pim_product_name =]] | |-----|-----|-----|-----| |[BasePrice](baseprice_sort_clause.md)|Base product price| ✔| | |[CreatedAt](createdat_sort_clause.md)|Date and time of the creation of a product| ✔| ✔| diff --git a/docs/snippets/elasticsearch_clear_index.md b/docs/snippets/elasticsearch_clear_index.md index 87f029b50d8..804b0eecead 100644 --- a/docs/snippets/elasticsearch_clear_index.md +++ b/docs/snippets/elasticsearch_clear_index.md @@ -13,7 +13,7 @@ yellow open default_location_eng_gb_46 fSGtpljwTpGfascFechmww 1 1 1 0 21kb (...) ``` -Create a list containing all indices used by the DXP, including the [custom indices](/search/search_engines/elasticsearch/configure_elasticsearch.md#define-field-type-mapping-templates) as well. +Create a list containing all indices used by [[= product_name =]], including the [custom indices](/search/search_engines/elasticsearch/configure_elasticsearch.md#define-field-type-mapping-templates) as well. Then, delete them by using the [delete index endpoint](https://www.elastic.co/guide/en/elasticsearch/reference/8.19/indices-delete-index.html) diff --git a/docs/templating/templates/templates.md b/docs/templating/templates/templates.md index 820453b77fb..94f340663a0 100644 --- a/docs/templating/templates/templates.md +++ b/docs/templating/templates/templates.md @@ -1,5 +1,5 @@ --- -description: Ibexa DXP uses the Twig template engine to customize the rendering of content in the site. +description: Cohesivo uses the Twig template engine to customize the rendering of content in the site. --- # Templates diff --git a/docs/templating/twig_function_reference/quable_twig_functions.md b/docs/templating/twig_function_reference/quable_twig_functions.md index 5cdad3b0a0d..775255b5687 100644 --- a/docs/templating/twig_function_reference/quable_twig_functions.md +++ b/docs/templating/twig_function_reference/quable_twig_functions.md @@ -4,7 +4,7 @@ page_type: reference month_change: false --- -# Quable Twig functions +# [[= pim_product_name =]] Twig functions The [[[= pim_product_name =]] connector](/product_catalog/quable/quable.md) provides the following Twig functions: diff --git a/docs/tutorials/beginner_tutorial/1_get_ready.md b/docs/tutorials/beginner_tutorial/1_get_ready.md index 2d4534e09be..162c7fc5cb6 100644 --- a/docs/tutorials/beginner_tutorial/1_get_ready.md +++ b/docs/tutorials/beginner_tutorial/1_get_ready.md @@ -1,12 +1,12 @@ --- -description: Start the tutorial by getting a clean installation of Ibexa DXP. +description: Start the tutorial by getting a clean installation of Cohesivo. --- # Step 1 — Get ready To begin the tutorial, you need a clean installation of [[= product_name =]]. -Get it by following the [install Ibexa DXP](install_ibexa_dxp.md) guide. +Get it by following the [Install [[= product_name =]]](../../getting_started/install_cohesivo.md) guide. You need a web server, a relational database and PHP. The clean installation contains only a root content item which displays a welcome page. diff --git a/docs/tutorials/beginner_tutorial/2_create_the_content_model.md b/docs/tutorials/beginner_tutorial/2_create_the_content_model.md index 8b4074bfc2d..cff82dff742 100644 --- a/docs/tutorials/beginner_tutorial/2_create_the_content_model.md +++ b/docs/tutorials/beginner_tutorial/2_create_the_content_model.md @@ -4,7 +4,7 @@ description: Learn how to create a content model consisting of content types and # Step 2 — Create the content model -How your content is structured is an important part of an [[= product_name =]] project. +How your content is structured is an important part of a [[= product_name =]] project. Think of it as the database design of your application. To get full information, read the [content model](content_model.md) documentation page. diff --git a/docs/tutorials/beginner_tutorial/3_customize_the_front_page.md b/docs/tutorials/beginner_tutorial/3_customize_the_front_page.md index 1844dc7a3be..f67caa305cd 100644 --- a/docs/tutorials/beginner_tutorial/3_customize_the_front_page.md +++ b/docs/tutorials/beginner_tutorial/3_customize_the_front_page.md @@ -88,9 +88,9 @@ To add a template like this to your site, create a `main_layout.html.twig` file - + - Ibexa DXP Beginner Tutorial + Cohesivo Beginner Tutorial @@ -162,7 +162,7 @@ To add a template like this to your site, create a `main_layout.html.twig` file
-

Website design & content © copyright {{ "now"|date("Y") }} Ibexa. This website was made with Ibexa DXP.

+

Website design & content © copyright {{ "now"|date("Y") }} Ibexa. This website was made with Cohesivo.

diff --git a/docs/tutorials/beginner_tutorial/6_improve_configuration.md b/docs/tutorials/beginner_tutorial/6_improve_configuration.md index 6368f572253..35604220436 100644 --- a/docs/tutorials/beginner_tutorial/6_improve_configuration.md +++ b/docs/tutorials/beginner_tutorial/6_improve_configuration.md @@ -1,5 +1,5 @@ --- -description: See how you can manage Ibexa DXP configuration files. +description: See how you can manage Cohesivo configuration files. --- # Step 6 — Improve configuration diff --git a/docs/tutorials/beginner_tutorial/8_enable_account_registration.md b/docs/tutorials/beginner_tutorial/8_enable_account_registration.md index 8983a207e91..b455c8e4ce9 100644 --- a/docs/tutorials/beginner_tutorial/8_enable_account_registration.md +++ b/docs/tutorials/beginner_tutorial/8_enable_account_registration.md @@ -233,9 +233,9 @@ Now you have created your first website with [[= product_name =]]. **You learned how to:** - create a content model -- organize files in an [[= product_name =]] project +- organize files in a [[= product_name =]] project - configure views for different content types -- add assets to an [[= product_name =]] project +- add assets to a [[= product_name =]] project - use and configure Webpack Encore - use Twig templates and controllers to display content - enable user registration diff --git a/docs/tutorials/beginner_tutorial/beginner_tutorial.md b/docs/tutorials/beginner_tutorial/beginner_tutorial.md index 21e71b8f685..94f87c174d7 100644 --- a/docs/tutorials/beginner_tutorial/beginner_tutorial.md +++ b/docs/tutorials/beginner_tutorial/beginner_tutorial.md @@ -1,10 +1,10 @@ --- -description: Go through a beginner tutorial which presents the Ibexa DXP content model and show how to configure and use templates to create a basic site. +description: Go through a beginner tutorial which presents the Cohesivo content model and show how to configure and use templates to create a basic site. --- # Beginner tutorial -This tutorial is a step-by-step guide to building an [[= product_name =]] website. +This tutorial is a step-by-step guide to building a [[= product_name =]] website. You can use it with both [[= product_name_headless =]] and [[= product_name_exp =]]. diff --git a/docs/tutorials/generic_field_type/1_implement_the_point2d_value_class.md b/docs/tutorials/generic_field_type/1_implement_the_point2d_value_class.md index d0af45e5ac5..3b6d096731b 100644 --- a/docs/tutorials/generic_field_type/1_implement_the_point2d_value_class.md +++ b/docs/tutorials/generic_field_type/1_implement_the_point2d_value_class.md @@ -7,7 +7,7 @@ description: Learn how to create a Value class that stores the value of the fiel ## Project installation To start the tutorial, you need to make a clean [[= product_name =]] installation. -Follow the guide for your system to [install Ibexa DXP](install_ibexa_dxp.md), [configure a server](requirements.md), and [start the web server](install_ibexa_dxp.md#use-phps-built-in-server). +Follow the guide for your system to [Install [[= product_name =]]](../../getting_started/install_cohesivo.md), [configure a server](requirements.md), and [start the web server](../../getting_started/install_cohesivo.md#use-phps-built-in-server). Remember to install using the `dev` environment. Open your project with a clean installation and create the base directory for a new Point 2D field type in `src/FieldType/Point2D`. diff --git a/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md b/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md index 7b99553e4ca..db6c20d89f3 100644 --- a/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md +++ b/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md @@ -11,7 +11,7 @@ To set up the starter website, you need to follow these steps: To begin the tutorial, you need a clean installation of [[= product_name_exp =]]. -Get it by following the [Install Ibexa DXP](install_ibexa_dxp.md) guide. +Get it by following the [Install [[= product_name =]]](../../getting_started/install_cohesivo.md) guide. ## Add content types diff --git a/docs/tutorials/tutorials.md b/docs/tutorials/tutorials.md index bba1ea65bc0..f8e2cc4d9db 100644 --- a/docs/tutorials/tutorials.md +++ b/docs/tutorials/tutorials.md @@ -1,5 +1,5 @@ --- -description: Get started with tutorials to learn how to create a site with Ibexa DXP +description: Get started with tutorials to learn how to create a site with Cohesivo page_type: landing_page --- diff --git a/docs/update_and_migration/from_2.5/to_3.3.md b/docs/update_and_migration/from_2.5/to_3.3.md index 0d8992a0b7c..372276656f8 100644 --- a/docs/update_and_migration/from_2.5/to_3.3.md +++ b/docs/update_and_migration/from_2.5/to_3.3.md @@ -10,12 +10,12 @@ Before you start this procedure, make sure you have completed the previous step, ## 5. Update to v3.3 -[[= product_name =]] v3.3 uses [Symfony Flex]([[= symfony_doc =]]/quick_tour/flex_recipes.html). +Ibexa DXP v3.3 uses [Symfony Flex]([[= symfony_doc =]]/quick_tour/flex_recipes.html). When updating from v3.2 to v3.3, you need to follow a special update procedure. !!! note - [[= product_name =]] v3.3 requires Composer 2.0.13 or higher. + Ibexa DXP v3.3 requires Composer 2.0.13 or higher. First, create an update branch `update-[[=target_version=]]` in git and commit your work. diff --git a/docs/update_and_migration/from_3.3/to_4.0.md b/docs/update_and_migration/from_3.3/to_4.0.md index 24a47309c3f..cfea9da1758 100644 --- a/docs/update_and_migration/from_3.3/to_4.0.md +++ b/docs/update_and_migration/from_3.3/to_4.0.md @@ -113,7 +113,7 @@ php bin/console cache:clear Apply the following database update script: -### [[= product_name =]] +### Ibexa DXP === "MySQL" ``` bash @@ -128,7 +128,7 @@ Apply the following database update script: ### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, apply the following database upgrade script: +If you have no access to Ibexa DXP's `ibexa/installer` package, apply the following database upgrade script: === "MySQL" ``` sql @@ -220,7 +220,7 @@ For more information, see [Get a content item](graphql_queries.md#get-a-content- ### Back office customization -The v4 version of [[= product_name =]] is using Bootstrap 5 in the back office. If you were using Bootstrap 4 for styling, you need to update and adjust all custom back office components [following the migration guide from Bootstrap 4](https://getbootstrap.com/docs/5.0/migration/). +The v4 version of Ibexa DXP is using Bootstrap 5 in the back office. If you were using Bootstrap 4 for styling, you need to update and adjust all custom back office components [following the migration guide from Bootstrap 4](https://getbootstrap.com/docs/5.0/migration/). ### Online editor diff --git a/docs/update_and_migration/from_3.3/update_from_3.3.md b/docs/update_and_migration/from_3.3/update_from_3.3.md index 43a0f026332..f75b2a118c8 100644 --- a/docs/update_and_migration/from_3.3/update_from_3.3.md +++ b/docs/update_and_migration/from_3.3/update_from_3.3.md @@ -7,7 +7,7 @@ month_change: false This update procedure applies if you're using a v3.3 installation without the latest maintenance release. To update from an 3.2 to 3.3, see [Updating the app to v3.3](to_3.3.md). -From older version, explore [this section](update_ibexa_dxp.md). +From older version, explore [this section](update_system.md). Go through the following steps to update to the latest maintenance release of v3.3 (v[[= latest_tag_3_3 =]]). @@ -241,7 +241,7 @@ Run the following scripts: ### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, apply the following database upgrade script: +If you have no access to Ibexa DXP's `ibexa/installer` package, apply the following database upgrade script: === "MySQL" @@ -384,7 +384,7 @@ See [Update Flex server](#update-flex-server). #### VCL configuration for Fastly -[[= product_name =]] now supports Fastly shielding. If you're using Fastly and want to use shielding, you need to update your VCL files. +Ibexa DXP now supports Fastly shielding. If you're using Fastly and want to use shielding, you need to update your VCL files. !!! tip @@ -454,7 +454,7 @@ If so, take appropriate action, for example by revoking passwords for all affect The [BREACH](https://www.breachattack.com/) attack is a security vulnerability against HTTPS when using HTTP compression. -If you're using Varnish, update the VCL configuration to stop compressing both the [[= product_name =]]'s REST API and JSON responses from your backend. +If you're using Varnish, update the VCL configuration to stop compressing both the Ibexa DXP's REST API and JSON responses from your backend. Fastly users are not affected. === "Varnish on [[= product_name_cloud =]]" @@ -543,7 +543,7 @@ There are no additional update steps to execute. #### Security -This security advisory resolves XSS vulnerabilities in several parts of the back office of the DXP. +This security advisory resolves XSS vulnerabilities in several parts of the back office of Ibexa DXP. Back office access and varying levels of editing and management permissions are required to exploit these vulnerabilities. For more information, see the [security advisory IBEXA-SA-2025-003](https://developers.ibexa.co/security-advisories/ibexa-sa-2025-003-xss-vulnerabilities-in-back-office). diff --git a/docs/update_and_migration/from_4.0/to_4.1.md b/docs/update_and_migration/from_4.0/to_4.1.md index ace1a1b4bb8..1dc1a43ac05 100644 --- a/docs/update_and_migration/from_4.0/to_4.1.md +++ b/docs/update_and_migration/from_4.0/to_4.1.md @@ -119,7 +119,7 @@ Apply the following database update scripts: #### Ibexa Open Source -If you're using [[= product_name_oss =]] and have no access to [[= product_name =]]'s `ibexa/installer` package, database upgrade isn't necessary. +If you're using Ibexa OSS and have no access to Ibexa DXP's `ibexa/installer` package, database upgrade isn't necessary. ## Update the app to latest version of v4.1 diff --git a/docs/update_and_migration/from_4.1/update_from_4.1.md b/docs/update_and_migration/from_4.1/update_from_4.1.md index 8bf995b766e..ad45d2ceabc 100644 --- a/docs/update_and_migration/from_4.1/update_from_4.1.md +++ b/docs/update_and_migration/from_4.1/update_from_4.1.md @@ -129,7 +129,7 @@ Apply the following database update scripts: #### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, database upgrade isn't necessary. +If you have no access to Ibexa DXP's `ibexa/installer` package, database upgrade isn't necessary. ## Ensure password safety diff --git a/docs/update_and_migration/from_4.2/update_from_4.2.md b/docs/update_and_migration/from_4.2/update_from_4.2.md index 1e4c711af44..63d326d2cb7 100644 --- a/docs/update_and_migration/from_4.2/update_from_4.2.md +++ b/docs/update_and_migration/from_4.2/update_from_4.2.md @@ -142,7 +142,7 @@ Apply the following database update scripts: #### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, database upgrade isn't necessary. +If you have no access to Ibexa DXP's `ibexa/installer` package, database upgrade isn't necessary. ### Clean-up taxonomy database diff --git a/docs/update_and_migration/from_4.3/update_from_4.3.md b/docs/update_and_migration/from_4.3/update_from_4.3.md index 072c20cc5e6..346361e03e2 100644 --- a/docs/update_and_migration/from_4.3/update_from_4.3.md +++ b/docs/update_and_migration/from_4.3/update_from_4.3.md @@ -6,7 +6,7 @@ description: Update your installation to the latest v4.4 version from v4.3.x. This update procedure applies if you're using the newest v4.3 installation. -This release deprecates all Commerce packages in[[= product_name =]]. They will be removed in v5. +This release deprecates all Commerce packages in Ibexa DXP. They will be removed in v5. Until that time, they will be maintained by Ibexa with fixes, including security fixes, but they won't be further developed. Old packages are replaced by [the all-new Ibexa Commerce packages](ibexa_dxp_v4.4.md#all-new-ibexa-commerce-packages). diff --git a/docs/update_and_migration/from_4.3/update_from_4.3_new_commerce.md b/docs/update_and_migration/from_4.3/update_from_4.3_new_commerce.md index 427eabd4416..2f2f2ad6d91 100644 --- a/docs/update_and_migration/from_4.3/update_from_4.3_new_commerce.md +++ b/docs/update_and_migration/from_4.3/update_from_4.3_new_commerce.md @@ -404,7 +404,7 @@ The tables that can be removed are prefixed with `ses_` and `sve_`. #### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, database upgrade isn't necessary. +If you have no access to Ibexa DXP's `ibexa/installer` package, database upgrade isn't necessary. ## Ensure password safety diff --git a/docs/update_and_migration/from_4.3/update_from_4.3_old_commerce.md b/docs/update_and_migration/from_4.3/update_from_4.3_old_commerce.md index dc4ca8aa878..a9e20078a9c 100644 --- a/docs/update_and_migration/from_4.3/update_from_4.3_old_commerce.md +++ b/docs/update_and_migration/from_4.3/update_from_4.3_old_commerce.md @@ -195,7 +195,7 @@ Apply the following database update scripts: #### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, database upgrade isn't necessary. +If you have no access to Ibexa DXP's `ibexa/installer` package, database upgrade isn't necessary. ## Ensure password safety diff --git a/docs/update_and_migration/from_4.4/update_from_4.4.md b/docs/update_and_migration/from_4.4/update_from_4.4.md index 24005108d0e..1e5b78fc9f7 100644 --- a/docs/update_and_migration/from_4.4/update_from_4.4.md +++ b/docs/update_and_migration/from_4.4/update_from_4.4.md @@ -119,7 +119,7 @@ php bin/console ibexa:migrate:richtext-namespaces #### Ibexa Open Source -If you have no access to [[= product_name =]]'s `ibexa/installer` package, apply the following database update: +If you have no access to Ibexa DXP's `ibexa/installer` package, apply the following database update: === "MySQL" diff --git a/docs/update_and_migration/from_4.5/update_from_4.5.md b/docs/update_and_migration/from_4.5/update_from_4.5.md index 642a4466fec..0901c8213ca 100644 --- a/docs/update_and_migration/from_4.5/update_from_4.5.md +++ b/docs/update_and_migration/from_4.5/update_from_4.5.md @@ -305,7 +305,7 @@ php bin/console ibexa:migrations:migrate --file=2023_11_20_14_33_order_dashboard ### Ibexa Open Source -If you don't have access to [[= product_name =]]'s `ibexa/installer` package and cannot apply the scripts from `vendor/ibexa/installer` directory, apply the following database update instead: +If you don't have access to Ibexa DXP's `ibexa/installer` package and cannot apply the scripts from `vendor/ibexa/installer` directory, apply the following database update instead: === "MySQL" @@ -342,7 +342,7 @@ ibexa: #### User profile -[[= product_name =]] v4.6 introduced user profile for Backoffice users, allowing users to upload avatars, and provide personal information. +Ibexa DXP v4.6 introduced user profile for Backoffice users, allowing users to upload avatars, and provide personal information. This feature is optional, and you can disable it by setting `enabled` flag to `false` in `ibexa.system..user_profile` configuration: @@ -370,7 +370,7 @@ ibexa: field_groups: ['about', 'contact'] ``` -You can use your own content type that represents the back office user, or use the default one provided by [[= product_name =]]: +You can use your own content type that represents the back office user, or use the default one provided by Ibexa DXP: ```bash php bin/console ibexa:migrations:import vendor/ibexa/installer/src/bundle/Resources/install/migrations/2023_12_07_20_23_editor_content_type.yaml --name=2023_12_07_20_23_editor_content_type.yaml diff --git a/docs/update_and_migration/from_4.6/update_from_4.6.md b/docs/update_and_migration/from_4.6/update_from_4.6.md index 70949ef3463..c182bfb72a7 100644 --- a/docs/update_and_migration/from_4.6/update_from_4.6.md +++ b/docs/update_and_migration/from_4.6/update_from_4.6.md @@ -205,7 +205,7 @@ If so, take appropriate action, for example by [revoking passwords](https://doc. The [BREACH](https://www.breachattack.com/) attack is a security vulnerability against HTTPS when using HTTP compression. -If you're using Varnish, update the VCL configuration to stop compressing both the [[= product_name =]]'s REST API and JSON responses from your backend. +If you're using Varnish, update the VCL configuration to stop compressing both the Ibexa DXP's REST API and JSON responses from your backend. Fastly users are not affected. === "Varnish on [[= product_name_cloud =]]" @@ -362,7 +362,7 @@ No additional steps needed. ### Security -This security advisory resolves XSS vulnerabilities in several parts of the back office of the DXP. +This security advisory resolves XSS vulnerabilities in several parts of the back office of Ibexa DXP. Back office access and varying levels of editing and management permissions are required to exploit these vulnerabilities. For more information, see the [security advisory IBEXA-SA-2025-003](https://developers.ibexa.co/security-advisories/ibexa-sa-2025-003-xss-vulnerabilities-in-back-office). @@ -393,9 +393,9 @@ Run the following scripts: This release adds support for [Solr 9](requirements.md#search). -To update Solr within an existing [[= product_name =]] project, first refer to the [Solr 9 upgrade planning](https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html) instructions. +To update Solr within an existing Ibexa DXP project, first refer to the [Solr 9 upgrade planning](https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html) instructions. -Then, follow the [instructions for setting up Solr 9 with [[= product_name =]]](/search/search_engines/solr_search_engine/install_solr.md#configure-and-start-solr) and merge them with your custom configuration. +Then, follow the [instructions for setting up Solr 9 with Ibexa DXP](https://doc.ibexa.co/en/4.6/search/search_engines/solr_search_engine/install_solr/#configure-and-start-solr) and merge them with your custom configuration. Changes include: @@ -467,9 +467,9 @@ No additional steps needed. ### Elasticsearch 8 support -As of v4.6.27, [[= product_name =]] adds optional support for Elasticsearch 8.19 or higher through the new `ibexa/elasticsearch8` package. +As of v4.6.27, Ibexa DXP adds optional support for Elasticsearch 8.19 or higher through the new `ibexa/elasticsearch8` package. -By default, [[= product_name =]] continues to support Elasticsearch 7.16.2+ with the `ibexa/elasticsearch` package. +By default, Ibexa DXP continues to support Elasticsearch 7.16.2+ with the `ibexa/elasticsearch` package. To use Elasticsearch 8, follow these steps: #### Install Elasticsearch 8 package @@ -579,7 +579,7 @@ composer require guzzlehttp/guzzle:^6.5 php-http/guzzle6-adapter:^2.0 ### Messenger support in CDP -If you're using [CDP](cdp.md) and haven't configured Ibexa Messenger yet, do so now. +If you're using [CDP](raptor_cdp.md) and haven't configured Ibexa Messenger yet, do so now. Follow the [Messenger setup instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#install-package) to continue. @@ -713,7 +713,7 @@ To use these packages in versions not affected by security vulnerabilities, PHP For projects meeting this requirement, you can update the packages with Composer. -If you're using PHP 7.4 or 8.0, to do the [[= product_name =]] update, you have two options: +If you're using PHP 7.4 or 8.0, to do the Ibexa DXP update, you have two options: #### Update PHP, the custom code, then the platform (recommended) diff --git a/docs/update_and_migration/from_4.6/update_to_5.0.md b/docs/update_and_migration/from_4.6/update_to_5.0.md index 7d601806881..625df973ec5 100644 --- a/docs/update_and_migration/from_4.6/update_to_5.0.md +++ b/docs/update_and_migration/from_4.6/update_to_5.0.md @@ -23,17 +23,17 @@ When you have the last version of 4.6, you can update to v5.0.0. First, match v5.0's [requirements](requirements.md). It supports only PHP 8.3 and above. -### Update custom code for PHP 8.3+ and DXP 4.6 +### Update custom code for PHP 8.3+ and Ibexa DXP 4.6 It's important to stop using deprecated PHP classes as they're removed in 5.0. The [`ibexa/compatibility-layer`](to_4.0.md#add-compatibility-layer-package) isn't supported in 5.0. If you use it, remove it (`composer remove ibexa/compatibility-layer`) and make the necessary changes. -See [[[= product_name =]] v4.0 deprecations and backwards compatibility breaks](/release_notes/ibexa_dxp_v4.0_deprecations.md) for the list of changes. +See [Ibexa DXP v4.0 deprecations and backwards compatibility breaks](/release_notes/ibexa_dxp_v4.0_deprecations.md) for the list of changes. [Rector](https://getrector.com/) and the [[= product_name_base =]] rule sets help to upgrade your code. -Install [`ibexa/rector`](https://github.com/ibexa/rector) which contains rules to ensure custom code is up to date with DXP 4.6: +Install [`ibexa/rector`](https://github.com/ibexa/rector) which contains rules to ensure custom code is up to date with Ibexa DXP 4.6: ```bash composer require --dev ibexa/rector @@ -106,11 +106,11 @@ You can do it, for example, with the following command: rm -r config/graphql ``` -### Update [[= product_name =]] application +### Update Ibexa DXP application #### Update package requirements -[[= product_name =]] 5.0 is based on Symfony 7.3 and both must be updated. +Ibexa DXP 5.0 is based on Symfony 7.3 and both must be updated. Your development packages must be updated as well. The example below assumes that [`symfony/debug-pack`](https://symfony.com/packages/debug-pack) and `ibexa/rector` are installed. Adjust the list based on your project requirements. @@ -219,7 +219,7 @@ If you were using the separate `ibexa/elasticsearch8` package in v4.6, you shoul composer remove --no-update ibexa/elasticsearch8 ``` -The `ibexa/elasticsearch` package is automatically installed as part of your [[= product_name =]] 5.0 update. +The `ibexa/elasticsearch` package is automatically installed as part of your Ibexa DXP 5.0 update. Your existing Elasticsearch 8 server and configuration continue to work with the `ibexa/elasticsearch` package. #### Remove PHP 8.2 error handler @@ -252,7 +252,7 @@ composer recipes:install symfony/webpack-encore-bundle --reset --force --yes Compare with your previous version, merge them together and test your customizations if needed. -#### Apply [[= product_name =]] recipe +#### Apply Ibexa DXP recipe === "[[= product_name_headless =]]" @@ -324,7 +324,7 @@ The main schema has changed and the provided SQL file `ibexa-4.6.latest-to-5.0.0 ??? note "Ibexa Open Source" - If you don't have access to [[= product_name =]]'s `ibexa/installer` package, apply the following database update: + If you don't have access to Ibexa DXP's `ibexa/installer` package, apply the following database update: === "MySQL" @@ -442,9 +442,9 @@ You can track the renaming in the `ibexa-4.6.latest-to-5.0.0.sql` file or below. ALTER TABLE ibexa_dfs_file RENAME INDEX ezdfsfile_mtime TO ibexa_dfs_file_mtime; ``` -### Update custom code for [[= product_name =]] 5.0 +### Update custom code for Ibexa DXP 5.0 -See [[[= product_name =]] v5.0 deprecations and backwards compatibility breaks](/release_notes/ibexa_dxp_v5.0_deprecations.md) for the list of changes. +See [Ibexa DXP v5.0 deprecations and backwards compatibility breaks](/release_notes/ibexa_dxp_v5.0_deprecations.md) for the list of changes. The following sections presents some of those changes and how to apply them. #### Update PHP framework standards @@ -1055,7 +1055,7 @@ php bin/console ibexa:migrations:migrate --file=2025_07_08_09_27_set_container_t ### Generate GraphQL schema -GraphQL usage is no longer required for the [[= product_name =]] back office. +GraphQL usage is no longer required for the Ibexa DXP back office. If you are using GraphQL in your project, you can generate its schema by running: ```bash @@ -1106,5 +1106,5 @@ composer ibexa:setup --platformsh #### Conclusion -Your project is now running the latest major version of [[= product_name =]]. +Your project is now running the latest major version of Ibexa DXP. To reach the last patch version, see [Update from v5.0.x to v5.0.latest](update_from_5.0.md) diff --git a/docs/update_and_migration/from_5.0/update_from_5.0.md b/docs/update_and_migration/from_5.0/update_from_5.0.md index 800b8f793f8..a7d3d13de37 100644 --- a/docs/update_and_migration/from_5.0/update_from_5.0.md +++ b/docs/update_and_migration/from_5.0/update_from_5.0.md @@ -6,7 +6,7 @@ month_change: true # Update from v5.0.x to v5.0.latest To update from v4.6.x, see [Update from v4.6 to v5.0](update_to_5.0.md). -To update from an older version, visit [the update page](update_ibexa_dxp.md) and choose the applicable path. +To update from an older version, visit [the update page](update_system.md) and choose the applicable path. ## Update the application @@ -187,7 +187,7 @@ If the platform comes from lower than v5.0.3 and is updated to higher than v5.0. ### Elasticsearch 8 support -As of v5.0.5, [[= product_name =]] adds support for Elasticsearch 8.19 or higher. +As of v5.0.5, Ibexa DXP adds support for Elasticsearch 8.19 or higher. You can continue using [unsupported Elasticsearch 7.16.2+](https://www.elastic.co/support/eol), but it's recommended to upgrade to Elasticsearch 8 for improved performance and security features. When choosing to keep using Elasticsearch 7.16.2, adjust your configuration as described in the [Update configuration](#update-configuration) section below to avoid using deprecated settings. @@ -334,7 +334,7 @@ curl -fs https://get.symfony.com/cloud/configurator | bash ### Update Symfony from 7.3 to 7.4 -This version of [[= product_name =]] requires [Symfony 7.4](https://symfony.com/releases/7.4). +This version of Ibexa DXP requires [Symfony 7.4](https://symfony.com/releases/7.4). Update Symfony constraints in `composer.json` before updating the packages. 1. In `composer.json`, update `extra.symfony.require` to allow installing a higher Symfony version: @@ -383,7 +383,7 @@ Update Symfony constraints in `composer.json` before updating the packages. !!! caution "Always clear the persistence cache with `cache:pool:clear` command" - Starting with Symfony 7.4, running `php bin/console cache:clear` doesn't clear the [[= product_name =]] persistence cache, even when using a filesystem-based cache pool. + Starting with Symfony 7.4, running `php bin/console cache:clear` doesn't clear the Ibexa DXP's persistence cache, even when using a filesystem-based cache pool. To clear the persistence cache, for example after adding a [custom Page Builder block](create_custom_page_block.md), you must always run: @@ -477,7 +477,7 @@ Make sure it contains the highlighted addition: ## v5.0.9 -No additional steps needed for [[= product_name =]], but the [MCP Servers LTS Update requires additional update steps](#mcp-servers) if you're using it. +No additional steps needed for Ibexa DXP, but the [MCP Servers LTS Update requires additional update steps](#mcp-servers) if you're using it. ## LTS Updates and additional packages diff --git a/docs/update_and_migration/migrate_to_ibexa_dxp/common_issues.md b/docs/update_and_migration/migrate_to_ibexa_dxp/common_issues.md index aa319317805..3c6c524e825 100644 --- a/docs/update_and_migration/migrate_to_ibexa_dxp/common_issues.md +++ b/docs/update_and_migration/migrate_to_ibexa_dxp/common_issues.md @@ -1,10 +1,10 @@ --- -description: Check common issues that occur when updating from earlier version to Ibexa DXP and how to resolve them. +description: Check common issues that occur when updating from earlier version to Ibexa DXP or Cohesivo and how to resolve them. --- # Common migration issues -Below you can find cleanup commands from the EzPublishMigrationBundle for the most common issues that can occur after migration to [[= product_name =]]. +Below you can find cleanup commands from the EzPublishMigrationBundle for the most common issues that can occur after migration to Ibexa DXP or [[= product_name =]]. !!! note "Enabling EzPublishMigrationBundle bundle" @@ -63,7 +63,7 @@ The command can be executed in two modes: ## Always available flag set on all fields Always available flag is set on all fields, instead of only on fields in the main language. -This problem occurs when [[= product_name =]] is used to create content that is both always available and has multiple translations. +This problem occurs when you create a content item in the platform is both always available and has multiple translations. The cleanup script correctly sets always available flag for prioritized language filtering in Legacy search engine. ```bash diff --git a/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md b/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md index 93217e3db81..849a8085a26 100644 --- a/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md +++ b/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md @@ -4,7 +4,7 @@ description: Migrate an older eZ Publish Platform installation to eZ Platform. # Migrating from eZ Publish Platform -eZ Publish Platform (5.x) was a transitional version of the Ibexa CMS, bridging the gap between the earlier generation called eZ Publish (sometimes referred to as *legacy*), and eZ Platform, the predecessor to [[= product_name =]]. +eZ Publish Platform (5.x) was a transitional version of the Ibexa CMS, bridging the gap between the earlier generation called eZ Publish (sometimes referred to as *legacy*), eZ Platform and Ibexa DXP, the predecessors to [[= product_name =]]. eZ Publish Platform introduced a new Symfony-based technology stack that could be run along the old (*legacy*) one. This bridging is still possible using something called Legacy Bridge, an optional package for eZ Platform. This fluid change allows eZ Publish users to migrate to eZ Platform gradually, using the bridging as an intermediary stepping stone. @@ -37,7 +37,7 @@ You can then proceed with consecutive upgrades to further versions: v1.13 LTS an !!! caution "Unsupported legacy sorting methods" In older eZ Publish versions, sub-items of content items could be sorted by Class identifier (option value 6) or Class name (option value 7). - These sorting methods are no longer supported in [[= product_name =]]. + These sorting methods are no longer supported in Ibexa DXP and [[= product_name =]]. After you migrate, trying to render the Sub-items tab of content items that are configured to use the unsupported sorting methods results in an error. To mitigate the problem, before you migrate, update the affected content items to use supported sorting methods such as Name, Published, or Priority. diff --git a/docs/update_and_migration/update_ibexa_dxp.md b/docs/update_and_migration/update_system.md similarity index 91% rename from docs/update_and_migration/update_ibexa_dxp.md rename to docs/update_and_migration/update_system.md index fbeec4c43c8..08010086d1d 100644 --- a/docs/update_and_migration/update_ibexa_dxp.md +++ b/docs/update_and_migration/update_system.md @@ -2,9 +2,9 @@ description: Update your installation to the latest supported version. --- -# Updating [[= product_name =]] +# Updating Ibexa DXP and [[= product_name =]] -To update [[= product_name =]] to a newer version, select the version you're currently using: +To update Ibexa DXP and [[= product_name =]] to a newer version, select the version you're currently using: === "I am using v1.13 or v2.x" diff --git a/docs/users/diagram_source/oauth2-client.drawio b/docs/users/diagram_source/oauth2-client.drawio index 8b47100370c..e0acda98ebb 100644 --- a/docs/users/diagram_source/oauth2-client.drawio +++ b/docs/users/diagram_source/oauth2-client.drawio @@ -16,7 +16,7 @@ - + diff --git a/docs/users/diagram_source/oauth2-server.drawio b/docs/users/diagram_source/oauth2-server.drawio index df63a7d62d0..306968c8f69 100644 --- a/docs/users/diagram_source/oauth2-server.drawio +++ b/docs/users/diagram_source/oauth2-server.drawio @@ -10,7 +10,7 @@ - + diff --git a/docs/users/img/oauth2-client.png b/docs/users/img/oauth2-client.png index 6874b8a4428..8babc60dc14 100644 Binary files a/docs/users/img/oauth2-client.png and b/docs/users/img/oauth2-client.png differ diff --git a/docs/users/img/oauth2-server.png b/docs/users/img/oauth2-server.png index da9202a1d21..4567a8e4877 100644 Binary files a/docs/users/img/oauth2-server.png and b/docs/users/img/oauth2-server.png differ diff --git a/docs/users/oauth_client.md b/docs/users/oauth_client.md index 889f140682e..9dbb80e6fc1 100644 --- a/docs/users/oauth_client.md +++ b/docs/users/oauth_client.md @@ -1,5 +1,5 @@ --- -description: Allow users to log into Ibexa DXP through external OAuth2 authorization servers. +description: Allow users to log into Cohesivo through external OAuth2 authorization servers. --- # OAuth client diff --git a/docs/users/oauth_server.md b/docs/users/oauth_server.md index d61f152fc34..4fe24cbf5a6 100644 --- a/docs/users/oauth_server.md +++ b/docs/users/oauth_server.md @@ -1,5 +1,5 @@ --- -description: Other applications can authenticate Ibexa DXP users through OAuth2 protocol then access to their resources on the platform. +description: Other applications can authenticate Cohesivo users through OAuth2 protocol then access to their resources on the platform. --- # OAuth Server @@ -148,7 +148,7 @@ Other commands let you list all the configured clients (`league:oauth2-server:li Your OAuth2 client needs the following information to be able to use your OAuth server: -- The URL of the [[= product_name =]] used as an OAuth server +- The URL of [[= product_name =]] used as an OAuth server - The client identifier - The client secret - The scope (`default`) diff --git a/docs/users/user_management_guide.md b/docs/users/user_management_guide.md index cbedff4cda6..3e964c76e80 100644 --- a/docs/users/user_management_guide.md +++ b/docs/users/user_management_guide.md @@ -1,5 +1,5 @@ --- -description: Find out what's user management and check what functions Ibexa DXP offers in this area to effectively manage the digital ecosystem. +description: Find out what's user management and check what functions Cohesivo offers in this area to effectively manage the digital ecosystem. --- # User management product guide diff --git a/docs/users/users.md b/docs/users/users.md index 5ce0f277cb4..04a1152c1df 100644 --- a/docs/users/users.md +++ b/docs/users/users.md @@ -1,5 +1,5 @@ --- -description: Users in Ibexa DXP refer to all kinds of user accounts, such as administrators, editors, managers or shop customers. +description: Users in Cohesivo refer to all kinds of user accounts, such as administrators, editors, managers or shop customers. page_type: landing_page --- diff --git a/mkdocs.yml b/mkdocs.yml index 608ef135ea7..b46be5f4609 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -20,15 +20,15 @@ not_in_nav: | /snippets/* nav: - Ibexa Developer Documentation: index.md - - Ibexa DXP editions: + - Cohesivo editions: - Editions: ibexa_products/editions.md - - Ibexa Headless: ibexa_products/ibexa_headless.md - - Ibexa Experience: ibexa_products/ibexa_experience.md - - Ibexa Commerce: ibexa_products/ibexa_commerce.md + - Cohesivo Headless: ibexa_products/ibexa_headless.md + - Cohesivo Experience: ibexa_products/ibexa_experience.md + - Cohesivo Commerce: ibexa_products/ibexa_commerce.md - Getting started: - Getting started: getting_started/getting_started.md - Requirements: getting_started/requirements.md - - Install Ibexa DXP: getting_started/install_ibexa_dxp.md + - Install Cohesivo: getting_started/install_cohesivo.md - Install on MacOS and Windows: getting_started/install_on_mac_os_and_windows.md - Install with DDEV: getting_started/install_with_ddev.md - First steps: getting_started/first_steps.md @@ -329,7 +329,7 @@ nav: - Image Twig functions: templating/twig_function_reference/image_twig_functions.md - Page Twig functions: templating/twig_function_reference/page_twig_functions.md - Product Twig functions: templating/twig_function_reference/product_twig_functions.md - - Quable functions: templating/twig_function_reference/quable_twig_functions.md + - Quable Twig functions: templating/twig_function_reference/quable_twig_functions.md - Recommendations Twig functions: templating/twig_function_reference/recommendations_twig_functions.md - Site context Twig functions: templating/twig_function_reference/site_context_twig_functions.md - Storefront Twig functions: templating/twig_function_reference/storefront_twig_functions.md @@ -373,8 +373,8 @@ nav: - Product catalog: - Product catalog: product_catalog/product_catalog.md - Product catalog guide: product_catalog/product_catalog_guide.md - - Quable PIM integration: - - Quable PIM Integration: product_catalog/quable/quable.md + - Quable integration: + - Quable integration: product_catalog/quable/quable.md - Quable product guide: product_catalog/quable/quable_guide.md - Install Quable: product_catalog/quable/install_quable.md - Configure Quable: product_catalog/quable/configure_quable_connector.md @@ -391,13 +391,13 @@ nav: - Prices: product_catalog/prices.md - Price API: product_catalog/price_api.md - Customize product catalog: + - Customize product catalog: product_catalog/customize_product_catalog.md - Create custom attribute type: product_catalog/create_custom_attribute_type.md - Create custom availability strategy: product_catalog/create_custom_availability_strategy.md - Create custom catalog filter: product_catalog/create_custom_catalog_filter.md - Create custom name schema: product_catalog/create_custom_name_schema_strategy.md - Create product code generator: product_catalog/create_product_code_generator.md - Customize product attribute templates: product_catalog/customize_product_attribute_templates.md - - Customize product catalog: product_catalog/customize_product_catalog.md - Customize product embed templates: product_catalog/customize_product_embed_templates.md - Add remote PIM support: product_catalog/add_remote_pim_support.md - Commerce: @@ -461,11 +461,11 @@ nav: - Create Customer Portal: customer_management/cp_page_builder.md - Customer Portal Applications: customer_management/cp_applications.md - Create registration form: customer_management/create_user_registration_form.md - - Ibexa Engage: - - Ibexa Engage: ibexa_engage/ibexa_engage.md - - Install Ibexa Engage: ibexa_engage/install_ibexa_engage.md - - Create campaign with Ibexa Engage: ibexa_engage/create_campaign.md - - Integrate Ibexa Engage with Ibexa Connect: ibexa_engage/integrate_ibexa_connect.md + - Data collection: + - Qualifio integration: qualifio/qualifio.md + - Install Qualifio: qualifio/install_qualifio.md + - Create campaign with Qualifio: qualifio/create_campaign.md + - Integrate Qualifio with Ibexa Connect: qualifio/integrate_ibexa_connect.md - Multisite: - Multisite: multisite/multisite.md - Multisite configuration: multisite/multisite_configuration.md @@ -509,26 +509,26 @@ nav: - Customer groups: users/customer_groups.md - Segment API: users/segment_api.md - Recommendations: - - Integration with Raptor: - - Raptor connector: recommendations/raptor_integration/raptor_connector.md - - Raptor connector guide: recommendations/raptor_integration/raptor_connector_guide.md - - Installation and configuration: recommendations/raptor_integration/connector_installation_configuration.md + - Raptor integration: recommendations/raptor_integration/raptor_connector.md + - Raptor integration guide: recommendations/raptor_integration/raptor_connector_guide.md + - Install and configure Raptor: recommendations/raptor_integration/connector_installation_configuration.md + - Track with Raptor: - Tracking functions: recommendations/raptor_integration/tracking_functions.md - Hybrid tracking: recommendations/raptor_integration/hybrid_tracking.md - Tracking with PHP API: recommendations/raptor_integration/tracking_php_api.md - - Recommendations blocks: recommendations/raptor_integration/recommendation_blocks.md - - Custom recommendation rendering: recommendations/raptor_integration/custom_recommendation_rendering.md - - CDP (Customer Data Platform): - - Customer Data Platform: cdp/cdp.md - - CDP guide: cdp/cdp_guide.md - - CDP installation: cdp/cdp_installation.md - - CDP activation: - - CDP activation: cdp/cdp_activation/cdp_activation.md - - CDP configuration: cdp/cdp_activation/cdp_configuration.md - - CDP data export: cdp/cdp_activation/cdp_data_export.md - - CDP add tracking: cdp/cdp_activation/cdp_add_tracking.md - - CDP data export schedule: cdp/cdp_data_export_schedule.md - - CDP data customization: cdp/cdp_data_customization.md + - Recommendation blocks: recommendations/raptor_integration/recommendation_blocks.md + - Render recommendations: recommendations/raptor_integration/custom_recommendation_rendering.md + - Customer Data Platform: + - Raptor CDP integration: raptor_cdp/raptor_cdp.md + - Raptor CDP guide: raptor_cdp/raptor_cdp_guide.md + - Install Raptor CDP: raptor_cdp/raptor_cdp_installation.md + - Activate Raptor CDP: + - Activate Raptor CDP: raptor_cdp/raptor_cdp_activation/raptor_cdp_activation.md + - Configure Raptor CDP: raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration.md + - Export Raptor CDP data: raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md + - Track with Raptor CDP: raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md + - Schedule Raptor CDP data export: raptor_cdp/raptor_cdp_data_export_schedule.md + - Customize Raptor CDP data: raptor_cdp/raptor_cdp_data_customization.md - Search: - Search: search/search.md - Search engines: @@ -885,7 +885,7 @@ nav: - Security advisories: infrastructure_and_maintenance/security/security_advisories.md - Support and maintenance FAQ: infrastructure_and_maintenance/support_and_maintenance_faq.md - Update and migration: - - Update Ibexa DXP: update_and_migration/update_ibexa_dxp.md + - Update your system: update_and_migration/update_system.md - Update from v1.13 and v2.x: - Update from v1.13 and v2.x: update_and_migration/from_1.x_2.x/update_from_1.x_2.x.md - Update app to v2.5: update_and_migration/from_1.x_2.x/update_app_to_2.5.md @@ -927,14 +927,14 @@ nav: - Update to v5.0: update_and_migration/from_4.6/update_to_5.0.md - Update from v5.0: - Update to v5.0: update_and_migration/from_5.0/update_from_5.0.md - - Migrate to Ibexa DXP: + - Migrate to Ibexa DXP or Cohesivo: - Migrate from eZ Publish Platform: update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md - Migrate from eZ Publish: update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish.md - Common migration issues: update_and_migration/migrate_to_ibexa_dxp/common_issues.md - Resources: - Resources: resources/resources.md - Release process and roadmap: resources/release_process_and_roadmap.md - - Ibexa DXP PhpStorm plugin: resources/phpstorm_plugin.md + - Ibexa PhpStorm plugin: resources/phpstorm_plugin.md - New in documentation: resources/new_in_doc.md - Contributing: - Report and follow issues: resources/contributing/report_and_follow_issues.md @@ -1005,16 +1005,17 @@ extra: # Global variables site_display_name: 'Ibexa Documentation' product_name_base: 'Ibexa' - product_name: 'Ibexa DXP' + product_name: 'Cohesivo' product_name_content: 'Ibexa Content' product_name_headless: 'Ibexa Headless' product_name_exp: 'Ibexa Experience' product_name_com: 'Ibexa Commerce' - product_name_cdp: 'Ibexa CDP' + product_name_cdp: 'Raptor CDP' + product_name_cdp_base: 'Raptor' product_name_connect: 'Ibexa Connect' product_name_cloud: 'Ibexa Cloud' product_name_oss: 'Ibexa OSS' - product_name_engage: 'Ibexa Engage' + product_name_engage: 'Qualifio' pim_product_name: 'Quable' eol_versions: ['2.5', '3.3'] diff --git a/plugins.yml b/plugins.yml index 39ea2aaeed2..d00dcacd7bc 100644 --- a/plugins.yml +++ b/plugins.yml @@ -520,7 +520,8 @@ plugins: 'community_resources/translations.md': 'resources/contributing/contribute_translations.md' 'community_resources/package_structure.md': 'resources/contributing/package_structure.md' - 'updating/update_ibexa_dxp.md': 'update_and_migration/update_ibexa_dxp.md' + 'updating/update_ibexa_dxp.md': 'update_and_migration/update_system.md' + 'update_and_migration/update_ibexa_dxp.md': 'update_and_migration/update_system.md' 'updating/from_1.x_2.x/update_from_1.x_2.x.md': 'update_and_migration/from_1.x_2.x/update_from_1.x_2.x.md' 'updating/from_1.x_2.x/update_app_to_2.5.md': 'update_and_migration/from_1.x_2.x/update_app_to_2.5.md' 'updating/from_1.x_2.x/update_db_to_2.5.md': 'update_and_migration/from_1.x_2.x/update_db_to_2.5.md' @@ -570,7 +571,8 @@ plugins: 'releases/ez_platform_v1.8.0.md': 'release_notes/ez_platform_v1.8.0.md' 'releases/ez_platform_v1.7.0_lts.md': 'release_notes/ez_platform_v1.7.0_lts.md' - 'getting_started/install_ez_platform.md': 'getting_started/install_ibexa_dxp.md' + 'getting_started/install_ez_platform.md': 'getting_started/install_cohesivo.md' + 'getting_started/install_ibexa_dxp.md': 'getting_started/install_cohesivo.md' 'templating/layout/create_user_registration_form.md': 'customer_management/create_user_registration_form.md' 'templating/twig_function_reference/other_twig_filters.md': 'templating/twig_function_reference/icon_twig_functions.md' @@ -608,7 +610,20 @@ plugins: 'ai_actions/configure_ai_actions.md': 'ai/ai_actions/configure_ai_actions.md' 'ai_actions/extend_ai_actions.md': 'ai/ai_actions/extend_ai_actions.md' - 'cdp/cdp_activation/cdp_add_clientside_tracking.md': 'cdp/cdp_activation/cdp_add_tracking.md' + 'cdp/cdp_activation/cdp_add_clientside_tracking.md': 'raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md' + 'ibexa_engage/ibexa_engage.md': 'qualifio/qualifio.md' + 'ibexa_engage/install_ibexa_engage.md': 'qualifio/install_qualifio.md' + 'ibexa_engage/create_campaign.md': 'qualifio/create_campaign.md' + 'ibexa_engage/integrate_ibexa_connect.md': 'qualifio/integrate_ibexa_connect.md' + 'cdp/cdp.md': 'raptor_cdp/raptor_cdp.md' + 'cdp/cdp_guide.md': 'raptor_cdp/raptor_cdp_guide.md' + 'cdp/cdp_installation.md': 'raptor_cdp/raptor_cdp_installation.md' + 'cdp/cdp_data_customization.md': 'raptor_cdp/raptor_cdp_data_customization.md' + 'cdp/cdp_data_export_schedule.md': 'raptor_cdp/raptor_cdp_data_export_schedule.md' + 'cdp/cdp_activation/cdp_activation.md': 'raptor_cdp/raptor_cdp_activation/raptor_cdp_activation.md' + 'cdp/cdp_activation/cdp_configuration.md': 'raptor_cdp/raptor_cdp_activation/raptor_cdp_configuration.md' + 'cdp/cdp_activation/cdp_data_export.md': 'raptor_cdp/raptor_cdp_activation/raptor_cdp_data_export.md' + 'cdp/cdp_activation/cdp_add_tracking.md': 'raptor_cdp/raptor_cdp_activation/raptor_cdp_add_tracking.md' - llmstxt: @@ -616,7 +631,7 @@ plugins: # The "> " prefix renders the description as a blockquote summary, # as expected by the llms.txt spec (https://llmstxt.org) markdown_description: >- - > Developer documentation for Ibexa DXP — architecture, APIs, templating, and extensibility for building and customizing Ibexa DXP projects. + > Developer documentation for Cohesivo — architecture, APIs, templating, and extensibility for building and customizing Ibexa DXP projects. # Pin links in the generated Markdown (and llms.txt) to this branch's # version instead of site_url's en/latest, without affecting the HTML @@ -626,5 +641,5 @@ plugins: full_output: llms-full.txt sections: # Built automatically when running MkDocs build based on MkDocs nav configuration, don't change - Ibexa DXP developer documentation: + Cohesivo developer documentation: - index.md diff --git a/theme/partials/eol_warning.html b/theme/partials/eol_warning.html index 94b9fa95436..ec0b46e7696 100644 --- a/theme/partials/eol_warning.html +++ b/theme/partials/eol_warning.html @@ -1,5 +1,5 @@
- This documentation is for a version that has reached its End Of Life. Such versions are no longer supported and don't receive security updates. Consider updating to a newer version. + This documentation is for a version that has reached its End Of Life. Such versions are no longer supported and don't receive security updates. Consider updating to a newer version.
diff --git a/tools/api_refs/.phpdoc/template/index.html.twig b/tools/api_refs/.phpdoc/template/index.html.twig index baa4764e976..020e55708ef 100644 --- a/tools/api_refs/.phpdoc/template/index.html.twig +++ b/tools/api_refs/.phpdoc/template/index.html.twig @@ -5,7 +5,7 @@

PHP API Reference

- Ibexa DXP's public PHP API is defined in the + Cohesivo's public PHP API is defined in the Ibexa\Contracts namespace. Ibexa promises backward compatibility to API consumers.