-
The newest LTS Update is Discounts
-
Install it to reduce prices on specific products, making deals more attractive to potential buyers.
+
The newest LTS Update is the Symbol attribute
+
Use it to store standarized identifiers of your products.
diff --git a/docs/permissions/limitation_reference.md b/docs/permissions/limitation_reference.md
index 09e49157c9..01b3cddad9 100644
--- a/docs/permissions/limitation_reference.md
+++ b/docs/permissions/limitation_reference.md
@@ -320,6 +320,41 @@ This limitation can be used as a role limitation.
For more information on how to restrict user's access to part of the subtree, see [the example in the Admin management section](permission_use_cases.md#restrict-editing-to-part-of-the-tree).
+## Taxonomy limitation
+
+The taxonomy (`Taxonomy`) limitation specifies with which [taxonomies](taxonomy.md) (tags, product categories, or custom ones) user can interact.
+
+The supported policies are:
+
+- `taxonomy/read`
+- `taxonomy/manage`
+- `taxonomy/assign`
+
+### Possible values
+
+|Value|UI value|Description|
+|------|------|------|
+|Taxonomy identifiers|Taxonomy names|List of allowed taxonomies|
+
+
+## Taxonomy Subtree limitation
+
+The taxonomy subtree (`TaxonomySubtree`) limitation specifies whether the user has access to a specific subtree within the [taxonomy](taxonomy.md) tree.
+Once a tag is selected, user can interact with it and all the child tags below it in the taxonomy tree.
+In addition, it grants read-only access to all the parent tags (up to the taxonomy root) so that the user can see the context.
+
+The supported policies are:
+
+- `taxonomy/read`
+- `taxonomy/manage`
+- `taxonomy/assign`
+
+### Possible values
+
+|Value|UI value|Description|
+|------|------|------|
+|Tag IDs|Selected tags| All valid Tag IDs are allowed|
+
## Version Lock limitation
The Version Lock (`VersionLock`) limitation specifies whether the user can perform actions, for example, edit or unlock, on content items that are in a workflow.
diff --git a/docs/pim/attributes/symbol_attribute_type.md b/docs/pim/attributes/symbol_attribute_type.md
new file mode 100644
index 0000000000..7f541efc0f
--- /dev/null
+++ b/docs/pim/attributes/symbol_attribute_type.md
@@ -0,0 +1,138 @@
+---
+description: Create a symbol attribute type that enables for the efficient representation of string-based values while enforcing their format in product specifications.
+edition: lts-update
+---
+
+# Symbol attribute type
+
+The Symbol attribute type LTS update enables the efficient representation of string-based data and enforces their format in product specifications.
+
+This feature allows you to store standard product identifiers (such as EAN or ISBN) in the [Product Information Management](pim_guide.md) system.
+
+## Installation
+
+### Download the bundle
+
+To get the most recent stable version of this bundle, open a command terminal, navigate to your project directory, and run the following command:
+
+``` bash
+composer require ibexa/product-catalog-symbol-attribute
+```
+
+### Enable the bundle
+
+Symfony Flex enables and configures the `IbexaProductCatalogSymbolAttributeBundle` automatically.
+If you don't use it, you can manually enable this bundle by adding the line below to the Kernel of your project:
+
+``` php
+// config/bundles.php
+
+return [
+ // ...
+ Ibexa\Bundle\ProductCatalogSymbolAttribute\IbexaProductCatalogSymbolAttributeBundle::class => ['all' => true],
+ // ...
+];
+```
+
+### Update database schema
+
+To store symbol attribute values, the `IbexaProductCatalogSymbolAttributeBundle` needs an extra table.
+The following SQL query can be used to build the required database structure:
+
+=== "MySQL"
+
+ ``` sql
+ [[= include_file('code_samples/symbol_attribute/config/mysql/symbol_attribute.sql', glue=' ') =]]
+ ```
+
+=== "PostgreSQL"
+
+ ``` sql
+ [[= include_file('code_samples/symbol_attribute/config/postgresql/symbol_attribute.sql', glue=' ') =]]
+ ```
+
+### Create symbol attribute definition (optional)
+
+Now, you're able to define symbol attributes at this point.
+
+To create symbol attribute definition, in the back office, go to **Product catalog** -> **Attributes**, and click **Create**.
+Then, choose **Symbol** attribute type.
+
+## Build-in symbol attribute formats
+
+The built-in symbol attribute formats in `ibexa/product-catalog-symbol-attribute` are listed below:
+
+| Name | Description | Example |
+|-----------------|-----------------|-----------------|
+| Generic | Accepts any string value | #FR1.2 |
+| Generic (alphabetic characters only) | Accepts any string value that contais only letters | ABCD |
+| Generic (digits only) | Accepts any string value that contais only digits | 123456 |
+| Generic (alphanumeric characters only) | Accepts any string value that contains only letters or digits | 2N6405G |
+| Generic (hexadecimal digits only) | Accepts any string value that contains only hexadecimal digits (digits or A-F characters) | DEADBEEF |
+| EAN-8 | European Article Number (8 characters) | 96385074 |
+| EAN-13 | European Article Number (13 characters) | 5023920187205 |
+| EAN-14 | European Article Number (14 characters) | 12345678901231 |
+| ISBN-10 | International Standard Book Number (10 characters) | 0-19-852663-6 |
+| ISBN-13 | International Standard Book Number (13 characters) | 978-1-86197-876-9 |
+
+!!! caution
+
+ Maximum length of the symbol value is 160 characters.
+
+## Create custom symbol attribute format
+
+Under the `ibexa_product_catalog_symbol_attribute.formats` key, you can use configuration to create your own symbol format.
+
+See the example below:
+
+``` yaml
+ibexa_product_catalog_symbol_attribute:
+ formats:
+ manufacturer_part_number:
+ name: 'Manufacturer Part Number'
+ pattern: '/^[A-Z]{3}-\d{5}$/'
+ examples:
+ - 'RPI-14645'
+ - 'MSS-24827'
+ - 'SEE-15444'
+```
+
+This following example specifies the format for a "Manufacturer Part Number", defined with the `manufacturer_part_number` identifier.
+
+The pattern is specified using a regular expression.
+According to the pattern option, the attribute value:
+
+- must be a string
+- begins with three capital letters (A-Z), followed by a hyphen ("-")
+- ends with five digits (0-9), with no other characters before or after
+
+Certain formats, such as the International Standard Book Number (ISBN-10) and the European Article Number (EAN-13), contain checksum digits and are self-validating.
+
+To validate checksum of symbol:
+
+1\. Create a class implementing the [`\Ibexa\Contracts\ProductCatalogSymbolAttribute\Value\ChecksumInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalogSymbolAttribute-Value-ChecksumInterface.html) interface.
+
+2\. Register the class as a service using the `ibexa.product_catalog.attribute.symbol.checksum` tag and specify the format identifier using the `format` attribute.
+
+See below the example implementation of checksum validation using Luhn formula:
+
+``` php
+[[= include_file('code_samples/pim/Symbol/Format/Checksum/LuhnChecksum.php') =]]
+```
+
+Example service definition:
+
+``` yaml
+services:
+ App\PIM\Symbol\Format\Checksum\LuhnChecksum:
+ tags:
+ - name: ibexa.product_catalog.attribute.symbol.checksum
+ format: my_format
+```
+The format attribute (`my_format`) is the identifier used under the `ibexa_product_catalog_symbol_attribute.formats` key.
+
+## Search for products with given symbol attribute
+
+You can use `SymbolAttribute` Search Criterion to find products by symbol attribute:
+
+For more information, see [SymbolAttribute Criterion](symbolattribute_criterion.md).
diff --git a/docs/release_notes/ibexa_dxp_v4.6.md b/docs/release_notes/ibexa_dxp_v4.6.md
index efa690c945..e630e9d6c4 100644
--- a/docs/release_notes/ibexa_dxp_v4.6.md
+++ b/docs/release_notes/ibexa_dxp_v4.6.md
@@ -10,6 +10,110 @@ month_change: true
+[[% set version = 'v4.6.22' %]]
+[[= release_note_entry_begin("Symbol attribute", '2025-08-05', ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature']) =]]
+
+The Symbol attribute allows you to store standarized identifiers of your products in the [Product Information Management](pim_guide.md) system.
+
+For more information, see [Symbol attribute type](symbol_attribute_type.md).
+
+#### PHP API
+
+The PHP API has been enhanced with the following new classes:
+
+- [`Ibexa\Contracts\ProductCatalogSymbolAttribute\Search\Criterion\SymbolAttribute`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalogSymbolAttribute-Search-Criterion-SymbolAttribute.html)
+- [`Ibexa\Contracts\ProductCatalogSymbolAttribute\Value\ChecksumInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalogSymbolAttribute-Value-ChecksumInterface.html)
+
+[[= release_note_entry_end() =]]
+
+[[= release_note_entry_begin("Discounts " + version, '2025-08-05', ['LTS Update', 'Commerce']) =]]
+
+#### Global discount codes limits
+
+- You can now [limit the number of times](discounts_guide.md#discount-codes) a discount code can be used before it expires. The discounts created before this release are set to unlimited global usage
+
+#### Discount codes prioritization
+
+- Discounts with discount codes now have priority over the other discounts
+
+#### Discount codes migrations
+
+- You can now create discount codes using [data migrations](importing_data.md#discount-codes)
+
+#### PHP API
+
+The PHP API has been enhanced with the following new classes:
+
+- [`Ibexa\Contracts\Discounts\Value\DiscountConditionsInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Value-DiscountConditionsInterface.html)
+- [`Ibexa\Contracts\Discounts\Value\Query\SortClause\OverridePrioritization`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Value-Query-SortClause-OverridePrioritization.html)
+
+[[= release_note_entry_end() =]]
+[[= release_note_entry_begin("Ibexa DXP " + version, '2025-08-05', ['Headless', 'Experience', 'Commerce', 'New feature']) =]]
+
+#### Special characters in online editor
+
+The [online editor](online_editor_guide.md) now allows to easily enter special characters like currency symbols.
+It uses the [special characters plugin](https://ckeditor.com/docs/ckeditor5/latest/features/special-characters.html),
+
+
+
+#### Support for Solr 9
+
+With this release, [[= product_name =]] starts supporting [Solr 9](requirements.md#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](ai_actions.md) feature.
+
+#### Improved content creation interface
+
+The editing interface of the back office has been improved to better highlight the language, creator, and the publication date when working with content items.
+
+
+
+#### Twig Components
+
+With the latest changes to [Twig Components](components.md), you can:
+
+- set component priority when using YAML configuration
+- render a menu with help of the new Menu component
+
+The list of built-in Twig Component groups has been expanded and includes:
+
+- one new group for the [back office](custom_components.md) (`admin-ui-versions-table-before`)
+- eight new groups for [storefront](customize_storefront_layout.md#customize-with-twig-components)
+
+#### Taxonomy Subtree limitation
+
+You can now manage access to [taxonomy items](taxonomy.md) more effectively by using the new [Taxonomy Subtree limitation](limitation_reference.md#taxonomy-subtree-limitation).
+
+In addition, you can now use the [Taxonomy limitation](limitation_reference.md#taxonomy-limitation) together with the `taxonomy/assign` policy.
+
+#### Pagination for ezobjectrelationlist in GraphQL
+
+To improve performance and gain greater control over the returned responses from the [GraphQL API](graphql.md), you can now [enable pagination](relationlistfield.md#enable-pagination-in-graphql) of relations specified using the RelationList field type.
+
+#### Breaking changes
+
+- The `Ibexa\FieldTypeRichText\RichText\Validator\CustomTagsValidator` class has been renamed to `Ibexa\FieldTypeRichText\RichText\Validator\CustomTemplateValidator`, expanding its responsibility to validate both [custom tags](extend_online_editor.md#configure-custom-tags) and [custom styles](extend_online_editor.md#configure-custom-styles)
+- The `Ibexa\Contracts\AdminUi\Permission\PermissionCheckContextProviderInterface` interface has been removed
+- The `Ibexa\Contracts\AdminUi\Values\PermissionCheckContext` class has been removed
+
+#### PHP API
+
+The PHP API has been enhanced with the following new classes:
+
+- [`Ibexa\Contracts\Cart\Exception\VatCalculationExceptionInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Cart-Exception-VatCalculationExceptionInterface.html)
+- [`Ibexa\Contracts\Core\Repository\Values\Notification\CriterionHandlerInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Notification-CriterionHandlerInterface.html)
+- [`Ibexa\Contracts\Core\Repository\Values\Notification\Query\CriterionInterface`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Notification-Query-CriterionInterface.html)
+- [`Ibexa\Contracts\Core\Repository\Values\Notification\Query\Criterion\DateCreated`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Notification-Query-Criterion-DateCreated.html)
+- [`Ibexa\Contracts\Core\Repository\Values\Notification\Query\NotificationQuery`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Notification-Query-NotificationQuery.html)
+- [`Ibexa\Contracts\ProductCatalog\Values\Product\Query\Criterion\AbstractPriceRange`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Values-Product-Query-Criterion-AbstractPriceRange.html)
+- [`Ibexa\Contracts\ProductCatalog\Values\Product\Query\Criterion\CustomPriceRange`](https://doc.ibexa.co/en/4.6/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Values-Product-Query-Criterion-CustomPriceRange.html)
+
+#### Full changelog
+
+[[% include 'snippets/release_46.md' %]]
+[[= release_note_entry_end() =]]
+
[[% set version = 'v4.6.21' %]]
[[= release_note_entry_begin("Discounts " + version, '2025-06-11', ['LTS Update', 'Commerce']) =]]
diff --git a/docs/release_notes/img/4.6_improved_editing.png b/docs/release_notes/img/4.6_improved_editing.png
new file mode 100644
index 0000000000..b514cd145d
Binary files /dev/null and b/docs/release_notes/img/4.6_improved_editing.png differ
diff --git a/docs/release_notes/img/4.6_special_characters.png b/docs/release_notes/img/4.6_special_characters.png
new file mode 100644
index 0000000000..37f278b2f3
Binary files /dev/null and b/docs/release_notes/img/4.6_special_characters.png differ
diff --git a/docs/search/criteria_reference/product_search_criteria.md b/docs/search/criteria_reference/product_search_criteria.md
index a31f6cabbc..35a3948ac3 100644
--- a/docs/search/criteria_reference/product_search_criteria.md
+++ b/docs/search/criteria_reference/product_search_criteria.md
@@ -42,4 +42,4 @@ Search Criterion let you filter product by specific attributes, for example, col
|[RangeMeasurementAttributeMinimum](rangemeasurementattributeminimum_criterion.md)|Minimum value of product's measurement attribute|
|[SelectionAttribute](selectionattribute_criterion.md)|Value of product's selection attribute|
|[SimpleMeasurementAttribute](simplemeasurementattribute_criterion.md)|Value of product's measurement attribute|
-
+|[SymbolAttribute](symbolattribute_criterion.md)|Value of product's symbol attribute|
diff --git a/docs/search/criteria_reference/symbolattribute_criterion.md b/docs/search/criteria_reference/symbolattribute_criterion.md
new file mode 100644
index 0000000000..53c6a241cd
--- /dev/null
+++ b/docs/search/criteria_reference/symbolattribute_criterion.md
@@ -0,0 +1,21 @@
+---
+description: SymbolAttribute Criterion
+edition: lts-update
+---
+
+# SymbolAttributeCriterion
+
+The `SymbolAttribute` Search Criterion searches for products by [symbol attribute](symbol_attribute_type.md).
+
+## Arguments
+
+- `identifier` - identifier of the format
+- `value` - array with the values to search for
+
+## Example
+
+### PHP
+
+``` php
+[[= include_file('code_samples/back_office/search/src/Query/SymbolAttributeTypeQuery.php') =]]
+```
\ No newline at end of file
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 fd619b8ab5..7fd54664a6 100644
--- a/docs/search/search_engines/solr_search_engine/install_solr.md
+++ b/docs/search/search_engines/solr_search_engine/install_solr.md
@@ -13,30 +13,71 @@ For configuring Solr in other ways, including examples, see [Solr Cores and `sol
!!! note "Solr versions"
- Supported Solr versions are Solr 7 and 8. Using most recent version of Solr 7.7 or 8.11 is recommended.
+ Supported Solr versions are Solr 7, 8 and 9.
+ Using the most recent version of Solr is recommended.
Download and extract Solr:
- [solr-7.7.2.tgz](http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.tgz) or [solr-7.7.2.zip](http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.zip)
- [solr-8.11.2.tgz](https://www.apache.org/dyn/closer.lua/lucene/solr/8.11.2/solr-8.11.2.tgz) or [solr-8.11.2.zip](https://www.apache.org/dyn/closer.lua/lucene/solr/8.11.2/solr-8.11.2.zip)
+- [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. In the example below from the root of your project to the place you extracted Solr:
+Copy the necessary configuration files.
+The examples below copy from the root of your DXP project to the place you've extracted Solr:
-``` bash
-# Make sure to replace the /opt/solr/ path with where you have placed Solr
-cd /opt/solr
-mkdir -p server/ibexa/template
-cp -R
/vendor/ibexa/solr/src/lib/Resources/config/solr/* server/ibexa/template
-cp server/solr/configsets/_default/conf/{solrconfig.xml,stopwords.txt,synonyms.txt} server/ibexa/template
-cp server/solr/solr.xml server/ibexa
-
-# Modify solrconfig.xml to remove the section that doesn't agree with your schema
-sed -i.bak '//d' server/ibexa/template/solrconfig.xml
-
-# Start Solr (but apply autocommit settings below first if you need to)
-bin/solr -s ibexa
-bin/solr create_core -c collection1 -d server/ibexa/template
-```
+=== "Solr 9"
+
+ [[= product_name =]] provides the following required configuration files:
+
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/solr.languages` directory
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/managed-schema.xml`
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/custom-fields-types-solr9.xml`
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/language-fieldtypes.xml`
+
+
+ ``` bash
+ # Make sure to replace the /opt/solr/ path with where you have placed Solr
+ cd /opt/solr
+ mkdir -p server/ibexa/template/conf
+ cp -R /vendor/ibexa/solr/src/lib/Resources/config/solr/solr.languages server/ibexa/template/conf
+ cp -R /vendor/ibexa/solr/src/lib/Resources/config/solr/{managed-schema.xml,custom-fields-types-solr9.xml,language-fieldtypes.xml} server/ibexa/template/conf
+ cp server/solr/configsets/_default/conf/{solrconfig.xml,stopwords.txt,synonyms.txt} server/ibexa/template/conf
+ cp server/solr/solr.xml server/ibexa
+
+ # Modify solrconfig.xml to remove the section that doesn't agree with your schema
+ sed -i.bak '//d' server/ibexa/template/conf/solrconfig.xml
+
+ # Start Solr (but apply autocommit settings below first if you need to)
+ # The configuration path is an absolute path
+ bin/solr -s ibexa
+ bin/solr create_core -c collection1 -d /opt/solr/server/ibexa/template
+ ```
+
+=== "Solr 7 and 8"
+
+ [[= product_name =]] provides the following required configuration files:
+
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/solr.languages` directory
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/schema.xml`
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/custom-fields-types.xml`
+ - `vendor/ibexa/solr/src/lib/Resources/config/solr/language-fieldtypes.xml`
+
+ ``` bash
+ # Make sure to replace the /opt/solr/ path with where you have placed Solr
+ cd /opt/solr
+ mkdir -p server/ibexa/template
+ cp -R /vendor/ibexa/solr/src/lib/Resources/config/solr/solr.languages server/ibexa/template
+ cp -R /vendor/ibexa/solr/src/lib/Resources/config/solr/{schema.xml,custom-fields-types.xml,language-fieldtypes.xml} server/ibexa/template
+ cp server/solr/configsets/_default/conf/{solrconfig.xml,stopwords.txt,synonyms.txt} server/ibexa/template
+ cp server/solr/solr.xml server/ibexa
+
+ # Modify solrconfig.xml to remove the section that doesn't agree with your schema
+ sed -i.bak '//d' server/ibexa/template/solrconfig.xml
+
+ # Start Solr (but apply autocommit settings below first if you need to)
+ bin/solr -s ibexa
+ bin/solr create_core -c collection1 -d server/ibexa/template
+ ```
#### Set up SolrCloud
@@ -50,6 +91,8 @@ To set SolrCloud up follow [SolrCloud reference guide](https://solr.apache.org/g
### Continue Solr configuration
+#### Configure commit frequency
+
The bundle doesn't commit Solr index changes directly on repository updates, leaving it up to you to tune this using `solrconfig.xml` as best practice suggests.
This setting is **required** if you want to see the changes after publish.
@@ -69,9 +112,41 @@ It's strongly recommended to set-up `solrconfig.xml` like this:
```
+#### Configure spellcheck
+
+Configure the spellcheck component in `solrconfig.xml`:
+
+```xml
+
+
+ default
+ meta_content__text_t
+ solr.DirectSolrSpellChecker
+ internal
+ 0.5
+ 2
+ 1
+ 5
+ 4
+ 0.01
+
+
+```
+
+Add this `spellcheck` component to the `/select` request handler:
+
+```xml
+
+
+ spellcheck
+
+
+
+```
+
### Generate Solr configuration automatically
-The command line tool `bin/generate-solr-config.sh` generates Solr 7 configuration automatically.
+The command line tool `bin/generate-solr-config.sh` generates Solr configuration automatically.
It can be used for deploying to [[= product_name_cloud =]] (Platform.sh) and on-premise installs.
Execute the script from the [[= product_name =]] root directory for further information:
@@ -91,6 +166,16 @@ The config further below assumes you have parameters set up for Solr DSN and sea
env(SOLR_CORE): collection1
```
+### Configure Solr version
+
+When using Solr 9, it's required to set the `version` parameter with the Solr version.
+The parameter is optional when using lower Solr versions.
+
+``` yaml
+ibexa_solr:
+ version: '9.8.1'
+```
+
### Single-core example (default)
Out of the box in [[= product_name =]] the following is enabled for a setup:
@@ -145,6 +230,7 @@ If full language analysis features are preferred, then each language can be conf
``` yaml
ibexa_solr:
+ version: '9.8.1' # Required only if using Solr 9
endpoints:
endpoint0:
dsn: '%solr_dsn%'
diff --git a/docs/templating/components.md b/docs/templating/components.md
index adcd682604..16bbfb807e 100644
--- a/docs/templating/components.md
+++ b/docs/templating/components.md
@@ -8,9 +8,12 @@ month_change: true
Twig Components are widgets (for example, **My dashboard** blocks from Headless edition) and HTML code (for example, a tag for loading JS or CSS files) that you can inject into the existing templates to customize and extend the user interface.
They are combined into groups that are rendered in designated templates.
-Built-in Twig Component groups are available for the [back office](custom_components.md), but you can create your own for use anywhere.
+Twig Component groups are available for:
-To learn which groups are available in a given view, use the [integration with Symfony Profiler](#symfony-profiler-integration).
+- [back office](custom_components.md)
+- [storefront](customize_storefront_layout.md)
+
+To learn which groups are available in a given view, use the [integration Symfony Profiler](#symfony-profiler-integration).
## Create Twig Component
@@ -44,11 +47,12 @@ ibexa_twig_components:
# Component name
google_tag_manager:
type: script
+ priority: 50
arguments:
src: 'https://...'
```
-The Component priority cannot be specified when using the YAML configuration, but it allows you to use the built-in components to quickly achieve common goals.
+YAML configuration allows you to use the built-in components to quickly achieve common goals.
You can use an unique group name when creating a Twig Component to create your own group.
@@ -56,11 +60,25 @@ You can use an unique group name when creating a Twig Component to create your o
| Name | Description | YAML type |
|---|---|---|
+| [Controller](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/ControllerComponent.php) | Renders a Symfony controller |`controller` |
+| [HTML](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/HtmlComponent.php) | Renders static HTML |`html` |
+| [Menu](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/MenuComponent.php) | Renders a [menu](https://symfony.com/bundles/KnpMenuBundle/current/index.html) |`menu` |
| [Script](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/ScriptComponent.php) | Renders a [`