ibexa · mnocon · Sep 7, 2026 · Sep 7, 2026
diff --git a/docs/administration/project_organization/project_organization.md b/docs/administration/project_organization/project_organization.md
@@ -6,8 +6,6 @@ description: A Cohesivo project follows Symfony's directory structure to organiz
 
 [[= product_name =]] is a Symfony application and follows the project structure used by Symfony.
 
-You can see an example of organizing a project in the [companion repository](https://github.com/ezsystems/ezplatform-ee-beginner-tutorial/tree/v3-master) for the [Beginner tutorial](page_and_form_tutorial.md).
-
 ## PHP code
 
 The project's PHP code (for example, controllers or event listeners) should be placed in the `src` folder.

diff --git a/docs/content_management/content_management_guide.md b/docs/content_management/content_management_guide.md
@@ -48,7 +48,6 @@ A structure of elements that *store* content information is referred to as the *
 [[= product_name =]] comes with a predefined content model that includes a broad set of various field types and several content types.
 
 You can customize and adapt the content model to your organization's needs and the type of output channel that you use.
-If need be, development teams can [create new field types](creating_a_point2d_field_type.md), to enhance editor and visitor experiences.
 Content managers or even editors can then apply such field types when they modify existing or create new content types.
 The editing interface lets all users, including those with no coding experience, create or modify certain areas of the content model.
 

diff --git a/docs/content_management/field_types/create_custom_generic_field_type.md b/docs/content_management/field_types/create_custom_generic_field_type.md
@@ -9,8 +9,6 @@ You can use it as a base for custom field types.
 The Generic field type comes with the implementation of basic methods,
 reduces the number of classes which must be created, and simplifies the tagging process.
 
-A more in-depth, step-by-step tutorial can be viewed here: [Creating a Point 2D field type](creating_a_point2d_field_type.md).
-
 !!! tip
 
     You should not use the Generic field type when you need a very specific implementation or complete control over the way data is stored.

diff --git a/docs/content_management/images/add_image_asset_from_dam.md b/docs/content_management/images/add_image_asset_from_dam.md
@@ -83,7 +83,7 @@ In the **Content** group, create a content type for DAM images, which includes t
 
 Now, when you use the Embed block in the Page Builder, you should see a DAM Image.
 
-For more information about block customization (defined templates, variations), see [Create custom block](4_create_a_custom_block.md).
+For more information about block customization (defined templates, variations), see [Page blocks](../pages/page_blocks.md).
 
 ## Extend DAM support by adding custom connector
 

diff --git a/docs/content_management/images/extend_image_editor.md b/docs/content_management/images/extend_image_editor.md
@@ -31,7 +31,7 @@ Configure the new Image Editor action under the `ibexa.system.<scope>.image_edit
 
 ## Add entry to the Webpack configuration
 
-Once you create and configure the React component, you must add an entry to [the Webpack configuration](3_customize_the_front_page.md#configuring-webpack).
+Once you create and configure the React component, you must add an entry to the Webpack configuration.
 In the root directory of your project, modify the `webpack.config.js` file by adding the following code:
 
 ``` js

diff --git a/docs/content_management/pages/ibexa_connect_scenario_block.md b/docs/content_management/pages/ibexa_connect_scenario_block.md
@@ -11,7 +11,6 @@ Scenario block is a regular [Page block](page_blocks.md) and can be configured o
 !!! caution
 
     When setting up your instance, ensure you have profiler enabled.
-    To set up Page Builder in [[= product_name =]], follow the [Page and Form tutorial](page_and_form_tutorial.md).
 
 ## Scenario block configuration
 

diff --git a/docs/getting_started/first_steps.md b/docs/getting_started/first_steps.md
@@ -7,10 +7,6 @@ description: Start off working with Cohesivo by doing initial configuration and
 This page lists first steps you can take after installing [[= product_name =]].
 These steps are the most common actions you may need to take in a new installation.
 
-!!! tip "Beginner tutorial"
-
-    To go through a full tutorial that leads from a clean installation to creating a full site, see [Beginner tutorial](beginner_tutorial.md).
-
 ## Remove welcome page
 
 ![Welcome page](welcome_page.png)

diff --git a/docs/index.md b/docs/index.md
@@ -6,22 +6,6 @@
             <h1>Ibexa Developer Documentation</h1>
             <h2>How to start?</h2>
         </div>
-        <div class="col-12 col-lg-6 col-fhd-3">
-            <a class="info-tile" href="tutorials/beginner_tutorial/beginner_tutorial/">
-                <div class="info-tile__circle" style="background-color: #f6e7ef;">
-                    <svg width="25" height="25"><use xlink:href="images/icons.svg#install-dxp" /></svg>
-                </div>
-                <div class="info-tile__content">
-                    <div class="info-tile__details">
-                        Details
-                        <svg class="info-tile__arrow-icon"><use xlink:href="images/icons.svg#arrow" /></svg>
-                    </div>
-                    <div>
-                        Follow the <strong>Beginner tutorial</strong>
-                    </div>
-                </div>
-            </a>
-        </div>
         <div class="col-12 col-lg-6 col-fhd-3">
             <a class="info-tile" href="api/api/">
                 <div class="info-tile__circle" style="background-color: #ecf8fb;">

diff --git a/docs/tutorials/beginner_tutorial/1_get_ready.md b/docs/tutorials/beginner_tutorial/1_get_ready.md
diff --git a/docs/tutorials/beginner_tutorial/2_create_the_content_model.md b/docs/tutorials/beginner_tutorial/2_create_the_content_model.md