From c158b9d7bce2dd8250227f953cea3ffb6531044e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Noco=C5=84?= <mnocon@users.noreply.github.com>
Date: Mon, 14 Jul 2025 13:30:35 +0200
Subject: [PATCH 1/5] Renamed fieldtype identifiers

---
 .../src/Command/AddMissingAltTextCommand.php  |  2 +-
 .../edit/form_fields_binary_ai.html.twig      |  4 +--
 .../src/Command/CreateContentTypeCommand.php  |  2 +-
 .../back_office/images/config/services.yaml   |  2 +-
 .../ibexa_fieldtypes_preview.en.yaml          |  8 ++---
 .../config/packages/custom_buttons.yaml       |  2 +-
 .../config/packages/custom_classes.yaml       |  2 +-
 .../packages/custom_data_attributes.yaml      |  2 +-
 .../config/packages/custom_plugin.yaml        |  2 +-
 .../config/packages/custom_styles.yaml        |  6 ++--
 .../packages/custom_styles_highlight.yaml     |  4 +--
 .../packages/custom_styles_note_box.yaml      |  4 +--
 .../acronym/config/packages/custom_tags.yaml  |  4 +--
 .../acronym/translations/custom_tags.en.yaml  |  4 +--
 .../factbox/config/packages/custom_tags.yaml  |  4 +--
 .../custom_tags/factbox.html.twig             |  0
 .../factbox/translations/custom_tags.en.yaml  |  6 ++--
 .../linktag/config/packages/custom_tags.yaml  |  4 +--
 .../custom_tags/linktag.html.twig             |  0
 .../linktag/translations/custom_tags.en.yaml  | 10 +++----
 .../translations/custom_styles.en.yaml        |  4 +--
 .../assets/js/image-tab/components/image.js   |  2 +-
 .../examples/create_blog_post_ct.yaml         |  4 +--
 .../examples/create_product_type.yaml         |  2 +-
 .../Step/ReplaceNameStepExecutor.php          |  2 +-
 .../themes/my_theme/fields/author.html.twig   |  2 +-
 .../ImageFieldEncoder.php                     |  4 +--
 .../page_tutorial/assets/css/style.css        |  2 +-
 .../templates/fields/form_field.html.twig     |  2 +-
 .../back_office_elements/custom_components.md |  2 +-
 .../extending_thumbnails.md                   | 12 ++++----
 docs/ai_actions/extend_ai_actions.md          |  4 +--
 docs/api/graphql/graphql_custom_ft.md         |  4 +--
 .../content_api/browsing_content.md           |  2 +-
 .../create_data_migration_step.md             |  2 +-
 .../data_migration/exporting_data.md          |  2 +-
 .../create_custom_field_type_comparison.md    |  2 +-
 .../customize_field_type_metadata.md          |  4 +--
 .../field_type_reference/floatfield.md        |  2 +-
 .../field_type_reference/imagefield.md        |  2 +-
 .../field_type_reference/matrixfield.md       |  6 ++--
 .../field_type_reference/mediafield.md        |  4 +--
 .../field_type_reference/pagefield.md         |  4 +--
 .../field_types/field_type_search.md          |  2 +-
 .../field_types/field_type_storage.md         |  2 +-
 .../field_types/field_type_validation.md      |  2 +-
 .../field_types/field_types.md                |  2 +-
 .../field_types/form_and_template.md          |  6 ++--
 .../field_types/type_and_value.md             |  6 ++--
 .../images/configure_image_editor.md          |  2 +-
 .../rich_text/extend_online_editor.md         | 30 +++++++++----------
 docs/content_management/taxonomy/taxonomy.md  |  4 +--
 docs/resources/phpstorm_plugin.md             |  2 +-
 .../isfieldempty_criterion.md                 |  2 +-
 .../search_criteria_and_sort_clauses.md       |  2 +-
 .../1_get_a_starter_website.md                |  2 +-
 docs/users/oauth_client.md                    |  2 +-
 docs/users/passwords.md                       | 10 +++----
 58 files changed, 112 insertions(+), 112 deletions(-)
 rename code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/{ezrichtext => ibexa_richtext}/custom_tags/factbox.html.twig (100%)
 rename code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/{ezrichtext => ibexa_richtext}/custom_tags/linktag.html.twig (100%)

diff --git a/code_samples/ai_actions/src/Command/AddMissingAltTextCommand.php b/code_samples/ai_actions/src/Command/AddMissingAltTextCommand.php
index 84928aab61..5084b61d4e 100644
--- a/code_samples/ai_actions/src/Command/AddMissingAltTextCommand.php
+++ b/code_samples/ai_actions/src/Command/AddMissingAltTextCommand.php
@@ -150,7 +150,7 @@ private function getModifiedImages(): ContentList
     /** @phpstan-assert-if-true string $value->uri */
     private function shouldGenerateAltText(Value $value): bool
     {
-        return $this->fieldTypeService->getFieldType('ezimage')->isEmptyValue($value) === false &&
+        return $this->fieldTypeService->getFieldType('ibexa_image')->isEmptyValue($value) === false &&
             $value->isAlternativeTextEmpty() &&
             $value->uri !== null;
     }
diff --git a/code_samples/ai_actions/templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig b/code_samples/ai_actions/templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig
index fb86063839..789db2c2b3 100644
--- a/code_samples/ai_actions/templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig
+++ b/code_samples/ai_actions/templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig
@@ -1,6 +1,6 @@
-{% extends '@ibexadesign/ui/field_type/edit/ezbinaryfile.html.twig' %}
+{% extends '@ibexadesign/ui/field_type/edit/ibexa_binaryfile.html.twig' %}
 
-{% block ezbinaryfile_preview %}
+{% block ibexa_binaryfile_preview %}
     {{ parent() }}
 
     {% import '@ibexadesign/connector_ai/ui/ai_module/macros.html.twig' as ai_macros %}
diff --git a/code_samples/api/public_php_api/src/Command/CreateContentTypeCommand.php b/code_samples/api/public_php_api/src/Command/CreateContentTypeCommand.php
index d65feed9f4..7a86405849 100644
--- a/code_samples/api/public_php_api/src/Command/CreateContentTypeCommand.php
+++ b/code_samples/api/public_php_api/src/Command/CreateContentTypeCommand.php
@@ -70,7 +70,7 @@ protected function execute(InputInterface $input, OutputInterface $output): int
             'eng-GB' => $contentTypeIdentifier,
         ];
 
-        $titleFieldCreateStruct = $this->contentTypeService->newFieldDefinitionCreateStruct('name', 'ezstring');
+        $titleFieldCreateStruct = $this->contentTypeService->newFieldDefinitionCreateStruct('name', 'ibexa_string');
         $titleFieldCreateStruct->names = ['eng-GB' => 'Name'];
         $titleFieldCreateStruct->descriptions = ['eng-GB' => 'The name'];
         $titleFieldCreateStruct->fieldGroup = 'content';
diff --git a/code_samples/back_office/images/config/services.yaml b/code_samples/back_office/images/config/services.yaml
index 63357d14b3..15bc40ce72 100644
--- a/code_samples/back_office/images/config/services.yaml
+++ b/code_samples/back_office/images/config/services.yaml
@@ -4,7 +4,7 @@ services:
         public: true
         arguments:
             - '@ibexa.api.service.content'
-            - '@ibexa.field_type.ezbinaryfile.io_service'
+            - '@ibexa.field_type.ibexa_binaryfile.io_service'
             - '@Ibexa\Core\Helper\TranslationHelper'
 
     App\Connector\Dam\Handler\WikimediaCommonsHandler:
diff --git a/code_samples/back_office/images/translations/ibexa_fieldtypes_preview.en.yaml b/code_samples/back_office/images/translations/ibexa_fieldtypes_preview.en.yaml
index c1cdfa4d4e..363c648603 100644
--- a/code_samples/back_office/images/translations/ibexa_fieldtypes_preview.en.yaml
+++ b/code_samples/back_office/images/translations/ibexa_fieldtypes_preview.en.yaml
@@ -1,4 +1,4 @@
-ezimageasset.dam_asset.page_url: Image page
-ezimageasset.dam_asset.author: Image author
-ezimageasset.dam_asset.license: License
-ezimageasset.dam_asset.license_url: License page
+ibexa_image_asset.dam_asset.page_url: Image page
+ibexa_image_asset.dam_asset.author: Image author
+ibexa_image_asset.dam_asset.license: License
+ibexa_image_asset.dam_asset.license_url: License page
diff --git a/code_samples/back_office/online_editor/config/packages/custom_buttons.yaml b/code_samples/back_office/online_editor/config/packages/custom_buttons.yaml
index 3fcfe9421d..83afb64de4 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_buttons.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_buttons.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_tags: [ezyoutube, eztwitter, ezfacebook]
                     toolbar:
                         group1:
diff --git a/code_samples/back_office/online_editor/config/packages/custom_classes.yaml b/code_samples/back_office/online_editor/config/packages/custom_classes.yaml
index cefe8cf20f..8011e6f1c7 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_classes.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_classes.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:                            
+                ibexa_richtext:                            
                     classes:
                         paragraph:
                             choices: [regular, special, tip_box, warning_box]
diff --git a/code_samples/back_office/online_editor/config/packages/custom_data_attributes.yaml b/code_samples/back_office/online_editor/config/packages/custom_data_attributes.yaml
index 53b4ae1938..d282a709f3 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_data_attributes.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_data_attributes.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     attributes:
                         heading:
                             custom-attribute:
diff --git a/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml b/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml
index d43d8dd82a..426b9b75b9 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     toolbars:
                         paragraph:
                             buttons:
diff --git a/code_samples/back_office/online_editor/config/packages/custom_styles.yaml b/code_samples/back_office/online_editor/config/packages/custom_styles.yaml
index ea81dded18..17180df9eb 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_styles.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_styles.yaml
@@ -2,13 +2,13 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_styles: [highlighted_block, highlighted_word]
 ibexa_fieldtype_richtext:
     custom_styles:
         highlighted_word:
-            template: '@ibexadesign/field_type/ezrichtext/custom_styles/highlighted_word.html.twig'
+            template: '@ibexadesign/field_type/ibexa_richtext/custom_styles/highlighted_word.html.twig'
             inline: true
         highlighted_block:
-            template: '@ibexadesign/field_type/ezrichtext/custom_styles/highlighted_block.html.twig'
+            template: '@ibexadesign/field_type/ibexa_richtext/custom_styles/highlighted_block.html.twig'
             inline: false
diff --git a/code_samples/back_office/online_editor/config/packages/custom_styles_highlight.yaml b/code_samples/back_office/online_editor/config/packages/custom_styles_highlight.yaml
index b56097a79c..157b8bb46f 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_styles_highlight.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_styles_highlight.yaml
@@ -2,10 +2,10 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_styles: [highlight]
 ibexa_fieldtype_richtext:
     custom_styles:
         highlight:
-            template: field_type/ezrichtext/custom_styles/highlight.html.twig
+            template: field_type/ibexa_richtext/custom_styles/highlight.html.twig
             inline: true
diff --git a/code_samples/back_office/online_editor/config/packages/custom_styles_note_box.yaml b/code_samples/back_office/online_editor/config/packages/custom_styles_note_box.yaml
index ba0169da8f..8c99fee49f 100644
--- a/code_samples/back_office/online_editor/config/packages/custom_styles_note_box.yaml
+++ b/code_samples/back_office/online_editor/config/packages/custom_styles_note_box.yaml
@@ -2,9 +2,9 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_styles: [note_box]
 ibexa_fieldtype_richtext:
     custom_styles:
         note_box:
-            template: field_type/ezrichtext/custom_styles/note_box.html.twig
+            template: field_type/ibexa_richtext/custom_styles/note_box.html.twig
diff --git a/code_samples/back_office/online_editor/custom_tags/acronym/config/packages/custom_tags.yaml b/code_samples/back_office/online_editor/custom_tags/acronym/config/packages/custom_tags.yaml
index 9768688d92..af2707f904 100644
--- a/code_samples/back_office/online_editor/custom_tags/acronym/config/packages/custom_tags.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/acronym/config/packages/custom_tags.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_tags: [acronym]
                     toolbar:
                         custom_tags_group:
@@ -12,7 +12,7 @@ ibexa:
 ibexa_fieldtype_richtext:
     custom_tags:
         acronym:
-            template: '@ibexadesign/field_type/ezrichtext/custom_tags/acronym.html.twig'
+            template: '@ibexadesign/field_type/ibexa_richtext/custom_tags/acronym.html.twig'
             icon: '/bundles/ibexaicons/img/all-icons.svg#edit'
             is_inline: true
             attributes:
diff --git a/code_samples/back_office/online_editor/custom_tags/acronym/translations/custom_tags.en.yaml b/code_samples/back_office/online_editor/custom_tags/acronym/translations/custom_tags.en.yaml
index e302b20424..f6c3228f48 100644
--- a/code_samples/back_office/online_editor/custom_tags/acronym/translations/custom_tags.en.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/acronym/translations/custom_tags.en.yaml
@@ -1,2 +1,2 @@
-ezrichtext.custom_tags.acronym.label: 'Acronym'
-ezrichtext.custom_tags.acronym.attributes.explanation.label: 'Explanation'
+ibexa_richtext.custom_tags.acronym.label: 'Acronym'
+ibexa_richtext.custom_tags.acronym.attributes.explanation.label: 'Explanation'
diff --git a/code_samples/back_office/online_editor/custom_tags/factbox/config/packages/custom_tags.yaml b/code_samples/back_office/online_editor/custom_tags/factbox/config/packages/custom_tags.yaml
index 5498c9327a..243b5f0c68 100644
--- a/code_samples/back_office/online_editor/custom_tags/factbox/config/packages/custom_tags.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/factbox/config/packages/custom_tags.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_tags: [factbox]
                     toolbar:
                         custom_tags_group:
@@ -12,7 +12,7 @@ ibexa:
 ibexa_fieldtype_richtext:
     custom_tags:
         factbox:
-            template: '@ibexadesign/field_type/ezrichtext/custom_tags/factbox.html.twig'
+            template: '@ibexadesign/field_type/ibexa_richtext/custom_tags/factbox.html.twig'
             icon: '/bundles/ibexaicons/img/all-icons.svg#information'
             attributes:
                 name:
diff --git a/code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ezrichtext/custom_tags/factbox.html.twig b/code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ibexa_richtext/custom_tags/factbox.html.twig
similarity index 100%
rename from code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ezrichtext/custom_tags/factbox.html.twig
rename to code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ibexa_richtext/custom_tags/factbox.html.twig
diff --git a/code_samples/back_office/online_editor/custom_tags/factbox/translations/custom_tags.en.yaml b/code_samples/back_office/online_editor/custom_tags/factbox/translations/custom_tags.en.yaml
index 8c503b5dcf..fde8e1917c 100644
--- a/code_samples/back_office/online_editor/custom_tags/factbox/translations/custom_tags.en.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/factbox/translations/custom_tags.en.yaml
@@ -1,3 +1,3 @@
-ezrichtext.custom_tags.factbox.label: 'Factbox'
-ezrichtext.custom_tags.factbox.attributes.name.label: 'Name'
-ezrichtext.custom_tags.factbox.attributes.style.label: 'Style'
+ibexa_richtext.custom_tags.factbox.label: 'Factbox'
+ibexa_richtext.custom_tags.factbox.attributes.name.label: 'Name'
+ibexa_richtext.custom_tags.factbox.attributes.style.label: 'Style'
diff --git a/code_samples/back_office/online_editor/custom_tags/linktag/config/packages/custom_tags.yaml b/code_samples/back_office/online_editor/custom_tags/linktag/config/packages/custom_tags.yaml
index 2d4f99c816..5b5dcb0efd 100644
--- a/code_samples/back_office/online_editor/custom_tags/linktag/config/packages/custom_tags.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/linktag/config/packages/custom_tags.yaml
@@ -2,7 +2,7 @@ ibexa:
     system:
         admin_group:
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     custom_tags: [linktag]
                     toolbar:
                         custom_tags_group:
@@ -12,7 +12,7 @@ ibexa:
 ibexa_fieldtype_richtext:
     custom_tags:
         linktag:
-            template: '@ibexadesign/field_type/ezrichtext/custom_tags/linktag.html.twig'
+            template: '@ibexadesign/field_type/ibexa_richtext/custom_tags/linktag.html.twig'
             icon: '/bundles/ibexaicons/img/all-icons.svg#link'
             is_inline: true
             attributes:
diff --git a/code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ezrichtext/custom_tags/linktag.html.twig b/code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ibexa_richtext/custom_tags/linktag.html.twig
similarity index 100%
rename from code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ezrichtext/custom_tags/linktag.html.twig
rename to code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ibexa_richtext/custom_tags/linktag.html.twig
diff --git a/code_samples/back_office/online_editor/custom_tags/linktag/translations/custom_tags.en.yaml b/code_samples/back_office/online_editor/custom_tags/linktag/translations/custom_tags.en.yaml
index 083f90183b..e9ea26760e 100644
--- a/code_samples/back_office/online_editor/custom_tags/linktag/translations/custom_tags.en.yaml
+++ b/code_samples/back_office/online_editor/custom_tags/linktag/translations/custom_tags.en.yaml
@@ -1,5 +1,5 @@
-ezrichtext.custom_tags.linktag.label: 'Link Tag'
-ezrichtext.custom_tags.linktag.attributes.title.label: 'Title'
-ezrichtext.custom_tags.linktag.attributes.description.label: 'Description'
-ezrichtext.custom_tags.linktag.attributes.color.label: 'Color'
-ezrichtext.custom_tags.linktag.attributes.url.label: 'URL'
+ibexa_richtext.custom_tags.linktag.label: 'Link Tag'
+ibexa_richtext.custom_tags.linktag.attributes.title.label: 'Title'
+ibexa_richtext.custom_tags.linktag.attributes.description.label: 'Description'
+ibexa_richtext.custom_tags.linktag.attributes.color.label: 'Color'
+ibexa_richtext.custom_tags.linktag.attributes.url.label: 'URL'
diff --git a/code_samples/back_office/online_editor/translations/custom_styles.en.yaml b/code_samples/back_office/online_editor/translations/custom_styles.en.yaml
index 227d8cda2f..58cec61346 100644
--- a/code_samples/back_office/online_editor/translations/custom_styles.en.yaml
+++ b/code_samples/back_office/online_editor/translations/custom_styles.en.yaml
@@ -1,2 +1,2 @@
-ezrichtext.custom_styles.highlighted_block.label: Highlighted block
-ezrichtext.custom_styles.highlighted_word.label: Highlighted word
+ibexa_richtext.custom_styles.highlighted_block.label: Highlighted block
+ibexa_richtext.custom_styles.highlighted_word.label: Highlighted word
diff --git a/code_samples/back_office/udw/assets/js/image-tab/components/image.js b/code_samples/back_office/udw/assets/js/image-tab/components/image.js
index 4466982251..a35836778c 100644
--- a/code_samples/back_office/udw/assets/js/image-tab/components/image.js
+++ b/code_samples/back_office/udw/assets/js/image-tab/components/image.js
@@ -40,7 +40,7 @@ const Image = ({ restInfo, location }) => {
     }, []);
 
     if (content) {
-        const imageField = content.CurrentVersion.Version.Fields.field.find((field) => field.fieldTypeIdentifier === 'ezimage').fieldValue;
+        const imageField = content.CurrentVersion.Version.Fields.field.find((field) => field.fieldTypeIdentifier === 'ibexa_image').fieldValue;
 
         src = imageField.uri;
         alt = imageField.fileName;
diff --git a/code_samples/data_migration/examples/create_blog_post_ct.yaml b/code_samples/data_migration/examples/create_blog_post_ct.yaml
index 5f5dcc678c..0956592d33 100644
--- a/code_samples/data_migration/examples/create_blog_post_ct.yaml
+++ b/code_samples/data_migration/examples/create_blog_post_ct.yaml
@@ -11,13 +11,13 @@
                 name: Blog Post
     fields:
         -   identifier: title
-            type: ezstring
+            type: ibexa_string
             required: true
             translations:
                 eng-GB:
                     name: 'Title'
         -   identifier: body
-            type: ezrichtext
+            type: ibexa_richtext
             required: false
             translations:
                 eng-GB:
diff --git a/code_samples/data_migration/examples/create_product_type.yaml b/code_samples/data_migration/examples/create_product_type.yaml
index 950e99cdb5..9c10c1cfb6 100644
--- a/code_samples/data_migration/examples/create_product_type.yaml
+++ b/code_samples/data_migration/examples/create_product_type.yaml
@@ -10,7 +10,7 @@
                 name: Hat
     fields:
         -   identifier: name
-            type: ezstring
+            type: ibexa_string
             required: true
             translations:
                 eng-GB:
diff --git a/code_samples/data_migration/src/Migrations/Step/ReplaceNameStepExecutor.php b/code_samples/data_migration/src/Migrations/Step/ReplaceNameStepExecutor.php
index 6ea22d920e..0f033f192c 100644
--- a/code_samples/data_migration/src/Migrations/Step/ReplaceNameStepExecutor.php
+++ b/code_samples/data_migration/src/Migrations/Step/ReplaceNameStepExecutor.php
@@ -30,7 +30,7 @@ protected function doHandle(StepInterface $step)
             $struct = $this->contentService->newContentUpdateStruct();
 
             foreach ($contentItem->getFields() as $field) {
-                if ($field->fieldTypeIdentifier !== 'ezstring') {
+                if ($field->fieldTypeIdentifier !== 'ibexa_string') {
                     continue;
                 }
 
diff --git a/code_samples/front/render_content/templates/themes/my_theme/fields/author.html.twig b/code_samples/front/render_content/templates/themes/my_theme/fields/author.html.twig
index 1554b2dd53..be851ae3c4 100644
--- a/code_samples/front/render_content/templates/themes/my_theme/fields/author.html.twig
+++ b/code_samples/front/render_content/templates/themes/my_theme/fields/author.html.twig
@@ -1,4 +1,4 @@
-{% block ezauthor_field %}
+{% block ibexa_author_field %}
 {% if field.value.authors|length() > 0 %}
     {% for author in field.value.authors %}
         <span class="author">{{ author.name }}</span>
diff --git a/code_samples/multisite/automated_translation/src/AutomatedTranslation/ImageFieldEncoder.php b/code_samples/multisite/automated_translation/src/AutomatedTranslation/ImageFieldEncoder.php
index bb229ddc39..675b914431 100644
--- a/code_samples/multisite/automated_translation/src/AutomatedTranslation/ImageFieldEncoder.php
+++ b/code_samples/multisite/automated_translation/src/AutomatedTranslation/ImageFieldEncoder.php
@@ -10,12 +10,12 @@ final class ImageFieldEncoder implements FieldEncoderInterface
 {
     public function canEncode(Field $field): bool
     {
-        return $field->fieldTypeIdentifier === 'ezimage';
+        return $field->fieldTypeIdentifier === 'ibexa_image';
     }
 
     public function canDecode(string $type): bool
     {
-        return $type === 'ezimage';
+        return $type === 'ibexa_image';
     }
 
     public function encode(Field $field): string
diff --git a/code_samples/tutorials/page_tutorial/assets/css/style.css b/code_samples/tutorials/page_tutorial/assets/css/style.css
index cbb198f8c7..9a38d11076 100644
--- a/code_samples/tutorials/page_tutorial/assets/css/style.css
+++ b/code_samples/tutorials/page_tutorial/assets/css/style.css
@@ -235,7 +235,7 @@ footer div {
     margin-top: 15px;
 }
 
-.block-form .ezstring-field {
+.block-form .ibexa-string-field {
     display: inline-block;
     font-variant: small-caps;
     font-size: 1.2em;
diff --git a/code_samples/tutorials/page_tutorial/templates/fields/form_field.html.twig b/code_samples/tutorials/page_tutorial/templates/fields/form_field.html.twig
index 6873f3a0f2..b8484beda4 100644
--- a/code_samples/tutorials/page_tutorial/templates/fields/form_field.html.twig
+++ b/code_samples/tutorials/page_tutorial/templates/fields/form_field.html.twig
@@ -1,4 +1,4 @@
-{% block ezform_field %}
+{% block ibexa_form_field %}
     {% set formValue = field.value.getForm() %}
     {% if formValue %}
         {% set form = formValue.createView() %}
diff --git a/docs/administration/back_office/back_office_elements/custom_components.md b/docs/administration/back_office/back_office_elements/custom_components.md
index e77dcd567e..48bef56ffb 100644
--- a/docs/administration/back_office/back_office_elements/custom_components.md
+++ b/docs/administration/back_office/back_office_elements/custom_components.md
@@ -34,7 +34,7 @@ The available groups for the back office are:
 |`admin-ui-global-search-autocomplete-templates`| `vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/global_search.html.twig` |
 |`admin-ui-global-search`| `vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/layout.html.twig` |
 |`admin-ui-header-user-menu-middle`| `vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/menu/user.html.twig` |
-|`admin-ui-image-edit-actions-after`| <ul><li>`vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/field_type/edit/ezimage.html.twig` </li><li>`vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/field_type/edit/ezimageasset.html.twig` </li></ul>|
+|`admin-ui-image-edit-actions-after`| <ul><li>`vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/field_type/edit/ibexa_image.html.twig` </li><li>`vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/field_type/edit/ibexa_image_asset.html.twig` </li></ul>|
 |`admin-ui-layout-content-after`| `vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/ui/layout.html.twig` |
 |`admin-ui-link-manager-block`| `vendor/ibexa/admin-ui-ui/src/bundle/Resources/views/themes/admin/url_management/url_management.html.twig` |
 |`admin-ui-location-view-content-alerts`| `vendor/ibexa/admin-ui/src/bundle/Resources/views/themes/admin/content/location_view.html.twig` |
diff --git a/docs/administration/back_office/back_office_elements/extending_thumbnails.md b/docs/administration/back_office/back_office_elements/extending_thumbnails.md
index 9155ac153a..0c3d9ae0cd 100644
--- a/docs/administration/back_office/back_office_elements/extending_thumbnails.md
+++ b/docs/administration/back_office/back_office_elements/extending_thumbnails.md
@@ -10,7 +10,7 @@ If you don't want to use custom thumbnails, `ContentType` is used instead.
 ## Thumbnail mechanism
 
 The thumbnail mechanism has two layers, and each layer can have many implementations.
-The mechanism checks if any of the implementations returns a field, for example, `ezimage`, that has function "Can be a thumbnail" turned on.
+The mechanism checks if any of the implementations returns a field, for example, `ibexa_image`, that has function "Can be a thumbnail" turned on.
 
 ![Can be a thumbnail setting](extending_thumbnail_can_be.png)
 
@@ -65,12 +65,12 @@ At this point you can go to the back office and check the results.
 
 Any field type can generate a thumbnail, for example:
 
-- DateAndTime (`ezdatetime`) - you can add a mini calendar thumbnail for Appointment content type and on the day of the appointment a clock thumbnail with a specific time when it takes place
-- TextBlock (`eztext`) -  you can add a first letter of the text block that is inside
+- DateAndTime (`ibexa_datetime`) - you can add a mini calendar thumbnail for Appointment content type and on the day of the appointment a clock thumbnail with a specific time when it takes place
+- TextBlock (`ibexa_text`) -  you can add a first letter of the text block that is inside
 
-### Add eztext field as thumbnail
+### Add ibexa_text field as thumbnail
 
-First, create a strategy that adds support for `eztext` as the thumbnail.
+First, create a strategy that adds support for `ibexa_text` as the thumbnail.
 It enables you to add a thumbnail URL in the text field.
 
 Add `FieldValueUrl.php` in `src/Thumbnails`.
@@ -91,7 +91,7 @@ class FieldValueUrl implements FieldTypeBasedThumbnailStrategy
 {
     public function getFieldTypeIdentifier(): string
     {
-        return 'eztext';
+        return 'ibexa_text';
     }
 
     public function getThumbnail(Field $field, ?VersionInfo $versionInfo = null): ?Thumbnail
diff --git a/docs/ai_actions/extend_ai_actions.md b/docs/ai_actions/extend_ai_actions.md
index 4992d9c0d2..b07ed511bb 100644
--- a/docs/ai_actions/extend_ai_actions.md
+++ b/docs/ai_actions/extend_ai_actions.md
@@ -322,8 +322,8 @@ Content-Type: application/vnd.ibexa.api.ai.TranscribeAudio+json
 
 The last step in fully integrating the Transcribe Audio Action Type embeds it directly into the back office, allowing Editors to invoke it while doing their daily work.
 
-Extend the default editing template of the `ezbinaryfile` fieldtype by creating a new file called `templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig`.
-This template embeds the AI component, but only if a dedicated `transcript` field (of `eztext` type) is available in the same content type to store the content of the transcription.
+Extend the default editing template of the `ibexa_binaryfile` fieldtype by creating a new file called `templates/themes/admin/admin/ui/fieldtype/edit/form_fields_binary_ai.html.twig`.
+This template embeds the AI component, but only if a dedicated `transcript` field (of `ibexa_text` type) is available in the same content type to store the content of the transcription.
 
 
 ``` twig
diff --git a/docs/api/graphql/graphql_custom_ft.md b/docs/api/graphql/graphql_custom_ft.md
index 30dc674d6d..002ceb7420 100644
--- a/docs/api/graphql/graphql_custom_ft.md
+++ b/docs/api/graphql/graphql_custom_ft.md
@@ -30,7 +30,7 @@ If your field definition doesn't require additional clarifications, you can map
 
 To map a custom field type with configuration use a compiler pass to modify a container parameter, `ibexa.graphql.schema.content.mapping.field_definition_type`.
 
-It's a hash that maps a field type identifier (`ezstring`) to the following entries:
+It's a hash that maps a field type identifier (`ibexa_string`) to the following entries:
 
 - `value_type` - the GraphQL type values of the custom field. It can be a native type (string, int), or a custom type. If none is specified, string is used.
 - `value_resolver` - how values of this field are resolved and passed to the defined value type.
@@ -145,7 +145,7 @@ The cardinality (single or collection) depends on the selection limit setting:
 #### Field input mapping
 
 The `mapToFieldValueInputType` method is used to document what input type is expected by field types that require a more complex input value.
-For example, `ezmatrix` generates its own input types depending on the configured columns.
+For example, `ibexa_matrix` generates its own input types depending on the configured columns.
 
 Example of a `MyCustomFieldDefinitionMapper` mapper for a complex field type:
 
diff --git a/docs/content_management/content_api/browsing_content.md b/docs/content_management/content_api/browsing_content.md
index f61a5f1cea..45c856a218 100644
--- a/docs/content_management/content_api/browsing_content.md
+++ b/docs/content_management/content_api/browsing_content.md
@@ -228,6 +228,6 @@ $nameComparison = $this->comparisonService->compare($versionFrom, $versionTo)->g
 ```
 
 `getComparisonResult` returns a `ComparisonResult` object, which depends on the field type being compared.
-In the example of a Text Line (ezstring) field, it's an array of `StringDiff` objects.
+In the example of a Text Line (ibexa_string) field, it's an array of `StringDiff` objects.
 
 Each diff contains a section of the field to compare (for example, a part of a text line) and its status, which can be "unchanged", "added" or "removed".
diff --git a/docs/content_management/data_migration/create_data_migration_step.md b/docs/content_management/data_migration/create_data_migration_step.md
index 70499cea71..d3f7da564e 100644
--- a/docs/content_management/data_migration/create_data_migration_step.md
+++ b/docs/content_management/data_migration/create_data_migration_step.md
@@ -12,7 +12,7 @@ To create a custom migration step, you need:
 - A step normalizer, to convert YAML definition into your step class.
 - A step executor, to handle the step.
 
-The following example shows how to create a step that replaces all `ezstring` fields that have an old company name with "New Company Name".
+The following example shows how to create a step that replaces all `ibexa_string` fields that have an old company name with "New Company Name".
 
 ## Create step class
 
diff --git a/docs/content_management/data_migration/exporting_data.md b/docs/content_management/data_migration/exporting_data.md
index 7cb301514d..7bb1f3b5d9 100644
--- a/docs/content_management/data_migration/exporting_data.md
+++ b/docs/content_management/data_migration/exporting_data.md
@@ -106,7 +106,7 @@ php bin/console ibexa:migrations:generate --type=content_type --mode=update --ma
     fields:
         -
             identifier: title
-            type: ezstring
+            type: ibexa_string
             position: 1
             translations:
                 eng-GB:
diff --git a/docs/content_management/field_types/create_custom_field_type_comparison.md b/docs/content_management/field_types/create_custom_field_type_comparison.md
index 7a3a036a9f..25407468ab 100644
--- a/docs/content_management/field_types/create_custom_field_type_comparison.md
+++ b/docs/content_management/field_types/create_custom_field_type_comparison.md
@@ -12,7 +12,7 @@ You can add the possibility to compare custom and other unsupported field types.
 !!! note
 
     The following task uses the [custom "Hello World" field type](create_custom_generic_field_type.md).
-    The configuration is based on the comparison mechanism created for the `ezstring` field type.
+    The configuration is based on the comparison mechanism created for the `ibexa_string` field type.
 
 ## Create Comparable class
 
diff --git a/docs/content_management/field_types/customize_field_type_metadata.md b/docs/content_management/field_types/customize_field_type_metadata.md
index 88d9d8fc0e..8ee9b70718 100644
--- a/docs/content_management/field_types/customize_field_type_metadata.md
+++ b/docs/content_management/field_types/customize_field_type_metadata.md
@@ -16,14 +16,14 @@ services:
     ibexa.field_type_identifier.form.type_extension.modify_field_definitions_for_field_type_identifier_field_type:
         class: 'Ibexa\AdminUi\Form\Type\Extension\ModifyFieldDefinitionsCollectionTypeExtension'
         arguments:
-            $fieldTypeIdentifier: 'ezimage'
+            $fieldTypeIdentifier: 'ibexa_image'
             $modifiedOptions:
                 disable_required_field: true
         tags:
             - form.type_extension
 ```
 
-`fieldTypeIdentifier` refers to the identifier of the field type, in this case `ezimage`.
+`fieldTypeIdentifier` refers to the identifier of the field type, in this case `ibexa_image`.
 
 `modifiedOptions` lists the changes you want to make. The following options are available:
 
diff --git a/docs/content_management/field_types/field_type_reference/floatfield.md b/docs/content_management/field_types/field_type_reference/floatfield.md
index 5f23b970f1..ec09b0eeaf 100644
--- a/docs/content_management/field_types/field_type_reference/floatfield.md
+++ b/docs/content_management/field_types/field_type_reference/floatfield.md
@@ -67,7 +67,7 @@ This field type supports `FloatValueValidator`, defining maximum and minimum flo
 use Ibexa\Core\FieldType\Float\Type;
 
 $contentTypeService = $repository->getContentTypeService();
-$floatFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "float", "ezfloat" );
+$floatFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "float", "ibexa_float" );
 
 // Accept only numbers between 0.1 and 203.99
 $floatFieldCreateStruct->validatorConfiguration = [
diff --git a/docs/content_management/field_types/field_type_reference/imagefield.md b/docs/content_management/field_types/field_type_reference/imagefield.md
index 065ef0dda2..94deb5af65 100644
--- a/docs/content_management/field_types/field_type_reference/imagefield.md
+++ b/docs/content_management/field_types/field_type_reference/imagefield.md
@@ -146,7 +146,7 @@ Requested through REST, this resource generates the variation if it doesn't exis
 
 #### Getting an image variation
 
-The variation service, `ibexa.field_type.ezimage.variation_service`, can be used to generate/get variations for a field.
+The variation service, `ibexa.field_type.ibexa_image.variation_service`, can be used to generate/get variations for a field.
 It expects a VersionInfo, the Image field, and the variation name as a string (`large`, `medium`, and more.):
 
 ``` php
diff --git a/docs/content_management/field_types/field_type_reference/matrixfield.md b/docs/content_management/field_types/field_type_reference/matrixfield.md
index 8c3aa56803..1542ceeebd 100644
--- a/docs/content_management/field_types/field_type_reference/matrixfield.md
+++ b/docs/content_management/field_types/field_type_reference/matrixfield.md
@@ -64,8 +64,8 @@ The types that are returned are named after the Type and the field:
 
 The example below shows a GraphQL query for a Recipe content item (belonging to a content type with a Matrix field added), that has two fields:
 
-- `name`: `ezstring`
-- `ingredients`: `ezmatrix` with two columns: `ingredient` and `quantity`
+- `name`: `ibexa_string`
+- `ingredients`: `ibexa_matrix` with two columns: `ingredient` and `quantity`
 
 ```graphql
 {
@@ -177,7 +177,7 @@ The types that are used for input are named after the Type and the field:
 The example below shows how to create a Recipe content item (belonging to a content type with a Matrix field type added) that has two fields:
 
 - `name`: `"Cake Ingredient List"`
-- `ingredients`: `ezmatrix` with two columns: `ingredient` and `quantity`
+- `ingredients`: `ibexa_matrix` with two columns: `ingredient` and `quantity`
 
 ```graphql
  mutation AddRecipe {
diff --git a/docs/content_management/field_types/field_type_reference/mediafield.md b/docs/content_management/field_types/field_type_reference/mediafield.md
index ff9bbeca15..42c04d15b9 100644
--- a/docs/content_management/field_types/field_type_reference/mediafield.md
+++ b/docs/content_management/field_types/field_type_reference/mediafield.md
@@ -77,7 +77,7 @@ The field type supports `FileSizeValidator`, defining maximum size of media file
 use Ibexa\Core\FieldType\Media\Type;
 
 $contentTypeService = $repository->getContentTypeService();
-$mediaFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "media", "ezmedia" );
+$mediaFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "media", "ibexa_media" );
 
 // Setting maximum file size to 5 megabytes
 $mediaFieldCreateStruct->validatorConfiguration = [
@@ -113,7 +113,7 @@ List of all available `mediaType` constants is defined in the `Ibexa\Core\FieldT
 use Ibexa\Core\FieldType\Media\Type;
 
 $contentTypeService = $repository->getContentTypeService();
-$mediaFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "media", "ezmedia" );
+$mediaFieldCreateStruct = $contentTypeService->newFieldDefinitionCreateStruct( "media", "ibexa_media" );
 
 // Setting Adobe Flash as the media type
 $mediaFieldCreateStruct->fieldSettings = [
diff --git a/docs/content_management/field_types/field_type_reference/pagefield.md b/docs/content_management/field_types/field_type_reference/pagefield.md
index 663a709bce..d5b0977f76 100644
--- a/docs/content_management/field_types/field_type_reference/pagefield.md
+++ b/docs/content_management/field_types/field_type_reference/pagefield.md
@@ -15,8 +15,8 @@ Page field type is only used in the page content type that is included in [[= pr
 
 !!! caution "Page Builder"
 
-    If you create content type with both `ezlandingpage` and `ezuser` field types, you aren't redirected to Page Builder after selecting `Edit` or `Create`.
-    This is caused by `ezuser` field type which requires separate handling.
+    If you create content type with both `ibexa_landing_page` and `ibexa_user` field types, you aren't redirected to Page Builder after selecting `Edit` or `Create`.
+    This is caused by `ibexa_user` field type which requires separate handling.
     You're redirected to the standard back office edit or create mode.
 
 ## Layout and zones
diff --git a/docs/content_management/field_types/field_type_search.md b/docs/content_management/field_types/field_type_search.md
index 63c511aa2b..5266ff7810 100644
--- a/docs/content_management/field_types/field_type_search.md
+++ b/docs/content_management/field_types/field_type_search.md
@@ -52,7 +52,7 @@ Example from [`indexable_fieldtypes.yaml`](https://github.com/ibexa/core/blob/ma
 Ibexa\Core\FieldType\Keyword\SearchField:
     class: Ibexa\Core\FieldType\Keyword\SearchField
     tags:
-        - {name: ibexa.field_type.indexable, alias: ezkeyword}
+        - {name: ibexa.field_type.indexable, alias: ibexa_keyword}
 ```
 
 The `alias` should be the same as field type ID.
diff --git a/docs/content_management/field_types/field_type_storage.md b/docs/content_management/field_types/field_type_storage.md
index 82fcd244d0..f6907eb661 100644
--- a/docs/content_management/field_types/field_type_storage.md
+++ b/docs/content_management/field_types/field_type_storage.md
@@ -73,7 +73,7 @@ Those converters also need to be correctly exposed as services and tagged with `
 services:
     Ibexa\Core\Persistence\Legacy\Content\FieldValue\Converter\TextLine:
         tags:
-            - {name: ibexa.field_type.storage.legacy.converter, alias: ezstring}
+            - {name: ibexa.field_type.storage.legacy.converter, alias: ibexa_string}
 ```
 
 The tag has the following attribute:
diff --git a/docs/content_management/field_types/field_type_validation.md b/docs/content_management/field_types/field_type_validation.md
index 8faab59a9c..d2f9a5553a 100644
--- a/docs/content_management/field_types/field_type_validation.md
+++ b/docs/content_management/field_types/field_type_validation.md
@@ -15,7 +15,7 @@ except it has an additional level, to group settings for a certain validation me
 - It's assigned to a 3rd level associative array, the setting description
 - This associative array should have the same format as for normal settings
 
-For example, for the `ezstring` type, the validator schema could be:
+For example, for the `ibexa_string` type, the validator schema could be:
 
 ``` php
 [
diff --git a/docs/content_management/field_types/field_types.md b/docs/content_management/field_types/field_types.md
index 08706cfa90..e7d00ba817 100644
--- a/docs/content_management/field_types/field_types.md
+++ b/docs/content_management/field_types/field_types.md
@@ -42,7 +42,7 @@ Below that, the field type must support the **public PHP API** implementation re
 - Communication with the Persistence SPI
 
 On the bottom level, a field type can additionally hook into the **Persistence SPI** to store data from a `FieldValue` in an external service.
-All non-standard [[= product_name =]] database tables (for example, `ezurl`) are treated as [external storage](field_type_storage.md#storing-data-externally).
+All non-standard [[= product_name =]] database tables (for example, `ibexa_url`) are treated as [external storage](field_type_storage.md#storing-data-externally).
 
 The following sequence diagrams visualize the process of creating and publishing new content across all layers, especially focused on the interaction with a field type.
 
diff --git a/docs/content_management/field_types/form_and_template.md b/docs/content_management/field_types/form_and_template.md
index 3adf4d98d2..471cdf36c9 100644
--- a/docs/content_management/field_types/form_and_template.md
+++ b/docs/content_management/field_types/form_and_template.md
@@ -21,7 +21,7 @@ The `FieldValueFormMapperInterface::mapFieldValueForm` method accepts two argume
 - `FormInterface` — form for the current field
 - `FieldData` — underlying data for current field form
 
-You have to add your form type to the content editing form. The example shows how `ezboolean` injects the form:
+You have to add your form type to the content editing form. The example shows how `ibexa_boolean` injects the form:
 
 ``` php
 use Ibexa\Contracts\ContentForms\Data\Content\FieldData;
@@ -77,7 +77,7 @@ public function mapFieldDefinitionForm(FormInterface $fieldDefinitionForm, Field
             CheckboxType::class, [
                 'required' => false,
                 'property_path' => 'fieldSettings[isMultiple]',
-                'label' => 'field_definition.ezcountry.is_multiple',
+                'label' => 'field_definition.ibexa_country.is_multiple',
             ]
         )
         ->add(
@@ -89,7 +89,7 @@ public function mapFieldDefinitionForm(FormInterface $fieldDefinitionForm, Field
                         'multiple' => true,
                         'expanded' => false,
                         'required' => false,
-                        'label' => 'field_definition.ezcountry.default_value',
+                        'label' => 'field_definition.ibexa_country.default_value',
                     ]
                 )
                 // Deactivate auto-initialize as you're not on the root form.
diff --git a/docs/content_management/field_types/type_and_value.md b/docs/content_management/field_types/type_and_value.md
index 67dda4b7c0..1b03733f65 100644
--- a/docs/content_management/field_types/type_and_value.md
+++ b/docs/content_management/field_types/type_and_value.md
@@ -42,7 +42,7 @@ Since it's not possible to define a generic format for such a schema, the field
 
 In addition to normal settings, the field type should provide schema settings for its validation process.
 The schema describes what kind of validation can be performed by the field type and which settings the user can specify to these validation methods.
-For example, the `ezstring` type can validate minimum and maximum length of the string.
+For example, the `ibexa_string` type can validate minimum and maximum length of the string.
 It therefore provides a schema to indicate to the user that they might specify the corresponding restrictions, when creating a `FieldDefinition` with this type.
 The schema doesn't underlie any regulations, except for that it must be serializable.
 
@@ -130,7 +130,7 @@ services:
     Ibexa\FieldTypeMatrix\FieldType\Type:
         parent: Ibexa\Core\FieldType\FieldType
         tags:
-            - {name: ibexa.field_type, alias: ezmatrix}
+            - {name: ibexa.field_type, alias: ibexa_matrix}
 ```
 
 #### `parent`
@@ -145,7 +145,7 @@ Like most API components, field types use the [Symfony service tag mechanism]([[
 
 A service can be assigned one or several tags, with specific parameters.
 When the [service container](php_api.md#service-container) is compiled into a PHP file, tags are read by `CompilerPass` implementations that add extra handling for tagged services.
-Each service tagged as `ibexa.field_type` is added to a [registry](https://martinfowler.com/eaaCatalog/registry.html) using the `alias` key as its unique `fieldTypeIdentifier`, for example, `ezstring`.
+Each service tagged as `ibexa.field_type` is added to a [registry](https://martinfowler.com/eaaCatalog/registry.html) using the `alias` key as its unique `fieldTypeIdentifier`, for example, `ibexa_string`.
 Each field type must also inherit from the abstract `ibexa.field_type` service.
 This ensures that the initialization steps shared by all field types are executed.
 
diff --git a/docs/content_management/images/configure_image_editor.md b/docs/content_management/images/configure_image_editor.md
index 10f362c1f3..ed37e270ec 100644
--- a/docs/content_management/images/configure_image_editor.md
+++ b/docs/content_management/images/configure_image_editor.md
@@ -4,7 +4,7 @@ description: Configure image editor to crop, flip, and modify images.
 
 # Configure Image Editor
 
-When a content item contains fields of the [ezimage](imageassetfield.md) type, users can perform basic image editing functions with the Image Editor.
+When a content item contains fields of the [ibexa_image](imageassetfield.md) type, users can perform basic image editing functions with the Image Editor.
 
 For more information, see [User Documentation]([[= user_doc =]]/image_management/edit_images/).
 
diff --git a/docs/content_management/rich_text/extend_online_editor.md b/docs/content_management/rich_text/extend_online_editor.md
index bec4947c3c..7b3f328bfe 100644
--- a/docs/content_management/rich_text/extend_online_editor.md
+++ b/docs/content_management/rich_text/extend_online_editor.md
@@ -18,7 +18,7 @@ For more information about extending the back office, see [Extend back office](b
 ## Configure custom tags
 
 With custom tags, you can enhance the Online Editor with features that go beyond the built-in ones.
-You configure custom tags under the `ezrichtext` key.
+You configure custom tags under the `ibexa_richtext` key.
 
 Start preparing the tag by adding a configuration file: 
 
@@ -33,10 +33,10 @@ Supported attribute types are:
 
 You must provide your own files for the Twig template and the icon.
 Place the `factbox.html.twig` template in the 
-`templates/themes/<your-theme>/field_type/ezrichtext/custom_tags` directory:
+`templates/themes/<your-theme>/field_type/ibexa_richtext/custom_tags` directory:
 
 ```html+twig
-[[= include_file('code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ezrichtext/custom_tags/factbox.html.twig') =]]
+[[= include_file('code_samples/back_office/online_editor/custom_tags/factbox/templates/themes/standard/field_type/ibexa_richtext/custom_tags/factbox.html.twig') =]]
 ```
 
 !!! tip
@@ -91,10 +91,10 @@ Provide your own files for the Twig template and the icon.
 
 The tag has the `url` attribute with the `type` parameter set as `link` (lines 30-31).
 
-Then create the `templates/themes/<your-theme>/field_type/ezrichtext/custom_tags/linktag.html.twig` template:
+Then create the `templates/themes/<your-theme>/field_type/ibexa_richtext/custom_tags/linktag.html.twig` template:
 
 ``` html+twig
-[[= include_file('code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ezrichtext/custom_tags/linktag.html.twig') =]]
+[[= include_file('code_samples/back_office/online_editor/custom_tags/linktag/templates/themes/standard/field_type/ibexa_richtext/custom_tags/linktag.html.twig') =]]
 ```
 
 Add labels for the tag by providing translations in `translations/custom_tags.en.yaml`:
@@ -146,8 +146,8 @@ Inline styles apply to the selected portion of text only, while block styles app
 
 Start creating a custom style by providing configuration:
 
-- a global list of custom styles, defined under the node `ezrichtext.custom_styles`,
-- a list of enabled custom styles for a given `admin` SiteAccess or `admin_group` SiteAccess group, located under the node `ibexa.system.<scope>.fieldtypes.ezrichtext.custom_styles`
+- a global list of custom styles, defined under the node `ibexa_richtext.custom_styles`,
+- a list of enabled custom styles for a given `admin` SiteAccess or `admin_group` SiteAccess group, located under the node `ibexa.system.<scope>.fieldtypes.ibexa_richtext.custom_styles`
 
 A sample configuration could look as follows:
 
@@ -172,19 +172,19 @@ It's recommended that you use the [design engine](design_engine.md).
 
 The template files for the front end could look as follows:
 
-- `templates/themes/standard/field_type/ezrichtext/custom_styles/highlighted_word.html.twig`:
+- `templates/themes/standard/field_type/ibexa_richtext/custom_styles/highlighted_word.html.twig`:
 
 ``` html+twig
 <span {% if id is defined %}id="{{ id }}"{% endif %} class="ezstyle-{{ name }}">{% apply spaceless %}{{ content|raw }}{% endapply %}</span>
 ```
 
-- `templates/themes/standard/field_type/ezrichtext/custom_styles/highlighted_block.html.twig`:
+- `templates/themes/standard/field_type/ibexa_richtext/custom_styles/highlighted_block.html.twig`:
 
 ``` html+twig
 <div {% if id is defined %}id="{{ id }}"{% endif %} class="{% if align is defined %}align-{{ align }}{% endif %} ezstyle-{{ name }}">{% apply spaceless %}{{ content|raw }}{% endapply %}</div>
 ```
 
-Templates for Content View in the back office would be `templates/themes/admin/field_type/ezrichtext/custom_styles/highlighted_word.html.twig` and `templates/themes/admin/field_type/ezrichtext/custom_styles/highlighted_block.html.twig` (assuming that the back office SiteAccess uses the default `admin` theme).
+Templates for Content View in the back office would be `templates/themes/admin/field_type/ibexa_richtext/custom_styles/highlighted_word.html.twig` and `templates/themes/admin/field_type/ibexa_richtext/custom_styles/highlighted_block.html.twig` (assuming that the back office SiteAccess uses the default `admin` theme).
 
 ### Use cases
 
@@ -221,7 +221,7 @@ You can now define the custom CSS for this template, for example by using [Webpa
 Add label for the new style by providing a translation in `translations/custom_styles.en.yaml`:
 
 ``` yaml
-ezrichtext.custom_styles.note_box.label: 'Note box'
+ibexa_richtext.custom_styles.note_box.label: 'Note box'
 ```
 
 ![Adding a Note box custom style](oe_custom_style_note_box_select.png)
@@ -258,7 +258,7 @@ You can now define the custom CSS for this template, for example by using [Webpa
 Add label for the new style by providing a translation in `translations/custom_styles.en.yaml`:
 
 ``` yaml
-ezrichtext.custom_styles.highlight.label: 'Highlight'
+ibexa_richtext.custom_styles.highlight.label: 'Highlight'
 ```
 
 ![Adding a Highlight custom style](oe_custom_style_highlight_select.png)
@@ -323,7 +323,7 @@ Here, the resulting values are `data-ezattribute-custom-attribute="false"` and `
 
 ### Custom CSS classes
 
-You configure custom CSS classes under the `fieldtypes.ezrichtext.classes` key.
+You configure custom CSS classes under the `fieldtypes.ibexa_richtext.classes` key.
 The configuration is SiteAccess-aware.
 
 You must provide the available `choices`.
@@ -426,7 +426,7 @@ module.exports = (ibexaConfig, ibexaConfigManager) => {
 
 See [Importing assets from a bundle](importing_assets_from_bundle.md) for alternative ways to add files to Webpack Encore entries.
 
-Add the plugin button to the RichText toolbar config (under `ibexa.system.<scope>.fieldtypes.ezrichtext.toolbar`).
+Add the plugin button to the RichText toolbar config (under `ibexa.system.<scope>.fieldtypes.ibexa_richtext.toolbar`).
 
 A new button group is defined in `config/packages/ibexa_admin_ui.yaml` with [the `specialcharacters` button exposed by the plugin API](https://ckeditor.com/docs/ckeditor5/latest/features/special-characters.html#common-api):
 
@@ -437,7 +437,7 @@ ibexa:
         admin_group:
             # …
             fieldtypes:
-                ezrichtext:
+                ibexa_richtext:
                     toolbar:
                         my_group:
                             priority: 25
diff --git a/docs/content_management/taxonomy/taxonomy.md b/docs/content_management/taxonomy/taxonomy.md
index 2f2fed4f58..23e4663465 100644
--- a/docs/content_management/taxonomy/taxonomy.md
+++ b/docs/content_management/taxonomy/taxonomy.md
@@ -47,8 +47,8 @@ taxonomy.content_categories: 'Content categories'
 
 Then, create a content type with `content_category` identifier and include the following field definitions:
 
-* `name` of `ezstring` type and required. Use this field, as `<name>`, for content name pattern.
-* `category_identifier` of `ezstring` type and required.
+* `name` of `ibexa_string` type and required. Use this field, as `<name>`, for content name pattern.
+* `category_identifier` of `ibexa_string` type and required.
 * `parent_category` of `ibexa_taxonomy_entry` type and not required. In its Taxonomy drop-down menu, select Content categories (or `taxonomy.content_categories` if no translation has been provided).
 
 Finish taxonomy setup by creating a new Content category named Root with identifier `content_categories_root` under the previously created container folder named Content categories.
diff --git a/docs/resources/phpstorm_plugin.md b/docs/resources/phpstorm_plugin.md
index eab598809b..57bc006521 100644
--- a/docs/resources/phpstorm_plugin.md
+++ b/docs/resources/phpstorm_plugin.md
@@ -192,7 +192,7 @@ Besides configuration structure, for the following YAML keys addition suggestion
 - List of available search engines, for:
     - `ibexa.repositories.<repository>.search.engine`
 - List of available custom tags, for:
-    - `ibexa.system.<scope>.fieldtypes.ezrichtext.custom_tags`
+    - `ibexa.system.<scope>.fieldtypes.ibexa_richtext.custom_tags`
 - List of available view types, for:
     - `ibexa.<scope>.content_view`
     - `ibexa.<scope>.content_create_view`
diff --git a/docs/search/criteria_reference/isfieldempty_criterion.md b/docs/search/criteria_reference/isfieldempty_criterion.md
index 97341ec019..a6bf07844a 100644
--- a/docs/search/criteria_reference/isfieldempty_criterion.md
+++ b/docs/search/criteria_reference/isfieldempty_criterion.md
@@ -16,7 +16,7 @@ or non-empty fields (`false`)
 
 The `IsFieldEmpty` Criterion isn't available in [Repository filtering](search_api.md#repository-filtering).
 
-The Richtext field type (`ezrichtext`) isn't searchable in the Legacy search engine.
+The Richtext field type (`ibexa_richtext`) isn't searchable in the Legacy search engine.
 
 ## Example
 
diff --git a/docs/search/search_criteria_and_sort_clauses.md b/docs/search/search_criteria_and_sort_clauses.md
index f2a13a1d7d..a6a624322b 100644
--- a/docs/search/search_criteria_and_sort_clauses.md
+++ b/docs/search/search_criteria_and_sort_clauses.md
@@ -23,7 +23,7 @@ Most often this is the case if you have a custom field type using external stora
 
 !!! note
 
-    Legacy (SQL-based) search can also be used in `ezkeyword` external storage.
+    Legacy (SQL-based) search can also be used in `ibexa_keyword` external storage.
 
 In such cases you can implement a custom Criterion or Sort Clause, together with the corresponding handlers for the storage engine you're using.
 
diff --git a/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md b/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md
index e654b0fdae..24a863dc03 100644
--- a/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md
+++ b/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md
@@ -46,7 +46,7 @@ Disable the Focus mode, go to content types screen and (under the content catego
 
 You also need to modify the built-in Article content type.
 It makes inserting photos into articles easier.
-Edit it to remove the Image field that has a Content Relation (ezobjectrelation) type, and create a new field in its place:
+Edit it to remove the Image field that has a Content Relation (ibexa_object_relation) type, and create a new field in its place:
 
 | Field type | Name  | Identifier | Required | Searchable | Translatable |
 |------------|-------|------------|----------|------------|--------------|
diff --git a/docs/users/oauth_client.md b/docs/users/oauth_client.md
index d845806a97..47e741d2e5 100644
--- a/docs/users/oauth_client.md
+++ b/docs/users/oauth_client.md
@@ -77,7 +77,7 @@ To use `ResourceOwnerToExistingOrNewUserMapper`, you need to extend it in your c
 
     To avoid issues with password restrictions in the built-in user content type, create a special content type (for example, "OAuth user"), without restrictions on the password.
 
-    This new content type must also contain the user (`ezuser`) field.
+    This new content type must also contain the user (`ibexa_user`) field.
 
 The following example shows how to create a Resource Owner mapper for the `google` client from previous examples.
 
diff --git a/docs/users/passwords.md b/docs/users/passwords.md
index ce90e7b900..371b6c0ac0 100644
--- a/docs/users/passwords.md
+++ b/docs/users/passwords.md
@@ -61,7 +61,7 @@ To access the password settings:
 1. In the back office, go to **Content** -> **Content types**.
 1. In the **Content type groups** table, click **Users**.
 1. Edit the **User** content type.
-1. In the **Field definitions** list, view the settings for **User account (ezuser)**.
+1. In the **Field definitions** list, view the settings for **User account (ibexa_user)**.
 
 !!! tip
 
@@ -70,7 +70,7 @@ To access the password settings:
 
 ## Password attributes
 
-In the **User account (ezuser)** Field definition, you can determine if the password must contain at least:
+In the **User account (ibexa_user)** Field definition, you can determine if the password must contain at least:
 
 - One uppercase letter
 - One lowercase letter
@@ -81,7 +81,7 @@ You can also set the minimum password length.
 
 ## Password expiration
 
-In the **User account (ezuser)** field definition, you can set password expiration rules, which forces users to change their passwords periodically.
+In the **User account (ibexa_user)** field definition, you can set password expiration rules, which forces users to change their passwords periodically.
 
 ![Password expiry settings](password_expiry.png)
 
@@ -91,7 +91,7 @@ The notification is displayed in the back office after login and in the user con
 ## Repeating passwords
 
 You can set a rule that the password cannot be reused.
-You set it for the user content type in the **User account (ezuser)** field type's settings.
+You set it for the user content type in the **User account (ibexa_user)** field type's settings.
 When this is set, the user cannot type in the same password when it expires.
 It has to be changed to a new one.
 
@@ -103,7 +103,7 @@ This rule is valid by default when password expiration is set.
 ## Breached passwords
 
 You can set a rule that prevents using passwords which have been exposed in a public breach.
-To do this, in the **User account (ezuser)** field definition, select "Password must not be contained in a public breach".
+To do this, in the **User account (ibexa_user)** field definition, select "Password must not be contained in a public breach".
 
 ![Protection against using breached passwords](password_breached.png)
 

From 9b8efebb215a00d77f1b228b96d6bfa8c31e32ec Mon Sep 17 00:00:00 2001
From: mnocon <mnocon@users.noreply.github.com>
Date: Mon, 14 Jul 2025 11:42:13 +0000
Subject: [PATCH 2/5] PHP & JS CS Fixes

---
 .../back_office/udw/assets/js/image-tab/components/image.js   | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/code_samples/back_office/udw/assets/js/image-tab/components/image.js b/code_samples/back_office/udw/assets/js/image-tab/components/image.js
index a35836778c..52e6360737 100644
--- a/code_samples/back_office/udw/assets/js/image-tab/components/image.js
+++ b/code_samples/back_office/udw/assets/js/image-tab/components/image.js
@@ -40,7 +40,9 @@ const Image = ({ restInfo, location }) => {
     }, []);
 
     if (content) {
-        const imageField = content.CurrentVersion.Version.Fields.field.find((field) => field.fieldTypeIdentifier === 'ibexa_image').fieldValue;
+        const imageField = content.CurrentVersion.Version.Fields.field.find(
+            (field) => field.fieldTypeIdentifier === 'ibexa_image',
+        ).fieldValue;
 
         src = imageField.uri;
         alt = imageField.fileName;

From 3a694b049734e46a90edcd2b8c38e0f26afd02e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Noco=C5=84?= <mnocon@users.noreply.github.com>
Date: Mon, 14 Jul 2025 13:45:05 +0200
Subject: [PATCH 3/5] Renamed tables

---
 .../data_migration/data_migration_actions.md              | 2 +-
 docs/content_management/field_types/field_type_storage.md | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/content_management/data_migration/data_migration_actions.md b/docs/content_management/data_migration/data_migration_actions.md
index 2550af6957..c3e076dd0d 100644
--- a/docs/content_management/data_migration/data_migration_actions.md
+++ b/docs/content_management/data_migration/data_migration_actions.md
@@ -183,4 +183,4 @@ mode: Update
 
 !!! note
 
-    In the `unassign_role_user_group` action, the ID is role assignment ID from the `ezuser_role` table.
+    In the `unassign_role_user_group` action, the ID is role assignment ID from the `ibexa_user_role` table.
diff --git a/docs/content_management/field_types/field_type_storage.md b/docs/content_management/field_types/field_type_storage.md
index f6907eb661..ed3ab221c3 100644
--- a/docs/content_management/field_types/field_type_storage.md
+++ b/docs/content_management/field_types/field_type_storage.md
@@ -28,17 +28,17 @@ The SPI `FieldValue` struct has properties which the field type can use:
 
 ### Legacy storage engine
 
-The Legacy storage engine uses the `ezcontentobject_attribute` table to store field values,
-and `ezcontentclass_attribute` to store field definition values.
+The Legacy storage engine uses the `ibexa_content_field` table to store field values,
+and `ibexa_content_type_field_definition` to store field definition values.
 They're both based on the same principle.
 
 Each row represents a field or a field definition, and offers several free fields of different types, where the type can store its data.
 
-- `ezcontentobject_attribute` offers:
+- `ibexa_content_field` offers:
     - `data_int`
     - `data_text`
     - `data_float`
-- `ezcontentclass_attribute` offers:
+- `ibexa_content_type_field_definition` offers:
     - four `data_int` (`data_int1` to `data_int4`) fields
     - four `data_float` (`data_float1` to `data_float4`) ones
     - five `data_text` (`data_text1` to `data_text5`)

From 307c681ad4ad2197e8637a98a14eb0909033f3bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Noco=C5=84?= <mnocon@users.noreply.github.com>
Date: Mon, 14 Jul 2025 13:48:12 +0200
Subject: [PATCH 4/5] Adjusted nginx configuration

---
 docs/infrastructure_and_maintenance/clustering/clustering.md | 2 +-
 docs/multisite/site_factory/site_factory.md                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/infrastructure_and_maintenance/clustering/clustering.md b/docs/infrastructure_and_maintenance/clustering/clustering.md
index 9fd87a53c5..409dfd0616 100644
--- a/docs/infrastructure_and_maintenance/clustering/clustering.md
+++ b/docs/infrastructure_and_maintenance/clustering/clustering.md
@@ -248,7 +248,7 @@ Place this before the standard image rewrite rule in your vhost config (or uncom
 rewrite "^/var/([^/]+/)?storage/images(-versioned)?/(.*)" "/index.php" break;
 ```
 
-Place this before the include of `ez_params.d`/`ez_rewrite_params` in your vhost config (or uncomment if already there).
+Place this before the include of `ibexa_params.d`/`ibexa_rewrite_params` in your vhost config (or uncomment if already there).
 
 ## Migrating to a cluster setup
 
diff --git a/docs/multisite/site_factory/site_factory.md b/docs/multisite/site_factory/site_factory.md
index aaf2783668..260baa9345 100644
--- a/docs/multisite/site_factory/site_factory.md
+++ b/docs/multisite/site_factory/site_factory.md
@@ -119,7 +119,7 @@ To add a new domain, add it in `command:` and under frontend and backend aliases
 ```yaml hl_lines="3 6 11"
 services:
   web:
-    command: /bin/bash -c "cd /var/www && cp -a doc/nginx/ez_params.d /etc/nginx && bin/vhost.sh --host-name=site.example.com --host-alias='admin.example.com test.example.com' --template-file=doc/nginx/vhost.template > /etc/nginx/conf.d/default.conf && nginx -g 'daemon off;'"
+    command: /bin/bash -c "cd /var/www && cp -a doc/nginx/ibexa_params.d /etc/nginx && bin/vhost.sh --host-name=site.example.com --host-alias='admin.example.com test.example.com' --template-file=doc/nginx/vhost.template > /etc/nginx/conf.d/default.conf && nginx -g 'daemon off;'"
     networks:
       frontend:
         aliases:

From e407aa09dbc522d3051e0dac22bc14cea66470b7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Noco=C5=84?= <mnocon@users.noreply.github.com>
Date: Tue, 15 Jul 2025 12:02:34 +0200
Subject: [PATCH 5/5] Update
 code_samples/tutorials/page_tutorial/assets/css/style.css

---
 code_samples/tutorials/page_tutorial/assets/css/style.css | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code_samples/tutorials/page_tutorial/assets/css/style.css b/code_samples/tutorials/page_tutorial/assets/css/style.css
index 9a38d11076..4ad7e37f52 100644
--- a/code_samples/tutorials/page_tutorial/assets/css/style.css
+++ b/code_samples/tutorials/page_tutorial/assets/css/style.css
@@ -235,7 +235,7 @@ footer div {
     margin-top: 15px;
 }
 
-.block-form .ibexa-string-field {
+.block-form .ibexa_string-field {
     display: inline-block;
     font-variant: small-caps;
     font-size: 1.2em;