update: upgrading node version for admin build

book/templates.rst

@@ -382,7 +382,7 @@ from within a block.
 
 .. note::
 
-    Because the ``&`` character needs to be escaped inside of XML files, you have to use ``AND`` instead of ``&&`` 
+    Because the ``&`` character needs to be escaped inside of XML files, you have to use ``AND`` instead of ``&&``
     if you want to connect conditions using a logical and. Additionally, you can use ``OR`` instead of ``||``.
 
 Language Independent Properties
@@ -942,23 +942,15 @@ node and the ``ref`` attribute:
     <block name="blocks" default-type="text_block" minOccurs="0">
         <types>
             <type ref="text_block" />
-            <type name="editor">
-                <meta>
-                    <title lang="en">Editor</title>
-                    <title lang="de">Editor</title>
-                </meta>
-                <properties>
-                    <property name="text_editor" type="text_editor">
-                        <meta>
-                            <title lang="en">Text Editor</title>
-                            <title lang="de">Texteditor</title>
-                        </meta>
-                    </property>
-                </properties>
-            </type>
         </types>
     </block>
 
+.. note::
+
+    Mixing global and local block types is supported, but it is recommended to keep your block type names unique
+    to avoid confusion. This approach also simplifies the transition to global blocks in the future, eliminating the need
+    for data migrations.
+
 Caching
 -------
 

bundles/reference.rst

@@ -7,15 +7,11 @@ and location in which an entity is utilized. Presently, the ReferenceBundle is c
 Media within PHPCR entities such as `pages` and `snippets`. These references are managed distinctly for the draft
 state within the `admin context` and the live state within the `website context`.
 
-|
-
 The main reason we need this bundle is that, unlike traditional database references, our content management system
 operates on an unstructured data model. Therefore, we cannot rely solely on database references, which are usually preferred.
 It is essential to note that the ReferenceBundle should only be used for unstructured data, where database relations are
 not feasible.
 
-|
-
 Content maintainers are able to see the references to a specific entity in the `Insights` tab of an entity like `Snippet`.
 
 .. figure:: ../img/snippet-insights.png
@@ -34,7 +30,6 @@ references by executing the `bin/console sulu:references:refresh` command. This
 
     bin/console sulu:references:refresh <resource-key>
 
-
 .. note::
 
     Please note that references are only refreshed for the current context. To refresh the references for both the
@@ -47,8 +42,6 @@ To integrate the ReferenceBundle for custom content-types, you need to implement
 content-type class. The interface requires you to implement the `getReferences` method. The method already receives the
 `ReferenceCollector` which you can use to add references to the collector.
 
-|
-
 Example implementation for a custom content-type:
 
 .. code-block:: php
@@ -65,4 +58,4 @@ Example implementation for a custom content-type:
                 (string) $data['id'],
                 $propertyPrefix . $property->getName()
             );
-    }
+    }

cookbook/build-admin-frontend.rst

@@ -31,7 +31,7 @@ Solution 2: Build manually with docker
 
 .. code-block:: bash
 
-    docker run --rm --interactive --tty --volume ${PWD}:/var/project node:14.16.0 /bin/bash
+    docker run --rm --interactive --tty --volume ${PWD}:/var/project node:20-alpine3.18 /bin/sh
 
     # for completion: using another node version is possible by adjusting the tag of the node image
     # docker run --rm --interactive --tty --volume ${PWD}:/var/project node:12.21.0 /bin/bash