Use [[= user_doc =]]

Author: adriendupuis

docs/administration/admin_panel/corporate_admin_panel.md

@@ -10,4 +10,4 @@ There, in the **Corporate** section, you can find basic information about existi
 
 ![Corporate section](admin_panel_corporate.png "Corporate section")
 
-For more information, see [Customer management](https://doc.ibexa.co/projects/userguide/en/latest/customer_management/manage_customers/).
+For more information, see [Customer management]([[= user_doc =]]/customer_management/manage_customers/).

docs/administration/content_organization/content_types.md

@@ -17,7 +17,7 @@ Content types are organized into groups.
 
 You can add your own groups here to keep your content types in better order.
 
-For a full tutorial, see [Add a content type](first_steps.md#add-a-content-type) or follow [User Documentation](https://doc.ibexa.co/projects/userguide/en/latest/content_management/create_edit_content_types/).
+For a full tutorial, see [Add a content type](first_steps.md#add-a-content-type) or follow [User Documentation]([[= user_doc =]]/content_management/create_edit_content_types/).
 For a detailed overview of the content model, see [Content model overview](content_model.md).
 
 ## Content type metadata

docs/administration/dashboard/customize_dashboard.md

@@ -10,7 +10,7 @@ Customized dashboard displays a set of widgets selected by the user.
 
 !!! tip
 
-     For detailed instruction on how to customize dashboards with the Dashboard Builder, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/latest/getting_started/dashboard/work_with_dashboard/#customize-dashboard).
+     For detailed instruction on how to customize dashboards with the Dashboard Builder, see [User Documentation]([[= user_doc =]]/getting_started/dashboard/work_with_dashboard/#customize-dashboard).
 
 ## Manage permissions
 
@@ -32,8 +32,8 @@ For more information, see [Customize storefront layout](customize_storefront_lay
 
 Dashboard Builder provides set of ready-to-use blocks, for example, Common content, Quick actions, or [[= product_name =]] News.
 
-For more information about available blocks, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/latest/getting_started/dashboard/dashboard_block_reference/).
+For more information about available blocks, see [User Documentation]([[= user_doc =]]/getting_started/dashboard/dashboard_block_reference/).
 
 In addition to existing blocks available in Dashboard Builder, you can also create custom blocks.
 
-To do it, follow the instruction on how to [create custom page block](create_custom_page_block.md).
+To do it, follow the instruction on how to [create custom page block](create_custom_page_block.md).

docs/cdp/cdp_guide.md

@@ -53,7 +53,7 @@ To create a personalized customer experience, you need to group your clients int
 [[= product_name =]] comes with a ready solution - segment groups.
 Segment group information is reused by various [[= product_name =]] functionalities, such as [Personalization](personalization_guide.md) or content targeting.
 
-You can [create a segment group](https://doc.ibexa.co/projects/userguide/en/latest/personalization/segment_management/) in the back office of [[= product_name =]].
+You can [create a segment group]([[= user_doc =]]/personalization/segment_management/) in the back office of [[= product_name =]].
 It serves as a container for all segments data generated by [[= product_name_cdp =]].
 When you create a segment group, you need to provide its name and identifier.
 Be careful while doing so, as 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.
@@ -133,4 +133,4 @@ Customize data to control what field type information you want to export.
 ### Real-time action
 
 Deliver relevant interactions in the right place at the right time for optimal results thanks to dynamic, real-time data updates.
-Take advantage of event-triggered communications which are aligned with your customers immediate interests.
+Take advantage of event-triggered communications which are aligned with your customers immediate interests.

docs/commerce/storefront/configure_storefront.md

@@ -10,7 +10,7 @@ The Storefront is accessible under the `<yourdomain>/product-catalog`.
 
 With the `ibexa/storefront` package, you can configure the product catalog and make it available to your shop users.
 
-Before you start configuring the Storefront, make sure you have created, configured, and published [catalogs](https://doc.ibexa.co/projects/userguide/en/latest/pim/work_with_catalogs/#create-catalogs) in the back office.
+Before you start configuring the Storefront, make sure you have created, configured, and published [catalogs]([[= user_doc =]]/pim/work_with_catalogs/#create-catalogs) in the back office.
 
 The configuration is available under the `ibexa.system.<scope>.storefront.catalog` [configuration key](configuration.md#configuration-files).
 It accepts the following values:

docs/content_management/content_model.md

@@ -12,7 +12,7 @@ Each content item is an instance of a content type.
 
 !!! tip
 
-    An introduction to the content model for non-developer users is available in User Documentation](https://doc.ibexa.co/projects/userguide/en/latest/content_management/content_model/).
+    An introduction to the content model for non-developer users is available in User Documentation]([[= user_doc =]]/content_management/content_model/).
 
 ## Content items
 

docs/content_management/locations.md

@@ -75,7 +75,7 @@ It contains user group content items.
 
 ### Forms [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]]
 
-**Forms** is the top level location that is intended for Forms created using the [Form Builder](https://doc.ibexa.co/projects/userguide/en/latest/content_management/work_with_forms/#create-forms).
+**Forms** is the top level location that is intended for Forms created using the [Form Builder]([[= user_doc =]]/content_management/work_with_forms/#create-forms).
 
 ![Forms](content_management_forms.png "Forms")
 

docs/customer_management/cp_applications.md

@@ -9,7 +9,7 @@ New business customers can apply for a company account.
 Applications go through the approval process in the back office where they can be accepted, rejected or put on hold.
 If they're accepted, the business partner receives an invitation link to the Customer Portal, where they can set up their team and manage their account.
 
-For more information on company self-registration, see [user guide documentation](https://doc.ibexa.co/projects/userguide/en/latest/customer_management/company_self_registration/).
+For more information on company self-registration, see [user guide documentation]([[= user_doc =]]/customer_management/company_self_registration/).
 If provided options are too limited, you can customize an approval process by yourself.
 
 ## Roles and policies
@@ -113,4 +113,3 @@ The subscriber only informs that the status has been changed (line 72).
 Now, if you click the **Verify** button during application review, the application gets **Verify** status.
 
 ![Verify status](img/cp_verify_status.png)
-

docs/multisite/languages/languages.md

@@ -22,7 +22,7 @@ However, even if work on a draft takes time and other translations are updated i
 ### Adding available languages
 
 The multilanguage system operates based on a global translation list that contains all languages available in the installation.
-Languages can be [added to this list from the **Admin** panel](https://doc.ibexa.co/projects/userguide/en/latest/content_management/translate_content/) in the back office.
+Languages can be [added to this list from the **Admin** panel]([[= user_doc =]]/content_management/translate_content/) in the back office.
 After adding a language be sure to dump all assets to the file system:
 
 ```

docs/templating/twig_function_reference/content_twig_functions.md

@@ -71,7 +71,7 @@ If the content item doesn't have a translation in the prioritized or passed lang
 
 ### `ibexa_seo_is_empty()`
 
-`ibexa_seo_is_empty()` returns a Boolean value which indicates whether [SEO](https://doc.ibexa.co/projects/userguide/en/latest/search_engine_optimization/seo/) data is available for the content item that is passed as an argument.
+`ibexa_seo_is_empty()` returns a Boolean value which indicates whether [SEO]([[= user_doc =]]/search_engine_optimization/seo/) data is available for the content item that is passed as an argument.
 
 | Argument | Type | Description |
 |---------------|------|-------------|
@@ -83,7 +83,7 @@ If the content item doesn't have a translation in the prioritized or passed lang
 
 ### `ibexa_seo()`
 
-`ibexa_seo()` attaches [SEO](https://doc.ibexa.co/projects/userguide/en/latest/search_engine_optimization/seo/) data to the content item's HTML code.
+`ibexa_seo()` attaches [SEO]([[= user_doc =]]/search_engine_optimization/seo/) data to the content item's HTML code.
 
 | Argument | Type | Description |
 |---------------|------|-------------|