ibexa · mnocon · Sep 4, 2026 · Sep 4, 2026
diff --git a/code_samples/collaboration/src/Command/ManageSessionsCommand.php b/code_samples/collaboration/src/Command/ManageSessionsCommand.php
diff --git a/code_samples/collaboration/src/Query/Search.php b/code_samples/collaboration/src/Query/Search.php
diff --git a/code_samples/templates/field_twig_functions/render_content.html.twig b/code_samples/templates/field_twig_functions/render_content.html.twig
diff --git a/code_samples/templates/field_twig_functions/render_product.html.twig b/code_samples/templates/field_twig_functions/render_product.html.twig
diff --git a/docs/administration/back_office/back_office_elements/custom_icons.md b/docs/administration/back_office/back_office_elements/custom_icons.md
@@ -27,98 +27,3 @@ Place the icon in `public/assets/images` and run `yarn encore <dev|prod>` after
     To ensure proper display in the back office, all icons should have SVG format with `symbol`.
 
 Use the [scope](multisite_configuration.md#scope) if you want different icons for different SiteAccesses.
-
-To see more Admin UI's `ids-assets` icons, see [the icon reference](icon_twig_functions.md#icons-reference).
-
-### Access icons in Twig templates
-
-#### Content type icons
-
-Content type icons are accessible in Twig templates via the [`ibexa_content_type_icon()` function](icon_twig_functions.md#ibexa_content_type_icon).
-It requires content type identifier as an argument. The function returns the path to a content type icon.
-
-```twig
-<svg class="ibexa-icon ibexa-icon-{{ content.contentType.identifier }}">
-    <use xlink:href="{{ ibexa_content_type_icon(content.contentType.identifier) }}"></use>
-</svg>
-```
-
-#### UI Icons
-
-User interface icons are accessible with [`ibexa_icon_path()` function](icon_twig_functions.md#ibexa_icon_path). The function returns a path from an icon identifier and an [icon set](#icon-sets) identifier arguments.
-
-### Access icons in JavaScript
-
-Content types icons configuration is stored in a global object: `ibexa.adminUiConfig.contentTypes`.
-
-You can retrieve the icon URL with the `getContentTypeIconUrl` helper function that is set on the global `ibexa.helpers.contentType` object.
-It takes content type identifier as an argument and returns one of the following items:
-
-- URL of a specified content type's icon
-- `null` if there is no content type with specified identifier
-
-Example with `getContentTypeIconUrl`:
-
-```jsx
-const contentTypeIconUrl = ibexa.helpers.contentType.getContentTypeIconUrl(contentTypeIdentifier);
-return (
-   <svg className="ibexa-icon">
-       <use xlinkHref={contentTypeIconUrl} />
-   </svg>
-)
-```
-
-### Icons React component
-
-You can use a React component to change icons in back office and Page Builder.
-
-The following example from the `alert.js` file shows configuration for icons in the [alert](reusable_components.md#alerts) component:
-
-```jsx hl_lines="2"
-<div className={className} role="alert">
-    <Icon name={iconName} customPath={iconPath} extraClasses="ibexa-icon--small ibexa-alert__icon" />
-    <div className={contentClassName}>
-        {title && <div className="ibexa-alert__title">{title}</div>}
-        {subtitle && <div className="ibexa-alert__subtitle">{subtitle}</div>}
-    <div className="ibexa-alert__extra_content">{children}</div>
-    </div>
-        {showCloseBtn && (
-            <button
-                className="btn ibexa-btn ibexa-btn--ghost ibexa-btn--small ibexa-btn--no-text ibexa-alert__close-btn"
-                onClick={onClose}>
-                <Icon name="discard" extraClasses="ibexa-icon--tiny-small" />
-            </button>
-        )}
-</div>
-```
-
-`Icon` component has three attributes (called props):
-
-- `customPath` - a path to the custom icon
-- `name` - the path is generated inside the component provided you use icon from the system
-- `extraClasses` - additional CSS classes, use to set for example, icon size.
-
-## Customize UI icons
-
-### Icon sets
-
-You can configure icon sets to be used per SiteAccess:
-
-``` yaml
-ibexa:
-    system:
-        <siteaccess>:
-            assets:
-                icon_sets:
-                    my_icons: /assets/images/icons/my_icons.svg
-                    additional_icons: /assets/images/icons/additional_icons.svg
-                default_icon_set: my_icons
-```
-
-The icon sets are used by [`ibexa_icon_path()` Twig function](icon_twig_functions.md#ibexa_icon_path).
-
-- If you change the `default_icon_set` from one SiteAccess to another, `ibexa_icon_path(icon)` without `set` argument targets icons from different set files
-- If you change the file path of an icon set from one SiteAccess to another, `ibexa_icon_path(icon, set)` with the same `set` argument targets icons from different set files
-
-The built-in default icon set is `ids-assets` (corresponding to `/bundles/ibexaadminuiassets/vendors/ids-assets/dist/img/all-icons.svg`).
-To see the icons available in this set, see [the icon reference](icon_twig_functions.md#icons-reference).
diff --git a/docs/administration/project_organization/architecture.md b/docs/administration/project_organization/architecture.md
@@ -17,19 +17,6 @@
 | Layer                                               | Description                                                                                                                                                                                    |
 |-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [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 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.                        |
-| SPI                                                 | Service Provider Interface which defines contracts for implementing various parts of the system, including persistence layer (`SPI\Persistence`), custom field types, custom limitations, and more. |
-| [Persistence cache](persistence_cache.md)           | The implementation of SPI\Persistence that decorates the main backend implementation.                                                                                                          |
-| [Search](search.md)                                 | Search API that allows both full-text search and querying the content.                                                                                                                         |
-| [SQL Storage Engine](legacy_search_overview.md)     | Legacy search engine is SQL-based and uses Doctrine's database connection.                                                                                                                     |
-| [Solr Storage Engine](solr_overview.md)             | Transparent drop-in replacement for the SQL-based Legacy search engine.                                                                                                                        |
-| [IO](file_management.md#native-io-handler)          | The IO API is organized around two types of handlers, both used by the IOService.                                                                                                              |
-| [IO Handler](clustering.md#dfs-io-handler)          | The IO Handler manipulates metadata, making up for the potential inconsistency of network-based filesystems.                                                                                   |
-| [Recommendations](connector_installation_configuration.md)         | Recommendation API.                                                                                                                                                                            |
-| [Raptor recommendation connector](raptor_connector.md) | Raptor recommendation connector allows displaying recommendations on the website.                                                                                                                       |
+
diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md
@@ -6,7 +6,7 @@ page_type: reference
 # Bundles
 
 A bundle in Symfony (and [[= product_name =]]) is a separate part of your application that implements a feature.
-You can [create bundles yourself](package_structure.md) or make use of available open-source bundles.
+You can create bundles yourself or make use of available open-source bundles.
 You can also reuse the bundles you create in other projects or share them with the community.
 
 Many [[= product_name =]] functionalities are provided through separate bundles included in the installation.
@@ -69,9 +69,7 @@ To remove a bundle (either one you created yourself, or an out-of-the-box one th
 |Bundle|Description|
 |---------|-----------|
 |ibexa/oss|Core packages|
-|ibexa/app-switcher|Integration with the [QNTM group](https://qntmgroup.com/solutions/)|
 |ibexa/calendar|Calendar tab with a calendar widget|
-|ibexa/collaboration|Collaboration functionality|
 |ibexa/connect|[[[= product_name_connect =]]]([[= connect_doc =]]/)|
 |ibexa/connector-ai|Foundation for the [AI Actions](ai_actions.md) framework|
 |ibexa/connector-dam|Connector for DAM (Digital Asset Management) systems|
@@ -92,7 +90,6 @@ To remove a bundle (either one you created yourself, or an out-of-the-box one th
 |ibexa/product-catalog|Product catalog functionality|
 |ibexa/scheduler|Date-based publishing functionality|
 |ibexa/seo|Search Engine Optimization (SEO) tool|
-|ibexa/share|Content-sharing functionality|
 |ibexa/taxonomy|Taxonomy functionality|
 |ibexa/tree-builder|Tree builder functionality|
 |ibexa/version-comparison|Enables comparing between two versions of the same field|

diff --git a/docs/administration/recent_activity/recent_activity.md b/docs/administration/recent_activity/recent_activity.md
@@ -34,8 +34,6 @@ 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_cohesivo.md#additional-scheduled-tasks-and-advanced-usage).
-
 ### Display limit
 
 The `ibexa.system.<scope>.activity_log.pagination.activity_logs_limit` setting sets the number of log items shown per page in the back office (default value: 25).

diff --git a/docs/ai/ai_actions/ai_actions.md b/docs/ai/ai_actions/ai_actions.md
@@ -27,7 +27,6 @@ You can also extend it to perform other tasks or support additional AI services.
 "ai/ai_actions/extend_ai_actions",
 "api/event_reference/ai_action_events",
 ("https://doc.ibexa.co/en/6.0/api/rest_api/rest_api_reference/rest_api_reference.html#tag/Connector-AI", "REST API Reference", "See the available endpoints for AI Actions"),
-"templating/twig_function_reference/ai_actions_twig_functions",
 "search/ai_actions_search_reference/action_configuration_criteria",
 "search/ai_actions_search_reference/action_configuration_sort_clauses",
 ("content_management/data_migration/importing_data#ai-action-configurations", "Importing AI actions", "Learn how to manage Action Configurations using data migrations"),