Skip to content

Commit fea2257

Browse files
Merge branch 'master' into IBX-9415
2 parents dbdf6ae + 761ad96 commit fea2257

File tree

44 files changed

+66
-67
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+66
-67
lines changed

docs/administration/admin_panel/corporate_admin_panel.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ There, in the **Corporate** section, you can find basic information about existi
1010

1111
![Corporate section](admin_panel_corporate.png "Corporate section")
1212

13-
For more information, see [Customer management](https://doc.ibexa.co/projects/userguide/en/latest/customer_management/manage_customers/).
13+
For more information, see [Customer management]([[= user_doc =]]/customer_management/manage_customers/).

docs/administration/back_office/content_tab_switcher.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The following example shows how to add a Meta tab with automatically assigned Ta
1111

1212
## Add Meta tab
1313

14-
Before you start adding the Meta tab, make sure the content type you want to edit has [Taxonomy Entry Assignment field type]([[= user_doc =]]/taxonomy/#assign-tag-to-content-from-taxonomy-tree).
14+
Before you start adding the Meta tab, make sure the content type you want to edit has [Taxonomy Entry Assignment field type]([[= user_doc =]]/content_management/taxonomy/work_with_tags/#assign-tag-to-content-from-taxonomy-tree).
1515

1616
Next, provide the semantic configuration under the `ibexa.system.<scope>.admin_ui_forms` [configuration key](configuration.md#configuration-files):
1717

docs/administration/back_office/customize_search_suggestion.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Customize search suggestion configuration and sources.
55
# Customize search suggestion
66

77
In the back office, when you start typing in the search field on the top bar, suggestions about what you could be looking for show up directly under the field.
8-
For more information about using this feature to search for content, see [User Documentation]([[= user_doc =]]/search/search_for_content).
8+
For more information about using this feature to search for content, see [User Documentation]([[= user_doc =]]/search/search_for_content/).
99

1010
## Configuration
1111

docs/administration/content_organization/content_types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Content types are organized into groups.
1717

1818
You can add your own groups here to keep your content types in better order.
1919

20-
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/).
20+
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/).
2121
For a detailed overview of the content model, see [Content model overview](content_model.md).
2222

2323
## Content type metadata

docs/administration/dashboard/customize_dashboard.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Customized dashboard displays a set of widgets selected by the user.
1010

1111
!!! tip
1212

13-
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).
13+
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).
1414

1515
## Manage permissions
1616

@@ -32,8 +32,8 @@ For more information, see [Customize storefront layout](customize_storefront_lay
3232

3333
Dashboard Builder provides set of ready-to-use blocks, for example, Common content, Quick actions, or [[= product_name =]] News.
3434

35-
For more information about available blocks, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/latest/getting_started/dashboard/dashboard_block_reference/).
35+
For more information about available blocks, see [User Documentation]([[= user_doc =]]/getting_started/dashboard/dashboard_block_reference/).
3636

3737
In addition to existing blocks available in Dashboard Builder, you can also create custom blocks.
3838

39-
To do it, follow the instruction on how to [create custom page block](create_custom_page_block.md).
39+
To do it, follow the instruction on how to [create custom page block](create_custom_page_block.md).

docs/administration/recent_activity/recent_activity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The [`activity_log/read`](policies.md#activity-log) policy gives a role the acce
4646
It can be limited to "Only own logs" ([`ActivityLogOwner`](limitation_reference.md#activitylogowner-limitation)).
4747

4848
The policy should be given to every roles having access to the back office, at least with the `ActivityLogOwner` owner limitation, to allow them to use the "Recent activity" block in the [default dashboard](configure_default_dashboard.md) or their [custom dashboard](customize_dashboard.md).
49-
This policy is required to view [activity log in user profile]([[= user_doc =]]/recent_activity/recent_activity/#user-profile), if [profile]([[= user_doc =]]/getting_started/get_started/#edit-user-profile) is enabled.
49+
This policy is required to view [activity log in user profile]([[= user_doc =]]/getting_started/get_started/#view-and-edit-user-profile), if [profile is enabled](update_from_4.5.md#user-profile).
5050

5151
!!! caution
5252

docs/ai_actions/install_ai_actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Run the following command, where `<database_name>` is the same name that you def
6868

6969
This command modifies the existing database schema by adding database configuration required for using AI Actions.
7070

71-
You can now restart you application and start [working with the AI Actions feature]([[= user_doc =]]/ai_actions/work_with_ai_actions//).
71+
You can now restart you application and start [working with the AI Actions feature]([[= user_doc =]]/ai_actions/work_with_ai_actions/).
7272

7373
### Install sample AI action configurations (optional)
7474

docs/cdp/cdp_guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ To create a personalized customer experience, you need to group your clients int
5353
[[= product_name =]] comes with a ready solution - segment groups.
5454
Segment group information is reused by various [[= product_name =]] functionalities, such as [Personalization](personalization_guide.md) or content targeting.
5555

56-
You can [create a segment group](https://doc.ibexa.co/projects/userguide/en/latest/personalization/segment_management/) in the back office of [[= product_name =]].
56+
You can [create a segment group]([[= user_doc =]]/personalization/segment_management/) in the back office of [[= product_name =]].
5757
It serves as a container for all segments data generated by [[= product_name_cdp =]].
5858
When you create a segment group, you need to provide its name and identifier.
5959
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.
133133
### Real-time action
134134

135135
Deliver relevant interactions in the right place at the right time for optimal results thanks to dynamic, real-time data updates.
136-
Take advantage of event-triggered communications which are aligned with your customers immediate interests.
136+
Take advantage of event-triggered communications which are aligned with your customers immediate interests.

docs/commerce/payment/configure_payment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,5 +50,5 @@ so that the system can identify which of your workflows handles the payment proc
5050

5151
## Configure payment methods
5252

53-
You can define payment methods [in the UI]([[= user_doc =]]/commerce/payment/configure_payment_method/).
53+
You can define payment methods [in the UI]([[= user_doc =]]/commerce/payment/work_with_payment_methods/).
5454
There is only one default payment method type available: `offline`, but you can configure more by [integrating with Payum](payum_integration.md), or [add custom ones](extend_payment.md).

docs/commerce/shipping_management/configure_shipment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,5 +43,5 @@ Reference it with `ibexa.repositories.<your_repository>.shipment.workflow: your_
4343

4444
## Configure shipping methods
4545

46-
You can define the shipping methods [in the UI]([[= user_doc =]]/commerce/shipping/configure_shipping_method/).
46+
You can define the shipping methods [in the UI]([[= user_doc =]]/commerce/shipping_management/work_with_shipping_methods/).
4747
The following shipping method types are available by default: `flat rate` and `free`.

0 commit comments

Comments
 (0)