From 8535c224528d11c3ab540a25eea9f955b5059545 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Tue, 21 Apr 2026 13:49:49 +0200 Subject: [PATCH 1/2] no-emphasis-as-heading --- .../admin_panel/roles_admin_panel.md | 4 ++-- docs/api/rest_api/rest_api_authentication.md | 2 +- docs/content_management/images/images.md | 6 +++--- .../cache/persistence_cache.md | 2 +- .../elasticsearch/elasticsearch_overview.md | 2 +- .../migrating_from_ez_publish_platform.md | 16 ++++++++-------- 6 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/administration/admin_panel/roles_admin_panel.md b/docs/administration/admin_panel/roles_admin_panel.md index cf26343d98..bd6bb31b01 100644 --- a/docs/administration/admin_panel/roles_admin_panel.md +++ b/docs/administration/admin_panel/roles_admin_panel.md @@ -10,7 +10,7 @@ To give users an access to your website you need to assign them roles in the **A Each role consists of: -**Policies** +## Policies ![Policies](admin_panel_policies.png "Policies") @@ -27,7 +27,7 @@ See [example use case](permission_use_cases.md#restrict-editing-to-part-of-the-t For more information, see [Limitation reference](limitation_reference.md). -**Assignments** +## Assignments ![Assignments](admin_panel_assignments.png "Assignments") diff --git a/docs/api/rest_api/rest_api_authentication.md b/docs/api/rest_api/rest_api_authentication.md index f7f77366f8..de97086451 100644 --- a/docs/api/rest_api/rest_api_authentication.md +++ b/docs/api/rest_api/rest_api_authentication.md @@ -353,7 +353,7 @@ For details, see [RFC 2617](https://datatracker.ietf.org/doc/html/rfc2617). Most HTTP client libraries and REST libraries support this method. [Creating content with binary attachments](rest_requests.md#creating-content-with-binary-attachments) is an example of using basic authentication with [cURL](https://www.php.net/manual/en/book.curl.php) and its `CURLOPT_USERPWD`. -**Raw HTTP request with basic authentication** +See the following raw HTTP request with basic authentication example: ```http GET / HTTP/1.1 diff --git a/docs/content_management/images/images.md b/docs/content_management/images/images.md index fc58207a04..0716111318 100644 --- a/docs/content_management/images/images.md +++ b/docs/content_management/images/images.md @@ -168,19 +168,19 @@ If there is no configuration assigned to the `binary_handler`, the placeholder g ##### Configuration examples: -**Example 1 - placeholders with basic information about original image** +##### Example 1 - placeholders with basic information about original image ```yaml [[= include_file('code_samples/back_office/images/config/packages/images_basic.yaml') =]] ``` -**Example 2 - placeholders from remote source** +##### Example 2 - placeholders from remote source ```yaml [[= include_file('code_samples/back_office/images/config/packages/images_remote.yaml') =]] ``` -**Example 3 - placeholders from live version of a site** +##### Example 3 - placeholders from live version of a site ```yaml [[= include_file('code_samples/back_office/images/config/packages/images_live.yaml') =]] diff --git a/docs/infrastructure_and_maintenance/cache/persistence_cache.md b/docs/infrastructure_and_maintenance/cache/persistence_cache.md index 4b34d52a2d..f33fc1dd7e 100644 --- a/docs/infrastructure_and_maintenance/cache/persistence_cache.md +++ b/docs/infrastructure_and_maintenance/cache/persistence_cache.md @@ -54,7 +54,7 @@ Use of Redis as shared cache back end is a requirement for use in clustering set For an overview of this feature, see [Clustering](clustering.md). Filesystem adapters, for example, are **not** intended to be used over a shared filesystem. -**Cache service** +### Cache service The underlying cache system is exposed as an `ibexa.cache_pool` service, and can be reused by any other service as described in the [Using Cache service](#using-cache-service) section. diff --git a/docs/search/search_engines/elasticsearch/elasticsearch_overview.md b/docs/search/search_engines/elasticsearch/elasticsearch_overview.md index 8902ba97f0..3951aad368 100644 --- a/docs/search/search_engines/elasticsearch/elasticsearch_overview.md +++ b/docs/search/search_engines/elasticsearch/elasticsearch_overview.md @@ -17,7 +17,7 @@ Thanks to this mechanism, it's able to achieve fast response. For a detailed description of advanced settings that you might require in a specific production environment, see the documentation provided by Elastic. Start with the [Set up Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/8.19/setup.html) section. -**Prerequisite** +## Prerequisite To proceed you need to be familiar with how indexing, filtering and queries work. 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 c90101af41..08ab4fcb64 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 @@ -427,9 +427,11 @@ Once you have fixed all the dump files in `ezxmltext-export/`, you may skip the `php -d memory_limit=1536M bin/console ezxmltext:import-xml --export-dir=ezxmltext-export -v` +##### Typical problems + Typical problems that needs manual fixing: -**Duplicate XHTML IDs** +###### Duplicate XHTML ID XHTML IDs needs to be unique. The following `ezxmltext` results in a warning: @@ -445,7 +447,7 @@ XHTML IDs needs to be unique. The following `ezxmltext` results in a warning: The conversion tool replaces the duplicate id (`inv5`) with a random value. If you need the ID value to match your CSS, you need to change it manually. The conversion tool also complains about IDs which contain invalid characters. -**Links with non-existing `object_remote_id` or `node_remote_id`.** +###### Links with non-existing `object_remote_id` or `node_remote_id` In `ezxmltext` you may have links which refer to other objects by their remote ID. This isn't supported in `richtext`, so the conversion tool must look up such remote IDs and replace them with the `object_id` or `node_id`. If the conversion tool cannot find the object by its remote id, it issues a warning about it. @@ -457,7 +459,7 @@ In older eZ Publish databases you may also have invalid links due to lack of ref When the conversion tool detects links with no reference it issues a warning and rewrite the URL to point to current page (`href="#"`). -**``** +###### `` The `` tag isn't yet supported in eZ Platform. @@ -465,7 +467,7 @@ When you're ready to migrate your eZ Publish XmlText content to the eZ Platform `php -d memory_limit=1536M bin/console ezxmltext:convert-to-richtext --export-dir=ezxmltext-export --export-dir-filter=notice,warning,error --concurrency 4 -v` -**Custom tags and attributes** +###### Custom tags and attributes eZ Platform now supports custom tags, including inline custom tags, and limited use of custom tag attributes. After migrating to RichText, you need to adapt your custom tag config for eZ Platform and rewrite the custom tags in Twig. @@ -593,18 +595,16 @@ new EzSystems\EzFlowMigrationToolkitBundle\EzSystemsEzFlowMigrationToolkitBundle bin/console cache:clear ``` -**4.** Run the script with the following parameters: +**4.** Run the script below with the following parameters: - absolute path of your legacy application - list of .ini files which define your legacy blocks -**Script command** - ``` bash bin/console ezflow:migrate —ini= [—ini= ...] ``` -**Example of the migration script command** +Example usage: ``` bash bin/console ezflow:migrate /var/www/legacy.application.com/ —ini=extension/myapplication/settings/block.ini.append.php From 7db38daccc58c092a8e23abfecf2aec7ce4af4fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Tue, 21 Apr 2026 14:56:21 +0200 Subject: [PATCH 2/2] table-column-count --- .markdownlint-cli2.yaml | 3 + .../back_office_elements/add_dropdowns.md | 4 +- .../reusable_components.md | 2 +- docs/api/event_reference/content_events.md | 22 +-- .../event_reference/content_type_events.md | 10 +- docs/api/event_reference/language_events.md | 8 +- docs/api/event_reference/location_events.md | 10 +- .../event_reference/object_state_events.md | 8 +- docs/api/event_reference/other_events.md | 6 +- docs/api/event_reference/page_events.md | 8 +- docs/api/event_reference/role_events.md | 14 +- docs/api/event_reference/section_events.md | 4 +- docs/api/event_reference/site_events.md | 2 +- docs/api/event_reference/trash_events.md | 10 +- docs/api/event_reference/url_events.md | 10 +- docs/api/event_reference/user_events.md | 16 +- .../transactional_emails_parameters.md | 84 +++++----- .../field_type_reference/dateandtimefield.md | 10 +- .../field_type_reference/keywordfield.md | 6 +- .../field_type_reference/maplocationfield.md | 18 +-- .../field_type_reference/relationfield.md | 6 +- .../field_type_reference/relationlistfield.md | 4 +- .../taxonomyentryfield.md | 2 +- .../field_type_reference/timefield.md | 6 +- .../field_type_reference/userfield.md | 2 +- docs/permissions/policies.md | 144 +++++++++--------- .../search_criteria_reference.md | 2 +- .../urls_and_routes/custom_breadcrumbs.md | 2 +- 28 files changed, 213 insertions(+), 210 deletions(-) diff --git a/.markdownlint-cli2.yaml b/.markdownlint-cli2.yaml index 2c1a1304e5..5d14206277 100644 --- a/.markdownlint-cli2.yaml +++ b/.markdownlint-cli2.yaml @@ -14,6 +14,9 @@ config: table-pipe-style: style: leading_and_trailing + no-emphasis-as-heading: true + table-column-count: true + ignores: - "docs/snippets/**" - "docs/index.md" diff --git a/docs/administration/back_office/back_office_elements/add_dropdowns.md b/docs/administration/back_office/back_office_elements/add_dropdowns.md index 811f3fd3b7..c3ba474859 100644 --- a/docs/administration/back_office/back_office_elements/add_dropdowns.md +++ b/docs/administration/back_office/back_office_elements/add_dropdowns.md @@ -108,13 +108,13 @@ The following attributes are available: |---|------|----------| |`source`| - |What is currently defined in the `