diff --git a/.editorconfig b/.editorconfig
index 25e24d98a..2913db533 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -1,25 +1,68 @@
-# EditorConfig is awesome: https://EditorConfig.org
-#
-# Use as master: https://github.com/TYPO3-Documentation/T3DocTeam/blob/main/.editorconfig
+# EditorConfig is awesome: http://EditorConfig.org
 
 # top-most EditorConfig file
 root = true
 
-[{*.rst,*.rst.txt}]
+# Unix-style newlines with a newline ending every file
+[*]
 charset = utf-8
 end_of_line = lf
+indent_style = space
+indent_size = 4
 insert_final_newline = true
 trim_trailing_whitespace = true
-indent_style = space
+
+# TS/JS-Files
+[*.{ts,js,mjs}]
+indent_size = 2
+
+# JSON-Files
+[*.json]
+indent_style = tab
+
+# ReST-Files
+[*.{rst,rst.txt}]
 indent_size = 4
 max_line_length = 80
 
-# MD-Files
+# Markdown-Files
 [*.md]
-charset = utf-8
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
-indent_style = space
-indent_size = 4
 max_line_length = 80
+
+# YAML-Files
+[*.{yaml,yml}]
+indent_size = 2
+
+# NEON-Files
+[*.neon]
+indent_size = 2
+indent_style = tab
+
+# stylelint
+[.stylelintrc]
+indent_size = 2
+
+# package.json
+[package.json]
+indent_size = 2
+
+# TypoScript
+[*.{typoscript,tsconfig}]
+indent_size = 2
+
+# XLF-Files
+[*.xlf]
+indent_style = tab
+
+# SQL-Files
+[*.sql]
+indent_style = tab
+indent_size = 2
+
+# .htaccess
+[{_.htaccess,.htaccess}]
+indent_style = tab
+
+[Makefile]
+# Use tabs for indentation (Makefiles require tabs)
+indent_style = tab
diff --git a/.github/workflows/apply-precommit.yml b/.github/workflows/apply-precommit.yml
new file mode 100644
index 000000000..a416a2d2b
--- /dev/null
+++ b/.github/workflows/apply-precommit.yml
@@ -0,0 +1,71 @@
+name: Check and Fix Whitespace on Schedule
+
+on:
+  schedule:
+    - cron: '0 0 * * *'
+  workflow_dispatch:
+
+jobs:
+  lint:
+    if: github.repository_owner == 'TYPO3-documentation'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+
+      - name: Install pre-commit
+        run: pip install pre-commit
+
+      - name: Run pre-commit hooks and apply fixes
+        id: pre-commit
+        run: |
+          # Run pre-commit with auto-fix and ignore exit code
+          pre-commit run --all-files --hook-stage=manual --show-diff-on-failure || true
+          # Check if any files were modified
+          git diff --exit-code || echo "FIX_NEEDED=true" >> $GITHUB_ENV
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Check for existing PR
+        if: env.FIX_NEEDED == 'true'
+        id: check_pr
+        run: |
+          EXISTING_PR=$(gh pr list --state open --search "Fix whitespace issues" --json number -q '.[].number')
+          if [[ -n "$EXISTING_PR" ]]; then
+            echo "EXISTING_PR=true" >> $GITHUB_ENV
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Create and push changes if needed
+        if: env.FIX_NEEDED == 'true' && env.EXISTING_PR != 'true'
+        id: create_branch
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          # Create a new branch for the changes
+          BRANCH_NAME="fix/whitespace-$(date +'%Y%m%d%H%M%S')"
+          git checkout -b "$BRANCH_NAME"
+          git add .
+          git commit -m "fix: apply whitespace fixes"
+          git push origin "$BRANCH_NAME"
+          echo "branch_name=$BRANCH_NAME" >> $GITHUB_ENV
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Open Pull Request
+        if: env.FIX_NEEDED == 'true' && env.EXISTING_PR != 'true'
+        uses: repo-sync/pull-request@v2
+        with:
+          source_branch: ${{ env.branch_name }}
+          destination_branch: ${{ github.ref_name }}
+          pr_title: "Fix whitespace issues"
+          pr_body: "This PR automatically applies whitespace fixes."
+          token: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index e31d41dc1..eb95547fe 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -35,8 +35,12 @@ jobs:
       - name: Composer validate
         run: Build/Scripts/runTests.sh -p ${{ env.php }} -s composerValidate
 
-      - name: Composer normalize
-        run: Build/Scripts/runTests.sh -p ${{ env.php }} -s composerNormalize -n
+      # Disabled composer-normalize for now because ergebnis/composer-normalize
+      # still hard-depends on localheinz/diff, which conflicts with sebastian/diff
+      # and causes fatal errors in our CI. Re-enable once the upstream dependency
+      # situation is resolved in a newer release.
+      # - name: Composer normalize
+      #   run: Build/Scripts/runTests.sh -p ${{ env.php }} -s composerNormalize -n
 
       - name: CGL
         run: Build/Scripts/runTests.sh -n -p ${{ env.php }} -s cgl -n
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
new file mode 100644
index 000000000..7be147642
--- /dev/null
+++ b/.pre-commit-config.yaml
@@ -0,0 +1,6 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.4.0  # Use the latest version
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
diff --git a/Documentation/About.rst b/Documentation/About.rst
deleted file mode 100644
index d11dcaed2..000000000
--- a/Documentation/About.rst
+++ /dev/null
@@ -1,60 +0,0 @@
-.. include:: /Includes.rst.txt
-
-
-.. _about:
-
-=================
-About This Manual
-=================
-
-This document is a complete reference to all objects types and properties of
-TypoScript as used in frontend TypoScript configuration, and not in
-:ref:`TSconfig backend configuration <t3tsconfig:start>`.
-
-.. seealso::
-
-    * For explanations about the syntax of TypoScript itself,
-      please refer to the
-      :ref:`TypoScript Syntax <t3coreapi:typoscript-syntax-start>`
-      chapter in "TYPO3 Explained"
-    * For an introduction to TypoScript configuration, see :ref:`t3ts45:start`
-
-.. _credits:
-
-Credits
-=======
-
-The manual was originally written by Kasper Skårhøj. Over the years it
-has been maintained and updated successively by Michael Stucki,
-François Suter and Christopher Stelmaszyk.
-
-
-.. _feedback:
-.. _contribute:
-
-Contribute
-==========
-
-If you find a bug in this manual, please be so kind as to check the
-`online version on <https://docs.typo3.org/typo3cms/TyposcriptReference/>`__.
-From there you can hit the "Edit me on GitHub" button in the top right corner
-and submit a pull request via GitHub. Alternatively you can `file an issue
-using the bug tracker <https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-Typoscript/issues>`__.
-
-Maintaining high quality documentation requires time and effort
-and the TYPO3 Documentation Team always appreciates support.
-
-.. _contact:
-
-Contact
-=======
-
-If you want to support us, please join the slack channel **#typo3-documentation**
-on `Slack <https://typo3.slack.com/>`__.
-Visit `forger <https://forger.typo3.com/slack>`__ to gain access to Slack.
-
-And finally, as a last resort, you can get in touch with the documentation team
-`by mail <documentation@typo3.org>`_.
-
-
-
diff --git a/Documentation/AppendixA/Index.rst b/Documentation/AppendixA/Index.rst
index 8b5b6b9e7..ff0fdc94d 100644
--- a/Documentation/AppendixA/Index.rst
+++ b/Documentation/AppendixA/Index.rst
@@ -1,9 +1,9 @@
 ..  include:: /Includes.rst.txt
 ..  _appendix-a:
 
-================================
-Appendix A – PHP include scripts
-================================
+==================
+PHP and TypoScript
+==================
 
 ..  _content-object-renderer:
 
@@ -57,6 +57,11 @@ This will stdWrap the content with the properties of `.stdWrap` of the
 TypoScriptFrontendController, TSFE
 ==================================
 
+..  deprecated:: 13.4
+    The class :php:`\TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController`
+    and its global instance :php:`$GLOBALS['TSFE']` have been marked as
+    deprecated. The class will be removed with TYPO3 v14.
+
 You can retrieve the :php:`\TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController`
 via the :ref:`request <t3coreapi:typo3-request>` attribute
 :ref:`frontend.controller <t3coreapi:typo3-request-attribute-frontend-controller>`.
diff --git a/Documentation/CodeSnippets/Config/Menus.php b/Documentation/CodeSnippets/Config/Menus.php
index b02176f13..79622a8ba 100644
--- a/Documentation/CodeSnippets/Config/Menus.php
+++ b/Documentation/CodeSnippets/Config/Menus.php
@@ -68,37 +68,11 @@
         'sourceFile' => 'EXT:fluid_styled_content/Resources/Private/Templates/MenuCategorizedPages.html',
         'targetFileName' => 'CodeSnippets/Menu/Template/MenuCategorizedPages.rst.txt',
     ],
-    // special = browse
-    [
-        'action' => 'createCodeSnippet',
-        'caption' => 'EXT:site_package/Configuration/TypoScript/Seo/Setup/RelPrevNextMenu.typoscript',
-        'sourceFile' => 'EXT:site_package/Configuration/TypoScript/Seo/Setup/RelPrevNextMenu.typoscript',
-        'targetFileName' => 'CodeSnippets/Menu/TypoScript/RelPrevNextMenu.rst.txt',
-    ],
     // special = rootline
     [
         'action' => 'createCodeSnippet',
-        'caption' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbLib.typoscript',
-        'sourceFile' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbLib.typoscript',
-        'targetFileName' => 'CodeSnippets/Menu/TypoScript/BreadcrumbLib.rst.txt',
-    ],
-    [
-        'action' => 'createCodeSnippet',
-        'caption' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbDataProcessor.typoscript',
-        'sourceFile' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbDataProcessor.typoscript',
-        'targetFileName' => 'CodeSnippets/Menu/TypoScript/BreadcrumbDataProcessor.rst.txt',
-    ],
-    [
-        'action' => 'createCodeSnippet',
-        'caption' => 'EXT:site_package/Resources/Private/Templates/Partials/Navigation/Breadcrumb.html',
-        'sourceFile' => 'EXT:site_package/Resources/Private/Templates/Partials/Navigation/Breadcrumb.html',
+        'caption' => 'EXT:site_package/Resources/Private/PageView/Partials/Navigation/Breadcrumb.html',
+        'sourceFile' => 'EXT:site_package/Resources/Private/PageView/Partials/Navigation/Breadcrumb.html',
         'targetFileName' => 'CodeSnippets/Menu/Template/BreadcrumbDataProcessor.rst.txt',
     ],
-    // special = language
-    [
-        'action' => 'createCodeSnippet',
-        'caption' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/LanguageMenuLib.typoscript',
-        'sourceFile' => 'EXT:site_package/Configuration/TypoScript/Menus/Setup/LanguageMenuLib.typoscript',
-        'targetFileName' => 'CodeSnippets/Menu/TypoScript/LanguageMenuLib.rst.txt',
-    ],
 ];
diff --git a/Documentation/CodeSnippets/Config/TSconfig.php b/Documentation/CodeSnippets/Config/TSconfig.php
new file mode 100644
index 000000000..f713ecd97
--- /dev/null
+++ b/Documentation/CodeSnippets/Config/TSconfig.php
@@ -0,0 +1,21 @@
+<?php
+
+// https=>//github.com/TYPO3-Documentation/t3docs-codesnippets
+// ddev exec vendor/bin/typo3  restructured_api_tools:php_domain public/fileadmin/TYPO3CMS-Reference-TSconfig/Documentation/CodeSnippets/
+
+return [
+    [
+        'action' => 'createCodeSnippet',
+        'sourceFile' => 'EXT:examples/Configuration/TsConfig/Page/Mod/csvExport.tsconfig',
+        'targetFileName' => 'CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt',
+        'caption' => 'EXT:examples/Configuration/TsConfig/Page/Mod/csvExport.tsconfig',
+        'language' => 'typoscript',
+    ],
+    [
+        'action' => 'createCodeSnippet',
+        'sourceFile' => 'EXT:examples/Configuration/TsConfig/Page/Mod/noExportRecordsLinks.tsconfig',
+        'targetFileName' => 'CodeSnippets/PageTSconfig/Mod/noExportRecordsLinks.rst.txt',
+        'caption' => 'EXT:examples/Configuration/TsConfig/Page/Mod/noExportRecordsLinks.tsconfig',
+        'language' => 'typoscript',
+    ],
+];
diff --git a/Documentation/CodeSnippets/DataProcessing/DataProcessingTemplates.rst.txt b/Documentation/CodeSnippets/DataProcessing/DataProcessingTemplates.rst.txt
index 47b3278d5..9ae07f452 100644
--- a/Documentation/CodeSnippets/DataProcessing/DataProcessingTemplates.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/DataProcessingTemplates.rst.txt
@@ -5,8 +5,7 @@
     :caption: EXT:examples/Configuration/TypoScript/DataProcessors/General.typoscript
 
     lib.contentElement {
-       templateRootPaths.200 = EXT:examples/Resources/Private/Templates/ContentElements/
-       partialRootPaths.200 = EXT:examples/Resources/Private/Partials/ContentElements/
-       layoutRootPaths.200 = EXT:examples/Resources/Private/Layout/
+        templateRootPaths.200 = EXT:examples/Resources/Private/Templates/ContentElements/
+        partialRootPaths.200 = EXT:examples/Resources/Private/Partials/ContentElements/
+        layoutRootPaths.200 = EXT:examples/Resources/Private/Layout/
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcCsv.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcCsv.rst.txt
index c5e3362a4..d8d671410 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcCsv.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcCsv.rst.txt
@@ -20,4 +20,3 @@
           </f:for>
        </table>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcCustom.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcCustom.rst.txt
index 97579d0c3..40fa455ae 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcCustom.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcCustom.rst.txt
@@ -18,4 +18,3 @@
        </ul>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcDb.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcDb.rst.txt
index 3dadf821c..84d8dd184 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcDb.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcDb.rst.txt
@@ -26,4 +26,3 @@
        </div>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcFiles.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcFiles.rst.txt
index 7440a8b5f..04f29681f 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcFiles.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcFiles.rst.txt
@@ -25,4 +25,3 @@
           </div>
        </div>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcGallery.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcGallery.rst.txt
index cc0d773c9..e731d05c8 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcGallery.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcGallery.rst.txt
@@ -25,4 +25,3 @@
        </f:for>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcLangMenu.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcLangMenu.rst.txt
index 5dfd13fbd..ea4293699 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcLangMenu.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcLangMenu.rst.txt
@@ -31,4 +31,3 @@
        </f:if>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt
index baf242f20..eabbc5b90 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt
@@ -49,4 +49,3 @@
           </f:for>
        </ul>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSite.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSite.rst.txt
index 28b194d06..5d3f7994d 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSite.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSite.rst.txt
@@ -13,4 +13,3 @@
        <p>Base url: <f:link.page pageUid="{site.rootPageId}">{site.configuration.base}</f:link.page></p>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSiteLanguage.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSiteLanguage.rst.txt
index 4c21ad9e7..faef9527d 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSiteLanguage.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSiteLanguage.rst.txt
@@ -13,4 +13,3 @@
     <p>language id: {language.languageId}</p>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSplit.rst.txt b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSplit.rst.txt
index 202b977ed..f757b5f04 100644
--- a/Documentation/CodeSnippets/DataProcessing/Template/DataProcSplit.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/Template/DataProcSplit.rst.txt
@@ -15,4 +15,3 @@
        </f:for>
 
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/CommaSeparatedValueProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/CommaSeparatedValueProcessor.rst.txt
index 1e7edcdf6..1f9f38c35 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/CommaSeparatedValueProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/CommaSeparatedValueProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_newcontentcsv =< lib.contentElement
         examples_newcontentcsv {
             templateName = DataProcCsv
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = comma-separated-value
             dataProcessing.10 {
                 if.isTrue.field = bodytext
@@ -22,4 +19,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/CustomCategoryProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/CustomCategoryProcessor.rst.txt
index c18956094..cff35d0ea 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/CustomCategoryProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/CustomCategoryProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataproccustom =< lib.contentElement
         examples_dataproccustom {
             templateName = DataProcCustom
-            # Before TYPO3 v12.1 you have to give the fully-qualified class name of the processor
-            # dataProcessing.10 = T3docs\Examples\DataProcessing\CustomCategoryProcessor
-            # Since TYPO3 v12.1 one can also use a (in Services.yaml) configured alias
             dataProcessing.10 = custom-category
             dataProcessing.10 {
                 as = categories
@@ -18,4 +15,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/DatabaseQueryProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/DatabaseQueryProcessor.rst.txt
index 113be1ae5..dda16084a 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/DatabaseQueryProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/DatabaseQueryProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataprocdb =< lib.contentElement
         examples_dataprocdb {
             templateName = DataProcDb
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = database-query
             dataProcessing.10 {
                 if.isTrue.field = pages
@@ -20,7 +17,7 @@
                 as = myHaikus
                 // recursively process the images in the records with the FilesProcessor
                 dataProcessing {
-                    10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
+                    10 = files
                     10 {
                         references.fieldName = image
                     }
@@ -28,4 +25,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/FilesProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/FilesProcessor.rst.txt
index 6c68fd394..74f4dfa26 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/FilesProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/FilesProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataprocfiles =< lib.contentElement
         examples_dataprocfiles {
             templateName = DataProcFiles
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = files
             dataProcessing.10 {
                 as = images
@@ -21,4 +18,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/GalleryProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/GalleryProcessor.rst.txt
index b62e9bac3..7a6fc82cd 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/GalleryProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/GalleryProcessor.rst.txt
@@ -10,9 +10,6 @@
             templateName = DataProcGallery
             dataProcessing {
                 # Process files
-                # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-                # 10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-                # Since TYPO3 v12.1 one can also use the available alias
                 10 = files
                 10 {
                     as = images
@@ -23,9 +20,6 @@
                 }
 
                 # Calculate gallery info
-                # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-                # 20 = TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor
-                # Since TYPO3 v12.1 one can also use the available alias
                 20 = gallery
                 20 {
                     filesProcessedDataKey = images
@@ -44,4 +38,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/LanguageMenuProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/LanguageMenuProcessor.rst.txt
index 6b576449b..5655698a5 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/LanguageMenuProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/LanguageMenuProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataproclang =< lib.contentElement
         examples_dataproclang {
             templateName = DataProcLangMenu
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = language-menu
             dataProcessing.10 {
                 languages = auto
@@ -18,4 +15,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt
index 730577e75..90b33b25c 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataprocmenu =< lib.contentElement
         examples_dataprocmenu {
             templateName = DataProcMenu
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = menu
             dataProcessing.10 {
                 levels = 2
@@ -19,9 +16,6 @@
                 includeSpacer = 1
                 titleField = nav_title // title
                 dataProcessing {
-                    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-                    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-                    # Since TYPO3 v12.1 one can also use the available alias
                     10 = files
                     10 {
                         references.fieldName = media
@@ -30,4 +24,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteLanguageProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteLanguageProcessor.rst.txt
index 63c0bdc7e..a9168572d 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteLanguageProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteLanguageProcessor.rst.txt
@@ -8,13 +8,9 @@
         examples_dataprocsitelanguage =< lib.contentElement
         examples_dataprocsitelanguage {
             templateName = DataProcSiteLanguage
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\SiteLanguageProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = site-language
             dataProcessing.10 {
                 as = language
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteProcessor.rst.txt
index 69da9a0e0..25593869c 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/SiteProcessor.rst.txt
@@ -8,13 +8,9 @@
         examples_dataprocsite =< lib.contentElement
         examples_dataprocsite {
             templateName = DataProcSite
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\SiteProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = site
             dataProcessing.10 {
                 as = site
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/DataProcessing/TypoScript/SplitProcessor.rst.txt b/Documentation/CodeSnippets/DataProcessing/TypoScript/SplitProcessor.rst.txt
index 7ade1bf1f..1b33b3d94 100644
--- a/Documentation/CodeSnippets/DataProcessing/TypoScript/SplitProcessor.rst.txt
+++ b/Documentation/CodeSnippets/DataProcessing/TypoScript/SplitProcessor.rst.txt
@@ -8,9 +8,6 @@
         examples_dataprocsplit =< lib.contentElement
         examples_dataprocsplit {
             templateName = DataProcSplit
-            # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-            # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\SplitProcessor
-            # Since TYPO3 v12.1 one can also use the available alias
             dataProcessing.10 = split
             dataProcessing.10 {
                 as = urlParts
@@ -22,4 +19,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/BreadcrumbDataProcessor.rst.txt b/Documentation/CodeSnippets/Menu/Template/BreadcrumbDataProcessor.rst.txt
index d2b9a3cb4..8c46b6df8 100644
--- a/Documentation/CodeSnippets/Menu/Template/BreadcrumbDataProcessor.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/BreadcrumbDataProcessor.rst.txt
@@ -1,25 +1,28 @@
 ..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
-..  Extracted from EXT:site_package/Resources/Private/Templates/Partials/Navigation/Breadcrumb.html
+..  Extracted from EXT:site_package/Resources/Private/PageView/Partials/Navigation/Breadcrumb.html
 
 ..  code-block:: html
-    :caption: EXT:site_package/Resources/Private/Templates/Partials/Navigation/Breadcrumb.html
+    :caption: EXT:site_package/Resources/Private/PageView/Partials/Navigation/Breadcrumb.html
 
     <f:if condition="{breadcrumb}">
-        <ol class="breadcrumb">
-            <f:for each="{breadcrumb}" as="item">
-                <li class="breadcrumb-item{f:if(condition: item.current, then: ' active')}" >
-                    <f:if condition="{item.current}">
-                        <f:then>
-                            <span class="breadcrumb-text">{item.title}</span>
-                        </f:then>
-                        <f:else>
-                            <a class="breadcrumb-link" href="{item.link}" title="{item.title}">
-                                <span class="breadcrumb-text">{item.title}</span>
-                            </a>
-                        </f:else>
-                    </f:if>
-                </li>
-            </f:for>
-        </ol>
+        <div class="container">
+            <nav aria-label="breadcrumb">
+                <ol class="breadcrumb breadcrumb-chevron p-3 bg-body-tertiary">
+                    <f:for each="{breadcrumb}" as="item">
+                        <f:if condition="{item.current}">
+                            <f:then>
+                                <li class="breadcrumb-item active" aria-current="page">{item.title}</li>
+                            </f:then>
+                            <f:else>
+                                <li class="breadcrumb-item">
+                                    <a class="link-body-emphasis fw-semibold text-decoration-none" href="{item.link}" title="{item.title}">
+                                        <span class="breadcrumb-text">{item.title}</span>
+                                    </a>
+                                </li>
+                            </f:else>
+                        </f:if>
+                    </f:for>
+                </ol>
+            </nav>
+        </div>
     </f:if>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/MenuCategorizedPages.rst.txt b/Documentation/CodeSnippets/Menu/Template/MenuCategorizedPages.rst.txt
index b80c04427..56f39a7c6 100644
--- a/Documentation/CodeSnippets/Menu/Template/MenuCategorizedPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/MenuCategorizedPages.rst.txt
@@ -22,4 +22,3 @@
 
     </f:section>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/MenuPages.rst.txt b/Documentation/CodeSnippets/Menu/Template/MenuPages.rst.txt
index 7f3550f74..c894d5ab0 100644
--- a/Documentation/CodeSnippets/Menu/Template/MenuPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/MenuPages.rst.txt
@@ -21,4 +21,3 @@
 
     </f:section>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/MenuRecentlyUpdated.rst.txt b/Documentation/CodeSnippets/Menu/Template/MenuRecentlyUpdated.rst.txt
index e8dd28c80..4cfdf1696 100644
--- a/Documentation/CodeSnippets/Menu/Template/MenuRecentlyUpdated.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/MenuRecentlyUpdated.rst.txt
@@ -22,4 +22,3 @@
 
     </f:section>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/MenuRelatedPages.rst.txt b/Documentation/CodeSnippets/Menu/Template/MenuRelatedPages.rst.txt
index 4233312f0..458eeae81 100644
--- a/Documentation/CodeSnippets/Menu/Template/MenuRelatedPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/MenuRelatedPages.rst.txt
@@ -22,4 +22,3 @@
 
     </f:section>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/Template/MenuSubpages.rst.txt b/Documentation/CodeSnippets/Menu/Template/MenuSubpages.rst.txt
index 9b74b0873..33d84fd46 100644
--- a/Documentation/CodeSnippets/Menu/Template/MenuSubpages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/Template/MenuSubpages.rst.txt
@@ -22,4 +22,3 @@
 
     </f:section>
     </html>
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbDataProcessor.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbDataProcessor.rst.txt
deleted file mode 100644
index ef7d3f845..000000000
--- a/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbDataProcessor.rst.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
-..  Extracted from EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbDataProcessor.typoscript
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbDataProcessor.typoscript
-
-    // include this breadcrumb menu in your Fluid template:
-    // <f:render partial="Page/Navigation/Breadcrumb" arguments="{_all}" />
-
-    page {
-      10 = FLUIDTEMPLATE
-      10 {
-        dataProcessing {
-          1657927210 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
-          1657927210 {
-            special = rootline
-            special.range = 0|-1
-            includeNotInMenu = 0
-            as = breadcrumb
-          }
-        }
-      }
-    }
-
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbLib.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbLib.rst.txt
deleted file mode 100644
index acb0b6c9a..000000000
--- a/Documentation/CodeSnippets/Menu/TypoScript/BreadcrumbLib.rst.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
-..  Extracted from EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbLib.typoscript
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbLib.typoscript
-
-    // include this breadcrumb menu in your Fluid template:
-    // <f:cObject typoscriptObjectPath="lib.breadcrumb" />
-
-    lib.breadcrumb = HMENU
-    lib.breadcrumb {
-      wrap = <ul class="breadcrumb">|</ul>
-      special = rootline
-      special.range = 1|-1
-      // render the menu
-      1 = TMENU
-      1 {
-        NO.wrapItemAndSub = <li>|</li>
-        // render the current page without link and with additional classs
-        CUR = 1
-        CUR.doNotLinkIt = 1
-        CUR.wrapItemAndSub = <li class="active">|</li>
-      }
-    }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/LanguageMenuLib.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/LanguageMenuLib.rst.txt
deleted file mode 100644
index cc9f57cdb..000000000
--- a/Documentation/CodeSnippets/Menu/TypoScript/LanguageMenuLib.rst.txt
+++ /dev/null
@@ -1,40 +0,0 @@
-..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
-..  Extracted from EXT:site_package/Configuration/TypoScript/Menus/Setup/LanguageMenuLib.typoscript
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/Menus/Setup/LanguageMenuLib.typoscript
-
-    lib.langMenu = HMENU
-    lib.langMenu {
-        special = language
-        special.value = 0,1,2
-        wrap = <ul class="langugageMenu">|</ul>
-        1 = TMENU
-        1 {
-            NO = 1
-            NO {
-                linkWrap = <li>|</li>
-                doNotLinkIt = 1
-                stdWrap.override = en || de || fr
-                stdWrap.typolink {
-                    parameter.data = page:uid
-                    additionalParams = &L=0 || &L=1 || &L=2
-                    addQueryString = 1
-                    addQueryString.exclude = L,id
-
-                }
-            }
-            // We are in the current language
-            ACT < .NO
-            ACT {
-                linkWrap = <li class="active">|</li>
-            }
-            // No translation available
-            USERDEF1 < .NO
-            USERDEF1 {
-                linkWrap = <li class="disabled">|</li>
-                stdWrap.typolink >
-            }
-        }
-    }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/MenuCategorizedPages.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/MenuCategorizedPages.rst.txt
index 78b1f3ac0..6200ffa2b 100644
--- a/Documentation/CodeSnippets/Menu/TypoScript/MenuCategorizedPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/TypoScript/MenuCategorizedPages.rst.txt
@@ -31,4 +31,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/MenuPages.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/MenuPages.rst.txt
index cd8543a56..9dd3dc978 100644
--- a/Documentation/CodeSnippets/Menu/TypoScript/MenuPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/TypoScript/MenuPages.rst.txt
@@ -26,4 +26,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/MenuRecentlyUpdated.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/MenuRecentlyUpdated.rst.txt
index bcbbf9a4a..ee1ff00da 100644
--- a/Documentation/CodeSnippets/Menu/TypoScript/MenuRecentlyUpdated.rst.txt
+++ b/Documentation/CodeSnippets/Menu/TypoScript/MenuRecentlyUpdated.rst.txt
@@ -30,4 +30,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/MenuRelatedPages.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/MenuRelatedPages.rst.txt
index e35207a3f..5a279aa95 100644
--- a/Documentation/CodeSnippets/Menu/TypoScript/MenuRelatedPages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/TypoScript/MenuRelatedPages.rst.txt
@@ -30,4 +30,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/MenuSubpages.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/MenuSubpages.rst.txt
index 3648670b4..6f32c6f0a 100644
--- a/Documentation/CodeSnippets/Menu/TypoScript/MenuSubpages.rst.txt
+++ b/Documentation/CodeSnippets/Menu/TypoScript/MenuSubpages.rst.txt
@@ -26,4 +26,3 @@
             }
         }
     }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/Menu/TypoScript/RelPrevNextMenu.rst.txt b/Documentation/CodeSnippets/Menu/TypoScript/RelPrevNextMenu.rst.txt
deleted file mode 100644
index e77de0dbe..000000000
--- a/Documentation/CodeSnippets/Menu/TypoScript/RelPrevNextMenu.rst.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
-..  Extracted from EXT:site_package/Configuration/TypoScript/Seo/Setup/RelPrevNextMenu.typoscript
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/Seo/Setup/RelPrevNextMenu.typoscript
-
-    page {
-      headerData {
-        // https://developers.google.com/search/blog/2011/09/pagination-with-relnext-and-relprev
-        10 = HMENU
-        10 {
-          special = browse
-          special {
-            items = prev|next
-            items.prevnextToSection = 1
-            excludeNoSearchPages = 1
-          }
-          1 = TMENU
-          1.NO {
-            allWrap = <link rel="prev" href="|"> |*| <link rel="next" href="|">
-            doNotLinkIt = 1
-            stdWrap {
-              typolink {
-                parameter.data = field:uid
-                returnLast = url
-              }
-            }
-          }
-        }
-      }
-    }
-    
\ No newline at end of file
diff --git a/Documentation/CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt b/Documentation/CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt
new file mode 100644
index 000000000..dfb08484a
--- /dev/null
+++ b/Documentation/CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt
@@ -0,0 +1,10 @@
+..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
+..  Extracted from EXT:examples/Configuration/TsConfig/Page/Mod/csvExport.tsconfig
+
+..  code-block:: typoscript
+    :caption: EXT:examples/Configuration/TsConfig/Page/Mod/csvExport.tsconfig
+
+    mod.web_list {
+       csvDelimiter = ;
+       csvQuote = '
+    }
diff --git a/Documentation/CodeSnippets/PageTSconfig/Mod/noExportRecordsLinks.rst.txt b/Documentation/CodeSnippets/PageTSconfig/Mod/noExportRecordsLinks.rst.txt
new file mode 100644
index 000000000..1c947d381
--- /dev/null
+++ b/Documentation/CodeSnippets/PageTSconfig/Mod/noExportRecordsLinks.rst.txt
@@ -0,0 +1,9 @@
+..  Generated by https://github.com/TYPO3-Documentation/t3docs-codesnippets
+..  Extracted from EXT:examples/Configuration/TsConfig/Page/Mod/noExportRecordsLinks.tsconfig
+
+..  code-block:: typoscript
+    :caption: EXT:examples/Configuration/TsConfig/Page/Mod/noExportRecordsLinks.tsconfig
+
+    mod.web_list {
+       noExportRecordsLinks = 1
+    }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock1.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock1.rst.txt
new file mode 100644
index 000000000..2909d1d6a
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock1.rst.txt
@@ -0,0 +1,8 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlock/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier.stdWrap.field = title
+   myIdentifier.stdWrap.ifEmpty.data = leveltitle:0
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock2.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock2.rst.txt
new file mode 100644
index 000000000..f11d7f745
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock2.rst.txt
@@ -0,0 +1,10 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlock2/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier {
+      stdWrap.field = title
+      stdWrap.ifEmpty.data = leveltitle:0
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock3.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock3.rst.txt
new file mode 100644
index 000000000..6c33f124e
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlock3.rst.txt
@@ -0,0 +1,14 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlock3/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier {
+      stdWrap {
+         field = title
+         ifEmpty {
+            data = leveltitle:0
+         }
+      }
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidClosingBrace.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidClosingBrace.rst.txt
new file mode 100644
index 000000000..5f5553543
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidClosingBrace.rst.txt
@@ -0,0 +1,8 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlockInvalidClosingBrace/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier {
+      value = bar }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidCondition.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidCondition.rst.txt
new file mode 100644
index 000000000..bbe676cc8
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidCondition.rst.txt
@@ -0,0 +1,12 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlockInvalidCondition/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier {
+      value = foo
+      [frontend.user.isLoggedIn]
+         value = bar
+      [end]
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidImport.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidImport.rst.txt
new file mode 100644
index 000000000..cbfb70f1a
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/CodeBlockInvalidImport.rst.txt
@@ -0,0 +1,10 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/CodeBlockInvalidCondition/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier {
+      @import 'EXT:my_extension/Configuration/TypoScript/bar.typoscript'
+      value = foo
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/Comments.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/Comments.rst.txt
new file mode 100644
index 000000000..85a1df506
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/Comments.rst.txt
@@ -0,0 +1,25 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/Comments/setup.typoscript
+
+    # This is a comment
+    // This is a comment
+    /* This is a
+       multiline comment */
+
+    foo < bar // This is a comment
+    foo < bar /* This is a valid comment, too */
+
+    foo > # Another valid comment
+
+    foo := addToList(1) # Yes, a comment
+
+    [foo = bar] # Many comment. Much wow.
+
+    foo (
+      # This is NOT a comment but part of the value assignment!
+      bar = barValue
+    ) # This is a comment
+
+    foo = bar // This is NOT a comment but part of the value assignment!
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers1.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers1.rst.txt
new file mode 100644
index 000000000..8436a8aaa
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers1.rst.txt
@@ -0,0 +1,6 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/General/setup.typoscript
+
+   myIdentifier.mySubIdentifier = myValue
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers2.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers2.rst.txt
new file mode 100644
index 000000000..8af10b920
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/Identifiers2.rst.txt
@@ -0,0 +1,6 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/Escaping/setup.typoscript
+
+   myIdentifier.my\.identifier\.with\.dots = myValue
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorAssignment.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorAssignment.rst.txt
new file mode 100644
index 000000000..2cd564d8c
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorAssignment.rst.txt
@@ -0,0 +1,31 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/Assignment/setup.typoscript
+
+   # Identifier "myIdentifier" is set to the value "foo"
+   myIdentifier = foo
+
+   # Identifier path "myIdentifier.mySubIdentifier" is set to the value "foo"
+   myIdentifier.mySubIdentifier = foo
+
+   # "myIdentifier.mySubIdentifier" it set to the value "foo",
+   # but is immediately overwritten to value "bar"
+   myIdentifier.mySubIdentifier = foo
+   myIdentifier.mySubIdentifier = bar
+
+   # Same as above, value of "myIdentifier.mySubIdentifier" is "bar"
+   myIdentifier.mySubIdentifier = foo
+   myIdentifier {
+      mySubIdentifier = bar
+   }
+
+   # Value assignments are not comment-aware, "#", "//" and "/*" after a
+   # "=" operator do not start a comment. The value of identifier
+   # "myIdentifier.mySubIdentifier" is "foo // not a comment"
+   myIdentifier.mySubIdentifier = foo // not a comment
+
+   # Value assignment using a constant:
+   # Ends up as "foo myConstantValue bar" if constant "myConstant" is set to "myConstantValue"
+   # Ends up as "foo {$myConstantValue} bar" if constant "myConstant" is not set
+   myIdentifier. mySubIdentifier = foo {$myConstantValue} bar
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy1.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy1.rst.txt
new file mode 100644
index 000000000..24fb9a718
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy1.rst.txt
@@ -0,0 +1,14 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorCopy1/setup.typoscript
+
+   myIdentifier = TEXT
+   myIdentifier.value = Hello world
+   myOtherIdentifier = TEXT
+   myOtherIdentifier.value = Hello world
+
+   # The above is identical to this:
+   myIdentifier = TEXT
+   myIdentifier.value = Hello world
+   myOtherIdentifier < myIdentifier
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy2.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy2.rst.txt
new file mode 100644
index 000000000..2185027fe
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy2.rst.txt
@@ -0,0 +1,10 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorCopy2/setup.typoscript
+
+   myIdentifier {
+      10 = TEXT
+      10.value = Hello world
+      20 < myIdentifier.10
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy3.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy3.rst.txt
new file mode 100644
index 000000000..c9370b46e
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy3.rst.txt
@@ -0,0 +1,10 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorCopy3/setup.typoscript
+
+   myIdentifier {
+      10 = TEXT
+      10.value = Hello world
+      20 < .10
+   }
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy4.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy4.rst.txt
new file mode 100644
index 000000000..fc0f211a2
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorCopy4.rst.txt
@@ -0,0 +1,19 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorCopy4/setup.typoscript
+
+   # The above is identical to this:
+   myIdentifier = TEXT
+   myIdentifier.value = Hello world
+   myOtherIdentifier < myIdentifier
+
+   # Changing myIdentifier *after* it has been copied over to myOtherIdentifier,
+   # does *not* change myOtherIdentifier. The below line only changes the
+   # value of myIdentifier, not myOtherIdentifier:
+   myIdentifier.value = Hello world 2
+
+   # Changing myOtherIdentifier *after* it has been copied from to myIdentifier,
+   # does *not* change myIdentifier. The below line only changes the
+   # value of myOtherIdentifier, not myIdentifier:
+   myOtherIdentifier.value = Hello world 3
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorMultiLine.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorMultiLine.rst.txt
new file mode 100644
index 000000000..20a8c5642
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorMultiLine.rst.txt
@@ -0,0 +1,24 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorMultiLine/setup.typoscript
+
+   myIdentifier= TEXT
+   myIdentifier.value (
+      This is a
+      multiline assignment
+   )
+
+   myIdentifier= TEXT
+   myIdentifier.value (
+      <p class="warning">
+         This is HTML code.
+      </p>
+   )
+
+   myIdentifier= TEXT
+   myIdentifier.value (
+      This looks up the value for constant {$myConstant}
+      and falls back to the string "{$myConstant}" if it can
+      not be resolved.
+   )
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorReference.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorReference.rst.txt
new file mode 100644
index 000000000..37188b59e
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorReference.rst.txt
@@ -0,0 +1,17 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/OperatorReference/setup.typoscript
+
+   lib.myIdentifier = TEXT
+   lib.myIdentifier {
+      value = Hello world
+      stdWrap.wrap = <p>|</p>
+   }
+   tt_content.text =< lib.myIdentifier
+   tt_content.textpic =< lib.myIdentifier
+
+   # This changes lib.myIdentifier.stdWrap.wrap *and* tt_content.text.stdWrap.wrap
+   lib.myIdentifier.stdWrap.wrap = <h1>|</h1>
+   # This changes only tt_content.textpic.stdWrap.wrap
+   tt_content.textpic.stdWrap.wrap = <h2>|</h2>
diff --git a/Documentation/CodeSnippets/TypoScriptSyntax/OperatorUnset.rst.txt b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorUnset.rst.txt
new file mode 100644
index 000000000..cf11d70a3
--- /dev/null
+++ b/Documentation/CodeSnippets/TypoScriptSyntax/OperatorUnset.rst.txt
@@ -0,0 +1,15 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. code-block:: typoscript
+   :caption: Extension examples, file Configuration/TypoScript/Syntax/ObjectUnset/setup.typoscript
+
+   myIdentifier.mySubIdentifier = TEXT
+   myIdentifier.mySubIdentifier = myValue
+   myIdentifier.mySubIdentifier.stdWrap = <p>|</p>
+
+   # "myIdentifier.mySubIdentifier" is completely removed, including value
+   # assignment and sub identifier "stdWrap"
+   myIdentifier.mySubIdentifier >
+
+   # Same as above: Everything after ">" operator is considered a comment
+   myIdentifier.mySubIdentifier > // Some comment
diff --git a/Documentation/Conditions/Index.rst b/Documentation/Conditions/Index.rst
index 44cf5518d..e20f2929a 100644
--- a/Documentation/Conditions/Index.rst
+++ b/Documentation/Conditions/Index.rst
@@ -1,3 +1,5 @@
+:navigation-title: Conditions
+
 ..  include:: /Includes.rst.txt
 ..  index::
     Conditions
@@ -12,10 +14,9 @@
 ..  _condition-functions-in-all-contexts:
 ..  _condition-functions-in-frontend-context:
 
-
-==========
-Conditions
-==========
+=======================================
+Frontend TypoScript conditions criteria
+=======================================
 
 Frontend TypoScript conditions offer a way to conditionally change TypoScript
 based on current context. Do not confuse conditions with the
@@ -24,7 +25,7 @@ on current data.
 
 ..  seealso::
     Have a look at the
-    :ref:`TypoScript syntax condition chapter <t3coreapi:typoscript-syntax-conditions>`
+    :ref:`TypoScript syntax condition chapter <typoscript-syntax-conditions>`
     for the basic syntax of conditions.
 
 The :ref:`Symfony expression language <t3coreapi:symfony-expression-language>`
@@ -176,15 +177,25 @@ tree.pagelayout
         :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
         # Using backend layout records
-        [tree.pagelayout == 2]
+        [tree.pagelayout === "2"]
             # ...
         [END]
 
         # Using the TSconfig provider of backend layouts
-        [tree.pagelayout == "pagets__Home"]
+        [tree.pagelayout === "pagets__Home"]
             # ...
         [END]
 
+        # Using backend layout records multiple
+        [tree.pagelayout in ['2','3','4','5']]
+            # ...
+        [END]
+
+    ..  attention::
+        The value of `pagelayout` is a string, even when using BE layout records.
+        This is especially important in conditions using `in` as shown here since
+        this operator performs a strict comparison by default. For clarity and
+        consistency strict comparisons should also be used in other cases.
 
 ..  index::
     Conditions; tree.rootLine
@@ -782,6 +793,9 @@ traverse()
         # Traverse query parameters of current request along tx_news_pi1[news]
         [request && traverse(request.getQueryParams(), 'tx_news_pi1/news') > 0]
 
+        # Traverse page properties for current page
+        [traverse(page ?? [], "pid") == 65]
+
     ..  tip::
         Checking for the :ref:`request object <t3coreapi:typo3-request>` to be
         available before using :typoscript:`traverse()` may be necessary, for
@@ -791,6 +805,9 @@ traverse()
         available). This avoids the error
         `Unable to call method "getQueryParams" of non-object "request"`.
 
+        Same is true for the `page` variable, which might not be available
+        in all contexts, for example backend modules without a page.
+        One can use the `?? []` workaround.
 
 ..  index:: Conditions; compatVersion
 ..  _condition-function-compatVersion:
@@ -940,18 +957,15 @@ ip()
 request()
 =========
 
-..  deprecated:: 12.3
-    Using this function in **page TSconfig** or **user TSconfig** conditions is
-    deprecated. Such conditions will stop working with TYPO3 v13 and will then
-    always evaluate to false. For migration hints see the
-    :ref:`changelog <ext_core:deprecation-100047-1677608959>`.
-
 ..  confval:: request()
     :name: condition-request
     :type: Mixed
 
     Allows to fetch information from current request.
 
+    ..  note:: This function cannot be used in **page TSconfig** or
+        **user TSconfig** conditions. They always evaluate to false.
+
 ..  tip::
     Checking for the :ref:`request object <t3coreapi:typo3-request>` before
     using in a condition may be necessary, for example, when using
@@ -1261,7 +1275,13 @@ siteLanguage()
         Returns the language ID as an integer.
 
     :typoscript:`siteLanguage("locale")`
-        Returns the current locale as a string, for example `en_GB` or `de_DE`.
+        Returns the current locale as :php:`\TYPO3\CMS\Core\Localization\Locale`.
+        You can call all public methods of the object, for example
+        :typoscript:`siteLanguage("locale").getName()` returns `en-GB` or `de-DE`.
+
+        **Note**: In TYPO3 v12 there was an unintentional breaking change,
+        whereby an object and not a string is returned.
+        A future TYPO3 release may address implementing a shortcut for this.
 
     :typoscript:`siteLanguage("base")`
         Returns the configured base URL as a string.
@@ -1300,8 +1320,8 @@ siteLanguage()
     ..  code-block:: typoscript
         :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        [siteLanguage("locale") == "de_CH"]
-            page.10.value = This site has the locale "de_CH"
+        [siteLanguage("locale").getName() == "de-CH"]
+            page.10.value = This site has the locale "de_CH" or "de_CH.utf8"
         [END]
 
         [siteLanguage("title") == "Italy"]
@@ -1346,7 +1366,7 @@ Check if a constant is set to a certain value
 ---------------------------------------------
 
 TypoScript constants can be used in conditions with the
-:ref:`Syntax <t3coreapi:typoscript-syntax-conditions-syntax>` for conditions:
+:ref:`Syntax <typoscript-syntax-conditions-syntax>` for conditions:
 
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
diff --git a/Documentation/ContentObjects/Content/Index.rst b/Documentation/ContentObjects/Content/Index.rst
index 274b444ac..0f4571460 100644
--- a/Documentation/ContentObjects/Content/Index.rst
+++ b/Documentation/ContentObjects/Content/Index.rst
@@ -33,6 +33,15 @@ Properties
     :display: table
     :type:
 
+..  _cobj-content-if:
+
+..  confval:: if
+    :name: content-if
+    :type: :ref:`->if <if>`
+
+    If "if" returns false, the content is not generated.
+
+
 ..  _cobj-content-select:
 
 ..  confval:: select
diff --git a/Documentation/ContentObjects/Extbaseplugin/Index.rst b/Documentation/ContentObjects/Extbaseplugin/Index.rst
index 1953d5074..6d54f3f05 100644
--- a/Documentation/ContentObjects/Extbaseplugin/Index.rst
+++ b/Documentation/ContentObjects/Extbaseplugin/Index.rst
@@ -1,13 +1,12 @@
 ..  include:: /Includes.rst.txt
 ..  index:: Content objects; EXTBASEPLUGIN
+..  _cobj-extbaseplugin-history:
 ..  _cobj-extbaseplugin:
 
 =============
 EXTBASEPLUGIN
 =============
 
-..  versionadded:: 12.3
-
 The content object :typoscript:`EXTBASEPLUGIN` allows to render
 :ref:`Extbase <t3coreapi:extbase>` plugins.
 
@@ -98,30 +97,3 @@ action by getting the currentContentObject from the request:
     :php-short:`\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer` as
     potential user input. Do not use it unescaped and do not trust to receive
     certain types.
-
-..  _cobj-extbaseplugin-history:
-
-History
-=======
-
-The :typoscript:`EXTBASEPLUGIN` allows Extbase authors to not reference the
-Extbase Bootstrap class anymore, like for previous TYPO3 versions below version
-12.
-
-Previously, TypoScript code for Extbase plugins looked like this:
-
-..  code-block:: typoscript
-
-    page.10 = USER
-    page.10 {
-        userFunc = TYPO3\\CMS\\Extbase\\Core\\Bootstrap->run
-        extensionName = MyExtension
-        pluginName = MyPlugin
-    }
-
-This way still works, but it is recommended to use the
-:typoscript:`EXTBASEPLUGIN` content object, as the direct reference to a PHP
-class (Bootstrap) might be optimized in future versions.
-
-For extension that need to remain compatible with TYPO3 v11 and v12, the
-Bootstrap way should be used.
diff --git a/Documentation/ContentObjects/Fluidtemplate/Index.rst b/Documentation/ContentObjects/Fluidtemplate/Index.rst
index 851249b42..945a2c33f 100644
--- a/Documentation/ContentObjects/Fluidtemplate/Index.rst
+++ b/Documentation/ContentObjects/Fluidtemplate/Index.rst
@@ -115,24 +115,6 @@ Properties
 
     Sets the extension name of the controller.
 
-    ..  warning::
-        Up to TYPO3 v11, this property could be used as an alternative to the `extensionName`
-        argument in the :ref:`f:translate <t3viewhelper:typo3-fluid-translate>`
-        and :ref:`f:uri.resource <t3viewhelper:typo3-fluid-uri-resource>` ViewHelpers,
-        provided that translations and public images were stored in the usual paths in your extension.
-
-        Since TYPO3 v12 this is no longer supported and it is recommended to either use absolute keys:
-
-        ..  code-block:: html
-
-            <f:translate key="LLL:EXT:my_extension/Resources/Private/Language/locallang.xlf:myKey" />
-
-        or the `extensionName` argument plus `key` argument in the ViewHelper:
-
-        ..  code-block:: html
-
-            <f:translate key="myKey" extensionName="MyExtension" />
-
 ..  _cobj-fluidtemplate-properties-extbase-controllername:
 
 ..  confval:: extbase.controllerName
@@ -292,14 +274,6 @@ Properties
     a template file. It is an alternative to ".file"; if ".template" is set, it
     takes precedence.
 
-    ..  warning::
-
-        The :typoscript:`FILE` object type has been removed in TYPO3 v10. As the :typoscript:`.template`
-        property used :typoscript:`FILE`, you should generally check your code to see if
-        this is used and switch to using :ref:`.templateName <cobj-fluidtemplate-properties-templatename>`
-        with :ref:`.templateRootPaths <cobj-fluidtemplate-properties-templaterootpaths>` or use
-        :ref:`.file <cobj-fluidtemplate-properties-file>`.
-
 ..  _cobj-fluidtemplate-properties-templatename:
 
 ..  confval:: templateName
@@ -450,11 +424,11 @@ as :fluid:`{page.title}`, the subtitle with :fluid:`{page.subtitle}`.
 In this example some Fluid templates have to be moved:
 
 :path:`EXT:my_sitepackage/Resources/Private/Templates/Pages/`
-    The page templates can stay in this folder.
+    Move files to :path:`EXT:my_sitepackage/Resources/Private/PageView/Pages/`
 :path:`EXT:my_sitepackage/Resources/Private/Partials/Pages/`
-    Move files to :path:`EXT:my_sitepackage/Resources/Private/Templates/Partials/`
+    Move files to :path:`EXT:my_sitepackage/Resources/Private/PageView/Partials/`
 :path:`EXT:my_sitepackage/Resources/Private/Layouts/Pages/`
-    Move files to :path:`EXT:my_sitepackage/Resources/Private/Templates/Layouts/`
+    Move files to :path:`EXT:my_sitepackage/Resources/Private/PageView/Layouts/`
 
 If the :path:`Private` folder previously looked like this:
 
@@ -484,7 +458,7 @@ It should look like this afterwards:
     *   :path:`EXT:my_sitepackage/Resources/Private/`
 
         *   :path:`Languages`
-        *   :path:`Templates`
+        *   :path:`PageView`
 
             *   :path:`Layouts`
             *   :path:`Pages`
diff --git a/Documentation/ContentObjects/Fluidtemplate/_includes/_AfterMigrationToPageview.typoscript b/Documentation/ContentObjects/Fluidtemplate/_includes/_AfterMigrationToPageview.typoscript
index dcc7a602a..b3b5d7497 100644
--- a/Documentation/ContentObjects/Fluidtemplate/_includes/_AfterMigrationToPageview.typoscript
+++ b/Documentation/ContentObjects/Fluidtemplate/_includes/_AfterMigrationToPageview.typoscript
@@ -3,7 +3,7 @@ page {
     10 = PAGEVIEW
     10 {
         paths {
-            100 = EXT:my_sitepackage/Resources/Private/Templates/
+            100 = EXT:my_sitepackage/Resources/Private/PageView/
         }
         variables {
             parentPageTitle = TEXT
@@ -14,4 +14,4 @@ page {
             10.as = mainMenu
         }
     }
-}
\ No newline at end of file
+}
diff --git a/Documentation/ContentObjects/Fluidtemplate/_includes/_templateNameAutomatic.typoscript b/Documentation/ContentObjects/Fluidtemplate/_includes/_templateNameAutomatic.typoscript
index dd16f960e..b3d78cb40 100644
--- a/Documentation/ContentObjects/Fluidtemplate/_includes/_templateNameAutomatic.typoscript
+++ b/Documentation/ContentObjects/Fluidtemplate/_includes/_templateNameAutomatic.typoscript
@@ -1,7 +1,6 @@
 lib.stdContent = FLUIDTEMPLATE
 lib.stdContent {
-    templateName = TEXT
-    templateName.stdWrap {
+    templateName {
         cObject = TEXT
         cObject {
             data = levelfield:-2,backend_layout_next_level,slide
diff --git a/Documentation/ContentObjects/GeneralInformation/Index.rst b/Documentation/ContentObjects/GeneralInformation/Index.rst
index f416f8c15..442ef3701 100644
--- a/Documentation/ContentObjects/GeneralInformation/Index.rst
+++ b/Documentation/ContentObjects/GeneralInformation/Index.rst
@@ -92,30 +92,29 @@ But this is not the case with :typoscript:`tt_content.bullets.10`. Here
 :typoscript:`lib.stdheader` is referenced and :typoscript:`lib.stdheader` will be used as the
 cObject at *runtime*.
 
-The reason why lib.stdheader was copied in the first case is the fact
-that it's needed to unset ".stdWrap.space" inside the cObject
-(:typoscript:`10.stdWrap.space >`). This could **not** be done in the second case
-where only a pointer is created.
+The reason why lib.stdheader is copied (and not referenced) in the first case is the fact
+that ".stdWrap.space" can be unset inside the cObject
+(:typoscript:`10.stdWrap.space >`). This **cannot** be done in the second case
+because it is only a reference pointer.
 
 
 .. _reusing-cobjects-temp-objects:
 
-Note:
------
+Reusing Temporary TypoScript Objects:
+-------------------------------------
 
-If :typoscript:`lib.stdheader` was :typoscript:`temp.stdheader` instead, the pointer would
+If :typoscript:`temp.stdheader` had been used instead of :typoscript:`lib.stdheader`, the reference pointer would
 not work! This is due to the fact that the runtime-reference would
 find nothing in `temp.` as this is unset before the template is stored
-in cache!
+in the cache!
 
 This goes for :typoscript:`temp.` and :typoscript:`styles.` (see the top-level object
 definition elsewhere).
 
 Overriding values anyway:
 
-Although you cannot override values TypoScript-style (using the
-operators and all) the properties of the object which has the
-reference will be merged with the configuration of the reference.
+Although you cannot override values in :typoscript:`styles.`, the properties of the object which gets a
+copy of the reference will be merged with the configuration of the reference.
 
 
 .. _reusing-cobjects-examples:
@@ -139,8 +138,8 @@ The result is this configuration:
 
 .. include:: /Images/ManualScreenshots/FrontendOutput/StdWrap/ContentObjectsExampleMerge1.rst.txt
 
-Notice that :typoscript:`.value` was *not* cleared, because it's simply two arrays
-which are joined:
+Notice that :typoscript:`.value` was *not* cleared, because these two arrays
+are simply merged:
 
 .. include:: /Images/ManualScreenshots/FrontendOutput/StdWrap/ContentObjectsExampleMerge2.rst.txt
 
diff --git a/Documentation/ContentObjects/Hmenu/Browse.rst b/Documentation/ContentObjects/Hmenu/Browse.rst
deleted file mode 100644
index d62920dfc..000000000
--- a/Documentation/ContentObjects/Hmenu/Browse.rst
+++ /dev/null
@@ -1,218 +0,0 @@
-..  include:: /Includes.rst.txt
-..  index:: HMENU; special = browse
-..  _hmenu-special-browse:
-
-================================
-Browse - previous and next links
-================================
-
-This menu contains pages which give your user the possibility to
-browse to the previous page, to the next page, to a page with the
-table of contents and so on. The menu is built of items given by a
-list from the property ".items".
-
-..  attention::
-   Mount pages are *not* supported!
-
-..  contents::
-   :local:
-
-..  _hmenu-special-browse-properties:
-
-Properties
-==========
-
-..  confval-menu::
-    :display: table
-    :type:
-    :Default:
-
-..  _hmenu-special-browse-value:
-
-..  confval:: special.value
-    :name: hmenu-browse-special-value
-    :type: integer /:ref:`stdWrap <stdwrap>`
-    :Default: current page ID
-
-    The default value can be overridden with a different page ID as starting
-    point for the menu in some rare use cases.
-
-
-..  _hmenu-special-browse-items:
-
-..  confval:: special.items
-    :name: hmenu-browse-special-items
-    :type: list of item names separated by `|`
-    :Default: Current page ID
-
-    Each element in the list (separated by `|`) is either a reserved item
-    name (see list) with a predefined function, or a user-defined name
-    which you can assign a link to any page. Note that the current page
-    cannot be the root-page of a site.
-
-    ..  rubric:: Reserved item names:
-
-    `next` / `prev`
-        Links to the next page / the previous page.
-        Next and previous pages are from the same "pid" as the current page id
-        (or "value") - that is the next item in a menu with the current page.
-        Also referred to as current level.
-
-        If :confval:`hmenu-browse-special-items-prevnextToSection` is set then
-        `next` / `prev` will link to the first
-        page of the next section / to the last page of the previous section,
-        too.
-
-    `nextsection` / `prevsection`
-        Links to the next section / the
-        previous section. A section is defined as the subpages of a page on
-        the same level as the parent (pid) page of the current page. Will not
-        work if the parent page of the current page is the root page of the
-        site.
-
-        ..  figure:: /Images/ManualScreenshots/FrontendOutput/Hmenu/ContentObjectsHmenuSpecialBrowse.png
-            :alt: Example for the usage of the property "items".
-
-    `nextsection_last` / `prevsection_last`
-        Where `nextsection` / `prevsection` links to the first page in a section, these
-        link to the last page. If there is only one page in the section that
-        will be both first and last. Will not work if the parent page of the
-        current page is the root page of the site.
-
-    `first` / `last`
-        First / last page on the current level. If
-        there is only one page on the current level that page will be both
-        first and last.
-
-    `up`
-        Links to the parent (pid) page of the current page (up 1
-        level). Will always be available.
-
-    `index`
-        Links to the parent of the parent page of the current
-        page(up 2 levels). May not be available, if that page is out of the
-        root line.
-
-
-..  _hmenu-special-browse-items-example:
-
-Example: Display different types of browse links
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If id = 20 is the current page then:
-
-21 = prev and first, 19 = next, 18 = last, 17 = up, 1 = index, 10 =
-nextsection, 11 = nextsection\_last
-
-prevsection and prevsection\_last are not present because id = 3 has
-no subpages!
-
-**TypoScript (only "browse"-part, needs also TMENU):**
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-    xxx = HMENU
-    xxx.special = browse
-    xxx.special {
-        items = index|up|next|prev
-        items.prevnextToSection = 1
-        index.target = _blank
-        index.fields.title = INDEX
-        index.uid = 8
-    }
-
-..  _hmenu-special-browse-prevnexttosection:
-
-special.items.prevnextToSection
---------------------------------
-
-..  confval:: special.items.prevnextToSection
-    :name: hmenu-browse-special-items-prevnextToSection
-    :type: boolean
-    :Default: false
-
-    If set, the `prev` and `next` navigation will jump to the next section
-    when it reaches the end of pages in the current section. That way
-    `prev` and `next` will also link to the first page of the next section
-    / to the last page of the previous section.
-
-
-..  _hmenu-special-browse-target:
-
-special.[itemname].target
---------------------------
-
-..  confval:: special.[itemname].target
-    :name: hmenu-browse-special-itemname-target
-    :type: string
-
-    Optional or alternative target of the item.
-
-..  _hmenu-special-browse-uid:
-
-special.[itemname].uid
------------------------
-
-..  confval:: special.[itemname].uid
-    :name: hmenu-browse-special-itemname-uid
-    :type: integer (UID of page)
-
-    Optional or alternative page UID to link to.
-
-..  _hmenu-special-browse-fields:
-
-special.[itemname].fields.[field name]
----------------------------------------
-
-..  confval:: special.[itemname].fields.[field name]
-    :name: hmenu-browse-special-itemname-fields
-    :type: string
-
-    Use the provided string as linked text instead of the pages title.
-
-
-..  _hmenu-special-browse-fields-example:
-
-Example: Use "back" as text on the `prev` link
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-This gives the link to the previous page the linked text "« back":
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-    prev.fields.title = « back
-
-
-..  _hmenu-special-browser-excludenosearchpages:
-
-special.excludeNoSearchPages
------------------------------
-
-
-..  confval:: special.excludeNoSearchPages
-    :name: hmenu-browse-special-excludeNoSearchPages
-    :type: boolean
-    :Default: false
-
-    If set, pages marked with the `no search` checkbox will be excluded from the menu.
-
-..  _hmenu-special-browser-example:
-
-Example: Pagination with rel="next" and rel="prev"
-==================================================
-
-The following snippet uses a :ref:`HMENU <cobj-hmenu>` with
-:typoscript:`special = browse` to display links like the following:
-
-..  code-block:: html
-   :caption: Example HTML output
-
-   <link rel="prev" href="http://www.example.org/page1" />
-   <link rel="next" href="http://www.example.org/page2" />
-
-The menu excludes pages with the flag :guilabel:`Include in Search` removed
-and jumps to the next section when the last of subpages is reached.
-
-..  include:: /CodeSnippets/Menu/TypoScript/RelPrevNextMenu.rst.txt
diff --git a/Documentation/ContentObjects/Hmenu/Index.rst b/Documentation/ContentObjects/Hmenu/Index.rst
index eed18f994..324bde13c 100644
--- a/Documentation/ContentObjects/Hmenu/Index.rst
+++ b/Documentation/ContentObjects/Hmenu/Index.rst
@@ -9,6 +9,12 @@
 HMENU
 =====
 
+..  warning::
+    This TypoScript object is still available to provide backward compatibility
+    for old sites. When creating a new menu or refactoring an existing one
+    always use the `menu data processor <https://docs.typo3.org/permalink/t3tsref:menuprocessor>`_
+    and a Fluid template.
+
 Objects of type HMENU generate hierarchical menus. In a
 :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>` the HMENU can be used as
 a DataProcessor called :ref:`MenuProcessor <MenuProcessor>`, which
@@ -24,9 +30,6 @@ structured in the page tree, HMENU also allows you to use the
 menus. These special menus take characteristics of special menu types
 into account.
 
-.. contents::
-   :local:
-
 ..  _cobj-hmenu-options:
 
 Properties
@@ -36,375 +39,189 @@ Properties
     :display: table
     :type:
 
-..  _hmenu-number:
-
-..  confval:: 1, 2, 3, ...
-    :name: hmenu-array
-    :type: :ref:`menu object <data-type-menuobj>`
-    :Default: (no menu)
-
-    For every menu level, that should be rendered, an according entry must
-    exist. It defines the menu object that should render the menu items on
-    the according level. 1 is the first level, 2 is the second level, 3 is
-    the third level and so on.
-
-    **The property "1" is required!**
-
-    The entry 1 for the first level always must exist. All other levels only
-    will be generated when they are configured.
-
-    **Example:**
-
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-       temp.sidemenu = HMENU
-       temp.sidemenu.1 = TMENU
-       temp.sidemenu.1 {
-         # Configuration of that TMENU here...
-       }
-       temp.sidemenu.2 = TMENU
-       temp.sidemenu.2 {
-         # Configuration of that TMENU here...
-       }
-       temp.sidemenu.3 = TMENU
-       temp.sidemenu.3 {
-         # Configuration of that TMENU here...
-       }
-
-    This creates a menu with up to three levels: Each TMENU level can hold a
-    different menu configuration.
-
-    TYPO3 offers :ref:`a variety of menu objects <menu-objects>`.
-
-
-..  _hmenu-cache-period:
-
-..  confval:: cache_period
-    :name: hmenu-cache-period
-    :type: :ref:`data-type-integer`
-
-    The number of seconds a menu may remain in cache. If this value is not
-    set, the first available value of the following will be used:
-
-    1) cache\_timeout of the current page
-
-    2) config.cache\_period defined globally
-
-    3) 86400 (= 1 day)
-
-
-..  _hmenu-cache:
-
-..  confval:: cache
-    :name: hmenu-cache
-    :type: :ref:`cache <cache>`
-
-    See :ref:`cache function description <cache>` for details.
-
-
-..  _hmenu-entrylevel:
-
-..  confval:: entryLevel
-    :name: hmenu-entryLevel
-    :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
-    :Default: 0
-
-    Defines at which level in the rootLine the menu should start.
-
-    Default is "0" which gives us a menu of the very first pages on the
-    site.
-
-    If the value is < 0, entryLevel is chosen from "behind" in the
-    rootLine. Thus "-1" is a menu with items from the outermost level,
-    "-2" is the level before the outermost...
-
-    **Note:** :typoscript:`entryLevel` does not show a menu **of a certain level of pages**
-    (use :typoscript:`special = directory` for that)
-    but it means that it will start to be visible **from that level on**.
-
-    So, for example if you build a simple "sitemap" menu like this one:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10 = HMENU
-        page.10 {
-          entryLevel = 4
-          1 = TMENU
-          1.wrap = <ul> | </ul>
-          1.NO.wrapItemAndSub = <li> | </li>
-          1.expAll = 1
-          2 < .1
-          3 < .2
-          4 < .3
-          5 < .4
-          6 < .5
-          7 < .6
-        }
-
-    it will start to be visible from the 4th level (and will contain only the subpages from that level).
-    Please note also that this affects also the menu generated with :typoscript:`MenuProcessor`. Example:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10 {
-           dataProcessing {
-            10 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
-            10 {
-               special = list
-               special.value.field = pages
-               levels = 7
-               entryLevel = 4
-               as = menu
-               expandAll = 1
-               titleField = nav_title // title
-            }
-          }
-        }
-
-..  _hmenu-special:
-
-..  confval:: special
-    :name: hmenu-special
-    :type: *"directory" / "list" / "updated" / "rootline" / "browse" / "keywords"
-         / "categories" / "language" / "userfunction"*
-
-    Lets you define special types of menus.
-
-    See the section about the :ref:`.special property <hmenu-special-property>`!
-
-
-..  _hmenu-special-value:
-
-..  confval:: special.value
-    :name: hmenu-special-value
-    :type: *list of page-uid's* / :ref:`stdWrap <stdwrap>`
-
-    List of page uid's to use for the special menu. What they are used
-    for depends on the menu type as defined by ".special"; see the
-    section about the :ref:`.special property <hmenu-special-property>`!
-
-
-..  _hmenu-minitems:
-
-..  confval:: minItems
-    :name: hmenu-minItems
-    :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
-
-    The minimum number of items in the menu. If the number of pages does
-    not reach this level, a dummy-page with the title "..." and
-    uid=[currentpage\_id] is inserted.
-
-    **Note:** Affects all sub menus as well. To set the value for each
-    menu level individually, set the properties in the menu objects (see
-    "Common properties" table).
-
-
-..  _hmenu-maxitems:
-
-..  confval:: maxItems
-    :name: hmenu-maxItems
-    :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
-
-    The maximum number of items in the menu. Additional items will be
-    ignored.
-
-    **Note:** Affects all sub menus as well. (See "minItems" for a
-    notice.)
-
-
-..  _hmenu-begin:
-
-..  confval:: begin
-    :name: hmenu-begin
-    :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>` :ref:`+calc <objects-calc>`
+    ..  _hmenu-number:
 
-    The first item in the menu.
+    ..  confval:: 1, 2, 3, ...
+        :name: hmenu-array
+        :type: :ref:`menu object <data-type-menuobj>`
+        :Default: (no menu)
 
-    **Example:**
+        For every menu level, that should be rendered, an according entry must
+        exist. It defines the menu object that should render the menu items on
+        the according level. 1 is the first level, 2 is the second level, 3 is
+        the third level and so on.
 
-    This results in a menu, where the first two items are skipped starting
-    with item number 3:
+        **The property "1" is required!**
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        The entry 1 for the first level always must exist. All other levels only
+        will be generated when they are configured.
 
-        begin = 3
+        TYPO3 offers :ref:`the menu object TMENU <menu-objects>`.
 
-    **Note:** Affects all sub menus as well. (See "minItems" for a
-    notice.)
+    ..  _hmenu-cache-period:
 
+    ..  confval:: cache_period
+        :name: hmenu-cache-period
+        :type: :ref:`data-type-integer`
 
-..  _hmenu-excludeuidlist:
+        The number of seconds a menu may remain in cache. If this value is not
+        set, the first available value of the following will be used:
 
-..  confval:: excludeUidList
-    :name: hmenu-excludeUidList
-    :type: list of :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
+        1) cache\_timeout of the current page
 
-    This is a list of page uids to exclude when the select statement is
-    done. Comma-separated. You may add "current" to the list to exclude
-    the current page.
+        2) config.cache\_period defined globally
 
-    **Example:**
+        3) 86400 (= 1 day)
 
-    The pages with these uid-numbers will **not** be within the menu!
-    Additionally the current page is always excluded too.
+    ..  _hmenu-cache:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  confval:: cache
+        :name: hmenu-cache
+        :type: :ref:`cache <cache>`
 
-        excludeUidList = 34,2,current
+        See :ref:`cache function description <cache>` for details.
 
+    ..  _hmenu-entrylevel:
 
-..  _hmenu-excludedoktypes:
+    ..  confval:: entryLevel
+        :name: hmenu-entryLevel
+        :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
+        :Default: 0
 
-..  confval:: excludeDoktypes
-    :name: hmenu-excludeDoktypes
-    :type: list of :ref:`data-type-integer`
-    :Default: 6,254
+        Defines at which level in the rootLine the menu should start.
 
-    Enter the list of page document types (doktype) to exclude from menus.
-    By default pages that are "backend user access only" (6) or "folder"
-    (254) are excluded.
+    ..  _hmenu-special:
 
-.. _hmenu-includenotinmenu:
+    ..  confval:: special
+        :name: hmenu-special
+        :type: *"directory" / "list" / "updated" / "rootline" / "browse" / "keywords"
+             / "categories" / "language" / "userfunction"*
 
-..  confval:: includeNotInMenu
-    :name: hmenu-includeNotInMenu
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap <stdwrap>`
+        Lets you define special types of menus.
 
-    If set, pages with the checkbox "Page enabled in menus" disabled will still be included
-    in menus.
+        See the section about the :ref:`.special property <hmenu-special-property>`!
 
-.. _hmenu-alwaysactivepidlist:
+    ..  _hmenu-special-value:
 
-..  confval:: alwaysActivePIDlist
-    :name: hmenu-alwaysActivePIDlist
-    :type: list of :ref:`data-type-integer` /:ref:`stdWrap <stdwrap>`
+    ..  confval:: special.value
+        :name: hmenu-special-value
+        :type: *list of page-uid's* / :ref:`stdWrap <stdwrap>`
 
-    This is a list of page UID numbers that will always be regarded as
-    active menu items and thereby automatically opened regardless of the
-    rootline.
+        List of page uid's to use for the special menu. What they are used
+        for depends on the menu type as defined by ".special"; see the
+        section about the :ref:`.special property <hmenu-special-property>`!
 
+    ..  _hmenu-minitems:
 
-..  _hmenu-protectlvar:
+    ..  confval:: minItems
+        :name: hmenu-minItems
+        :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
 
-..  confval:: protectLvar
-    :name: hmenu-protectlvar
-    :type: :ref:`data-type-boolean` / keyword
+        The minimum number of items in the menu. If the number of pages does
+        not reach this level, a dummy-page with the title "..." and
+        `uid=[currentpage\_id]` is inserted.
 
-    If set, then for each page in the menu it will be checked if an
-    Alternative Page Language record for the language defined in
-    "config.sys\_language\_uid" exists for the
-    page. If that is not the case and the pages "Localization settings"
-    have the "Hide page if no translation for current language exists"
-    flag set, then the menu item will link to a non accessible page that
-    will yield an error page to the user. Setting this option will prevent
-    that situation by adding "&L=0" for such pages, meaning that
-    they will switch to the default language rather than keeping the
-    current language.
+        **Note:** Affects all sub menus as well. To set the value for each
+        menu level individually, set the properties in the menu objects (see
+        "Common properties" table).
 
-    The check is only carried out if a translation is requested
-    ("config.sys\_language\_uid" is not zero).
+    ..  _hmenu-maxitems:
 
-    **Keyword: "all"**
+    ..  confval:: maxItems
+        :name: hmenu-maxItems
+        :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
 
-    When set to "all" the same check is carried out but it will not look
-    if "Hide page if no translation for current language exists" is set -
-    it always reverts to default language if no translation is found.
+        The maximum number of items in the menu. Additional items will be
+        ignored.
 
-    For these options to make sense, they should only be used when
-    "config.sys\_language\_mode" is not set to "content\_fallback".
+        **Note:** Affects all sub menus as well. (See "minItems" for a
+        notice.)
 
+    ..  _hmenu-begin:
 
-..  _hmenu-addquerystring:
+    ..  confval:: begin
+        :name: hmenu-begin
+        :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>` :ref:`+calc <objects-calc>`
 
-..  confval:: addQueryString
-    :name: hmenu-addquerystring
-    :type: :ref:`->addQueryString <typolink-addQueryString>`
+        The first item in the menu.
 
-    **Note:** This works only for *special=language*.
+        **Note:** Affects all sub menus as well. (See "minItems" for a
+        notice.)
 
+    ..  _hmenu-excludeuidlist:
 
-..  _hmenu-if:
+    ..  confval:: excludeUidList
+        :name: hmenu-excludeUidList
+        :type: list of :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
 
-..  confval:: if
-    :name: hmenu-if
-    :type: :ref:`->if <if>`
+        See :confval:`MenuProcessor-excludeUidList`.
 
-    If "if" returns false, the menu is not generated.
+    ..  _hmenu-excludedoktypes:
 
+    ..  confval:: excludeDoktypes
+        :name: hmenu-excludeDoktypes
+        :type: list of :ref:`data-type-integer`
+        :Default: 6,254
 
-..  _hmenu-wrap:
+        See :confval:`MenuProcessor-excludeDoktypes`.
 
-..  confval:: wrap
-    :name: hmenu-wrap
-    :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap <stdwrap>`
+    .. _hmenu-includenotinmenu:
 
-    Wrap for the HMENU.
+    ..  confval:: includeNotInMenu
+        :name: hmenu-includeNotInMenu
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap <stdwrap>`
 
+        See :confval:`MenuProcessor-includeNotInMenu`
 
-..  _hmenu-stdwrap:
+    .. _hmenu-alwaysactivepidlist:
 
-..  confval:: stdWrap
-    :name: hmenu-stdWrap
-    :type: :ref:`->stdWrap <stdwrap>`
+    ..  confval:: alwaysActivePIDlist
+        :name: hmenu-alwaysActivePIDlist
+        :type: list of :ref:`data-type-integer` /:ref:`stdWrap <stdwrap>`
 
-    (Executed after ".wrap".)
+        See :confval:`MenuProcessor-alwaysActivePIDlist`
 
+    ..  _hmenu-protectlvar:
 
-..  _hmenu-examples:
+    ..  confval:: protectLvar
+        :name: hmenu-protectlvar
+        :type: :ref:`data-type-boolean` / keyword
 
-Example
-=======
+        See :confval:`MenuProcessor-protectlvar`.
 
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  _hmenu-if:
 
-    temp.sidemenu = HMENU
-    temp.sidemenu.entryLevel = 1
-    temp.sidemenu.1 = TMENU
-    temp.sidemenu.1 {
-      target = page
-      NO.afterImg = media/bullets/dots2.gif |*||*| _
-      NO.afterImgTagParams = style="margin: 0px 20px;"
-      NO.linkWrap = {$fontTag}
-      NO.ATagBeforeWrap = 1
+    ..  confval:: if
+        :name: hmenu-if
+        :type: :ref:`->if <if>`
 
-      ACT < .NO
-      ACT = 1
-      ACT.linkWrap = <b>{$fontTag}</b>
-    }
+        If "if" returns false, the menu is not generated.
+    ..  _hmenu-wrap:
 
+    ..  confval:: wrap
+        :name: hmenu-wrap
+        :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap <stdwrap>`
 
-..  index:: HMENU; special
-..  _hmenu-special-property:
+        Wrap for the HMENU.
 
-The .special property
-=====================
+    ..  _hmenu-stdwrap:
 
-This property makes it possible to create menus that are not strictly
-reflecting the current page-structure, but rather creating a
-:ref:`breadcrumb menu <hmenu-special-rootline>`, a
-:ref:`language menu <hmenu-special-language>` or menus with
-links to pages like :ref:`next/previous <hmenu-special-browse>`,
-:ref:`last modified <hmenu-special-updated-examples>`,
-:ref:`all subpages of a page <hmenu-special-directory>` and so on.
+    ..  confval:: stdWrap
+        :name: hmenu-stdWrap
+        :type: :ref:`->stdWrap <stdwrap>`
 
-..  note::
-    :typoscript:`.entryLevel` generally is not supported together with the
-    :typoscript:`.special` property! The only exception is :typoscript:`special = keywords`.
+        (Executed after ".wrap".)
 
-Also be aware that this property selects pages for the first level in
-the menu. Submenus by menuObjects 2+ will be created as usual.
+    ..  _hmenu-examples:
+    ..  _hmenu-special-property:
 
-See the following menus types based on the :typoscript:`special` property:
+    For examples on how to use the HMENU please refer to old version of this
+    document, for example :ref:`HMENU <t3tsref/11.5:cobj-hmenu>`
 
-..  toctree::
-    :titlesonly:
-    :glob:
+    ..  toctree::
+        :titlesonly:
+        :glob:
+        :hidden:
 
-    Tmenu/Index
-    *
+        Tmenu/Index
+        *
diff --git a/Documentation/ContentObjects/Hmenu/Language.rst b/Documentation/ContentObjects/Hmenu/Language.rst
deleted file mode 100644
index a4b33dd26..000000000
--- a/Documentation/ContentObjects/Hmenu/Language.rst
+++ /dev/null
@@ -1,75 +0,0 @@
-..  include:: /Includes.rst.txt
-..  index:: HMENU; special = categories
-..  _hmenu-special-language:
-
-=============
-Language menu
-=============
-
-..  seealso::
-    The :ref:`LanguageMenuProcessor <LanguageMenuProcessor>` can be used to
-    create a language menu styled by Fluid.
-
-Creates a language selector menu.
-
-The :typoscript:`special = language` type will create menu items based on
-the current page record but with the language record for each language
-overlaid if available.
-
-..  contents::
-    :local:
-
-..  _hmenu-special-language-properties:
-
-Properties
-==========
-
-..  confval-menu::
-    :display: table
-    :type:
-
-..  _hmenu-special-language-value:
-
-..  confval:: special.value
-    :name: hmenu-language-special-value
-    :type: comma separated list of language UIDs /:ref:`stdWrap <stdwrap>` or `auto`
-
-    The number of elements in this list determines the number of menu
-    items. Setting to `auto` will include all available languages from
-    the current site.
-
-..  _hmenu-special-language-normalwhennolanguage:
-
-..  confval:: special.normalWhenNoLanguage
-    :name: hmenu-language-special-normalWhenNoLanguage
-    :type: boolean
-
-    If set, the button for a language will be rendered as a non-
-    disabled button even if no translation is found for the language.
-
-
-..  _hmenu-special-language-examples:
-
-Example: Create a language menu with pure TypoScript
-====================================================
-
-..  include:: /CodeSnippets/Menu/TypoScript/LanguageMenuLib.rst.txt
-
-..  seealso::
-   For a language menu styled by Fluid see
-   :ref:`LanguageMenuProcessor <LanguageMenuProcessor>`.
-
-Note on item states
-====================
-
-When the language of the menu element matches the current language of the page
-displayed, the state is set to `ACT`, otherwise `NO`. However, if a page
-is not available due to the pages "Localization settings" (which can
-disable translations) or if no Alternative Page Language record was
-found (can be disabled with `.normalWhenNoLanguage`, see below) the
-state is set to `USERDEF1` for non-active items and `USERDEF2` for
-active items. So in total there are four states to create designs for.
-It is recommended to disable the link on menu items rendered with
-`USERDEF1` and `USERDEF2` in this case since they are disabled exactly
-because a page in that language does not exist and might even issue an
-error if tried accessed (depending on site configuration).
diff --git a/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst b/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst
index 8c7b8cf0f..42ba8ceb1 100644
--- a/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst
+++ b/Documentation/ContentObjects/Hmenu/Tmenu/Index.rst
@@ -8,7 +8,14 @@
 TMENU
 =====
 
-:typoscript:`TMENU` is a menu object type.
+..  warning::
+    This TypoScript object is still available to provide backward compatibility
+    for old sites. When creating a new menu or refactoring an existing one
+    always use the `menu data processor <https://docs.typo3.org/permalink/t3tsref:menuprocessor>`_
+    and a Fluid template.
+
+For examples on how to use the TMENU please refer to old version of this
+document, for example :ref:`TMENU <t3tsref/11.5:tmenu>`-.
 
 ..  toctree::
     :glob:
@@ -20,16 +27,16 @@ TMENU
 
 ..  index:: TMENU; Item states
 
-.. _tmenu-common-property-no:
-.. _tmenu-common-property-ifsub:
-.. _tmenu-common-property-act:
-.. _tmenu-common-property-actifsub:
-.. _tmenu-common-property-cur:
-.. _tmenu-common-property-curifsub:
-.. _tmenu-common-property-usr:
-.. _tmenu-common-property-spc:
-.. _tmenu-common-property-userdef1:
-.. _tmenu-common-property-userdef2:
+..  _tmenu-common-property-no:
+..  _tmenu-common-property-ifsub:
+..  _tmenu-common-property-act:
+..  _tmenu-common-property-actifsub:
+..  _tmenu-common-property-cur:
+..  _tmenu-common-property-curifsub:
+..  _tmenu-common-property-usr:
+..  _tmenu-common-property-spc:
+..  _tmenu-common-property-userdef1:
+..  _tmenu-common-property-userdef2:
 ..  _tmenu-common-properties:
 
 TMENU item states
@@ -37,6 +44,12 @@ TMENU item states
 
 These properties are all the item states used by :typoscript:`TMENU`.
 
+..  warning::
+
+    Be aware to properly escape menu item content in order to prevent
+    Cross-site scripting vulnerabilities. It is therefore highly recommended
+    to use :php:`stdWrap.htmlSpecialChars = 1` in all TMENU item states.
+
 The following Item states are listed from the least to the highest priority:
 
 ..  confval-menu::
@@ -55,23 +68,6 @@ The following Item states are listed from the least to the highest priority:
         The default "Normal" state rendering of Item. This is required for all
         menus.
 
-        If you specify properties for the "NO" property you do not have to set
-        it "1". Otherwise with no properties setting "NO=1" will render the
-        menu anyways (for TMENU this may make sense).
-
-        The simplest menu TYPO3 can generate is then:
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            page.20 = HMENU
-            page.20.1 = TMENU
-            page.20.1.NO = 1
-
-        That will be pure `<a>` tags wrapped around page titles.
-
-
-
     ..  confval:: IFSUB
         :name: tmenu-common-property-ifsub
         :type: :ref:`data-type-boolean` / :ref:`tmenuitem`
@@ -79,8 +75,6 @@ The following Item states are listed from the least to the highest priority:
 
         Enable/Configuration for menu items which has subpages.
 
-
-
     ..  confval:: ACT
         :name: tmenu-common-property-act
         :type: :ref:`data-type-boolean` / :ref:`tmenuitem`
@@ -101,7 +95,6 @@ The following Item states are listed from the least to the highest priority:
         :type: :ref:`data-type-boolean` / :ref:`tmenuitem`
         :Default: 0
 
-
         Enable/Configuration for a menu item if the item is the current page.
 
     ..  confval:: CURIFSUB
@@ -171,14 +164,6 @@ Properties
         has clicked a menu item and the menu folds out the next level. This
         can enable that to happen on all items as default.
 
-    ..  confval:: collapse (removed)
-        :name: menu-common-properties-collapse
-
-        ..  versionchanged:: 12.0
-            The property was removed with TYPO3 v12.0. Use a custom user function or
-            the PSR-14 event :ref:`t3coreapi:FilterMenuItemsEvent` to modify the menu
-            items.
-
     ..  confval:: sectionIndex
         :name: menu-common-properties-sectionIndex
         :type: :ref:`data-type-boolean`
@@ -238,64 +223,13 @@ Properties
 
                 tt_content.menu.20.3.1.sectionIndex.useColPos = -1
 
-
-        .. rubric:: The data record in sectionIndex menus
-
-        When the menu-records are selected it works like this: The parent page
-        record is used as the "base" for the menu-record. That means that any
-        "no\_cache" or "target"-properties of the parent page are used for the
-        whole menu.
-
-        But of course some fields from the tt\_content records are
-        transferred. This is how it is mapped:
-
-        ..  code-block:: none
-            :caption: Example of data mapping
-
-            $temp[$row[uid]]=$basePageRow;
-            $temp[$row[uid]]['title']=$row['header'];
-            $temp[$row[uid]]['subtitle']=$row['subheader'];
-            $temp[$row[uid]]['starttime']=$row['starttime'];
-            $temp[$row[uid]]['endtime']=$row['endtime'];
-            $temp[$row[uid]]['fe_group']=$row['fe_group'];
-            $temp[$row[uid]]['media']=$row['media'];
-            $temp[$row[uid]]['header_layout']=$row['header_layout'];
-            $temp[$row[uid]]['bodytext']=$row['bodytext'];
-            $temp[$row[uid]]['image']=$row['image'];
-            $temp[$row[uid]]['sectionIndex_uid']=$row['uid'];
-
-        Basically this shows that
-
-        -   the field "header" and "subheader" from tt\_content are mapped to
-            "title" and "subtitle" in the pages-record. Thus you shouldn't need to
-            change your standard menu objects to fit this thing.
-
-        -   the fields "starttime", "endtime", "fe\_group", "media" from
-            tt\_content are mapped to the same fields in a pages-record.
-
-        -   the fields "header\_layout", "bodytext" and "image" are mapped to
-            non-existing fields in the page-record
-
-        -   a new field, "sectionIndex\_uid" is introduced in the page record
-            which is detected by the `\TYPO3\CMS\Frontend\Typolink\PageLinkBuilder`. If this field
-            is present in a page record, the `PageLinkBuilder` will prepend a
-            hash-mark and the number of the field.
-
-        ..  note::
-            You cannot create submenus to sectionIndex menus. These elements are not
-            pages and thereby have no children.
-
-
-
     ..  confval:: target
         :name: menu-common-properties-target
-        :type: :ref:`data-type-target`
+        :type: string
         :Default: self
 
         Target of the menu links
 
-
-
     ..  confval:: forceTypeValue
         :name: menu-common-properties-forceTypeValue
         :type: :ref:`data-type-integer`
@@ -311,29 +245,12 @@ Properties
 
         Wraps the whole block of sub items.
 
-        ..  rubric:: Example
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            2 = TMENU
-            2 {
-               stdWrap.dataWrap = <ul class="{register : parentProperty}"> | </ul>
-               NO {
-                  // ...
-               }
-            }
-
-
-
     ..  confval:: wrap
         :name: menu-common-properties-wrap
         :type: :ref:`wrap <data-type-wrap>`
 
         Wraps the whole block of sub items, but only if there were items in the menu!
 
-
-
     ..  confval:: IProcFunc
         :name: menu-common-properties-IProcFunc
         :type: function name
@@ -343,7 +260,6 @@ Properties
         compiled by implode()'ing the array $I[parts] in the passed array.
         Thus you may modify this if you need to.
 
-
     ..  confval:: alternativeSortingField
         :name: menu-common-properties-alternativeSortingField
         :type: :ref:`data-type-string`
@@ -353,19 +269,11 @@ Properties
         is used in the SQL- "ORDER BY" statement instead. You can also provide
         the sorting order.
 
-        **Examples (for "pages" table):**
-
-        alternativeSortingField = title desc
-
-        (This will render the menu in reversed alphabetical order.)
-
         **Limitations:**
 
         This property works with normal menus, sectionsIndex menus and
         special-menus of type "directory".
 
-
-
     ..  confval:: minItems
         :name: menu-common-properties-minItems
         :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
@@ -380,34 +288,16 @@ Properties
         :name: menu-common-properties-maxItems
         :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
 
-
         The maximum items in the menu. More items will be ignored.
 
         Takes precedence over HMENU property :ref:`hmenu-maxitems`.
 
-
-
     ..  confval:: begin
         :name: menu-common-properties-begin
         :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>` :ref:`+calc <objects-calc>`
 
-
         The first item in the menu.
 
-        **Example:**
-
-        This results in a menu, where the first two items are skipped starting
-        with item number 3:
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            begin = 3
-
-        Takes precedence over :HMENU property :ref:`hmenu-begin`.
-
-
-
     ..  confval:: debugItemConf
         :name: menu-common-properties-debugItemConf
         :type: :ref:`data-type-boolean`
@@ -415,8 +305,6 @@ Properties
         Outputs (by the :php:`debug()` function) the configuration arrays for each
         menu item. Useful to debug :ref:`optionsplit` things and such...
 
-
-
     ..  confval:: overrideId
         :name: menu-common-properties-overrideId
         :type: :ref:`data-type-integer` (page id)
@@ -434,17 +322,12 @@ Properties
 
         Additional parameter for the menu links.
 
-        **Example:**
-
-        "&some\_var=some%20value"
-
         Must be rawurlencoded.
 
     ..  confval:: showAccessRestrictedPages
         :name: menu-common-properties-showaccessrestrictedpages
         :type: :ref:`data-type-integer` (page ID) / keyword "NONE"
 
-
         If set, pages in the menu will include pages with frontend user group
         access enabled. However the page is of course not accessible and
         therefore the URL in the menu will be linked to the page with the ID
@@ -466,24 +349,8 @@ Properties
         holding the page ID of the page coming from (could be used to look up
         which fe\_groups was required for access.
 
-        ..  versionadded:: 12.3
-
         **.ATagParams**: Add custom attributes to the anchor tag.
 
-        ..  rubric:: Example
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            showAccessRestrictedPages = 22
-            showAccessRestrictedPages.addParams = &return_url=###RETURN_URL###&pageId=###PAGE_ID###
-            showAccessRestrictedPages.ATagParams = class="restricted"
-
-        The example will link access restricted menu items to page ID 22 with
-        the return URL in the GET variable `return_url` and the page ID in the GET
-        variable "pageId". Additionally, a CSS class "restricted" is added to the
-        anchor tag.
-
     ..  confval:: additionalWhere
         :name: menu-common-properties-additionalWhere
         :type: :ref:`data-type-string` / :ref:`stdWrap <stdwrap>`
@@ -491,20 +358,10 @@ Properties
         Adds an additional part to the WHERE clause for this menu.
         Make sure to start the part with "AND "!
 
-        ..  rubric:: Example
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            lib.authormenu = HMENU
-            lib.authormenu.1 = TMENU
-            lib.authormenu.1.additionalWhere = AND author!=""
-
     ..  confval:: itemArrayProcFunc
         :name: menu-common-properties-itemArrayProcFunc
         :type: function name
 
-
         The first variable passed to this function is the "menuArr" array with
         the menu items as they are collected based on the type of menu.
 
@@ -527,45 +384,4 @@ Properties
         :name: menu-common-properties-submenuObjSuffixes
         :type: :ref:`data-type-string` / :ref:`optionsplit`
 
-        Defines a suffix for alternative sub-level menu objects. Useful to
-        create special submenus depending on their parent menu element. See
-        example below.
-
-        ..  rubric:: Example
-
-        This example will generate a menu where the menu objects for the
-        second level will differ depending on the number of the first level
-        item for which the submenu is rendered. The second level objects used
-        are "2" (the default), "2a" and "2b" (the alternatives). Which of them
-        is used is defined by "1.submenuObjSuffixes" which has the
-        configuration "a \|\*\| \|\*\| b". This configuration means that the
-        first menu element will use configuration "2a" and the last will use
-        "2b" while anything in between will use "2" (no suffix applied) :
-
-        ..  code-block:: typoscript
-            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-            page.200 = HMENU
-            page.200 {
-                1 = TMENU
-                1.wrap = <div style="width:200px; border: 1px solid;">|</div>
-                1.expAll = 1
-                1.submenuObjSuffixes = a |*|  |*| b
-                1.NO.allWrap = <b>|</b><br/>
-
-                2 = TMENU
-                2.NO.allWrap = <div style="background:red;">|</div>
-
-                2a = TMENU
-                2a.NO.allWrap = <div style="background:yellow;">|</div>
-
-                2b = TMENU
-                2b.NO.allWrap = <div style="background:green;">|</div>
-            }
-
-        The result can be seen in the image below:
-
-        ..  figure:: /Images/ManualScreenshots/FrontendOutput/Hmenu/MenuObjectsCommonPropertiesSubmenuObjSuffixes.png
-            :alt: Output of the above example.
-
-        Applies to TMENU on >= 2 :sup:`nd` level in a menu.
+        Defines a suffix for alternative sub-level menu objects.
diff --git a/Documentation/ContentObjects/Hmenu/Tmenu/Tmenuitem.rst b/Documentation/ContentObjects/Hmenu/Tmenu/Tmenuitem.rst
index cf4398b7b..753e5070a 100644
--- a/Documentation/ContentObjects/Hmenu/Tmenu/Tmenuitem.rst
+++ b/Documentation/ContentObjects/Hmenu/Tmenu/Tmenuitem.rst
@@ -6,10 +6,21 @@
 TMENUITEM
 =========
 
+..  warning::
+    This TypoScript object is still available to provide backward compatibility
+    for old sites. When creating a new menu or refactoring an existing one
+    always use the `menu data processor <https://docs.typo3.org/permalink/t3tsref:menuprocessor>`_
+    and a Fluid template.
+
+For examples on how to use the TMENUITEM please refer to old version of this
+document, for example :ref:`TMENUITEM <t3tsref/11.5:tmenuitem>`-.
+
 The current record is the page record of the menu item. If you would
 like to get data from the current menu item's page record, use
 :typoscript:`stdWrap.data = field : [field name]`.
 
+..  _tmenuitem-properties:
+
 Properties
 ==========
 
@@ -118,13 +129,6 @@ Properties
 
     Additional parameters
 
-    **Example:** :
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        ATagParams = class="board"
-
 
 ..  _tmenuitem-ATagTitle:
 
@@ -135,16 +139,6 @@ Properties
     Allows you to specify the "title" attribute of the :html:`<a>` tag around
     the menu item.
 
-    **Example:** :
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        ATagTitle.field = abstract // description
-
-    This would use the abstract or description field for the
-    :html:`<a title="">` attribute.
-
 
 ..  _tmenuitem-additionalParams:
 
@@ -193,7 +187,7 @@ Properties
 
 ..  confval:: altTarget
     :name: tmenuitem-altTarget
-    :type: :ref:`data-type-target`
+    :type: string
 
     Alternative target overriding the target property of the
     ref:`TMENU <tmenu>`, if set.
diff --git a/Documentation/ContentObjects/Hmenu/Userfunction.rst b/Documentation/ContentObjects/Hmenu/Userfunction.rst
deleted file mode 100644
index 99f0fe42d..000000000
--- a/Documentation/ContentObjects/Hmenu/Userfunction.rst
+++ /dev/null
@@ -1,51 +0,0 @@
-..  include:: /Includes.rst.txt
-..  index:: HMENU; special = userfunction
-..  _hmenu-special-userfunction:
-
-=================
-Userfunction menu
-=================
-
-..  attention::
-    It is still possible to create a menu with :typoscript:`special = userfunction`
-    for backward compatibility reasons.
-
-    However we would advise you to write a :ref:`customized MenuProcessor <CustomDataProcessors>`
-    and style the output with Fluid instead.
-
-Calls a user function/method in class which should return an array with
-page records for the menu.
-
-..  contents::
-    :local:
-
-..  _hmenu-special-userfunction-properties:
-
-Properties
-==========
-
-..  confval-menu::
-    :display: table
-    :type:
-
-..  _hmenu-special-userfunction-userfunc:
-
-..  confval:: special.userFunc
-    :name: hmenu-userfunction-special-userfunc
-    :type: string
-
-    Name of the user function
-
-..  _hmenu-special-userfunction-examples:
-
-Example: Set a userFunc
-=======================
-
-..  code-block:: typoscript
-    :caption: This is still possible for backward compability reasons but not recommended:
-
-    lib.custommenu = HMENU
-    lib.custommenu {
-        special = userfunction
-        special.userFunc = MyVendor\MyExtension\Userfuncs\CustomMenu->makeMenuArray
-    }
diff --git a/Documentation/ContentObjects/Image/Index.rst b/Documentation/ContentObjects/Image/Index.rst
index 5cd6817fa..44705911e 100644
--- a/Documentation/ContentObjects/Image/Index.rst
+++ b/Documentation/ContentObjects/Image/Index.rst
@@ -11,22 +11,6 @@ IMAGE
 Objects of type IMAGE return an image tag with the image file defined in the property
 "file" and is processed using the properties that are set on the object.
 
-The array :php:`$GLOBALS['TSFE']->lastImageInfo` is set with the info-array
-of the returning image (if any) and contains width, height and other properties:
-
-=============================  =============================================
-Name of the getText property   Content
-=============================  =============================================
-0                              width
-1                              height
-2                              file extension
-3                              resource
-origFile                       relative URL pointing to the original file
-_mtime                         modification time of the original file
-originalFile                   The FAL object referencing the original file
-processedFile                  The FAL object referencing the processed file
-=============================  =============================================
-
 **Note:** Gifbuilder also has an :ref:`IMAGE object <gifbuilder-image>` -
 it is not the same as the cObject described here; both are completely
 different objects.
diff --git a/Documentation/ContentObjects/Pageview/Index.rst b/Documentation/ContentObjects/Pageview/Index.rst
index 147258856..3498f6107 100644
--- a/Documentation/ContentObjects/Pageview/Index.rst
+++ b/Documentation/ContentObjects/Pageview/Index.rst
@@ -7,21 +7,26 @@ PAGEVIEW
 ========
 
 ..  versionadded:: 13.1
+    The content object PAGEVIEW can be used instead of
+    `FLUIDTEMPLATE <https://docs.typo3.org/permalink/t3tsref:cobj-template>`_
+    to configure the HTML body of a page using Fluid templates.
 
-    This API is considered experimental until TYPO3 v13 LTS. It will be further
-    adapted to be used for further rendering of
-    custom Content Elements and Content Blocks.
+This content object has very specific conventions and
+defaults, that requires (and allows) less configuration as compared to using
+`FLUIDTEMPLATE <https://docs.typo3.org/permalink/t3tsref:cobj-template>`_.
 
-The content object :typoscript:`EXTBASEPLUGIN` allows to render
-:ref:`Extbase <t3coreapi:extbase>` plugins.
-
-The new :typoscript:`PAGEVIEW` content object has very specific conventions and
-defaults, that requires (and allows) less configuration. The benefit is that
-following these conventions means less boilerplate code to maintain.
+The benefit is that following these conventions means less boilerplate code
+to maintain.
 
 If you follow these conventions, a few directories and files must follow the
 structure outlined below.
 
+..  tip::
+    Chapters `The TYPO3 Fluid version <https://docs.typo3.org/permalink/t3sitepackage:minimal-extension-fluid>`_
+    and `Display the content elements on your page <https://docs.typo3.org/permalink/t3sitepackage:content-mapping>`_
+    of the Site Package Tutorial give practical examples on how to use
+    the `PAGEVIEW` object.
+
 ..  contents:: Table of contents
     :local:
     :depth: 2
@@ -35,6 +40,42 @@ Example: Display a page with Fluid templates
     :language: typoscript
     :caption: EXT:my_sitepackage/Configuration/TypoScript/setup.typoscript
 
+..  _cobj-pageview-template-naming:
+
+Template naming and locations
+=============================
+
+To ensure proper rendering, the following requirements and
+fallback mechanisms apply:
+
+..  _cobj-pageview-template-naming-path:
+
+Target path structure
+---------------------
+
+*   The target directory **must contain a folder named :directory:`Pages/`**.
+*   This folder must contain Fluid templates in :file`*.html` format.
+
+..  _cobj-pageview-template-naming-conventions:
+
+Template naming convention
+--------------------------
+
+*   The Fluid template file **must** match the name of the selected backend layout
+    of your current page.
+*   The first letter of the Fluid template file must be **uppercase**.
+
+..  _cobj-pageview-template-naming-fallback:
+
+Fallback behavior when no backend layout is defined
+----------------------------------------------------
+
+*   If the page record does not specify a backend layout, TYPO3 tries to detect
+    next-level backend layouts by traversing up the page rootline.
+*   If still no backend layout could be found, TYPO3 falls back to `Default.html`.
+*   If you explicitly set the backend layout to `none`, a Fluid template
+    with name :file:`None.html` will be used.
+
 .. _cobj-pageview-data:
 
 Default variables in Fluid templates
@@ -74,7 +115,8 @@ Additional variables can be defined with property
 
         The variable :fluid:`{settings}` contains all TypoScript
         :ref:`constants <typoscript-syntax-constants>` that are set on the current
-        page.
+        page. Settings from the site can be accessed via the :confval:`pageview-data-site` with
+        :fluid:`{site.settings}`
 
     ..  confval:: site
         :name: pageview-data-site
@@ -96,7 +138,7 @@ Example: Display the site title in the current language
 
 ..  literalinclude:: _includes/_DisplaySiteTitle.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
 
 .. _cobj-pageview-data-page-example:
 
@@ -105,7 +147,7 @@ Example: Display the title and abstract of the current page
 
 ..  literalinclude:: _includes/_DisplayPageInfo.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
 
 .. _cobj-pageview-data-settings-example:
 
@@ -120,7 +162,7 @@ Let us assume, the current page loads the following TypoScript constants:
 
 ..  literalinclude:: _includes/_PageWithConstant.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
 
 .. _cobj-pageview-data-site-example:
 
@@ -129,7 +171,7 @@ Example: Link to the root page of the current site
 
 ..  literalinclude:: _includes/_LinkToRootPage.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
 
 ..  _cobj-pageview-properties:
 
@@ -168,8 +210,8 @@ Properties
         :Example 2: :ref:`cobj-pageview-paths-example-extended`
 
         Sets an array of paths for the Fluid templates, usually
-        :file:`EXT:my_extension/Resources/Private/Templates/` or a folder below that
-        path like :file:`EXT:my_extension/Resources/Private/Templates/MyPages`.
+        :file:`EXT:my_extension/Resources/Private/PageView/` or a
+        path like :file:`EXT:my_extension/Resources/Private/PageView/MyPage`.
 
         The templates are expected in a subfolder :path:`Pages`.
 
@@ -191,12 +233,12 @@ Properties
 ..  _cobj-pageview-examples:
 
 Examples
---------
+========
 
 ..  _cobj-pageview-dataProcessing-example:
 
 Example: Display a main menu and a breadcrumb on the page
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+---------------------------------------------------------
 
 ..  literalinclude:: _includes/_pageWithBreadcrumb.typoscript
     :language: typoscript
@@ -206,25 +248,25 @@ The page template could look like this:
 
 ..  literalinclude:: _includes/_PageWithBreadcrumb.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
 
 
 With the following partials:
 
 ..  literalinclude:: _includes/_PartialBreadCrumb.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Partials/Navigation/Breadcrumb.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Partials/Navigation/Breadcrumb.html
 
 And
 
 ..  literalinclude:: _includes/_PartialMainNavigation.html
     :language: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Partials/Navigation/MainNavigation.html
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Partials/Navigation/MainNavigation.html
 
 ..  _cobj-pageview-paths-example:
 
 Example: Define a path that contains all templates
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------------------------------
 
 This is a basic definition of a :fluid:`PAGEVIEW` object with only one path to the
 templates:
@@ -234,14 +276,14 @@ templates:
 
     page = PAGE
     page.10 = PAGEVIEW
-    page.10.paths.100 = EXT:my_sitepackage/Resources/Private/Templates/
+    page.10.paths.100 = EXT:my_sitepackage/Resources/Private/PageView/
 
 The content of the folder could look like this:
 
 ..  directory-tree::
     :level: 2
 
-    *   EXT:my_sitepackage/Resources/Private/Templates/
+    *   EXT:my_sitepackage/Resources/Private/PageView/
 
         *   Layouts
 
@@ -269,22 +311,22 @@ The content of the folder could look like this:
 
 So for backend layout named "with_sidebar", the template file is
 then resolved to
-:file:`EXT:my_sitepackage/Resources/Private/Templates/Pages/With_sidebar.html`.
+:file:`EXT:my_sitepackage/Resources/Private/PageView/Pages/With_sidebar.html`.
 
 If the backend layout is named "TwoColumns" it is resovled to
-:file:`EXT:my_sitepackage/Resources/Private/Templates/Pages/TwoColumns.html`.
+:file:`EXT:my_sitepackage/Resources/Private/PageView/Pages/TwoColumns.html`.
 
 For all these templates
 :doc:`partial  <t3viewhelper:Global/Render#viewhelper-argument-typo3-cms-fluid-viewhelpers-renderviewhelper-partial>`
 are expected in folder
-:path:`EXT:my_sitepackage/Resources/Private/Templates/Pages/Partials` and
+:path:`EXT:my_sitepackage/Resources/Private/PageView/Pages/Partials` and
 :ref:`layouts <t3viewhelper:typo3fluid-fluid-layout>` in
-:path:`EXT:my_sitepackage/Resources/Private/Templates/Pages/Layouts`.
+:path:`EXT:my_sitepackage/Resources/Private/PageView/Pages/Layouts`.
 
 ..  _cobj-pageview-paths-example-extended:
 
 Example: Define fallbacks for a template paths
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+----------------------------------------------
 
 You can use the directories defined in :confval:`pageview-paths` to
 define fallback directories for the templates:
@@ -295,21 +337,21 @@ define fallback directories for the templates:
     page {
         10 = PAGEVIEW
         10.paths {
-            100 = EXT:my_basic_sitepackage/Resources/Private/Templates/
-            200 = EXT:my_general_sitepackage/Resources/Private/Templates/
-            300 = EXT:my_special_sitepackage/Resources/Private/Templates/
+            100 = EXT:my_basic_sitepackage/Resources/Private/PageView/
+            200 = EXT:my_general_sitepackage/Resources/Private/PageView/
+            300 = EXT:my_special_sitepackage/Resources/Private/PageView/
         }
     }
 
 The template for a page with a certain backend layout is first searched in
-:path:`EXT:my_special_sitepackage/Resources/Private/Templates/Pages/` then in
-:path:`EXT:my_general_sitepackage/Resources/Private/Templates/Pages/` and last
-in :path:`EXT:my_basic_sitepackage/Resources/Private/Templates/Pages/`.
+:path:`EXT:my_special_sitepackage/Resources/Private/PageView/Pages/` then in
+:path:`EXT:my_general_sitepackage/Resources/Private/PageView/Pages/` and last
+in :path:`EXT:my_basic_sitepackage/Resources/Private/PageView/Pages/`.
 
 ..  _cobj-pageview-variables-example:
 
 Example: Make additional variables available in the Fluid template
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+------------------------------------------------------------------
 
 ..  literalinclude:: _includes/_pageWithVariables.typoscript
     :langugage: typoscript
@@ -319,5 +361,4 @@ The following variables are now available in the Fluid template:
 
 ..  literalinclude:: _includes/_PageWithVariables.html
     :langugage: html
-    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
-
+    :caption: EXT:my_sitepackage/Resources/Private/PageView/Pages/Default.html
diff --git a/Documentation/ContentObjects/Pageview/_includes/_LinkToRootPage.html b/Documentation/ContentObjects/Pageview/_includes/_LinkToRootPage.html
index 8bb96d09b..582feefd7 100644
--- a/Documentation/ContentObjects/Pageview/_includes/_LinkToRootPage.html
+++ b/Documentation/ContentObjects/Pageview/_includes/_LinkToRootPage.html
@@ -1,7 +1,7 @@
 <f:layout name="Default" />
 <f:section name="Main">
     <main role="main">
-        <p>Go to the root page: <f:link.page pageUid="{page.rootPageId}">Home</f:link.page></p>
+        <p>Go to the root page: <f:link.page pageUid="{site.rootPageId}">Home</f:link.page></p>
         <p>...</p>
     </main>
-</f:section>
\ No newline at end of file
+</f:section>
diff --git a/Documentation/ContentObjects/Pageview/_includes/_PageWithConstant.html b/Documentation/ContentObjects/Pageview/_includes/_PageWithConstant.html
index d5483e4e9..93acd8b79 100644
--- a/Documentation/ContentObjects/Pageview/_includes/_PageWithConstant.html
+++ b/Documentation/ContentObjects/Pageview/_includes/_PageWithConstant.html
@@ -4,6 +4,6 @@
         <p>...</p>
     </main>
     <footer>
-        See also our <f:page pageUid="{settings.page.uid.dataPrivacy}">data privacy policy</f:page>
+        See also our <f:page pageUid="{settings.page.uids.dataPrivacy}">data privacy policy</f:page>
     </footer>
 </f:section>
\ No newline at end of file
diff --git a/Documentation/ContentObjects/Pageview/_includes/_pageWithBreadcrumb.typoscript b/Documentation/ContentObjects/Pageview/_includes/_pageWithBreadcrumb.typoscript
index 5ec979d1a..7e17fc463 100644
--- a/Documentation/ContentObjects/Pageview/_includes/_pageWithBreadcrumb.typoscript
+++ b/Documentation/ContentObjects/Pageview/_includes/_pageWithBreadcrumb.typoscript
@@ -3,7 +3,7 @@ page {
     10 = PAGEVIEW
     10 {
         paths {
-            100 = EXT:my_sitepackage/Resources/Private/Templates/
+            100 = EXT:my_sitepackage/Resources/Private/PageView/
         }
         dataProcessing {
             10 = menu
@@ -21,4 +21,4 @@ page {
             }
         }
     }
-}
\ No newline at end of file
+}
diff --git a/Documentation/ContentObjects/Pageview/_includes/_pageWithFluid.typoscript b/Documentation/ContentObjects/Pageview/_includes/_pageWithFluid.typoscript
index dcc7a602a..b44bd4fca 100644
--- a/Documentation/ContentObjects/Pageview/_includes/_pageWithFluid.typoscript
+++ b/Documentation/ContentObjects/Pageview/_includes/_pageWithFluid.typoscript
@@ -3,15 +3,16 @@ page {
     10 = PAGEVIEW
     10 {
         paths {
-            100 = EXT:my_sitepackage/Resources/Private/Templates/
+            100 = EXT:my_sitepackage/Resources/Private/PageView/
         }
         variables {
             parentPageTitle = TEXT
             parentPageTitle.data = levelfield:-1:title
         }
         dataProcessing {
-            10 = menu
-            10.as = mainMenu
+            10 = page-content
+            20 = menu
+            20.as = mainMenu
         }
     }
-}
\ No newline at end of file
+}
diff --git a/Documentation/ContentObjects/Pageview/_includes/_pageWithVariables.typoscript b/Documentation/ContentObjects/Pageview/_includes/_pageWithVariables.typoscript
index d532a45c6..a261b1816 100644
--- a/Documentation/ContentObjects/Pageview/_includes/_pageWithVariables.typoscript
+++ b/Documentation/ContentObjects/Pageview/_includes/_pageWithVariables.typoscript
@@ -3,7 +3,7 @@ page {
     10 = PAGEVIEW
     10 {
         paths {
-            100 = EXT:my_sitepackage/Resources/Private/Templates/
+            100 = EXT:my_sitepackage/Resources/Private/PageView/
         }
         variables {
             parentPageTitle = TEXT
@@ -11,4 +11,4 @@ page {
             another_variable =< lib.anotherVariable
         }
     }
-}
\ No newline at end of file
+}
diff --git a/Documentation/ContentObjects/UserAndUserInt/_Hostname.php b/Documentation/ContentObjects/UserAndUserInt/_Hostname.php
index e20bece27..28225f064 100644
--- a/Documentation/ContentObjects/UserAndUserInt/_Hostname.php
+++ b/Documentation/ContentObjects/UserAndUserInt/_Hostname.php
@@ -4,6 +4,8 @@
 
 namespace Vendor\SitePackage\UserFunctions;
 
+use Psr\Http\Message\ServerRequestInterface;
+
 final class Hostname
 {
     /**
@@ -11,9 +13,10 @@ final class Hostname
      *
      * @param  string Empty string (no content to process)
      * @param  array  TypoScript configuration
+     * @param  ServerRequestInterface The current PSR-7 request object
      * @return string HTML result
      */
-    public function getHostname(string $content, array $conf): string
+    public function getHostname(string $content, array $conf, ServerRequestInterface $request): string
     {
         return gethostname() ?: '';
     }
diff --git a/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst b/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst
index 7b56dba1c..0fbbb3204 100644
--- a/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst
+++ b/Documentation/DataProcessing/CommaSeparatedValueProcessor.rst
@@ -1,104 +1,94 @@
+:navigation-title: comma-separated-value
 ..  include:: /Includes.rst.txt
 ..  _CommaSeparatedValueProcessor:
 
-============================
-CommaSeparatedValueProcessor
-============================
+======================================
+`comma-separated-value` data processor
+======================================
 
-The :php:`CommaSeparatedValueProcessor` allows to split values into a
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor`,
+alias `comma-separated-value`, allows to split values into a
 two-dimensional array used for :abbr:`CSV (Comma-separated values)` files or
 :sql:`tt_content` records of CType `table`.
 
 The table data is transformed to a multi-dimensional array, taking the delimiter
 and enclosure into account, before it is passed to the view.
 
+..  contents:: Table of contents
+
 ..  _CommaSeparatedValueProcessor-options:
 
 Options:
 ========
 
-..  _CommaSeparatedValueProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: CommaSeparatedValueProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
-
-    If the condition is met, the data processor is processed.
-
-..  _CommaSeparatedValueProcessor-fieldName:
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-fieldName
----------
+    ..  _CommaSeparatedValueProcessor-if:
 
-..  confval:: fieldName
-    :name: CommaSeparatedValueProcessor-fieldName
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ''
+    ..  confval:: if
+        :name: CommaSeparatedValueProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
-    Name of the field in the processed ContentObjectRenderer.
+        If the condition is met, the data processor is processed.
 
+    ..  _CommaSeparatedValueProcessor-fieldName:
 
-..  _CommaSeparatedValueProcessor-as:
+    ..  confval:: fieldName
+        :name: CommaSeparatedValueProcessor-fieldName
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ''
 
-as
---
+        Name of the field in the processed ContentObjectRenderer.
 
-..  confval:: as
-    :name: CommaSeparatedValueProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: defaults to the fieldName
 
-    The variable's name to be used in the Fluid template.
+    ..  _CommaSeparatedValueProcessor-as:
 
-..  _CommaSeparatedValueProcessor-maximumColumns:
+    ..  confval:: as
+        :name: CommaSeparatedValueProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: defaults to the fieldName
 
-maximumColumns
---------------
+        The variable's name to be used in the Fluid template.
 
-..  confval:: maximumColumns
-    :name: CommaSeparatedValueProcessor-maximumColumns
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: :typoscript:`0`
+    ..  _CommaSeparatedValueProcessor-maximumColumns:
 
-    Maximal number of columns to be transformed. Surplus columns will be
-    silently dropped. When set to :typoscript:`0` (default) all columns will be
-    transformed.
+    ..  confval:: maximumColumns
+        :name: CommaSeparatedValueProcessor-maximumColumns
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: :typoscript:`0`
 
+        Maximal number of columns to be transformed. Surplus columns will be
+        silently dropped. When set to :typoscript:`0` (default) all columns will be
+        transformed.
 
-..  _CommaSeparatedValueProcessor-fieldDelimiter:
+    ..  _CommaSeparatedValueProcessor-fieldDelimiter:
 
-fieldDelimiter
---------------
+    ..  confval:: fieldDelimiter
+        :name: CommaSeparatedValueProcessor-fieldDelimiter
+        :Required:  false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: :typoscript:`,`
 
-..  confval:: fieldDelimiter
-    :name: CommaSeparatedValueProcessor-fieldDelimiter
-    :Required:  false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: :typoscript:`,`
+        The field delimiter, a character separating the values.
 
-    The field delimiter, a character separating the values.
 
+    ..  _CommaSeparatedValueProcessor-fieldEnclosure:
 
-..  _CommaSeparatedValueProcessor-fieldEnclosure:
+    ..  confval:: fieldEnclosure
+        :name: CommaSeparatedValueProcessor-fieldEnclosure
+        :Required:  false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: :typoscript:`"`
 
-fieldEnclosure
---------------
-
-..  confval:: fieldEnclosure
-    :name: CommaSeparatedValueProcessor-fieldEnclosure
-    :Required:  false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: :typoscript:`"`
-
-    The field enclosure, a character surrounding the values.
+        The field enclosure, a character surrounding the values.
 
 ..  _CommaSeparatedValueProcessor-examples:
 
@@ -114,8 +104,7 @@ the values can be specified.
 This example is also described in-depth in :ref:`TYPO3 Explained:
 Extended content element example <t3coreapi:AddingCE-Extended-Example>`.
 
-Example data in the field :php:`bodytext`
------------------------------------------
+..  rubric:: Example data in the field :php:`bodytext`
 
 Field :sql:`bodytext` in table :sql:`tt_content`:
 
@@ -125,31 +114,21 @@ Field :sql:`bodytext` in table :sql:`tt_content`:
     "This is row 2 column 1","This is row 2 column 2","This is row 2 column 3"
     "This is row 3 column 1","This is row 3 column 2","This is row 3 column 3"
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 We define the :typoscript:`dataProcessing` property to use the
 :php:`CommaSeparatedValueProcessor`:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/CommaSeparatedValueProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`comma-separated-value` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor`.
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 In the Fluid template, you can iterate over the processed data. "myContentTable" can
 be used as a variable :html:`{myContentTable}` inside Fluid for iteration.
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcCsv.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 Using :typoscript:`maximumColumns` limits the amount of columns in the multi dimensional array.
 In this example, the field data of the last column will be stripped off. Therefore the output would be:
diff --git a/Documentation/DataProcessing/CustomDataProcessors.rst b/Documentation/DataProcessing/CustomDataProcessors.rst
index 8a69cfbeb..13cca9b51 100644
--- a/Documentation/DataProcessing/CustomDataProcessors.rst
+++ b/Documentation/DataProcessing/CustomDataProcessors.rst
@@ -17,11 +17,6 @@ data processor:
 The available configuration depends on the implementation of the
 specific custom data processor, of course.
 
-..  versionadded:: 12.1
-    One can configure a custom alias in :file:`Configuration/Services.yaml`
-    and use it in TypoScript instead of the fully-qualified class name.
-
-
 Example output
 ==============
 
diff --git a/Documentation/DataProcessing/DatabaseQueryProcessor.rst b/Documentation/DataProcessing/DatabaseQueryProcessor.rst
index 85fba8c83..acad1d342 100644
--- a/Documentation/DataProcessing/DatabaseQueryProcessor.rst
+++ b/Documentation/DataProcessing/DatabaseQueryProcessor.rst
@@ -1,19 +1,23 @@
+:navigation-title: database-query
 ..  include:: /Includes.rst.txt
 ..  _DatabaseQueryProcessor:
 
-======================
-DatabaseQueryProcessor
-======================
+===============================
+`database-query` data processor
+===============================
 
-The :php:`DatabaseQueryProcessor` fetches records from the database, using
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor`,
+alias `database-query`, fetches records from the database, using
 standard TypoScript :ref:`select` semantics. The result is then passed to the
 :ref:`cobj-fluidtemplate` as an array.
 
 This way a :ref:`cobj-fluidtemplate` cObject can iterate over the
 array of records.
 
+..  contents:: Table of contents
+
 ..  versionadded:: 13.2
-    The :php:`DatabaseQueryProcessor` can be used in combination with the
+    The :typoscript:`database-query` processor can be used in combination with the
     :ref:`RecordTransformationProcessor` to use additional computed information.
 
 ..  _DatabaseQueryProcessor-options:
@@ -21,70 +25,63 @@ array of records.
 Options:
 ========
 
-..  _DatabaseQueryProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: DatabaseQueryProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
-
-    Only if the condition is met the data processor is executed.
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
+    ..  _DatabaseQueryProcessor-if:
 
-..  _DatabaseQueryProcessor-table:
+    ..  confval:: if
+        :name: DatabaseQueryProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
-table
------
+        Only if the condition is met the data processor is executed.
 
-..  confval:: table
-    :name: DatabaseQueryProcessor-table
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ''
 
-    Name of the table from which the records should be fetched.
+    ..  _DatabaseQueryProcessor-table:
 
-..  _DatabaseQueryProcessor-as:
+    ..  confval:: table
+        :name: DatabaseQueryProcessor-table
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ''
 
-as
---
+        Name of the table from which the records should be fetched.
 
-..  confval:: as
-    :name: DatabaseQueryProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: 'records'
+    ..  _DatabaseQueryProcessor-as:
 
-    The variable's name to be used in the Fluid template.
+    ..  confval:: as
+        :name: DatabaseQueryProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: 'records'
 
-..  _DatabaseQueryProcessor-dataProcessing:
+        The variable's name to be used in the Fluid template.
 
-dataProcessing
---------------
+    ..  _DatabaseQueryProcessor-dataProcessing:
 
-..  confval:: dataProcessing
-    :name: DatabaseQueryProcessor-dataProcessing
-    :Required: false
-    :type: array of :ref:`dataProcessing`
-    :Default: []
+    ..  confval:: dataProcessing
+        :name: DatabaseQueryProcessor-dataProcessing
+        :Required: false
+        :type: array of :ref:`dataProcessing`
+        :Default: []
 
-    Array of data processors to be applied to all fetched records.
+        Array of data processors to be applied to all fetched records.
 
-..  note::
-    All other options will be interpreted as in the TypoScript function
-    :typoscript:`select`, including :typoscript:`pidInList`,
-    :typoscript:`orderBy`, :typoscript:`where`, etc. See the reference of
-    :ref:`select`.
+    ..  note::
+        All other options will be interpreted as in the TypoScript function
+        :typoscript:`select`, including :typoscript:`pidInList`,
+        :typoscript:`orderBy`, :typoscript:`where`, etc. See the reference of
+        :ref:`select`.
 
-..  warning::
-    When using the DatabaseQueryProcessor, you may encounter issues with
-    language and/or versioning overlays, that currently can not be resolved.
-    See `here <https://forge.typo3.org/issues/85284#note-5>`__ for more
-    information.
+    ..  warning::
+        When using the DatabaseQueryProcessor, you may encounter issues with
+        language and/or versioning overlays, that currently can not be resolved.
+        See `here <https://forge.typo3.org/issues/85284#note-5>`__ for more
+        information.
 
 ..  _DatabaseQueryProcessor-example-record-transformation:
 
@@ -110,22 +107,14 @@ Example: Display haiku records
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-TypoScript
-----------
+..  rubric:: TypoScript
 
 We define the :typoscript:`dataProcessing` property to use the
 :php:`DatabaseQueryProcessor`:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/DatabaseQueryProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`database-query` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor`.
-
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 In the Fluid template then iterate over the records. As we used the recursive
 data processor :ref:`FilesProcessor` on the image records, we can also output
@@ -133,9 +122,7 @@ the images.
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcDb.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 Each entry of the records array contains the data of the table in :php:`data`
 and the data of the images in :php:`files`.
diff --git a/Documentation/DataProcessing/FilesProcessor.rst b/Documentation/DataProcessing/FilesProcessor.rst
index b80cf394b..9b5598e07 100644
--- a/Documentation/DataProcessing/FilesProcessor.rst
+++ b/Documentation/DataProcessing/FilesProcessor.rst
@@ -1,11 +1,13 @@
+:navigation-title: files
 ..  include:: /Includes.rst.txt
 ..  _FilesProcessor:
 
-==============
-FilesProcessor
-==============
+======================
+`files` data processor
+======================
 
-This data processor can be used for processing file information:
+This data processor :php:`\TYPO3\CMS\Frontend\DataProcessing\FilesProcessor`,
+alias `files`, can be used for processing file information:
 
 *   relations to file records (:sql:`sys_file_reference`)
 *   fetch files records by their uids in table (:sql:`sys_file`)
@@ -15,200 +17,163 @@ This data processor can be used for processing file information:
 A :typoscript:`FLUIDTEMPLATE` can then iterate over processed data
 automatically.
 
+..  contents:: Table of contents
+
 ..  _FilesProcessor-options:
 
 Options:
 ========
 
-..  _FilesProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: FilesProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
-
-    Only, if the condition is met the data processor is executed.
-
-
-..  _FilesProcessor-references:
-
-references
-----------
-
-..  confval:: references
-    :name: FilesProcessor-references
-    :Required: false
-    :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
-    :Default: ''
-    :Example: '1,303,42'
-
-    If this option contains a comma-separated list of integers, these are
-    treated as uids of file references (:sql:`sys_file_reference`).
-
-    The corresponding file records are added to the output array.
-
-    :ref:`stdWrap` properties can also be used, see
-    :ref:`FilesProcessor-stdWrap-on-references`.
-
-
-..  _FilesProcessor-references-fieldName:
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-references.fieldName
-~~~~~~~~~~~~~~~~~~~~
+    ..  _FilesProcessor-if:
 
-..  confval:: references.fieldName
-    :name: FilesProcessor-references-fieldName
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ''
-    :Example: 'media'
+    ..  confval:: if
+        :name: FilesProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
-    If both :typoscript:`references.fieldName` and
-    :typoscript:`references.table` are set, the file records are fetched from
-    the referenced table and field, for example the :sql:`media` field of a
-    :sql:`tt_content` record.
+        Only, if the condition is met the data processor is executed.
 
+    ..  _FilesProcessor-references:
 
-..  _FilesProcessor-references-table:
+    ..  confval:: references
+        :name: FilesProcessor-references
+        :Required: false
+        :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
+        :Default: ''
+        :Example: '1,303,42'
 
-references.table
-~~~~~~~~~~~~~~~~
+        If this option contains a comma-separated list of integers, these are
+        treated as uids of file references (:sql:`sys_file_reference`).
 
-..  confval:: references.table
-    :name: FilesProcessor-references.table
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ''
-    :Example: 'tt_content'
+        The corresponding file records are added to the output array.
 
-    If :typoscript:`references` should be interpreted as TypoScript
-    :ref:`select` function, :typoscript:`references.fieldName` must be set to
-    the desired field name of the table to be queried.
+        :ref:`stdWrap` properties can also be used, see
+        :ref:`FilesProcessor-stdWrap-on-references`.
 
+    ..  _FilesProcessor-references-fieldName:
 
-..  _FilesProcessor-files:
+    ..  confval:: references.fieldName
+        :name: FilesProcessor-references-fieldName
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ''
+        :Example: 'media'
 
-files
------
+        If both :typoscript:`references.fieldName` and
+        :typoscript:`references.table` are set, the file records are fetched from
+        the referenced table and field, for example the :sql:`media` field of a
+        :sql:`tt_content` record.
 
-..  confval:: files
-    :name: FilesProcessor-files
-    :Required: false
-    :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
-    :Default: ''
-    :Example: '1,303,42'
+    ..  _FilesProcessor-references-table:
 
-    If this option contains a comma-separated list of integers,
-    these are treated as uids of files (:sql:`sys_file`).
+    ..  confval:: references.table
+        :name: FilesProcessor-references.table
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ''
+        :Example: 'tt_content'
 
+        If :typoscript:`references` should be interpreted as TypoScript
+        :ref:`select` function, :typoscript:`references.fieldName` must be set to
+        the desired field name of the table to be queried.
 
-..  _FilesProcessor-collections:
+    ..  _FilesProcessor-files:
 
-collections
------------
+    ..  confval:: files
+        :name: FilesProcessor-files
+        :Required: false
+        :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
+        :Default: ''
+        :Example: '1,303,42'
 
-..  confval:: collections
-    :name: FilesProcessor-collections
-    :Required: false
-    :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
-    :Default: ''
-    :Example: '1,303,42'
+        If this option contains a comma-separated list of integers,
+        these are treated as uids of files (:sql:`sys_file`).
 
-    If this option contains a comma-separated list of integers,
-    these are treated as uids of collections. The file records in each
-    collection are then being added to the output array.
+    ..  _FilesProcessor-collections:
 
+    ..  confval:: collections
+        :name: FilesProcessor-collections
+        :Required: false
+        :type: :ref:`data-type-string` (comma-separated integers) / :ref:`stdWrap`
+        :Default: ''
+        :Example: '1,303,42'
 
-..  _FilesProcessor-folders:
+        If this option contains a comma-separated list of integers,
+        these are treated as uids of collections. The file records in each
+        collection are then being added to the output array.
 
-folders
--------
+    ..  _FilesProcessor-folders:
 
-..  confval:: folders
-    :name: FilesProcessor-folders
-    :Required: false
-    :type: :ref:`data-type-string` (comma-separated folders), :ref:`stdWrap`
-    :Default: ""
-    :Example: "23:/other/folder/"
+    ..  confval:: folders
+        :name: FilesProcessor-folders
+        :Required: false
+        :type: :ref:`data-type-string` (comma-separated folders), :ref:`stdWrap`
+        :Default: ""
+        :Example: "23:/other/folder/"
 
-    Fetches all files from the referenced folders. The following syntax is
-    possible:
+        Fetches all files from the referenced folders. The following syntax is
+        possible:
 
-    `t3://folder?storage=2&identifier=/my/folder/`
-        Folder :file:`/my/folder/` from storage with uid `2`
+        `t3://folder?storage=2&identifier=/my/folder/`
+            Folder :file:`/my/folder/` from storage with uid `2`
 
-    `23:/other/folder/`
-        Folder :file:`/other/folder/` from storage with uid `23`
+        `23:/other/folder/`
+            Folder :file:`/other/folder/` from storage with uid `23`
 
-    `/folderInMyFileadmin/something/`:
-        Folder :file:`/folderInMyFileadmin/something/` from the default storage
-        `0` (:file:`fileadmin`)
+        `/folderInMyFileadmin/something/`:
+            Folder :file:`/folderInMyFileadmin/something/` from the default storage
+            `0` (:file:`fileadmin`)
 
+    ..  _FilesProcessor-folders-recursive:
 
-..  _FilesProcessor-folders-recursive:
+    ..  confval:: folders.recursive
+        :name: FilesProcessor-folders-recursive
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ""
+        :Example: "1"
 
-folders.recursive
-~~~~~~~~~~~~~~~~~
+        If set to a non-empty value file, records will be added from folders
+        recursively.
 
-..  confval:: folders.recursive
-    :name: FilesProcessor-folders-recursive
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ""
-    :Example: "1"
+    ..  _FilesProcessor-sorting:
 
-    If set to a non-empty value file, records will be added from folders
-    recursively.
+    ..  confval:: sorting
+        :name: FilesProcessor-sorting
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ""
+        :Example: "filesize"
 
+        The property of the file records by which they should be sorted.
+        For example, filesize or title.
 
-..  _FilesProcessor-sorting:
+    ..  _FilesProcessor-sorting-direction:
 
-sorting
--------
+    ..  confval:: sorting.direction
+        :name: FilesProcessor-sorting-direction
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default:  "ascending"
+        :Example: "descending"
 
-..  confval:: sorting
-    :name: FilesProcessor-sorting
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ""
-    :Example: "filesize"
+        The sorting direction (:typoscript:`ascending` or :typoscript:`descending`).
 
-    The property of the file records by which they should be sorted.
-    For example, filesize or title.
+    ..  _FilesProcessor-as:
 
+    ..  confval:: as
+        :name: FilesProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: "files"
 
-..  _FilesProcessor-sorting-direction:
-
-sorting.direction
-~~~~~~~~~~~~~~~~~
-
-..  confval:: sorting.direction
-    :name: FilesProcessor-sorting-direction
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default:  "ascending"
-    :Example: "descending"
-
-    The sorting direction (:typoscript:`ascending` or :typoscript:`descending`).
-
-
-..  _FilesProcessor-as:
-
-as
---
-
-..  confval:: as
-    :name: FilesProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: "files"
-
-    The variable name to be used in the Fluid template.
-
+        The variable name to be used in the Fluid template.
 
 ..  _FilesProcessor-example-render-image:
 
@@ -217,30 +182,19 @@ Example 1: Render the images stored in field image
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 Using the :php:`FilesProcessor` the following scenario is possible:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/FilesProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`files` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\FilesProcessor`.
-
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 Then iterate over the files in the :ref:`Fluid <t3coreapi:fluid>` template:
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcFiles.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 The array :php:`images` contains the data of the files now:
 
diff --git a/Documentation/DataProcessing/FlexFormProcessor.rst b/Documentation/DataProcessing/FlexFormProcessor.rst
index c5757ae76..1c912128d 100644
--- a/Documentation/DataProcessing/FlexFormProcessor.rst
+++ b/Documentation/DataProcessing/FlexFormProcessor.rst
@@ -1,70 +1,70 @@
+:navigation-title: flex-form
 ..  include:: /Includes.rst.txt
 ..  _FlexFormProcessor:
 ..  index:: FlexForm, DataProcessing
 
-=================
-FlexFormProcessor
-=================
+==========================
+`flex-form` data processor
+==========================
 
 TYPO3 offers :ref:`FlexForms <t3coreapi:flexforms>` which can be used to store
 data within an XML structure inside a single database column. The data processor
-:php:`\TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor` converts the
+:php:`\TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor`,
+alias `flex-form`, converts the
 FlexForm data of a given field into a Fluid-readable array.
 
+..  contents:: Table of contents
+
 ..  _FlexFormProcessor-options:
 
 Options
 =======
 
-..  _FlexFormProcessor-fieldname:
-
-fieldname
----------
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-..  confval:: fieldname
-    :name: FlexFormProcessor-fieldname
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: 'pi_flexform'
+    ..  _FlexFormProcessor-fieldname:
 
-    Field name of the column the FlexForm data is stored in.
+    ..  confval:: fieldName
+        :name: FlexFormProcessor-fieldname
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: 'pi_flexform'
 
+        Field name of the column the FlexForm data is stored in.
 
-..  _FlexFormProcessor-references:
 
-references
-----------
+    ..  _FlexFormProcessor-references:
 
-..  confval:: references
-    :name: FlexFormProcessor-references
+    ..  confval:: references
+        :name: FlexFormProcessor-references
 
-    ..  versionadded:: 13.0
-    :Required: false
-    :type: array
+        ..  versionadded:: 13.0
+        :Required: false
+        :type: array
 
-    Associative array of FlexForm fields (key) and the according database field
-    (value).
+        Associative array of FlexForm fields (key) and the according database field
+        (value).
 
-    Each FlexForm field, which should be resolved, needs a reference definition
-    to the :ref:`foreign_match_fields <t3tca:columns-inline-properties-foreign-match-fields>`.
-    This reference is used in the :ref:`FilesProcessor <FilesProcessor>` to
-    resolve the correct :ref:`FAL <t3coreapi:fal>` resource.
+        Each FlexForm field, which should be resolved, needs a reference definition
+        to the :ref:`foreign_match_fields <t3tca:columns-inline-properties-foreign-match-fields>`.
+        This reference is used in the :ref:`FilesProcessor <FilesProcessor>` to
+        resolve the correct :ref:`FAL <t3coreapi:fal>` resource.
 
-    See :ref:`FlexFormProcessor-resolving-fal`.
+        See :ref:`FlexFormProcessor-resolving-fal`.
 
 
-..  _FlexFormProcessor-as:
+    ..  _FlexFormProcessor-as:
 
-as
---
+    ..  confval:: as
+        :name: FlexFormProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: 'flexFormData'
 
-..  confval:: as
-    :name: FlexFormProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: 'flexFormData'
-
-    Name for the variable in the Fluid template.
+        Name for the variable in the Fluid template.
 
 ..  _FlexFormProcessor-examples:
 
@@ -79,16 +79,8 @@ Example of a minimal TypoScript configuration
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`flex-form` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor`.
-
 The converted array can be accessed within the Fluid template with the
 :html:`{flexFormData}` variable.
 
@@ -100,9 +92,6 @@ Example of an advanced TypoScript configuration
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
     10 {
         fieldName = my_flexform_field
@@ -120,9 +109,6 @@ Example with a custom sub-processor
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
 
-    # Before TYPO3 v12.1 you have to specify the fully-qualified class name of the processor
-    # dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
-    # Since TYPO3 v12.1 one can also use the available alias
     10 = flex-form
     10 {
         fieldName = my_flexform_field
diff --git a/Documentation/DataProcessing/GalleryProcessor.rst b/Documentation/DataProcessing/GalleryProcessor.rst
index d871d778a..9742739f7 100644
--- a/Documentation/DataProcessing/GalleryProcessor.rst
+++ b/Documentation/DataProcessing/GalleryProcessor.rst
@@ -1,235 +1,194 @@
+:navigation-title: gallery
 ..  include:: /Includes.rst.txt
 ..  _GalleryProcessor:
 
-================
-GalleryProcessor
-================
+========================
+`gallery` data processor
+========================
 
-The :php:`GalleryProcessor` provides the logic for working with galleries and
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor`,
+alias `gallery`, provides the logic for working with galleries and
 calculates the maximum asset size. It uses the files already present in
 the `processedData` array for its calculations. The :ref:`FilesProcessor` can
 be used to fetch the files.
 
+..  contents:: Table of contents
+
 ..  _GalleryProcessor-options:
 
 Options:
 ========
 
-..  _GalleryProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: GalleryProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
-
-    Only if the condition is met the data processor is executed.
-
-
-..  _GalleryProcessor-filesProcessedDataKey:
-
-filesProcessedDataKey
----------------------
-
-..  confval:: filesProcessedDataKey
-    :name: GalleryProcessor-filesProcessedDataKey
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: 'files'
-    :Example: 'myImages'
-
-    Key of the array previously processed by the :php:`FilesProcessor`.
-
-
-..  _GalleryProcessor-numberOfColumns:
-
-numberOfColumns
----------------
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-..  confval:: numberOfColumns
-    :name: GalleryProcessor-numberOfColumns
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: field:imagecols
-    :Example: 4
+    ..  _GalleryProcessor-if:
 
-    Expects the desired number of columns. Defaults to the value of the field
-    `imagecols` (:guilabel:`Number of Columns`) if used with content elements.
+    ..  confval:: if
+        :name: GalleryProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
+        Only if the condition is met the data processor is executed.
 
-..  _GalleryProcessor-mediaOrientation:
 
-mediaOrientation
-----------------
+    ..  _GalleryProcessor-filesProcessedDataKey:
 
-..  confval:: mediaOrientation
-    :name: GalleryProcessor-mediaOrientation
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: field:imageorient
-    :Example: 2
+    ..  confval:: filesProcessedDataKey
+        :name: GalleryProcessor-filesProcessedDataKey
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: 'files'
+        :Example: 'myImages'
 
-    Expects the image orientation as used in the field `imageorient` in content
-    elements such as text with images. Defaults to the value of the field
-    `imageorient` (:guilabel:`Position and Alignment`) if used with content
-    elements.
+        Key of the array previously processed by the :php:`FilesProcessor`.
 
-    ..  include:: /Images/AutomaticScreenshots/Fluidtemplate/ImageOrientation.rst.txt
 
+    ..  _GalleryProcessor-numberOfColumns:
 
-..  _GalleryProcessor-maxGalleryWidth:
+    ..  confval:: numberOfColumns
+        :name: GalleryProcessor-numberOfColumns
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: field:imagecols
+        :Example: 4
 
-maxGalleryWidth
----------------
+        Expects the desired number of columns. Defaults to the value of the field
+        `imagecols` (:guilabel:`Number of Columns`) if used with content elements.
 
-..  confval:: maxGalleryWidth
-    :name: GalleryProcessor-maxGalleryWidth
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 600
+    ..  _GalleryProcessor-mediaOrientation:
 
-    Maximal gallery width in pixels.
+    ..  confval:: mediaOrientation
+        :name: GalleryProcessor-mediaOrientation
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: field:imageorient
+        :Example: 2
 
+        Expects the image orientation as used in the field `imageorient` in content
+        elements such as text with images. Defaults to the value of the field
+        `imageorient` (:guilabel:`Position and Alignment`) if used with content
+        elements.
 
-..  _GalleryProcessor-maxGalleryWidthInText:
+        ..  include:: /Images/AutomaticScreenshots/Fluidtemplate/ImageOrientation.rst.txt
 
-maxGalleryWidthInText
----------------------
+    ..  _GalleryProcessor-maxGalleryWidth:
 
-..  confval:: maxGalleryWidthInText
-    :name: GalleryProcessor-maxGalleryWidthInText
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 300
+    ..  confval:: maxGalleryWidth
+        :name: GalleryProcessor-maxGalleryWidth
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 600
 
-    Maximal gallery width in pixels if displayed in a text.
+        Maximal gallery width in pixels.
 
-..  _GalleryProcessor-equalMediaHeight:
-..  _GalleryProcessor-equalMediaWidth:
+    ..  _GalleryProcessor-maxGalleryWidthInText:
 
-equalMediaHeight, equalMediaWidth
----------------------------------
+    ..  confval:: maxGalleryWidthInText
+        :name: GalleryProcessor-maxGalleryWidthInText
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 300
 
-..  confval:: equalMediaHeight, equalMediaWidth
-    :name: GalleryProcessor-equalMediaHeight
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: field:imageheight, field:imagewidth
-    :Example: 300
+        Maximal gallery width in pixels if displayed in a text.
 
-    If set all images get scaled to a uniform height / width. Defaults
-    to the value of the fields `imageheight` (:guilabel:`Height of each element
-    (px)`), `imagewidth` (:guilabel:`Width of each element (px)`) if used with
-    content elements.
+    ..  _GalleryProcessor-equalMediaHeight:
+    ..  _GalleryProcessor-equalMediaWidth:
 
-    ..  include:: /Images/AutomaticScreenshots/Fluidtemplate/MediaHeight.rst.txt
+    ..  confval:: equalMediaHeight, equalMediaWidth
+        :name: GalleryProcessor-equalMediaHeight
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: field:imageheight, field:imagewidth
+        :Example: 300
 
+        If set all images get scaled to a uniform height / width. Defaults
+        to the value of the fields `imageheight` (:guilabel:`Height of each element
+        (px)`), `imagewidth` (:guilabel:`Width of each element (px)`) if used with
+        content elements.
 
-..  _GalleryProcessor-columnSpacing:
+        ..  include:: /Images/AutomaticScreenshots/Fluidtemplate/MediaHeight.rst.txt
 
-columnSpacing
--------------
+    ..  _GalleryProcessor-columnSpacing:
 
-..  confval:: columnSpacing
-    :name: GalleryProcessor-columnSpacing
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 4
+    ..  confval:: columnSpacing
+        :name: GalleryProcessor-columnSpacing
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 4
 
-    Space between columns in pixels
+        Space between columns in pixels
 
+    ..  _GalleryProcessor-borderEnabled:
 
-..  _GalleryProcessor-borderEnabled:
+    ..  confval:: borderEnabled
+        :name: GalleryProcessor-borderEnabled
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: field:imageborder
+        :Example: 1
 
-borderEnabled
--------------
+        Should there be a border around the images? Defaults to the value of the
+        fields `imageborder` (:guilabel:`Number of Columns`) if used with content
+        elements.
 
-..  confval:: borderEnabled
-    :name: GalleryProcessor-borderEnabled
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: field:imageborder
-    :Example: 1
+    ..  _GalleryProcessor-borderWidth:
 
-    Should there be a border around the images? Defaults to the value of the
-    fields `imageborder` (:guilabel:`Number of Columns`) if used with content
-    elements.
+    ..  confval:: borderWidth
+        :name: GalleryProcessor-borderWidth
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 2
 
-..  _GalleryProcessor-borderWidth:
+        Width of the border in pixels.
 
-borderWidth
------------
+    ..  _GalleryProcessor-borderPadding:
 
-..  confval:: borderWidth
-    :name: GalleryProcessor-borderWidth
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 2
+    ..  confval:: borderPadding
+        :name: GalleryProcessor-borderPadding
+        :Required: false
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 20
 
-    Width of the border in pixels.
+        Padding around the border in pixels.
 
 
-..  _GalleryProcessor-borderPadding:
+    ..  _GalleryProcessor-cropVariant:
 
-borderPadding
--------------
+    ..  confval:: cropVariant
+        :name: GalleryProcessor-cropVariant
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: "default"
+        :Example: "mobile"
 
-..  confval:: borderPadding
-    :name: GalleryProcessor-borderPadding
-    :Required: false
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 20
+        See :ref:`crop variants in the TCA reference <t3tca:columns-imageManipulation-properties-cropVariants>`
 
-    Padding around the border in pixels.
+    ..  _GalleryProcessor-as:
 
+    ..  confval:: as
+        :name: GalleryProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: "files"
 
-..  _GalleryProcessor-cropVariant:
+        The variable name to be used in the Fluid template.
 
-cropVariant
------------
+    ..  _GalleryProcessor-dataProcessing:
 
-..  confval:: cropVariant
-    :name: GalleryProcessor-cropVariant
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: "default"
-    :Example: "mobile"
+    ..  confval:: dataProcessing
+        :name: GalleryProcessor-dataProcessing
+        :Required: false
+        :type: array of :ref:`dataProcessing`
+        :Default: []
 
-    See :ref:`crop variants in the TCA reference <t3tca:columns-imageManipulation-properties-cropVariants>`
-
-
-..  _GalleryProcessor-as:
-
-as
---
-
-..  confval:: as
-    :name: GalleryProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: "files"
-
-    The variable name to be used in the Fluid template.
-
-
-..  _GalleryProcessor-dataProcessing:
-
-dataProcessing
---------------
-
-..  confval:: dataProcessing
-    :name: GalleryProcessor-dataProcessing
-    :Required: false
-    :type: array of :ref:`dataProcessing`
-    :Default: []
-
-    Array of data processors to be applied to all fetched records.
+        Array of data processors to be applied to all fetched records.
 
 ..  _GalleryProcessor-example-rows-columns:
 
@@ -238,9 +197,7 @@ Example: display images in rows and columns
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 As the :php:`GalleryProcessor` expects the data of the files to be
 present in the the `processedData` array, the :php:`FilesProcessor`
@@ -254,18 +211,11 @@ in the :php:`GalleryProcessor` has to be equal to the content of
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/GalleryProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`gallery` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor`.
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcGallery.rst.txt
 
-Output
-------
+..  rubric:: Output
 
 The array now contains the images ordered in rows and columns. For each image
 there is a desired width and height supplied.
diff --git a/Documentation/DataProcessing/Index.rst b/Documentation/DataProcessing/Index.rst
index f138a8081..232b8b270 100644
--- a/Documentation/DataProcessing/Index.rst
+++ b/Documentation/DataProcessing/Index.rst
@@ -3,9 +3,9 @@
 ..  _cobj-fluidtemplate-properties-dataprocessing:
 ..  _dataProcessing:
 
-==============
-dataProcessing
-==============
+===============
+Data processors
+===============
 
 :ref:`dataProcessing <fluidtemplate-dataProcessing>` is a property of
 :ref:`cobj-fluidtemplate` and :ref:`cobj-pageview`.
@@ -27,7 +27,7 @@ for example for comma-separated values, related files or related records.
     FlexFormProcessor
     GalleryProcessor
     LanguageMenuProcessor
-    MenuProcessor
+    MenuProcessor/Index
     PageContentFetchingProcessor
     RecordTransformationProcessor
     SiteProcessor
diff --git a/Documentation/DataProcessing/LanguageMenuProcessor.rst b/Documentation/DataProcessing/LanguageMenuProcessor.rst
index ef543d10a..3acbe292d 100644
--- a/Documentation/DataProcessing/LanguageMenuProcessor.rst
+++ b/Documentation/DataProcessing/LanguageMenuProcessor.rst
@@ -1,13 +1,17 @@
+:navigation-title: language-menu
 ..  include:: /Includes.rst.txt
 ..  _LanguageMenuProcessor:
 
-=====================
-LanguageMenuProcessor
-=====================
+============================
+language-menu data processor
+============================
 
-This menu processor generates a list of language menu items which can be
+The processor :php:`\TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor`,
+alias `language-menu`, generates a list of language menu items which can be
 assigned to the :typoscript:`FLUIDTEMPLATE` as a variable.
 
+..  contents:: Table of contents
+
 ..  hint::
     The third-party extension
     `b13/menus <https://extensions.typo3.org/extension/menus>`__ also provides
@@ -17,70 +21,60 @@ assigned to the :typoscript:`FLUIDTEMPLATE` as a variable.
     <https://github.com/b13/menus/blob/master/README.md>`__ for more
     information.
 
-
 ..  _LanguageMenuProcessor-options:
 
 Options:
 ========
 
-..  _LanguageMenuProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: LanguageMenuProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-
-    Only if the condition is met the data processor is executed.
-
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-..  _LanguageMenuProcessor-languages:
+    ..  _LanguageMenuProcessor-if:
 
-languages
----------
+    ..  confval:: if
+        :name: LanguageMenuProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
 
-..  confval:: languages
-    :name: LanguageMenuProcessor-languages
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: "auto"
-    :Example: "0,1,2"
+        Only if the condition is met the data processor is executed.
 
-    A list of comma-separated language IDs (e.g. 0,1,2) to use for the menu
-    creation or `auto` to load from the :ref:`site configuration
-    <t3coreapi:sitehandling>`.
+    ..  _LanguageMenuProcessor-languages:
 
+    ..  confval:: languages
+        :name: LanguageMenuProcessor-languages
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: "auto"
+        :Example: "0,1,2"
 
-..  _LanguageMenuProcessor-addQueryString-exclude:
+        A list of comma-separated language IDs (e.g. 0,1,2) to use for the menu
+        creation or `auto` to load from the :ref:`site configuration
+        <t3coreapi:sitehandling>`.
 
-addQueryString.exclude
-----------------------
 
-..  confval:: addQueryString.exclude
-    :name: LanguageMenuProcessor-addQueryString-exclude
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ""
-    :Example: "gclid,contrast"
+    ..  _LanguageMenuProcessor-addQueryString-exclude:
 
-    A list of comma-separated parameter names to be excluded from the language
-    menu URLs.
+    ..  confval:: addQueryString.exclude
+        :name: LanguageMenuProcessor-addQueryString-exclude
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ""
+        :Example: "gclid,contrast"
 
+        A list of comma-separated parameter names to be excluded from the language
+        menu URLs.
 
-..  _LanguageMenuProcessor-as:
+    ..  _LanguageMenuProcessor-as:
 
-as
---
+    ..  confval:: as
+        :name: LanguageMenuProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: defaults to the fieldName
 
-..  confval:: as
-    :name: LanguageMenuProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: defaults to the fieldName
-
-    The variable name to be used in the Fluid template.
+        The variable name to be used in the Fluid template.
 
 ..  _LanguageMenuProcessor-example:
 
@@ -89,30 +83,19 @@ Example: Menu of all language from site configuration
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 Using the :php:`LanguageMenuProcessor` the following scenario is possible:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/LanguageMenuProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`language-menu` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor`.
-
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 This generated menu can be used in Fluid like this:
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcLangMenu.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 The array now contains information on all languages as defined in the site
 configuration. As the current page is not translated into German, the
diff --git a/Documentation/DataProcessing/MenuProcessor.rst b/Documentation/DataProcessing/MenuProcessor.rst
deleted file mode 100644
index d53d92653..000000000
--- a/Documentation/DataProcessing/MenuProcessor.rst
+++ /dev/null
@@ -1,140 +0,0 @@
-..  include:: /Includes.rst.txt
-..  _MenuProcessor:
-
-=============
-MenuProcessor
-=============
-
-The :php:`MenuProcessor` utilizes :ref:`HMENU <cobj-hmenu>` to generate a list
-of menu items which can be assigned to :typoscript:`FLUIDTEMPLATE` as a
-variable.
-
-Additional data processing is supported and will be applied to each record.
-
-..  hint::
-    The third party extension `b13/menus
-    <https://extensions.typo3.org/extension/menus>`__ also provides menu
-    processors like :php:`\B13\Menus\DataProcessing\TreeMenu` and
-    :php:`\B13\Menus\DataProcessing\BreadcrumbsMenu`.
-
-    Refer to the `manual of the extension b13/menus
-    <https://github.com/b13/menus/blob/master/README.md>`__ for more
-    information.
-
-..  _MenuProcessor-options:
-
-Options
-=======
-
-..  _MenuProcessor-levels:
-
-levels
-------
-
-..  confval:: levels
-    :name: MenuProcessor-levels
-    :Required: true
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
-    :Default: 1
-    :Example: 5
-
-    Maximal number of levels to be included in the output array.
-
-
-..  _MenuProcessor-expandAll:
-
-expandAll
----------
-
-..  confval:: expandAll
-    :name: MenuProcessor-expandAll
-    :Required: true
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: 1
-    :Example: 0
-
-    Include all submenus (`1`) or only those of the active pages (`0`).
-
-
-..  _MenuProcessor-includeSpacer:
-
-includeSpacer
--------------
-
-..  confval:: includeSpacer
-    :name: MenuProcessor-includeSpacer
-    :Required: true
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 1
-
-    Include pages with type "spacer".
-
-
-..  _MenuProcessor-titleField:
-
-titleField
-----------
-
-..  confval:: titleField
-    :name: MenuProcessor-titleField
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: "nav_title // title"
-    :Example: "subtitle"
-
-    Fields to be used as title.
-
-
-..  _MenuProcessor-as:
-
-as
---
-
-..  confval:: as
-    :name: MenuProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: "menu"
-
-    Name for the variable in the Fluid template.
-
-..  hint::
-    Additionally, all :ref:`HMENU options <cobj-hmenu-options>` are available.
-
-..  _MenuProcessor-example-two-levels:
-
-Example: Two level menu of the web page
-=======================================
-
-Please see also :ref:`dataProcessing-about-examples`.
-
-
-TypoScript
-----------
-
-Using the :php:`MenuProcessor` the following scenario is possible:
-
-..  include:: /CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt
-
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`menu` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\MenuProcessor`.
-
-
-The Fluid template
-------------------
-
-This generated menu can be used in Fluid like this:
-
-..  include:: /CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt
-
-
-Output
-------
-
-The array now contains the menu items on level one. Each item in return has the
-menu items of level 2 in an array called :php:`children`.
-
-..  include:: /Images/AutomaticScreenshots/DataProcessing/MenuProcessor.rst.txt
diff --git a/Documentation/DataProcessing/MenuProcessor/Browse.rst b/Documentation/DataProcessing/MenuProcessor/Browse.rst
new file mode 100644
index 000000000..ab3d67fb3
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/Browse.rst
@@ -0,0 +1,122 @@
+:navigation-title: Browse
+..  include:: /Includes.rst.txt
+..  _hmenu-special-browse:
+..  _MenuProcessor-special-browse:
+
+===========================================
+Browse navigation - previous and next links
+===========================================
+
+This data processor provides pages which give your reader the possibility to
+browse to the previous page, to the next page, to a page with the
+table of contents and so on.
+
+..  tip::
+    In older TypoScript browser menus were created using the `HMENU` object.
+    This still works for backward compatibility reasons. We recommend to only use
+    data processors for newly created menus.
+
+    See :ref:`TYPO3 11, Browse navigation <t3tsref/:hmenu-special-browse>` for
+    examples how this was done.
+
+..  attention::
+    Mount pages are *not* supported!
+
+..  contents::
+    :local:
+
+..  _MenuProcessor-special-browse-properties:
+
+Properties
+==========
+
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
+
+    ..  confval:: special.value
+        :name: hmenu-browse-special-value
+        :type: integer /:ref:`stdWrap <stdwrap>`
+        :Default: current page ID
+
+        The default value can be overridden with a different page ID as starting
+        point for the menu in some rare use cases.
+
+    ..  confval:: special.items
+        :name: hmenu-browse-special-items
+        :type: list of item names separated by `|`
+        :Default: `index|up|next|prev`
+
+        A list, separated by pipes `|`, containing the following item types:
+
+        `next` / `prev`
+            Links to the next page / the previous page.
+            Next and previous pages are from the same "pid" as the current page id
+            (or "value") - that is the next item in a menu with the current page.
+            Also referred to as current level.
+
+            If :confval:`hmenu-browse-special-items-prevnextToSection` is set then
+            `next` / `prev` will link to the first
+            page of the next section / to the last page of the previous section,
+            too.
+
+        `nextsection` / `prevsection`
+            Links to the next section / the
+            previous section. A section is defined as the subpages of a page on
+            the same level as the parent (pid) page of the current page. Will not
+            work if the parent page of the current page is the root page of the
+            site.
+
+        `nextsection_last` / `prevsection_last`
+            Where `nextsection` / `prevsection` links to the first page in a section, these
+            link to the last page. If there is only one page in the section that
+            will be both first and last. Will not work if the parent page of the
+            current page is the root page of the site.
+
+        `first` / `last`
+            First / last page on the current level. If
+            there is only one page on the current level that page will be both
+            first and last.
+
+        `up`
+            Links to the parent (pid) page of the current page (up 1
+            level). Will always be available.
+
+        `index`
+            Links to the parent of the parent page of the current
+            page(up 2 levels). May not be available, if that page is out of the
+            root line.
+
+    ..  confval:: special.items.prevnextToSection
+        :name: hmenu-browse-special-items-prevnextToSection
+        :type: boolean
+        :Default: false
+
+        If set, the `prev` and `next` navigation will jump to the next section
+        when it reaches the end of pages in the current section. That way
+        `prev` and `next` will also link to the first page of the next section
+        / to the last page of the previous section.
+
+    ..  confval:: special.excludeNoSearchPages
+        :name: hmenu-browse-special-excludeNoSearchPages
+        :type: boolean
+        :Default: false
+
+        If set, pages marked with the `no search` checkbox will be excluded from the menu.
+
+..  _MenuProcessor-special-browse-example:
+
+Example: Display a browse navigation
+====================================
+
+The menu data processor with `special = browse` returns the found items as an
+array. The items in this array contain no information about what kind of item
+(previous, next, up, etc) they are. We therefore recommend to only use one
+item kind per data processor:
+
+..  literalinclude:: _code-snippets/_BrowseNavigation.typoscript
+    :caption: config/sites/mySite/setup.typoscript
+
+The result of each data processor can then be used, assuming that the result is
+the first item of the array saved into the database.
diff --git a/Documentation/ContentObjects/Hmenu/Categories.rst b/Documentation/DataProcessing/MenuProcessor/Categories.rst
similarity index 98%
rename from Documentation/ContentObjects/Hmenu/Categories.rst
rename to Documentation/DataProcessing/MenuProcessor/Categories.rst
index 0d4c03b9b..e80bceb5a 100644
--- a/Documentation/ContentObjects/Hmenu/Categories.rst
+++ b/Documentation/DataProcessing/MenuProcessor/Categories.rst
@@ -1,11 +1,12 @@
+:navigation-title: Categories
 ..  include:: /Includes.rst.txt
 
 ..  index:: HMENU; special = categories
 ..  _hmenu-special-categories:
 
-================
-Categories HMENU
-================
+==========
+Categories
+==========
 
 Makes a menu of pages belonging to one or more categories. If a page
 belongs to several of the selected categories, it will appear only once.
diff --git a/Documentation/ContentObjects/Hmenu/Directory.rst b/Documentation/DataProcessing/MenuProcessor/Directory.rst
similarity index 98%
rename from Documentation/ContentObjects/Hmenu/Directory.rst
rename to Documentation/DataProcessing/MenuProcessor/Directory.rst
index 72199c217..b28218068 100644
--- a/Documentation/ContentObjects/Hmenu/Directory.rst
+++ b/Documentation/DataProcessing/MenuProcessor/Directory.rst
@@ -1,3 +1,4 @@
+:navigation-title: Directory
 ..  include:: /Includes.rst.txt
 ..  index:: HMENU; special = directory
 ..  _hmenu-special-directory:
diff --git a/Documentation/DataProcessing/MenuProcessor/Index.rst b/Documentation/DataProcessing/MenuProcessor/Index.rst
new file mode 100644
index 000000000..9391951f0
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/Index.rst
@@ -0,0 +1,243 @@
+:navigation-title: menu
+..  include:: /Includes.rst.txt
+..  _MenuProcessor:
+
+=====================
+`menu` data processor
+=====================
+
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\MenuProcessor`,
+alias `menu`, utilizes :ref:`HMENU <cobj-hmenu>` to generate a list
+of menu items which can be assigned to :typoscript:`FLUIDTEMPLATE` as a
+variable.
+
+Additional data processing is supported and will be applied to each record.
+
+..  contents:: Table of contents
+
+..  hint::
+    The third party extension `b13/menus
+    <https://extensions.typo3.org/extension/menus>`__ also provides menu
+    processors like :php:`\B13\Menus\DataProcessing\TreeMenu` and
+    :php:`\B13\Menus\DataProcessing\BreadcrumbsMenu`.
+
+    Refer to the `manual of the extension b13/menus
+    <https://github.com/b13/menus/blob/master/README.md>`__ for more
+    information.
+
+..  _MenuProcessor-options:
+
+Options
+=======
+
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
+
+    ..  _MenuProcessor-as:
+
+    ..  confval:: as
+        :name: MenuProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: "menu"
+
+        Name for the variable in the Fluid template.
+
+    ..  confval:: alwaysActivePIDlist
+        :name: MenuProcessor-alwaysActivePIDlist
+        :type: list of :ref:`data-type-integer` /:ref:`stdWrap <stdwrap>`
+
+        This is a list of page UID numbers that will always be regarded as
+        active menu items and thereby automatically opened regardless of the
+        rootline.
+
+    ..  confval:: entryLevel
+        :name: MenuProcessor-entryLevel
+        :type: :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
+        :Default: 0
+
+        Defines at which level in the rootLine the menu should start.
+
+        Default is "0" which gives us a menu of the very first pages on the
+        site.
+
+        If the value is < 0, entryLevel is chosen from "behind" in the
+        rootLine. Thus "-1" is a menu with items from the outermost level,
+        "-2" is the level before the outermost...
+
+        **Note:** :typoscript:`entryLevel` does not show a menu **of a certain level of pages**
+        (use :typoscript:`special = directory` for that)
+        but it means that it will start to be visible **from that level on**.
+
+        So, for example if you build a simple "sitemap" menu like this one:
+
+        ..  literalinclude:: _code-snippets/_entryLevel.typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        it will start to be visible from the 4th level (and will contain only
+        the subpages from that level).
+
+    ..  confval:: excludeDoktypes
+        :name: MenuProcessor-excludeDoktypes
+        :type: list of :ref:`data-type-integer`
+        :Default: 6,254
+
+        Enter the list of page document types (doktype) to exclude from menus.
+        By default pages that are "backend user access only" (6) or "folder"
+        (254) are excluded.
+
+    ..  confval:: excludeUidList
+        :name: MenuProcessor-excludeUidList
+        :type: list of :ref:`data-type-integer` / :ref:`stdWrap <stdwrap>`
+
+        This is a list of page uids to exclude when the select statement is
+        done. Comma-separated. You may add "current" to the list to exclude
+        the current page.
+
+        **Example:**
+
+        The pages with these uid-numbers will **not** be within the menu!
+        Additionally the current page is always excluded too.
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+            page.10.dataProcessing.20.excludeUidList = 34,2,current
+
+    ..  _MenuProcessor-expandAll:
+
+    ..  confval:: expandAll
+        :name: MenuProcessor-expandAll
+        :Required: true
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: 1
+        :Example: 0
+
+        Include all submenus (`1`) or only those of the active pages (`0`).
+
+    ..  _MenuProcessor-levels:
+
+    ..  confval:: levels
+        :name: MenuProcessor-levels
+        :Required: true
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
+        :Default: 1
+        :Example: 5
+
+        Maximal number of levels to be included in the output array.
+
+    ..  confval:: includeNotInMenu
+        :name: MenuProcessor-includeNotInMenu
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap <stdwrap>`
+
+        If set, pages with the checkbox "Page enabled in menus" disabled will still be included
+        in menus.
+
+    ..  _MenuProcessor-includeSpacer:
+
+    ..  confval:: includeSpacer
+        :name: MenuProcessor-includeSpacer
+        :Required: true
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 1
+
+        Include pages with type "spacer".
+
+    ..  confval:: protectLvar
+        :name: MenuProcessor-protectlvar
+        :type: :ref:`data-type-boolean` / keyword
+
+        If set, then for each page in the menu it will be checked if an
+        Alternative Page Language record for the language defined in
+        the site exists for the
+        page. If that is not the case and the pages "Localization settings"
+        have the "Hide page if no translation for current language exists"
+        flag set, then the menu item will link to a non accessible page that
+        will yield an error page to the user. Setting this option will prevent
+        that situation by adding "&L=0" for such pages, meaning that
+        they will switch to the default language rather than keeping the
+        current language.
+
+        The check is only carried out if a translation is requested, not for the
+        standard language.
+
+        **Keyword: "all"**
+
+        When set to "all" the same check is carried out but it will not look
+        if "Hide page if no translation for current language exists" is set -
+        it always reverts to default language if no translation is found.
+
+    ..  confval:: special
+        :name: MenuProcessor-special
+        :type: *"directory" / "list" / "updated" / "rootline" / "browse" / "keywords"
+             / "categories"
+
+        Lets you define special types of menus.
+
+        For backward compatibility reason the special type `language` can be
+        used with an HMENU. We recommend to use the
+        `language-menu data processor <https://docs.typo3.org/permalink/t3tsref:languagemenuprocessor>`_
+        to create language menus.
+
+        See the section about the :ref:`.special property <MenuProcessor-special>`.
+
+        ..  confval:: value
+            :name: MenuProcessor-special-value
+            :type: *list of page-uid's* / :ref:`stdWrap <stdwrap>`
+
+            List of page uid's to use for the special menu. What they are used
+            for depends on the menu type as defined by ".special"; see the
+            section about the :ref:`.special property <MenuProcessor-special>`.
+
+    ..  _MenuProcessor-titleField:
+
+    ..  confval:: titleField
+        :name: MenuProcessor-titleField
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: "nav_title // title"
+        :Example: "subtitle"
+
+        Fields to be used as title.
+
+..  _MenuProcessor-special:
+
+Special menu types
+==================
+
+The following special menu types are available:
+
+..  toctree::
+    :glob:
+    :titlesonly:
+
+    *
+
+..  _MenuProcessor-example-two-levels:
+
+Example: Two level menu of the web page
+=======================================
+
+Please see also :ref:`dataProcessing-about-examples`.
+
+..  rubric:: TypoScript
+
+Using the :php:`MenuProcessor` the following scenario is possible:
+
+..  include:: /CodeSnippets/DataProcessing/TypoScript/MenuProcessor.rst.txt
+
+..  rubric:: The Fluid template
+
+This generated menu can be used in Fluid like this:
+
+..  include:: /CodeSnippets/DataProcessing/Template/DataProcMenu.rst.txt
+
+..  rubric:: Output
+
+The array now contains the menu items on level one. Each item in return has the
+menu items of level 2 in an array called :php:`children`.
+
+..  include:: /Images/AutomaticScreenshots/DataProcessing/MenuProcessor.rst.txt
diff --git a/Documentation/ContentObjects/Hmenu/Keywords.rst b/Documentation/DataProcessing/MenuProcessor/Keywords.rst
similarity index 99%
rename from Documentation/ContentObjects/Hmenu/Keywords.rst
rename to Documentation/DataProcessing/MenuProcessor/Keywords.rst
index bbcc89fbf..b06ec563a 100644
--- a/Documentation/ContentObjects/Hmenu/Keywords.rst
+++ b/Documentation/DataProcessing/MenuProcessor/Keywords.rst
@@ -1,3 +1,4 @@
+:navigation-title: Keywords
 ..  include:: /Includes.rst.txt
 ..  index:: HMENU; special = keywords
 ..  _hmenu-special-keywords:
diff --git a/Documentation/DataProcessing/MenuProcessor/Language.rst b/Documentation/DataProcessing/MenuProcessor/Language.rst
new file mode 100644
index 000000000..0e7de4a78
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/Language.rst
@@ -0,0 +1,18 @@
+:navigation-title: Language
+..  include:: /Includes.rst.txt
+..  index:: HMENU; special = categories
+..  _hmenu-special-language:
+
+==========================================================
+Pure TypoScript language menu (For backward compatibility)
+==========================================================
+
+..  attention::
+    It is still possible to create a menu with :typoscript:`special = userfunction`
+    for backward compatibility reasons to be used with HMENU.
+
+    The :ref:`LanguageMenuProcessor <LanguageMenuProcessor>` can be used to
+    create a language menu styled by Fluid.
+
+See :ref:`TYPO3 11.5 - Language menu <t3tsref/11.5:hmenu-special-language>` for examples
+how to use the language menu with the HMENU.
diff --git a/Documentation/ContentObjects/Hmenu/List.rst b/Documentation/DataProcessing/MenuProcessor/List.rst
similarity index 98%
rename from Documentation/ContentObjects/Hmenu/List.rst
rename to Documentation/DataProcessing/MenuProcessor/List.rst
index 69ae4c7d6..f168a9b59 100644
--- a/Documentation/ContentObjects/Hmenu/List.rst
+++ b/Documentation/DataProcessing/MenuProcessor/List.rst
@@ -1,3 +1,4 @@
+:navigation-title: List
 ..  include:: /Includes.rst.txt
 ..  index:: HMENU; special = list
 ..  _hmenu-special-list:
diff --git a/Documentation/ContentObjects/Hmenu/Rootline.rst b/Documentation/DataProcessing/MenuProcessor/Rootline.rst
similarity index 90%
rename from Documentation/ContentObjects/Hmenu/Rootline.rst
rename to Documentation/DataProcessing/MenuProcessor/Rootline.rst
index c684894e6..7986d37d7 100644
--- a/Documentation/ContentObjects/Hmenu/Rootline.rst
+++ b/Documentation/DataProcessing/MenuProcessor/Rootline.rst
@@ -1,3 +1,4 @@
+:navigation-title: Rootline / Breadcrumb
 ..  include:: /Includes.rst.txt
 ..  index:: HMENU; special = rootline
 ..  _hmenu-special-rootline:
@@ -84,7 +85,8 @@ Breadcrumb styled with Fluid
 The following breadcrumb menu is created with the
 :ref:`MenuProcessor <MenuProcessor>`, based on the HMENU. It is styled via Fluid:
 
-..  include:: /CodeSnippets/Menu/TypoScript/BreadcrumbDataProcessor.rst.txt
+..  literalinclude:: _code-snippets/_BreadcrumbDataProcessor.typoscript
+    :caption: EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbDataProcessor.typoscript
 
 The following Fluid partial can be used to style the breadcrumb menu:
 
@@ -97,7 +99,8 @@ Breadcrumb with pure TypoScript
 
 The following breadcrumb menu is styled with pure Typoscript:
 
-..  include:: /CodeSnippets/Menu/TypoScript/BreadcrumbLib.rst.txt
+..  literalinclude:: _code-snippets/_BreadcrumbLib.typoscript
+    :caption: EXT:site_package/Configuration/TypoScript/Menus/Setup/BreadcrumbLib.typoscript
 
 ..  _hmenu-special-rootline-range-example:
 
diff --git a/Documentation/ContentObjects/Hmenu/Updated.rst b/Documentation/DataProcessing/MenuProcessor/Updated.rst
similarity index 99%
rename from Documentation/ContentObjects/Hmenu/Updated.rst
rename to Documentation/DataProcessing/MenuProcessor/Updated.rst
index 1a2bfbaef..0b6670e56 100644
--- a/Documentation/ContentObjects/Hmenu/Updated.rst
+++ b/Documentation/DataProcessing/MenuProcessor/Updated.rst
@@ -1,3 +1,4 @@
+:navigation-title: Updated
 ..  include:: /Includes.rst.txt
 ..  index:: HMENU; special = updated
 ..  _hmenu-special-updated:
diff --git a/Documentation/DataProcessing/MenuProcessor/Userfunction.rst b/Documentation/DataProcessing/MenuProcessor/Userfunction.rst
new file mode 100644
index 000000000..b61d87542
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/Userfunction.rst
@@ -0,0 +1,19 @@
+:navigation-title: Userfunction
+..  include:: /Includes.rst.txt
+..  index:: HMENU; special = userfunction
+..  _hmenu-special-userfunction:
+..  _hmenu-special-userfunction-examples:
+
+============================================
+Userfunction menu (For backward compability)
+============================================
+
+..  attention::
+    It is still possible to create a menu with :typoscript:`special = userfunction`
+    for backward compatibility reasons.
+
+    However we would advise you to write a :ref:`customized MenuProcessor <CustomDataProcessors>`
+    and style the output with Fluid instead.
+
+See :ref:`TYPO3 11.5 -Userfunction menu <t3tsref/11.5:hmenu-special-userfunction>`
+for examples how to use the language menu with the HMENU.
diff --git a/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbDataProcessor.typoscript b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbDataProcessor.typoscript
new file mode 100644
index 000000000..2ddab6649
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbDataProcessor.typoscript
@@ -0,0 +1,14 @@
+page {
+  10 = FLUIDTEMPLATE
+  10 {
+    dataProcessing {
+      1657927210 = menu
+      1657927210 {
+        special = rootline
+        special.range = 0|-1
+        includeNotInMenu = 0
+        as = breadcrumb
+      }
+    }
+  }
+}
diff --git a/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbLib.typoscript b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbLib.typoscript
new file mode 100644
index 000000000..3ab1e26d9
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BreadcrumbLib.typoscript
@@ -0,0 +1,18 @@
+// include this breadcrumb menu in your Fluid template:
+// <f:cObject typoscriptObjectPath="lib.breadcrumb" />
+
+lib.breadcrumb = HMENU
+lib.breadcrumb {
+  wrap = <ul class="breadcrumb">|</ul>
+  special = rootline
+  special.range = 1|-1
+  // render the menu
+  1 = TMENU
+  1 {
+    NO.wrapItemAndSub = <li>|</li>
+    // render the current page without link and with additional classs
+    CUR = 1
+    CUR.doNotLinkIt = 1
+    CUR.wrapItemAndSub = <li class="active">|</li>
+  }
+}
diff --git a/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.html b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.html
new file mode 100644
index 000000000..21371b181
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.html
@@ -0,0 +1,9 @@
+<f:if condition="{prevNavigation.0}">
+    <a href="{prevNavigation.0.link}">&lt;- {prevNavigation.0.title}</a>
+</f:if>
+<f:if condition="{nextNavigation.0}">
+    <a href="{nextNavigation.0.link}">{nextNavigation.0.title} -&gt;</a>
+</f:if>
+<f:if condition="{upNavigation.0}">
+    <a href="{upNavigation.0.link}">{upNavigation.0.title}</a>
+</f:if>
diff --git a/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.typoscript b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.typoscript
new file mode 100644
index 000000000..1311fd100
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_BrowseNavigation.typoscript
@@ -0,0 +1,34 @@
+page = PAGE
+page {
+    10 = PAGEVIEW
+    10 {
+        dataProcessing {
+            50 = menu
+            50 {
+                special = browse
+                as = prevNavigation
+                special {
+                    items = prev
+                    items.prevnextToSection = 1
+                }
+            }
+            60 = menu
+            60 {
+                special = browse
+                as = nextNavigation
+                special {
+                    items = next
+                    items.prevnextToSection = 1
+                }
+            }
+            70 = menu
+            70 {
+                special = browse
+                as = upNavigation
+                special {
+                    items = up
+                }
+            }
+        }
+    }
+}
diff --git a/Documentation/DataProcessing/MenuProcessor/_code-snippets/_entryLevel.typoscript b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_entryLevel.typoscript
new file mode 100644
index 000000000..389273d07
--- /dev/null
+++ b/Documentation/DataProcessing/MenuProcessor/_code-snippets/_entryLevel.typoscript
@@ -0,0 +1,14 @@
+page.10 {
+  dataProcessing {
+    10 = menu
+    10 {
+      special = list
+      special.value.field = pages
+      levels = 7
+      entryLevel = 4
+      as = menu
+      expandAll = 1
+      titleField = nav_title // title
+    }
+  }
+}
diff --git a/Documentation/DataProcessing/PageContentFetchingProcessor.rst b/Documentation/DataProcessing/PageContentFetchingProcessor.rst
index a53986017..d831e3319 100644
--- a/Documentation/DataProcessing/PageContentFetchingProcessor.rst
+++ b/Documentation/DataProcessing/PageContentFetchingProcessor.rst
@@ -1,37 +1,51 @@
+:navigation-title: page-content
 ..  include:: /Includes.rst.txt
 ..  _PageContentFetchingProcessor:
 
-============================
-PageContentFetchingProcessor
-============================
+=============================
+`page-content` data processor
+=============================
 
-This Data Processor loads all :sql:`tt_content` records from the current
+..  versionadded:: 13.2
+
+This data processor :php:`\TYPO3\CMS\Frontend\DataProcessing\PageContentFetchingProcessor`,
+alias `page-content`, loads all :sql:`tt_content` records from the current
 :ref:`backend layout <t3coreapi:be-layout>` into
 the template with a given identifier for each :sql:`colPos`, also respecting slideMode or
 collect options based on the page layouts content columns.
 
+An array of :ref:`Record objects <t3coreapi:record_objects>` will be passed to
+the Fluid template. You can use the
+:ref:`CObject ViewHelper <f:cObject> <t3viewhelper:typo3-fluid-cobject>` to
+display the content elements.
+
+..  contents:: Table of contents
+
 ..  _PageContentFetchingProcessor-options:
 
 Options
 =======
 
 ..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-..  confval:: as
-    :name: PageContentFetchingProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: "content"
+    ..  confval:: as
+        :name: PageContentFetchingProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: "content"
 
-    Name for the variable in the Fluid template.
+        Name for the variable in the Fluid template.
 
-..  confval:: if
-    :name: PageContentFetchingProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
+    ..  confval:: if
+        :name: PageContentFetchingProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
-    Only if the condition is met the data processor is executed.
+        Only if the condition is met the data processor is executed.
 
 ..  _PageContentFetchingProcessor-example:
 
@@ -46,9 +60,34 @@ Use the identifiers of the columns in the Fluid template:
 ..  literalinclude:: _PageContentFetchingProcessor/_Default.html
     :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
 
-..  todo: Use new viewhelper once https://review.typo3.org/c/Packages/TYPO3.CMS/+/83718/2 is merged
+You can use the :ref:`CObject ViewHelper <f:cObject> <t3viewhelper:typo3-fluid-cobject>`
+to render the content element using :composer:`typo3/cms-fluid-styled-content`
+or render it your self.
+
+`{contentElement.mainType}`
+    Is always "tt_content" for content elements.
+`{contentElement.fullType}`
+    Is composed of "tt_content.[CType]". For a content element of type text it
+    contains "tt_content.text".
 
 The :ref:`backend layout <t3coreapi:be-layout>` is defined like this:
 
 ..  literalinclude:: _PageContentFetchingProcessor/_BackendLayout.tsconfig
     :caption: config/sites/my-site/page.tsconfig
+
+..  _PageContentFetchingProcessor-AfterContentHasBeenFetchedEvent:
+
+Modify the result via AfterContentHasBeenFetchedEvent
+=====================================================
+
+..  versionadded:: 13.4.2 | 14.0
+    The event `AfterContentHasBeenFetchedEvent <https://docs.typo3.org/permalink/t3coreapi:aftercontenthasbeenfetchedevent>`_
+    has been introduced to adjust the page content fetched by the `page-content`
+    data processor.
+
+The event `AfterContentHasBeenFetchedEvent <https://docs.typo3.org/permalink/t3coreapi:aftercontenthasbeenfetchedevent>`_
+can be used to modify the content elements fetched by the `page-content`
+data processor.
+
+See the following example:
+`Filter content elements provided by the page-content data processor <https://docs.typo3.org/permalink/t3coreapi:aftercontenthasbeenfetchedevent-example>`_.
diff --git a/Documentation/DataProcessing/RecordTransformationProcessor.rst b/Documentation/DataProcessing/RecordTransformationProcessor.rst
index 1fd7790d6..2dee82c74 100644
--- a/Documentation/DataProcessing/RecordTransformationProcessor.rst
+++ b/Documentation/DataProcessing/RecordTransformationProcessor.rst
@@ -1,15 +1,17 @@
+:navigation-title: record-transformation
 ..  include:: /Includes.rst.txt
 ..  _RecordTransformationProcessor:
 
-=============================
-RecordTransformationProcessor
-=============================
+======================================
+`record-transformation` data processor
+======================================
 
 ..  versionadded:: 13.2
     A new TypoScript data processor for :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>` and
     :typoscript:`PAGEVIEW` has been added.
 
-The :typoscript:`record-transformation` Data Processor can typically be used in
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\RecordTransformationProcessor`,
+alias `record-transformation`, can typically be used in
 conjunction with the DatabaseQuery Data Processor. The DatabaseQuery Data
 Processor typically fetches records from the database, and the
 :typoscript:`record-transformation` will take the result, and transforms
@@ -26,12 +28,6 @@ addressed in a unified way.
 The `type` property contains the database table name and the actual type based
 on the record, such `tt_content.textmedia` for Content Elements.
 
-..  note::
-
-    The Record object is available but details are still to be finalized in
-    the API until TYPO3 v13 LTS. Right now only the usage in Fluid is public
-    API.
-
 ..  _RecordTransformationProcessor-databasequeryprocessor-example:
 
 Example: Usage with the DatabaseQueryProcessor
@@ -68,9 +64,9 @@ is most of all a better organized overview of all available information. E.g.
 the property `properties` lists all relevant fields for the current Content
 Type.
 
-We are dealing with an object here, which behaves like an array. In short: you
-can access your record properties as you are used to with :html:`{record.title}`
-or :html:`{record.uid}`. In addition, you gain special, context-aware properties
+We are dealing with an object here. You however can access your record
+properties as you are used to with :html:`{record.title}` or
+:html:`{record.uid}`. In addition, you gain special, context-aware properties
 like the language :html:`{record.languageId}` or workspace
 :html:`{data.versionInfo.workspaceId}`.
 
@@ -79,42 +75,49 @@ Overview of all possibilities:
 ..  literalinclude:: _RecordTransformationProcessor/_FluidUsage.html
     :caption: Demonstration of available variables in Fluid
 
+..  contents:: Table of contents
+
 ..  _RecordTransformationProcessor-options:
 
 Options:
 ========
 
-..  confval:: as
-    :name: RecordTransformationProcessor-as
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: 'record' or 'records'
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
+
+    ..  confval:: as
+        :name: RecordTransformationProcessor-as
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: 'record' or 'records'
 
-    The target variable containing the resolved record objects.
-    If empty, 'record' or 'records' (if multiple records are given) is used.
+        The target variable containing the resolved record objects.
+        If empty, 'record' or 'records' (if multiple records are given) is used.
 
-..  confval:: if
-    :name: RecordTransformationProcessor-if
-    :type: :ref:`if` condition
-    :Default: ''
+    ..  confval:: if
+        :name: RecordTransformationProcessor-if
+        :type: :ref:`if` condition
+        :Default: ''
 
-    Only if the condition is met the Data Processor is executed.
+        Only if the condition is met the Data Processor is executed.
 
-..  confval:: table
-    :name: RecordTransformationProcessor-table
-    :type: :ref:`data-type-string`
-    :Default: auto-resolved
+    ..  confval:: table
+        :name: RecordTransformationProcessor-table
+        :type: :ref:`data-type-string`
+        :Default: auto-resolved
 
-    The name of the database table of the records. Leave empty to auto-resolve
-    the table from context.
+        The name of the database table of the records. Leave empty to auto-resolve
+        the table from context.
 
-    If you are dealing with a custom data source you can adjust it here.
+        If you are dealing with a custom data source you can adjust it here.
 
-..  confval:: variableName
-    :name: RecordTransformationProcessor-variableName
-    :type: :ref:`data-type-string`
-    :Default: 'data'
+    ..  confval:: variableName
+        :name: RecordTransformationProcessor-variableName
+        :type: :ref:`data-type-string`
+        :Default: 'data'
 
-    The variable that contains the record(s) from a previous Data Processor,
-    or from a :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>` view.
+        The variable that contains the record(s) from a previous Data Processor,
+        or from a :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>` view.
 
-    If you are dealing with a custom data source you can adjust it here.
+        If you are dealing with a custom data source you can adjust it here.
diff --git a/Documentation/DataProcessing/SiteLanguageProcessor.rst b/Documentation/DataProcessing/SiteLanguageProcessor.rst
index a7db07c03..9c2c4e170 100644
--- a/Documentation/DataProcessing/SiteLanguageProcessor.rst
+++ b/Documentation/DataProcessing/SiteLanguageProcessor.rst
@@ -1,13 +1,13 @@
+:navigation-title: site-language
 ..  include:: /Includes.rst.txt
 ..  _SiteLanguageProcessor:
 
-=====================
-SiteLanguageProcessor
-=====================
+==============================
+`site-language` data processor
+==============================
 
-..  versionadded:: 12.0
-
-The :php:`SiteLanguageProcessor` fetches language-related data from the
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteLanguageProcessor`,
+alias `site-language`, fetches language-related data from the
 :ref:`site configuration<t3coreapi:sitehandling>`.
 
 ..  _SiteLanguageProcessor-options:
@@ -15,18 +15,20 @@ The :php:`SiteLanguageProcessor` fetches language-related data from the
 Options
 =======
 
-..  _SiteLanguageProcessor-as:
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-as
---
+    ..  _SiteLanguageProcessor-as:
 
-..  confval:: as
-    :name: SiteLanguageProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: "site"
+    ..  confval:: as
+        :name: SiteLanguageProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: "site"
 
-    The variable name to be used in the Fluid template.
+        The variable name to be used in the Fluid template.
 
 ..  _SiteLanguageProcessor-example:
 
@@ -35,31 +37,20 @@ Example: Output some data from the site language configuration
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 Using the :php:`SiteLanguageProcessor` the following scenario is possible:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/SiteLanguageProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`site-language` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteLanguageProcessor`.
-
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 In the Fluid template the properties of the site language configuration can
 be accessed:
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcSiteLanguage.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 The array now contains the information from the site language configuration:
 
diff --git a/Documentation/DataProcessing/SiteProcessor.rst b/Documentation/DataProcessing/SiteProcessor.rst
index f5e4c48ea..1728a082a 100644
--- a/Documentation/DataProcessing/SiteProcessor.rst
+++ b/Documentation/DataProcessing/SiteProcessor.rst
@@ -1,31 +1,36 @@
+:navigation-title: site
 ..  include:: /Includes.rst.txt
 ..  _SiteProcessor:
 
-=============
-SiteProcessor
-=============
+=====================
+`site` data processor
+=====================
 
-The :php:`SiteProcessor` fetches data from the :ref:`site configuration
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteProcessor`,
+alias `site`, fetches data from the :ref:`site configuration
 <t3coreapi:sitehandling>`.
 
+..  contents:: Table of contents
 
 ..  _SiteProcessor-options:
 
 Options
 =======
 
-..  _SiteProcessor-as:
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-as
---
+    ..  _SiteProcessor-as:
 
-..  confval:: as
-    :name: SiteProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: "site"
+    ..  confval:: as
+        :name: SiteProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: "site"
 
-    The variable name to be used in the Fluid template.
+        The variable name to be used in the Fluid template.
 
 ..  _SiteProcessor-examples:
 
@@ -34,30 +39,19 @@ Example: Output some data from the site configuration
 
 Please see also :ref:`dataProcessing-about-examples`.
 
-
-TypoScript
-----------
+..  rubric:: TypoScript
 
 Using the :php:`SiteProcessor` the following scenario is possible:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/SiteProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`site` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SiteProcessor`.
-
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 In the Fluid template the properties of the site configuration can be accessed:
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcSite.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 The array now contains the information from the site configuration:
 
diff --git a/Documentation/DataProcessing/SplitProcessor.rst b/Documentation/DataProcessing/SplitProcessor.rst
index ba760c560..58b4095e9 100644
--- a/Documentation/DataProcessing/SplitProcessor.rst
+++ b/Documentation/DataProcessing/SplitProcessor.rst
@@ -1,119 +1,101 @@
+:navigation-title: split
 ..  include:: /Includes.rst.txt
 ..  _splitProcessor:
 
-==============
-SplitProcessor
-==============
+======================
+`split` data processor
+======================
 
-The :php:`SplitProcessor` allows to split values separated with a delimiter
+The :php:`\TYPO3\CMS\Frontend\DataProcessing\SplitProcessor`,
+alias `split`, allows to split values separated with a delimiter
 from a single database field. The result is an array that can be iterated over.
 Whitespaces are automatically trimmed.
 
+..  contents:: Table of contents
+
 ..  _splitProcessor-options:
 
 Options
 =======
 
-..  _splitProcessor-if:
-
-if
---
-
-..  confval:: if
-    :name: splitProcessor-if
-    :Required: false
-    :type: :ref:`if` condition
-    :Default: ''
-
-    Only if the condition is met the data processor is executed.
-
-
-..  _splitProcessor-fieldName:
-
-fieldName
----------
-
-..  confval:: fieldName
-    :name: splitProcessor-fieldName
-    :Required: true
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: ''
+..  confval-menu::
+    :display: table
+    :type:
+    :Default:
 
-    Name of the field to be used.
+    ..  _splitProcessor-if:
 
+    ..  confval:: if
+        :name: splitProcessor-if
+        :Required: false
+        :type: :ref:`if` condition
+        :Default: ''
 
-..  _splitProcessor-as:
+        Only if the condition is met the data processor is executed.
 
-as
---
+    ..  _splitProcessor-fieldName:
 
-..  confval:: as
-    :name: splitProcessor-as
-    :Required: false
-    :type: :ref:`data-type-string`
-    :Default: defaults to the fieldName
+    ..  confval:: fieldName
+        :name: splitProcessor-fieldName
+        :Required: true
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: ''
 
-    The variable name to be used in the Fluid template.
+        Name of the field to be used.
 
+    ..  _splitProcessor-as:
 
-..  _splitProcessor-delimiter:
+    ..  confval:: as
+        :name: splitProcessor-as
+        :Required: false
+        :type: :ref:`data-type-string`
+        :Default: defaults to the fieldName
 
-delimiter
----------
+        The variable name to be used in the Fluid template.
 
-..  confval:: delimiter
-    :name: splitProcessor-delimiter
-    :Required: false
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-    :Default: Line Feed
-    :Example: ","
+    ..  _splitProcessor-delimiter:
 
-    The field delimiter, a character separating the values.
+    ..  confval:: delimiter
+        :name: splitProcessor-delimiter
+        :Required: false
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :Default: Line Feed
+        :Example: ","
 
+        The field delimiter, a character separating the values.
 
-..  _splitProcessor-filterIntegers:
+    ..  _splitProcessor-filterIntegers:
 
-filterIntegers
---------------
+    ..  confval:: filterIntegers
+        :name: splitProcessor-filterIntegers
+        :Required: false
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 1
 
-..  confval:: filterIntegers
-    :name: splitProcessor-filterIntegers
-    :Required: false
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 1
+        If set to `1`, all values are being cast to int.
 
-    If set to `1`, all values are being cast to int.
+    ..  _splitProcessor-filterUnique:
 
+    ..  confval:: filterUnique
+        :name: splitProcessor-filterUnique
+        :Required: false
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 1
 
-..  _splitProcessor-filterUnique:
+        If set to `1`, all duplicates will be removed.
 
-filterUnique
-------------
+    ..  _splitProcessor-removeEmptyEntries:
 
-..  confval:: filterUnique
-    :name: splitProcessor-filterUnique
-    :Required: false
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 1
+    ..  confval:: removeEmptyEntries
+        :name: splitProcessor-removeEmptyEntries
+        :Required: false
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: 0
+        :Example: 1
 
-    If set to `1`, all duplicates will be removed.
-
-
-..  _splitProcessor-removeEmptyEntries:
-
-removeEmptyEntries
-------------------
-
-..  confval:: removeEmptyEntries
-    :name: splitProcessor-removeEmptyEntries
-    :Required: false
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: 0
-    :Example: 1
-
-    If set to `1`, all empty values will be removed.
+        If set to `1`, all empty values will be removed.
 
 ..  _splitProcessor-example-split-url:
 
@@ -123,29 +105,20 @@ Example: Splitting a URL
 Please see also :ref:`dataProcessing-about-examples`.
 
 
-TypoScript
-----------
+..  rubric:: TypoScript
 
 With the help of the :php:`SplitProcessor` the following scenario is
 possible:
 
 ..  include:: /CodeSnippets/DataProcessing/TypoScript/SplitProcessor.rst.txt
 
-..  versionadded:: 12.1
-    One can use the alias :typoscript:`split` instead
-    of the fully-qualified class name
-    :php:`\TYPO3\CMS\Frontend\DataProcessing\SplitProcessor`.
-
-The Fluid template
-------------------
+..  rubric:: The Fluid template
 
 In the Fluid template then iterate over the split data:
 
 ..  include:: /CodeSnippets/DataProcessing/Template/DataProcSplit.rst.txt
 
-
-Output
-------
+..  rubric:: Output
 
 The array now contains the split strings:
 
diff --git a/Documentation/DataProcessing/_PageContentFetchingProcessor/_BackendLayout.tsconfig b/Documentation/DataProcessing/_PageContentFetchingProcessor/_BackendLayout.tsconfig
index 2891fd19f..29a7f5fd6 100644
--- a/Documentation/DataProcessing/_PageContentFetchingProcessor/_BackendLayout.tsconfig
+++ b/Documentation/DataProcessing/_PageContentFetchingProcessor/_BackendLayout.tsconfig
@@ -18,7 +18,7 @@ mod.web_layout.BackendLayouts {
                         }
                     }
 
-                    1 {
+                    2 {
                         columns {
                             1 {
                                 name = Left
@@ -38,4 +38,4 @@ mod.web_layout.BackendLayouts {
             }
         }
     }
-}
\ No newline at end of file
+}
diff --git a/Documentation/DataProcessing/_PageContentFetchingProcessor/_Default.html b/Documentation/DataProcessing/_PageContentFetchingProcessor/_Default.html
index 6b8c2d636..44cac1c7c 100644
--- a/Documentation/DataProcessing/_PageContentFetchingProcessor/_Default.html
+++ b/Documentation/DataProcessing/_PageContentFetchingProcessor/_Default.html
@@ -1,10 +1,22 @@
-<f:render partial="Jumbotron" arguments="{jumbotronContent: myContent.jumbotron}"/>
 <main>
+    <f:for each="{myContent.jumbotron.records}" as="contentElement">
+        <f:if condition="{contentElement.fullType} = 'tt_content.my_extension_jumbotron'">
+            <h2>{contentElement.header}</h2>
+            <f:format.html>{contentElement.bodytext}</f:format.html>
+        </f:if>
+    </f:for>
     <f:for each="{myContent.left.records}" as="contentElement">
-        <h3>{contentElement.header}</h3>
-        <p>{contentElement.bodytext -> f:format.html()}</p>
+        <f:cObject
+            typoscriptObjectPath="{contentElement.mainType}"
+            table="{contentElement.mainType}"
+            data="{contentElement}"
+        />
     </f:for>
 </main>
 <aside>
-    <f:render partial="Aside" arguments="{content: myContent.right}"/>
+    <f:for each="{myContent.right.records}" as="contentElement">
+        <f:if condition="{contentElement.fullType} = 'tt_content.header'">
+            <h2>{contentElement.header}</h2>
+        </f:if>
+    </f:for>
 </aside>
diff --git a/Documentation/DataTypes/Index.rst b/Documentation/DataTypes/Index.rst
deleted file mode 100644
index a2cd613e7..000000000
--- a/Documentation/DataTypes/Index.rst
+++ /dev/null
@@ -1,565 +0,0 @@
-..  include:: /Includes.rst.txt
-..  index:: Simple data types
-..  _data-types:
-..  _data-types-reference:
-
-=================
-Simple data types
-=================
-
-The values assigned to properties in TypoScript are often of a
-specific format. These formats are described in this chapter.
-
-For example, if a value is defined as the type :typoscript:`<tag>`, HTML code has to be
-supplied. If it is of the type :typoscript:`resource`, it's a reference to a file from
-the resource-field in the template. If the type is :typoscript:`GraphicColor`, a
-color-definition is expected and an HTML color code or comma-separated
-RGB-values have to be provided.
-
-The following is a list of available data types, their usage, purpose and
-examples.
-
-..  contents::
-    :local:
-
-..  index:: Simple data types; align
-..  _data-type-align:
-
-align
-=====
-
-..  confval:: align
-    :name: data-type-align
-    :Default: :typoscript:`left`
-    :Allowed values: :typoscript:`left`, :typoscript:`center`, :typoscript:`right`
-
-    Decides about alignment.
-
-
-..  index:: Simple data types; boolean
-..  _data-type-boolean:
-
-boolean
-=======
-
-..  confval:: boolean
-    :name: data-type-boolean
-
-    Possible values for boolean variables are `1` and `0`
-    meaning TRUE and FALSE.
-
-    Everything else is `evaluated to one of these values by PHP`__:
-    Non-empty strings (except `0` [zero]) are treated as TRUE,
-    empty strings are evaluated to FALSE.
-
-    __ https://www.php.net/manual/en/language.types.boolean.php
-
-    ..  rubric:: Examples
-
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-       dummy.enable = 0   # false, preferred notation
-       dummy.enable = 1   # true,  preferred notation
-       dummy.enable =     # false, because the value is empty
-
-
-..  index:: Simple data types; case
-..  _data-type-case:
-
-case
-====
-
-..  confval:: case
-    :name: data-type-case
-
-    Do a case conversion.
-
-    ..  rubric:: Possible values:
-
-    ============================= ==========================================================
-    Value                         Effect
-    ============================= ==========================================================
-    :typoscript:`upper`           Convert all letters of the string to upper case
-    :typoscript:`lower`           Convert all letters of the string to lower case
-    :typoscript:`capitalize`      Uppercase the first character of each word in the string
-    :typoscript:`ucfirst`         Convert the first letter of the string to upper case
-    :typoscript:`lcfirst`         Convert the first letter of the string to lower case
-    :typoscript:`uppercamelcase`  Convert underscored `upper_camel_case` to `UpperCamelCase`
-    :typoscript:`lowercamelcase`  Convert underscored `lower_camel_case` to `lowerCamelCase`
-    ============================= ==========================================================
-
-    ..  rubric:: Example
-
-    Code:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        10 = TEXT
-        10.value = Hello world!
-        10.case = upper
-
-    Result:
-
-    ..  code-block:: text
-        :caption: Example Output
-
-        HELLO WORLD!
-
-
-..  index:: Simple data types; date-conf
-..  _data-type-date-conf:
-
-date-conf
-=========
-
-..  confval:: date-conf
-    :name: data-type-date-conf
-
-    Used to format a date, see PHP function :php:`date()`. See the
-    documentation of `allowed date time formats in
-    PHP <https://www.php.net/manual/en/datetime.format.php>`__.
-
-    ..  rubric:: Example
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.date-conf = d-m-y
-
-
-..  index:: Simple data types; degree
-..  _data-type-degree:
-
-degree
-======
-
-..  confval:: degree
-    :name: data-type-degree
-
-    `-90` to `90`, integers
-
-    Example: `45`
-
-
-..  index:: Simple data types; dir
-..  _data-type-dir:
-
-dir
-===
-
-..  confval:: dir
-    :name: data-type-dir
-
-    ..  rubric:: Syntax
-
-    [path relative to the web root of the site] \| [list of valid
-    extensions] \| [sorting: name, size, ext, date] \| [reverse: "r"] \|
-    [return full path: boolean]
-
-
-    Files matching are returned in a comma-separated string.
-
-    ..  rubric:: Example
-
-    This example returns a list of all pdf, gif and jpg-files from
-    :file:`fileadmin/files/` sorted by their name reversely and with the full path (with
-    :file:`fileadmin/files/` prepended):
-
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.dir = fileadmin/files/ | pdf,gif,jpg | name | r | true
-
-
-..  index:: Simple data types; function name
-..  _data-type-function-name:
-
-function name
-=============
-
-..  confval:: function name
-    :name: data-type-function-name
-
-    Indicates a function or method in a class to call. See more information at
-    the :ref:`USER cObject <cobj-user>`.
-
-    If no namespaces are used, then the class or function name, but not the method
-    name, should probably be prefixed with :php:`user_`. The prefix can be
-    changed in the :php:`$GLOBALS['TYPO3_CONF_VARS']` config though. The function
-    / method is normally called with 2 parameters, :php:`$conf` which is the
-    TypoScript configuration and :php:`$content`, some content to be processed and
-    returned.
-
-    ..  todo: Which entry in TYPO3_CONF_VARS enables the user-prefix to be changed? This
-        should be mentioned. Looks like this entry has gone and this info no
-        longer valid.
-
-    If no namespaces are used and if a method in a class is called, it is checked (when using the
-    :typoscript:`USER`/:typoscript:`USER_INT` objects) whether a class with the same name, but
-    prefixed with :php:`ux_` is present and if so, *this* class is instantiated
-    instead. See the document "Inside TYPO3" for more information on extending
-    classes in TYPO3!
-
-    ..  todo: Where is this feature mentioned? We should add a reference here.
-
-    ..  rubric:: Examples
-
-    Method in namespaced class. This is the preferred version:
-
-    ..  code-block:: typoscript
-
-        lib.someThing = USER_INT
-        lib.someThing.userFunc = MyVendor\MyExtension\SomeNamespace\SomeClass->someFunction
-
-    ..  literalinclude:: _FunctionName.php
-        :language: php
-        :caption: EXT:my_extension/Classes/SomeNamespace/SomeClass.php
-
-    Single Function:
-
-    ..  code-block:: text
-
-        user_reverseString
-
-    Method in class without namespace:
-
-    ..  code-block:: text
-
-        user_yourClass->reverseString
-
-
-..  index:: Simple data types; getText
-..  _data-type-function-getText:
-
-getText
-=======
-
-The getText data type is some kind of tool box allowing to retrieve
-values from a variety of sources. Read more: :ref:`data-type-gettext`
-
-
-..  index:: Simple data types; GraphicColor
-..  _data-type-GraphicColor:
-
-GraphicColor
-============
-
-..  confval:: GraphicColor
-    :name: data-type-GraphicColor
-
-    ..  rubric:: Syntax:
-
-    [colordef] : [modifier]
-
-    Where modifier can be an integer which is added or subtracted to the three
-    RGB-channels or a floating point with an :typoscript:`*` before, which will then
-    multiply the values with that factor.
-
-
-    The color can be given as HTML-color or as a comma-separated list of
-    RGB-values (integers). An extra parameter can be given, that will modify the
-    color mathematically:
-
-    ..  rubric:: Examples
-
-    *   :typoscript:`red` (HTML color)
-    *   :typoscript:`#ffeecc` (HTML color as hexadecimal notation)
-    *   :typoscript:`255,0,255` (HTML color as decimal notation)
-
-    *Extra:*
-
-    *   :typoscript:`red : *0.8` ("red" is darkened by factor 0.8)
-    *   :typoscript:`#ffeecc : +16` ("ffeecc" is going to #fffedc because 16 is added)
-
-
-..  index:: Simple data types; imageExtension
-..  _data-type-imageExtension:
-
-imageExtension
-==============
-
-..  confval:: imageExtension
-    :name: data-type-imageExtension
-
-    Image extensions can be anything among the allowed types defined in the
-    global variable :php:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']`.
-    Standard is pdf, gif, jpg, jpeg, tif, bmp, ai, pcx, tga, png.
-
-    The value **"web"** is special. This will ensure that an image is
-    converted to a web image format (gif or jpg) if it happens not to be already!
-
-    ..  rubric:: Examples
-
-    jpg
-
-    web *(gif or jpg ..)*
-
-
-..  index:: Simple data types; imgResource
-..  _data-type-imgResource:
-
-imgResource
-===========
-
-..  todo: This seems to be a duplicate of Documentation/Functions/Imgresource.rst?
-
-..  confval:: imgResource
-    :name: data-type-imgResource
-
-    #.  A :confval:`data-type-resource` plus imgResource properties.
-
-        Filetypes can be anything among the allowed types defined in the
-        configuration variable
-        :php:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']`.  Standard is
-        pdf, gif, jpg, jpeg, tif, bmp, ai, pcx, tga, png.
-
-    #.  A GIFBUILDER object. See the object reference for :ref:`gifbuilder`.
-
-    ..  rubric:: Examples
-
-    Here "file" is an imgResource:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        10 = IMAGE
-        10 {
-            file = fileadmin/toplogo.gif
-            file.width = 200
-        }
-
-    GIFBUILDER:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        10 = IMAGE
-        10.file = GIFBUILDER
-        10.file {
-            # GIFBUILDER properties here...
-        }
-
-
-..  index:: Simple data types; integer
-..  _data-type-integer:
-
-integer
-=======
-
-..  confval:: integer
-    :name: data-type-integer
-
-    ..  rubric:: Examples
-
-    42, -8, -9, 0
-
-
-    This data type is sometimes used generally though another type would have
-    been more appropriate, like :ref:`pixels <data-type-pixels>`.
-
-
-..  index:: Simple data types; path
-..  _data-type-path:
-
-path
-====
-
-..  confval:: path
-    :name: data-type-path
-
-
-    Path relative to the root directory from which we operate.
-    Also resolves `EXT:` syntax.
-
-    ..  rubric:: Example
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.settings.somePath = fileadmin/stuff/
-
-
-..  index:: Simple data types; pixels
-..  _data-type-pixels:
-
-pixels
-======
-
-..  confval:: pixels
-    :name: data-type-pixels
-
-    pixel-distance
-
-    ..  rubric:: Example
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.someWidth = 345
-
-
-..  index:: Simple data types; positive integer
-..  _data-type-positive-integer:
-
-positive integer
-================
-
-..  confval:: positive integer
-    :name: data-type-positive-integer
-
-
-    Positive :confval:`data-type-integer`.
-
-    ..  rubric:: Examples
-
-    42, 8, 9
-
-
-..  index:: Simple data types; resource
-..  _data-type-resource:
-
-resource
-========
-
-..  confval:: resource
-    :name: data-type-resource
-
-    If the value contains a "/", it is expected to be a reference (absolute or
-    relative) to a file in the file system. There is no support for wildcard
-    characters in the name of the reference.
-
-    ..  rubric:: Example
-
-    Reference to a file in the file system:
-
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-       page.10.settings.someFile = fileadmin/picture.gif
-
-..  index:: Simple data types; strftime-conf
-..  _data-type-strftime-conf:
-
-strftime-conf
-=============
-
-..  confval:: strftime-conf
-    :name: data-type-strftime-conf
-
-    See function `strftime on php.net <https://www.php.net/manual/en/function.strftime>`__.
-
-
-..  index:: Simple data types; string
-..  _data-type-string:
-
-string
-======
-
-..  confval:: string
-    :name: data-type-string
-
-    Sometimes used generally though another type would have been more
-    appropriate, like "align".
-
-    ..  rubric:: Example
-
-    The quick brown fox jumps over the lazy dog.
-
-
-..  index:: Simple data types; tag
-..  _data-type-tag:
-
-tag
-===
-
-..  confval:: tag
-    :name: data-type-tag
-
-    An HTML tag.
-
-    ..  rubric:: Example
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.settings.bodyTag = <body lang="de">
-
-
-..  index:: Simple data types; tag-params
-..  _data-type-tag-params:
-
-tag-params
-==========
-
-..  confval:: tag-params
-    :name: data-type-tag-params
-
-    Parameters for a tag.
-
-    ..  rubric:: Examples
-
-    For <frameset>-params:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.settings.someParams = border="0" framespacing="0"
-
-
-..  index:: Simple data types; target
-..  _data-type-target:
-
-target
-======
-
-..  confval:: target
-    :name: data-type-target
-
-    ..  rubric:: Examples
-
-    :typoscript:`_top`, :typoscript:`_blank`, :typoscript:`content`
-
-
-    Target in an :html:`<a>`-tag.
-
-    This is normally the same value as the name of the root-level object
-    that defines the frame.
-
-
-..  index:: Simple data types; wrap
-..  _data-type-wrap:
-
-wrap
-====
-
-..  confval:: wrap
-    :name: data-type-wrap
-
-    :Syntax: <...> \| </...>
-
-
-    Used to wrap something. The vertical bar ("|") is the place, where
-    your content will be inserted; the parts on the left and right of the
-    vertical line are placed on the left and right side of the content.
-
-    Spaces between the wrap-parts and the divider ("|") are trimmed off
-    from each part of the wrap.
-
-    If you want to use more sophisticated data functions, then you
-    should use `stdWrap.dataWrap` instead of `wrap`.
-
-    A `wrap` is processed and rendered as the last of the other components of
-    a cObject.
-
-    ..  rubric:: Examples
-
-    This will cause the value to be wrapped in a p-tag coloring the
-    value red:
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.stdWrap.wrap = <p class="bg-red"> | </p>
diff --git a/Documentation/Functions/Data.rst b/Documentation/Functions/Data.rst
index a124c6b51..4c95cdaa0 100644
--- a/Documentation/Functions/Data.rst
+++ b/Documentation/Functions/Data.rst
@@ -1,15 +1,16 @@
 ..  include:: /Includes.rst.txt
 ..  index:: Function; getText
+..  _data-type-function-getText:
 ..  _data-type-gettext:
 
 ==============
 Data / getText
 ==============
 
-The `getText` data type is some kind of tool box allowing to retrieve
-values from a variety of sources, for example from `GET`/`POST` variables, from
-registers, values from the page tree, items in the page menus, records
-from any database table, etc.
+The `getText` data type is a kind of tool box for retrieving
+values from different sources, for example, `GET`/`POST` variables,
+registers, values from the page tree, items in the page menus and records
+from database tables.
 
 The general syntax is as follows:
 
@@ -18,31 +19,28 @@ The general syntax is as follows:
 
     lib.foo.data = <key> : <code>
 
-where :typoscript:`<key>` indicates the source and :typoscript:`<code>` is some form of path or
-pointer to the value, which depends on the key used. The various keys and
-their possible codes are described below.
+where :typoscript:`<key>` indicates the source and :typoscript:`<code>` contains paths or
+pointers to values. Possible keys and codes are described below.
 
-The :typoscript:`code` can contain pipe characters :typoscript:`|` to separate keys
-in a multidimensional array. This, for example, works with :typoscript:`TSFE`:
+The :typoscript:`code` can contain pipe characters :typoscript:`|` which will
+result in a multidimensional array. This, for example, works with :typoscript:`TSFE`:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
     lib.foo.data = TSFE : fe_user | user | username
 
-Some codes work with a different separator, which is documented right at the
+Some codes use a different separator, but this is documented in the
 code.
 Spaces around the colon (:typoscript:`:`) are irrelevant. The :typoscript:`key` is
 case-insensitive.
 
 ..  _data-type-gettext-double-slash:
 
-By separating the value of getText with :typoscript:`//` (double slash) a number of
-codes can be supplied and getText will return the first one, which is not
-empty ("" or zero).
-
-To get the content of the field "header". If "header is empty, "title" is
-retrieved. If "title" is empty as well, it finally gets the field "uid":
+Using multiple codes separated by a :typoscript:`//` (double slash) will return
+the first one that is not empty ("" or zero). The TypoScript below gets the
+content of the "header" field. If "header" is empty, "title" is
+retrieved. If "title" is also empty, the "uid" field is retrieved:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -68,7 +66,7 @@ applicationcontext
     :name: data-applicationcontext
 
     Returns the current :ref:`application context <t3coreapi:application-context>`
-    as string.
+    as a string.
 
 
 ..  _data-type-gettext-applicationcontext-example:
@@ -95,16 +93,16 @@ asset
     :name: data-asset
 
     ..  versionadded:: 13.2
-        Local resources can be cache-busted. It is not necessary anymore
-        to rename the asset when it is exchanged, forcing browsers to relod the file.
+        Local resources can be cache-busted. It is no longer necessary
+        to rename the asset when it is exchanged, forcing browsers to reload the file.
 
     The getText `asset` function includes assets like images, CSS or
-    JavaScript in a cache-busted way.
+    JavaScript that are cache-busted.
 
     Depending on :confval:`$GLOBALS['TYPO3_CONF_VARS']['FE']['versionNumberInFilename'] <t3coreapi:typo3-conf-vars-fe-versionnumberinfilename>`
-    the cache buster is applied as query string or embedded in the filename.
+    the cache buster is applied as a query string or embedded in the filename.
 
-    The result is the same like using argument :fluid:`useCacheBusting="true"`
+    The result is the same as using the argument :fluid:`useCacheBusting="true"`
     in :ref:`t3viewhelper:typo3-fluid-uri-resource`.
 
 Example: Display extension icon with cache buster
@@ -181,7 +179,7 @@ current
 ..  confval:: current
     :name: data-current
 
-    current (gets the "current" value)
+    Current (gets the "current" value)
 
     ..  TODO: What is the "current" value? We should explain that.
 
@@ -223,11 +221,11 @@ DB
     :name: data-db
     :Syntax: DB : [table name] : [uid] : [field]
 
-    Value from database. Any record from a table in TCA can be selected here.
-    Records marked as deleted will not return any value.
+    Value from the database. Any record from any table that is in the TCA can be
+    selected here. Records marked as deleted will not return a value.
 
-    In contrast to other keys, colons are used here to get deeper into the
-    structure, instead of pipes.
+    In contrast to the other keys, colons are used here instead of pipes to drill down into the
+    structure.
 
 ..  _data-type-gettext-db-example:
 
@@ -242,8 +240,8 @@ Get the value of the header field of record with uid 234 from table
 
     lib.foo.data = DB : tt_content:234:header
 
-Get the value of the header field of a record, whose uid is stored in a GET
-parameter `myContentId`:
+Get the value of the header field of a record, where the uid is in the
+`myContentId` GET parameter :
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -251,10 +249,10 @@ parameter `myContentId`:
     lib.foo.data.dataWrap = DB : tt_content:{GP : myContentId}:header
 
 ..  note::
-    It is safe to directly use a client-/user-provided input for the id of a DB
+    It is safe to use client-/user-provided input for the id of a DB
     record here. The function :php:`ContentObjectRenderer->getData()` internally
     calls the function :php:`PageRepository->getRawRecord()`, which converts the
-    parameter to int via :php:`QueryBuilder->createNamedParameter()`
+    parameter to an int via :php:`QueryBuilder->createNamedParameter()`
 
 ..  _data-type-gettext-debug:
 
@@ -265,8 +263,8 @@ debug
 ..  confval:: debug
     :name: data-debug
 
-    Returns HTML-formatted content of the PHP variable defined by the keyword.
-    Available keywords are :typoscript:`rootLine`, :typoscript:`fullRootLine`, :typoscript:`data`,
+    Returns HTML-formatted content of a PHP variable.
+    Available variables are :typoscript:`rootLine`, :typoscript:`fullRootLine`, :typoscript:`data`,
     :typoscript:`register` and :typoscript:`page`.
 
 ..  _data-type-gettext-debug-example:
@@ -288,19 +286,18 @@ field
 
 ..  confval:: field
     :name: data-field
-    :Syntax: field : [field name from the current :php:`$cObj->data` array in the cObject, multi-dimensional.]
+    :Syntax: field : [a field name in the current :php:`$cObj->data` array in the cObject, multidimensional]
 
 
-    This gives read access to the current value of an internal global variable determined by the given key.
+    This gives read access to the value of an internal global variable depending on the key.
 
-    -   As default the :php:`$cObj->data` array is :php:`$GLOBALS['TSFE']->page`
-        (record of the current page)
+    -   By default, the :php:`$cObj->data` array is the record of the current page.
 
-    -   In :ref:`TMENU <tmenu>` :php:`$cObj->data` is set in a loop to the page-record for
-        each menu item during its rendering process.
+    -   In :ref:`TMENU <tmenu>` :php:`$cObj->data` is set to the page-record of
+        each menu item in loop iterations during the rendering process.
 
     -   In :ref:`cobj-content` / :ref:`cobj-records` :php:`$cObj->data` is set to
-        the actual record
+        the current record
 
     -   In :ref:`GIFBUILDER <gifbuilder>` :php:`$cObj->data` is set to the data
         :ref:`GIFBUILDER <gifbuilder>` is supplied with.
@@ -317,7 +314,7 @@ Get content from :php:`$cObj->data['header']`:
 
     lib.foo.data = field : header
 
-Example: Get data of a field
+Example: Get data in a field
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Get content from :php:`$cObj->data['fieldname']['level1']['level2']`:
@@ -338,27 +335,27 @@ file
 
     Retrieves a property from a file object (:ref:`FAL <t3coreapi:fal>`) by identifying it through its
     :sql:`sys_file` UID. Note that during execution of the :ref:`cobj-files` cObject,
-    it is also possible to reference the current file with :confval:`data-current` as UID like
-    :typoscript:`file : current : size`.
+    it is possible to reference the current file using :confval:`data-current` as the UID,
+    for example, :typoscript:`file : current : size`.
 
     The following properties are available: name, uid, originalUid, size, sha1,
-    extension, mimetype, contents, publicUrl, modification_date, creation_date
+    extension, mimetype, contents, publicUrl, modification_date and creation_date.
 
-    Furthermore when manipulating references (such as images in content elements
-    or media in pages), additional properties are available (not all are
+    Furthermore, when manipulating references (such as images in content elements
+    and media on pages), these additional properties are available (not all are
     available all the time, it depends on the setup of *references* of the
-    :ref:`cobj-files` cObject): title, description, link, alternative.
+    :ref:`cobj-files` cObject): title, description, link and alternative.
 
-    Additionally, any data in the :sql:`sys_file_metadata` table can be accessed too.
+    Any data in the :sql:`sys_file_metadata` table can also be accessed.
 
-    See the :ref:`FILES <cobj-files-examples>` cObject for usage examples.
+    See the :ref:`FILES <cobj-files-examples>` cObject for examples of usage.
 
 ..  _data-type-gettext-file-example:
 
 Example: Get the size of a file
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Get the file size of the file with the sys\_file UID 17:
+Get the size of the file with sys\_file UID 17:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -372,10 +369,9 @@ flexform
 
 ..  confval:: flexform
     :name: data-flexform
-    :Syntax: flexform : [field containing flexform data].[property of this flexform]
+    :Syntax: flexform : [field containing flexform data] : [property of this flexform]
 
-    Access values from :ref:`FlexForms <t3coreapi:flexforms>`, for example inside of :sql:`tt_content` record. In contrast
-    to most parts, deeper levels are accessed through dots, not pipes.
+    Access values in :ref:`FlexForms <t3coreapi:flexforms>`, for example, inside a :sql:`tt_content` record.
 
 ..  _data-type-gettext-flexform-example:
 
@@ -398,12 +394,12 @@ fullRootLine
     :name: data-fullRootLine
     :Syntax: fullRootLine : [pointer, integer], [field name], ["slide"]
 
-This property can be used to retrieve values from "above" the current page's
-root. Take the below page tree and assume that we are on the page "Here you
-are!". Using the :ref:`data-type-gettext-levelfield` property, it is possible
-to go up only to the page "Site root", because it is the root of a new
-(sub-)site.  With :typoscript:`fullRootLine` it is possible to go all the way up to page
-tree root. The numbers between square brackets indicate to which page each
+Used to retrieve values from "above" the current page's
+root. Assume that you are on the page "You are here!" in the page tree below.
+Using the :ref:`data-type-gettext-levelfield` property, you
+can only go up to the page "Site root", because it is the root of a new
+(sub-)site.  :typoscript:`fullRootLine` allows you to go all the way up to the page
+tree root. The numbers in square brackets indicate  which page each
 value of *pointer* would point to:
 
 ..  code-block:: text
@@ -411,17 +407,17 @@ value of *pointer* would point to:
     - Page tree root [-2]
       |- 1. page before [-1]
         |- Site root (root template here!) [0]
-          |- Here you are! [1]
+          |- You are here! [1]
 
-A "slide" parameter can be added just as for the
-:ref:`data-type-gettext-levelfield` property.
+A "slide" parameter can be added (like in :ref:`data-type-gettext-levelfield`
+property).
 
 ..  _data-type-gettext-fullrootline-example:
 
 Example: Get the title of the previous page
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Get the title of the page right before the start of the current website:
+Get the title of the page before the start of the current website:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -438,14 +434,14 @@ getenv
 
     Value from PHP environment variables.
 
-    For a cached variation of this feature, please refer to :ref:`getEnv <getenv>`.
+    For a cached version of this feature, see :ref:`getEnv <getenv>`.
 
 ..  _data-type-gettext-getenv-example:
 
 Example: Get the HTTP referer
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Get the environment variable `HTTP_REFERER`:
+Get the environment variable `HTTP_REFERER`.
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -462,10 +458,9 @@ getIndpEnv
     :Syntax: getIndpEnv : <name>
 
     Returns the value of a *System Environment Variable* denoted by
-    *name* regardless of server OS, CGI/MODULE version etc. The result is
-    identical to the :php:`$_SERVER` variable in most cases. This method should
-    be used instead of *getEnv* to get reliable values for all situations. The
-    internal processing is handled by
+    *name* regardless of server OS, CGI/MODULE version, etc. The result is
+    usually identical to the :php:`$_SERVER` variable. This method is more reliable
+    then *getEnv*. Internal processing is handled by
     :php:`TYPO3\CMS\Core\Utility\GeneralUtility::getIndpEnv()`
 
     Available names:
@@ -521,7 +516,7 @@ global
     :name: data-global
     :Syntax: global : [variable]
 
-    Deprecated, use :ref:`data-type-gettext-gp`, :ref:`data-type-gettext-tsfe` or
+    Deprecated. Use :ref:`data-type-gettext-gp`, :ref:`data-type-gettext-tsfe` or
     :ref:`data-type-gettext-getenv`.
 
 ..  _data-type-gettext-gp:
@@ -533,7 +528,7 @@ GP
     :name: data-gp
     :Syntax: GP : [Value from GET or POST method]
 
-    Get a variable from :php:`$_GET` or :php:`$_POST` where a variable, which
+    Get a variable from :php:`$_GET` or :php:`$_POST` when a variable, which
     exists in both arrays, is returned from :php:`$_POST`.
 
 ..  _data-type-gettext-gp-example:
@@ -584,15 +579,15 @@ levelfield
     :name: data-levelfield
     :Syntax: levelfield : [pointer, integer], [field name], ["slide"]
 
-    Like :ref:`data-type-gettext-leveltitle` but the field do be fetched from the
-    record is configurable.
+    Like :ref:`data-type-gettext-leveltitle` but you can choose which field should
+    be fetched from the record.
 
 ..  _data-type-gettext-levelfield-example:
 
-Example: Get a field from a page up in the root-line
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Example: Get a field from a page up the root-line
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Get the value of the user-defined field :sql:`tx_myextension_myfield` in the root line.
+Get the value of user-defined field :sql:`tx_myextension_myfield` in the root line.
 
 ..  code-block:: typoscript
     :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
@@ -606,7 +601,7 @@ Get the value of the user-defined field :sql:`tx_myextension_myfield` in the roo
     use custom fields.
 
     To stay compatible with both TYPO3 v12 and v13, add the following to your
-    extensions :file:`ext_localconf.php`:
+    extension's :file:`ext_localconf.php`:
 
     ..  literalinclude:: _Data/_addRootlineFields_ext_localconf.php
         :caption: EXT:my_extension/ext_localconf.php
@@ -623,9 +618,9 @@ levelmedia
 
     Get the media field of a page in the root-line.
 
-    *   Use an absolute level with 0 or a positive integer.
-    *   With a negative integer got x levels up
-    *   The slide parameter slides until there is a non-empty value found.
+    *   Use an absolute level: 0 or a positive integer.
+    *   Negative integers determine x levels up.
+    *   The slide parameter slides until there is a non-empty value.
 
 ..  _data-type-gettext-leveltitle:
 
@@ -638,12 +633,12 @@ leveltitle
 
     Get the title of a page in the root-line.
 
-    *   Use an absolute level with 0 or a positive integer.
-    *   With a negative integer got x levels up
-    *   The slide parameter slides until there is a non-empty value found.
+    *   Use an absolute level: 0 or a positive integer.
+    *   Negative integers determine x levels up
+    *   The slide parameter slides until there is a non-empty value.
 
-Example: Get the title of a page up in the root line
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Example: Get the title of a page up the root line
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Get the title of the page on the first level of the root line:
 
@@ -652,8 +647,8 @@ Get the title of the page on the first level of the root line:
 
     lib.foo.data = leveltitle : 1
 
-Get the title of the page on the level right below the current page AND if
-that is not present, walk to the bottom of the root line until there's a
+Get the title of the page on the level immediately below the current. If
+it is empty, walk to the bottom of the root line until there is a
 title:
 
 ..  code-block:: typoscript
@@ -672,8 +667,8 @@ leveluid
 
     Get the UID of a page in the root line.
 
-    *   Use an absolute level with 0 or a positive integer.
-    *   With a negative integer got x levels up
+    *   Use an absolute level: 0 or a positive integer.
+    *   Negative integers determine x levels up.
 
 ..  _data-type-gettext-leveluid-example:
 
@@ -739,7 +734,7 @@ pagelayout
 ..  confval:: pagelayout
     :name: data-pagelayout
 
-    Get the current backend layout
+    Get the current backend layout.
 
 ..  _data-type-gettext-pagelayout-example:
 
@@ -760,7 +755,7 @@ parameters
     :name: data-parameters
     :Syntax: parameters: [field name from the current :php:`$cObj->parameters` array in the cObject.]
 
-    Get the content of a key in :php:`parameters` array of the current cObject.
+    Get the content of a key in the :php:`parameters` array of the current cObject.
 
 ..  _data-type-gettext-parameters-examples:
 
@@ -782,7 +777,7 @@ path
 ..  confval:: path
     :name: data-path
 
-    Path to a file, possibly placed in an extension, returns empty if the file
+    Path to a file, for example, that is in an extension. Returns an empty value if the file
     does not exist.
 
 ..  _data-type-gettext-path-example:
@@ -825,7 +820,7 @@ register
 Example: Get the content of a register
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Get content from the :ref:`register <using-setting-register>`:
+Get content from a :ref:`register <using-setting-register>`:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -847,9 +842,9 @@ request
     Retrieve the property of a
     :ref:`PSR-7 request attribute <t3coreapi:request-attributes>`.
 
-    Note that only scalar properties can be retrieved: int, float, string or
-    bool as value. If the property is an object or an array, a subproperty can
-    be given which then calls the getter method of the object or retrieves the
+    Only scalar properties can be retrieved: int, float, string or
+    bool values. If the property is an object or an array, a subproperty can
+    be used to call the getter method of the object or retrieve the
     key of the array.
 
 ..  _data-type-gettext-request-example-page-type:
@@ -896,7 +891,7 @@ session
     :name: data-session
     :Syntax: session : [key]
 
-    The `key` refers to the session key used to store the value.
+    The `key` is the session key used to store a value.
 
 ..  _data-type-gettext-session-example:
 
@@ -920,7 +915,7 @@ site
     :name: data-site
     :Syntax: site : [key]
 
-    Accessing the current
+    Accesses the current
     :ref:`site configuration <t3coreapi:sitehandling-basics>`.
 
     .. rubric:: Possible keys:
@@ -932,7 +927,7 @@ site
         The base URL for this site.
 
     :typoscript:`baseVariants`
-        The base variants for this site.
+        The base variants of this site.
 
     :typoscript:`rootPageId`
         The root page ID of this site.
@@ -955,8 +950,8 @@ Example: Get values from the current site
     page.10.data = site:base
     page.10.wrap = This is your base URL: |
 
-Where :typoscript:`site` is the keyword for accessing an aspect, and the
-following parts are the configuration key(s) to access.
+:typoscript:`site` is the keyword, and the parts after the colon are the
+configuration key(s) to access.
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -974,7 +969,7 @@ siteLanguage
     :name: data-siteLanguage
     :Syntax: siteLanguage : [key]
 
-    Accessing the current
+    Accesses the current
     :ref:`site language configuration <t3coreapi:sitehandling-addingLanguages>`.
 
 
@@ -987,32 +982,48 @@ siteLanguage
         The base URL for this language.
 
     :typoscript:`flagIdentifier`
-        The flag key (like `gb` or `fr`) used in the TYPO3 backend.
+        The flag key (for example, `gb` or `fr`) used in the TYPO3 backend.
 
-        ..  versionadded:: 12.4
-            You can also use :typoscript:`flag` to match the corresponding site
-            configuration setting.
+        :typoscript:`flag` can be used to match the site
+        configuration setting.
 
     :typoscript:`hreflang`
-        ..  versionchanged:: 12.4
-            This option is not relevant anymore for regular websites without
-            rendering hreflang tag, but is now customizable, and has a proper
-            fallback.
+        The language tag for this language defined by RFC 1766 / 3066
+        :html:`hreflang` attributes.
 
-        The language tag for this language defined by RFC 1766 / 3066 for
-        :html:`hreflang` attributes
+        This option is not relevant for regular websites without
+        rendering hreflang tag.
 
     :typoscript:`languageId`
         The language mapped to the ID of the site language.
 
     :typoscript:`locale`
-        The locale, like `de_CH` or `en_GB`.
+        ..  versionchanged:: 12.3
+            The :typoscript:`locale` property in typoscript can be subdivided
+            using subkeys separated by a colon `:`.
+            The subkeys `languageCode`, `countryCode`, and `full` allow access
+            to the individual components of the :typoscript:`locale` value. For
+            instance, a :typoscript:`locale` value of "en_US.UTF-8" can be
+            broken down into "en", "US", and for the `full` subkey, "en-US".
+
+            *   :typoscript:`languageCode`: this contains the two-letter
+                language code (previously
+                :typoscript:`siteLanguage:twoLetterIsoCode`)
+            *   :typoscript:`countryCode`: contains the uppercase country code
+                part of the locale
+            *   :typoscript:`full`: contains the entire locale (this is also the default
+                if no subkey is specified)
+
+        The :typoscript:`locale` property represents the language, country, and
+        character encoding settings for TYPO3. It is a composite value, such as
+        "en_US.UTF-8", which can be dissected into different components via
+        subkeys for more precise language and location specifications.
 
     :typoscript:`navigationTitle`
-        The label to be used within language menus.
+        The label used in language menus.
 
     :typoscript:`title`
-        The label to be used within TYPO3 to identify the language.
+        The label used in TYPO3 to identify the language.
 
     :typoscript:`typo3Language`
         The prefix for TYPO3's language files (`default` for English), otherwise
@@ -1020,8 +1031,8 @@ siteLanguage
         TypoScript :typoscript:`config.language = fr`.
 
     :typoscript:`websiteTitle`
-        The website title for this language. No automatic fallback to the
-        :typoscript:`site:websiteTitle`!
+        The website title for this language. Note: there is no automatic fallback to the
+        :typoscript:`site:websiteTitle`.
 
 ..  _data-type-siteLanguage-example:
 
@@ -1048,12 +1059,10 @@ Example: Get values from the current site language
 siteSettings
 ------------
 
-..  versionadded:: 12.1
-
 ..  confval:: siteSettings
     :name: data-siteSettings
 
-    Access the :ref:`site settings <t3coreapi:sitehandling-settings>` for the
+    Access the :ref:`site settings <t3coreapi:sitehandling-settings>` of the
     current site.
 
 ..  _data-type-siteSettings-example:
@@ -1082,7 +1091,7 @@ TSFE
 
 
 ..  versionchanged:: 13.0
-    The following properties within TypoScriptFrontendController (TSFE) have
+    The following TypoScriptFrontendController (TSFE) properties have
     been removed:
 
     *   :php:`spamProtectEmailAddresses`
@@ -1091,7 +1100,7 @@ TSFE
     *   :php:`fileTarget`
     *   :php:`baseUrl`
 
-    Migrate these properties to use the config property. You can access the
+    Migrate these properties to the config property. You can access the
     TypoScript properties directly, for example, via
     :typoscript:`lib.something.data = TSFE : config | config | fileTarget`
 
diff --git a/Documentation/Functions/Htmlparser.rst b/Documentation/Functions/Htmlparser.rst
index bba9d6d2a..0566fbe6a 100644
--- a/Documentation/Functions/Htmlparser.rst
+++ b/Documentation/Functions/Htmlparser.rst
@@ -128,11 +128,28 @@ removeTags
 
 ..  confval:: removeTags
     :name: htmlparser-removeTags
-    :type: (ibid)
+    :type: string-list / array
 
     List of tags (among the already set tags), which will be configured so
     they are surely removed.
 
+    ..  code-block:: yaml
+        :caption: EXT:rte_ckeditor/Configuration/RTE/Processing.yaml
+
+        processing:
+          HTMLparser_db:
+            removeTags: [link, meta, o:p, sdfield, style, title]
+            # "string" definition is also possible:
+            # removeTags: link, meta, o:p, sdfield, style, title
+
+    ..  code-block:: typoscript
+        :caption: EXT:my_extension/Configuration/TypoScript/page.tsconfig
+
+        RTE.default.proc {
+          HTMLparser_db {
+            removeTags = link, meta, o:p, sdfield, style, title
+          }
+        }
 
 ..  _htmlparser-keepNonMatchedTags:
 
diff --git a/Documentation/Functions/If.rst b/Documentation/Functions/If.rst
index ba68eb5a0..5556fbe74 100644
--- a/Documentation/Functions/If.rst
+++ b/Documentation/Functions/If.rst
@@ -52,8 +52,8 @@ bitAnd
     .. code-block:: typoscript
        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-       hideDefaultLanguageOfPage = TEXT
-       hideDefaultLanguageOfPage {
+       lib.hideDefaultLanguageOfPage = TEXT
+       lib.hideDefaultLanguageOfPage {
            value = 0
            value {
                override = 1
@@ -70,8 +70,6 @@ bitAnd
 contains
 --------
 
-..  versionadded:: 12.1
-
 ..  confval::  contains
     :name: if-contains
     :type:  value / :ref:`stdwrap`
@@ -119,8 +117,6 @@ directReturn
 endsWith
 --------
 
-..  versionadded:: 12.1
-
 ..  confval::  endsWith
     :name: if-endsWith
     :type:  value / :ref:`stdwrap`
@@ -302,8 +298,6 @@ negate
 startsWith
 ----------
 
-..  versionadded:: 12.1
-
 ..  confval::  startsWith
     :name: if-startsWith
     :type:  value / :ref:`stdwrap`
@@ -362,8 +356,8 @@ If you want to compare values, you must load a base-value in the
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    page.10.value = 10
-    page.10.isGreaterThan = 11
+    page.10.if.value = 10
+    page.10.if.isGreaterThan = 11
 
 This would return true because the value of :typoscript:`isGreaterThan` is
 greater than 10, which is the base-value.
@@ -373,7 +367,7 @@ More complex is this:
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    page.10 {
+    page.10.if {
       value = 10
       isGreaterThan = 11
       isTrue.field = header
diff --git a/Documentation/Functions/Imagelinkwrap.rst b/Documentation/Functions/Imagelinkwrap.rst
index be8630cc5..38bec9505 100644
--- a/Documentation/Functions/Imagelinkwrap.rst
+++ b/Documentation/Functions/Imagelinkwrap.rst
@@ -143,7 +143,7 @@ bodyTag
 
 ..  confval:: imageLinkWrap.bodyTag
     :name: imagelinkwrap-bodyTag
-    :type: :ref:`data-type-tag` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
 
     This is the `<body>`-tag of the preview window.
     Needs :typoscript:`JSwindow = 1`.
@@ -181,7 +181,7 @@ target
 
 ..  confval:: imageLinkWrap.target
     :name: imagelinkwrap-target
-    :type: :ref:`data-type-target` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
     :Default: :typoscript:`thePicture`
 
     This specifies the `target` attribute of the link. The attribute
@@ -243,10 +243,10 @@ JSwindow.newWindow
     :type: :ref:`data-type-boolean` / :ref:`stdwrap`
     :Default: 0
 
-    If the :ref:`Doctype <setup-config-doctype>` allows the :ref:`data-type-target`
+    If the :ref:`Doctype <setup-config-doctype>` allows the string
     attribute then the image will be opened in a window with the name given
     by `target`. If that windows is kept open and the next image with the
-    same :ref:`data-type-target` attribute is to be shown then it will appear
+    same string attribute is to be shown then it will appear
     in the same preview window.
     If :typoscript:`JSwindow.newWindow` is set to True,
     then a unique hash value is used as `target` value for each image.
diff --git a/Documentation/Functions/Imgresource.rst b/Documentation/Functions/Imgresource.rst
index 2c115a404..9ae994afd 100644
--- a/Documentation/Functions/Imgresource.rst
+++ b/Documentation/Functions/Imgresource.rst
@@ -2,14 +2,48 @@
 ..  index::
     Functions; imgResource
     imgResource
+..  _data-type-imgResource:
 ..  _imgresource:
 
 ===========
 imgResource
 ===========
 
-imgResource contains the properties that are used with the data type
-imgResource.
+An imgResource one of the following:
+
+#.  A :confval:`data-type-resource` plus imgResource properties.
+
+    Filetypes can be anything among the allowed types defined in the
+    configuration variable
+    :php:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']`.  Standard is
+    gif,jpg,jpeg,tif,tiff,bmp,pcx,tga,png,pdf,ai,svg,webp.
+
+#.  A GIFBUILDER object. See the object reference for :ref:`gifbuilder`.
+
+..  rubric:: Examples
+
+Here "file" is an imgResource:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+    10 = IMAGE
+    10 {
+        file = fileadmin/toplogo.gif
+        file.width = 200
+    }
+
+GIFBUILDER:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+    10 = IMAGE
+    10.file = GIFBUILDER
+    10.file {
+        # GIFBUILDER properties here...
+    }
+
 
 ..  contents::
     :local:
@@ -20,6 +54,7 @@ imgResource.
 Properties
 ==========
 
+..  _data-type-imageExtension:
 ..  _imgresource-ext:
 
 ext
@@ -27,7 +62,7 @@ ext
 
 ..  confval:: ext
     :name: imgresource-ext
-    :type: :ref:`data-type-imageExtension` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
     :Default: web
 
     Target file extension for the processed image. The value :typoscript:`web` checks if
@@ -37,6 +72,8 @@ ext
     :php:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']` in the install
     tool.
 
+    Standard is gif,jpg,jpeg,tif,tiff,bmp,pcx,tga,png,pdf,ai,svg,webp.
+
 
 ..  _imgresource-width:
 
@@ -45,7 +82,7 @@ width
 
 ..  confval:: width
     :name: imgresource-width
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     If both the width and the height are set and one of the numbers is
     appended by an :typoscript:`m`, the proportions will be preserved and thus
@@ -107,7 +144,7 @@ height
 
 ..  confval:: height
     :name: imgresource-height
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     See :ref:`imgresource-width`.
 
@@ -315,7 +352,7 @@ maxW
 
 ..  confval:: maxW
     :name: imgresource-maxW
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     Maximum width
 
@@ -327,7 +364,7 @@ maxH
 
 ..  confval:: maxH
     :name: imgresource-maxH
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     Maximum height
 
@@ -339,7 +376,7 @@ minW
 
 ..  confval:: minW
     :name: imgresource-minW
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     Minimum width (overrules maxW/maxH)
 
@@ -351,7 +388,7 @@ minH
 
 ..  confval:: minH
     :name: imgresource-minH
-    :type: :ref:`data-type-pixels` / :ref:`stdwrap`
+    :type: integer / :ref:`stdwrap`
 
     Minimum height (overrules maxW/maxH)
 
diff --git a/Documentation/Functions/Makelinks.rst b/Documentation/Functions/Makelinks.rst
index a2da999b1..fc8b22c52 100644
--- a/Documentation/Functions/Makelinks.rst
+++ b/Documentation/Functions/Makelinks.rst
@@ -49,7 +49,7 @@ http.extTarget
 
 ..  confval:: http.extTarget
     :name: makelinks-http-extTarget
-    :type: :ref:`data-type-target`
+    :type: string
     :Default: \_top
 
     The target of the link.
@@ -111,7 +111,7 @@ http.ATagParams
 
 ..  confval:: http.ATagParams
     :name: makelinks-http-ATagParams
-    :type: :ref:`data-type-tag-params` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
 
     Additional parameters
 
@@ -167,7 +167,7 @@ mailto.ATagParams
 
 ..  confval:: mailto.ATagParams
     :name: makelinks-mailto.ATagParams
-    :type: :ref:`data-type-tag-params` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
 
     Additional parameters
 
diff --git a/Documentation/Functions/Parsefunc.rst b/Documentation/Functions/Parsefunc.rst
index 955e654b7..10dd3e007 100644
--- a/Documentation/Functions/Parsefunc.rst
+++ b/Documentation/Functions/Parsefunc.rst
@@ -167,9 +167,6 @@ userFunc
     Similar to, for example, :ref:`stdwrap-postUserFunc` in :ref:`stdWrap`,
     or :ref:`typolink.userFunc <typolink-userFunc>`.
 
-    Remember the function name must possibly be prepended :php:`user_`.
-
-
 ..  _parsefunc-nonTypoTagStdWrap:
 
 nonTypoTagStdWrap
diff --git a/Documentation/Functions/Select.rst b/Documentation/Functions/Select.rst
index 718b3a82a..a111404fb 100644
--- a/Documentation/Functions/Select.rst
+++ b/Documentation/Functions/Select.rst
@@ -38,7 +38,7 @@ uidInList
 
 ..  confval:: uidInList
     :name: select-uidInList
-    :type: *list of record\_ids* / :ref:`stdWrap`
+    :type: *list of record uids* / :ref:`stdWrap`
 
     Comma-separated list of record uids from the according database table.
     For example when the select function works on the table `tt_content`, then
@@ -72,7 +72,7 @@ pidInList
 
 ..  confval:: pidInList
     :name: select_pidInList
-    :type: *list of page\_ids* / :ref:`stdWrap`
+    :type: *list of page uids* / :ref:`stdWrap`
     :Default: :typoscript:`this`
 
     Comma-separated list of pids of the record. This will be page uids (pids). For
diff --git a/Documentation/Functions/Stdwrap.rst b/Documentation/Functions/Stdwrap.rst
index f032fb9e5..fcc3114b3 100644
--- a/Documentation/Functions/Stdwrap.rst
+++ b/Documentation/Functions/Stdwrap.rst
@@ -64,186 +64,159 @@ Properties
 Properties for getting data
 ----------------------------
 
-..  _stdwrap-setContentToCurrent:
+..  confval-menu::
+    :name: stdwrap-get
+    :display: table
+    :type:
 
-setContentToCurrent
-~~~~~~~~~~~~~~~~~~~
+    ..  _stdwrap-setContentToCurrent:
 
-..  confval:: setContentToCurrent
-    :name: stdwrap-setContentToCurrent
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  confval:: setContentToCurrent
+        :name: stdwrap-setContentToCurrent
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    Sets the current value to the incoming content of the function.
+        Sets the current value to the incoming content of the function.
 
-..  _stdwrap-addpagecachetags:
+    ..  _stdwrap-addpagecachetags:
 
-addPageCacheTags
-~~~~~~~~~~~~~~~~
+    ..  confval:: addPageCacheTags
+        :name: stdwrap-addpagecachetags
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  confval:: addPageCacheTags
-    :name: stdwrap-addpagecachetags
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        Comma-separated list of cache tags, which should be added to the page
+        cache.
 
-    Comma-separated list of cache tags, which should be added to the page
-    cache.
+        ..  rubric:: Examples
 
-    ..  rubric:: Examples
+        .. code-block:: typoscript
 
-    .. code-block:: typoscript
+            addPageCacheTags = pagetag1,pagetag2,pagetag3
 
-        addPageCacheTags = pagetag1,pagetag2,pagetag3
+        This will add the tags "pagetag1", "pagetag2" and "pagetag3" to the
+        according cached pages in cache_pages.
 
-    This will add the tags "pagetag1", "pagetag2" and "pagetag3" to the
-    according cached pages in cache_pages.
+        Pages, which have been cached with a tag, can be deleted from cache
+        again with the TSconfig option
+        :ref:`TCEMAIN.clearCacheCmd <pagetcemain-clearcachecmd>`.
 
-    Pages, which have been cached with a tag, can be deleted from cache
-    again with the TSconfig option
-    :ref:`TCEMAIN.clearCacheCmd <t3tsconfig:pagetcemain-clearcachecmd>`.
+        ..  note::
+            If you instead want to store rendered content into the
+            caching framework, see the stdWrap feature :ref:`stdwrap-cache`.
 
-    ..  note::
-        If you instead want to store rendered content into the
-        caching framework, see the stdWrap feature :ref:`stdwrap-cache`.
 
+    ..  _stdwrap-setCurrent:
 
-..  _stdwrap-setCurrent:
+    ..  confval:: setCurrent
+        :name: stdwrap-setCurrent
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-setCurrent
-~~~~~~~~~~
+        Sets the "current"-value. This is normally set from some outside
+        routine, so be careful with this. But it might be handy to do this
 
-..  confval:: setCurrent
-    :name: stdwrap-setCurrent
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-    Sets the "current"-value. This is normally set from some outside
-    routine, so be careful with this. But it might be handy to do this
+    ..  _stdwrap-lang:
 
+    ..  confval:: lang
+        :name: stdwrap-lang
+        :type: Array of language keys / :ref:`stdWrap`
 
-..  _stdwrap-lang:
+        This is used to define optional language specific values based on the
+        :ref:`current site language <t3coreapi:sitehandling-addingLanguages>`.
 
-lang
-~~~~
+        ..  rubric:: Examples
 
-..  confval:: lang
-    :name: stdwrap-lang
-    :type: Array of language keys / :ref:`stdWrap`
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    This is used to define optional language specific values based on the
-    :ref:`current site language <t3coreapi:sitehandling-addingLanguages>`.
+            page.10 = TEXT
+            page.10.value = I am a Berliner!
+            page.10.stdWrap.lang.de = Ich bin ein Berliner!
 
-    ..  rubric:: Examples
+        Output will be "Ich bin..." instead of "I am..."
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10 = TEXT
-        page.10.value = I am a Berliner!
-        page.10.stdWrap.lang.de = Ich bin ein Berliner!
-
-    Output will be "Ich bin..." instead of "I am..."
-
-
-..  _stdwrap-data:
-
-data
-~~~~
-
-..  confval:: data
-    :name: stdwrap-data
-    :type: :ref:`data-type-gettext` / :ref:`stdWrap`
-
-
-..  _stdwrap-field:
-
-field
-~~~~~
-
-..  confval:: field
-    :name: stdwrap-field
-    :type: Field name / :ref:`stdWrap`
+    ..  _stdwrap-data:
 
-    Sets the content to the value of the according field
-    (which comes from :php:`$cObj->data[*field*]`).
+    ..  confval:: data
+        :name: stdwrap-data
+        :type: :ref:`data-type-gettext` / :ref:`stdWrap`
 
-    ..  note::
-        :php:`$cObj->data` changes depending on the context.
-        See the description for the data type ":ref:`data-type-gettext`"/field!
+    ..  _stdwrap-field:
 
-    ..  rubric:: Examples
+    ..  confval:: field
+        :name: stdwrap-field
+        :type: Field name / :ref:`stdWrap`
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10.field = title
+        Sets the content to the value of the according field
+        (which comes from :php:`$cObj->data[*field*]`).
 
-    This sets the content to the value of the field "title".
+        ..  note::
+            :php:`$cObj->data` changes depending on the context.
+            See the description for the data type ":ref:`data-type-gettext`"/field!
 
-    You can also check multiple field names, if you divide them
-    by "//".
+        ..  rubric:: Examples
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        page.10.field = nav_title // title
+            page.10.field = title
 
-    Here the content from the field nav\_title will be returned
-    unless it is a blank string. If a blank string, the value of
-    the title field is returned.
+        This sets the content to the value of the field "title".
 
+        You can also check multiple field names, if you divide them
+        by "//".
 
-..  _stdwrap-current:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-current
-~~~~~~~
+            page.10.field = nav_title // title
 
-..  confval:: current
-    :name: stdwrap-current
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        Here the content from the field nav\_title will be returned
+        unless it is a blank string. If a blank string, the value of
+        the title field is returned.
 
-    Sets the content to the "current" value (see :ref:`->split <split>`)
 
+    ..  _stdwrap-current:
 
-..  _stdwrap-cObject:
+    ..  confval:: current
+        :name: stdwrap-current
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-cObject
-~~~~~~~
+        Sets the content to the "current" value (see :ref:`->split <split>`)
 
-..  confval:: cObject
-    :name: stdwrap-cObject
-    :type: :ref:`data-type-cobject`
 
-    Loads content from a content object.
+    ..  _stdwrap-cObject:
 
+    ..  confval:: cObject
+        :name: stdwrap-cObject
+        :type: :ref:`data-type-cobject`
 
-..  _stdwrap-numRows:
+        Loads content from a content object.
 
-numRows
-~~~~~~~
 
-..  confval:: numRows
-    :name: stdwrap-numRows
-    :type: :ref:`->numRows <numrows>` / :ref:`stdWrap`
+    ..  _stdwrap-numRows:
 
-    Returns the number of rows resulting from the supplied :sql:`SELECT` query.
+    ..  confval:: numRows
+        :name: stdwrap-numRows
+        :type: :ref:`->numRows <numrows>` / :ref:`stdWrap`
 
+        Returns the number of rows resulting from the supplied :sql:`SELECT` query.
 
-..  _stdwrap-preUserFunc:
 
-preUserFunc
-~~~~~~~~~~~
+    ..  _stdwrap-preUserFunc:
 
-..  confval:: preUserFunc
-    :name: stdwrap-preUserFunc
-    :type: :ref:`data-type-function-name`
+    ..  confval:: preUserFunc
+        :name: stdwrap-preUserFunc
+        :type: :ref:`data-type-function-name`
 
-    Calls the provided PHP function. If you specify the name with a '->'
-    in it, then it is interpreted as a call to a method in a class.
+        Calls the provided PHP function. If you specify the name with a '->'
+        in it, then it is interpreted as a call to a method in a class.
 
-    Two parameters are sent to the PHP function: As first parameter a
-    content variable, which contains the current content. This is the
-    value to be processed. As second parameter any sub-properties of
-    preUserFunc are provided to the function.
+        Two parameters are sent to the PHP function: As first parameter a
+        content variable, which contains the current content. This is the
+        value to be processed. As second parameter any sub-properties of
+        preUserFunc are provided to the function.
 
-    See :ref:`stdwrap-postUserFunc`.
+        See :ref:`stdwrap-postUserFunc`.
 
 
 ..  index:: Function stdWrap; Override and conditions
@@ -252,1647 +225,1516 @@ preUserFunc
 Properties for overriding and conditions
 ----------------------------------------
 
-..  _stdwrap-override:
-
-override
-~~~~~~~~
-
-..  confval:: override
+..  confval-menu::
     :name: stdwrap-override
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+    :display: table
+    :type:
 
-    If `override` returns something else than "" or zero (trimmed), the
-    content is loaded with this!
+    ..  _stdwrap-override:
 
+    ..  confval:: override
+        :name: stdwrap-override
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  _stdwrap-preIfEmptyListNum:
+        If `override` returns something else than "" or zero (trimmed), the
+        content is loaded with this!
 
-preIfEmptyListNum
-~~~~~~~~~~~~~~~~~
 
-..  confval:: preIfEmptyListNum
-    :name: stdwrap-preIfEmptyListNum
-    :type: (as ":ref:`stdwrap-listNum`" below)
+    ..  _stdwrap-preIfEmptyListNum:
 
+    ..  confval:: preIfEmptyListNum
+        :name: stdwrap-preIfEmptyListNum
+        :type: (as ":ref:`stdwrap-listNum`" below)
 
-..  _stdwrap-ifNull:
 
-ifNull
-~~~~~~
+    ..  _stdwrap-ifNull:
 
-..  confval:: ifNull
-    :name: stdwrap-ifNull
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+    ..  confval:: ifNull
+        :name: stdwrap-ifNull
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-    If the content is null (:php:`NULL` type in PHP), the content is overridden
-    with the value defined here.
+        If the content is null (:php:`NULL` type in PHP), the content is overridden
+        with the value defined here.
 
-    ..  rubric:: Examples
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  rubric:: Examples
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        page.10 = COA_INT
-        page.10 {
-           10 = TEXT
-           10 {
-              stdWrap.field = description
-              stdWrap.ifNull = No description defined.
-           }
-        }
+            page.10 = COA_INT
+            page.10 {
+               10 = TEXT
+               10 {
+                  stdWrap.field = description
+                  stdWrap.ifNull = No description defined.
+               }
+            }
 
-    This example shows the content of the field description or, if that
-    field contains the value :php:`NULL`, the text "No description defined.".
+        This example shows the content of the field description or, if that
+        field contains the value :php:`NULL`, the text "No description defined.".
 
 
-..  _stdwrap-ifEmpty:
+    ..  _stdwrap-ifEmpty:
 
-ifEmpty
-~~~~~~~
+    ..  confval:: ifEmpty
+        :name: stdwrap-ifEmpty
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  confval:: ifEmpty
-    :name: stdwrap-ifEmpty
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        If the trimmed content is empty at this point, the content is loaded
+        with :typoscript:`ifEmpty`. Zeros are treated as empty values!
 
-    If the trimmed content is empty at this point, the content is loaded
-    with :typoscript:`ifEmpty`. Zeros are treated as empty values!
 
+    ..  _stdwrap-ifBlank:
 
-..  _stdwrap-ifBlank:
+    ..  confval:: ifBlank
+        :name: stdwrap-ifBlank
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-ifBlank
-~~~~~~~
+        Same as :typoscript:`ifEmpty` but the check is done against ''. Zeros are not
+        treated as blank values!
 
-..  confval:: ifBlank
-    :name: stdwrap-ifBlank
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-    Same as :typoscript:`ifEmpty` but the check is done against ''. Zeros are not
-    treated as blank values!
+    ..  _stdwrap-listNum:
 
+    ..  confval:: listNum
+        :name: stdwrap-listNum
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  _stdwrap-listNum:
+        Explodes the current content :ref:`stdwrap-listNum-splitChar`
+        (Default: `,`) and returns the object specified by `listNum`.
 
-listNum
-~~~~~~~
+        Possible values:
 
-..  confval:: listNum
-    :name: stdwrap-listNum
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        :typoscript:`last`
+            The special keyword :typoscript:`last` is replaced with the index of
+            the last element in the exploded content.
 
-    Explodes the current content :ref:`stdwrap-listNum-splitChar`
-    (Default: `,`) and returns the object specified by `listNum`.
+        :typoscript:`rand`
+            The special keyword :typoscript:`rand` is replaced with the index of
+            a random element in the exploded content.
 
-    Possible values:
+        :ref:`calc`
+            After the special keywords are replaced with their according numeric
+            values the
 
-    :typoscript:`last`
-        The special keyword :typoscript:`last` is replaced with the index of
-        the last element in the exploded content.
+        0 - last
+            If the content of `listNum` can be interpreted as integer the according
+            index of the exploded content is returned. Counting starts with 0.
 
-    :typoscript:`rand`
-        The special keyword :typoscript:`rand` is replaced with the index of
-        a random element in the exploded content.
+        .. rubric:: Examples
 
-    :ref:`calc`
-        After the special keywords are replaced with their according numeric
-        values the
+        This would return "item 1":
 
-    0 - last
-        If the content of `listNum` can be interpreted as integer the according
-        index of the exploded content is returned. Counting starts with 0.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    .. rubric:: Examples
+            page.10 = TEXT
+            page.10.value = item 1, item 2, item 3, item 4
+            page.10.listNum = 0
 
-    This would return "item 1":
+        This would return "item 3"
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10 = TEXT
-        page.10.value = item 1, item 2, item 3, item 4
-        page.10.listNum = 0
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    This would return "item 3"
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            page.10 = TEXT
+            page.10.value = item 1, item 2, item 3, item 4
+            page.10.listNum = last – 1
 
-        page.10 = TEXT
-        page.10.value = item 1, item 2, item 3, item 4
-        page.10.listNum = last – 1
 
+        ..  _stdwrap-listNum-splitChar:
 
-..  _stdwrap-listNum-splitChar:
+        ..  confval:: listNum.splitChar
+            :name: stdwrap-listNum-splitChar
+            :type: :ref:`data-type-string`
+            :Default: `,` (comma)
 
-listNum.splitChar
-"""""""""""""""""
+            .. rubric:: Examples
 
-..  confval:: listNum.splitChar
-    :name: stdwrap-listNum-splitChar
-    :type: :ref:`data-type-string`
-    :Default: `,` (comma)
+            Splits the content of the field `subtitle` by the pipe character and returns
+            a random element
 
-    .. rubric:: Examples
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    Splits the content of the field `subtitle` by the pipe character and returns
-    a random element
+                page.5 = COA_INT
+                page.5 {
+                   10 = TEXT
+                   10 {
+                      stdWrap.field = subtitle
+                      stdWrap.listNum = rand
+                      stdWrap.listNum.splitChar = |
+                   }
+                }
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        page.5 = COA_INT
-        page.5 {
-           10 = TEXT
-           10 {
-              stdWrap.field = subtitle
-              stdWrap.listNum = rand
-              stdWrap.listNum.splitChar = |
-           }
-        }
+    ..  _stdwrap-trim:
 
+    ..  confval:: trim
+        :name: stdwrap-trim
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-..  _stdwrap-trim:
+        If set, the PHP-function :php:`trim()` will be used to remove whitespaces
+        around the value.
 
-trim
-~~~~
 
-..  confval:: trim
-    :name: stdwrap-trim
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  _stdwrap-strPad:
 
-    If set, the PHP-function :php:`trim()` will be used to remove whitespaces
-    around the value.
+    ..  confval:: strPad
+        :name: stdwrap-strPad
+        :type: :ref:`strPad`
 
+        Pads the current content to a certain length. You can define the padding
+        characters and the side(s), on which the padding should be added.
 
-..  _stdwrap-strPad:
 
-strPad
-~~~~~~
+    ..  _stdwrap-stdWrap:
 
-..  confval:: strPad
-    :name: stdwrap-strPad
-    :type: :ref:`strPad`
+    ..  confval:: stdWrap
+        :name: stdwrap-stdWrap
+        :type: :ref:`stdWrap`
 
-    Pads the current content to a certain length. You can define the padding
-    characters and the side(s), on which the padding should be added.
+        Recursive call to the :typoscript:`stdWrap` function.
 
 
-..  _stdwrap-stdWrap:
+    ..  _stdwrap-required:
 
-stdWrap
-~~~~~~~
+    ..  confval:: required
+        :name: stdwrap-required
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-..  confval:: stdWrap
-    :name: stdwrap-stdWrap
-    :type: :ref:`stdWrap`
+        This flag requires the content to be set to some value after any
+        content-import and treatment that might have happened until now
+        (data, field, current, listNum, trim). Zero is **not** regarded as
+        empty! Use "if" instead!
 
-    Recursive call to the :typoscript:`stdWrap` function.
+        If the content is empty, "" is returned immediately.
 
 
-..  _stdwrap-required:
+    ..  _stdwrap-if:
 
-required
-~~~~~~~~
+    ..  confval:: if
+        :name: stdwrap-if
+        :type: :ref:`if`
 
-..  confval:: required
-    :name: stdwrap-required
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        If the if-object returns false, stdWrap returns "" immediately.
 
-    This flag requires the content to be set to some value after any
-    content-import and treatment that might have happened until now
-    (data, field, current, listNum, trim). Zero is **not** regarded as
-    empty! Use "if" instead!
 
-    If the content is empty, "" is returned immediately.
+    ..  _stdwrap-fieldRequired:
 
+    ..  confval:: fieldRequired
+        :name: stdwrap-fieldRequired
+        :type: Field name / :ref:`stdWrap`
 
-..  _stdwrap-if:
-
-if
---
-
-..  confval:: if
-    :name: stdwrap-if
-    :type: :ref:`if`
-
-    If the if-object returns false, stdWrap returns "" immediately.
-
-
-..  _stdwrap-fieldRequired:
-
-fieldRequired
-~~~~~~~~~~~~~
-
-..  confval:: fieldRequired
-    :name: stdwrap-fieldRequired
-    :type: Field name / :ref:`stdWrap`
-
-    The value in this field **must** be set.
+        The value in this field **must** be set.
 
 ..  _stdwrap-properties-parsing:
 
 Properties for parsing data
 ---------------------------
 
-..  _stdwrap-csConv:
-
-csConv
-~~~~~~
-
-..  confval:: csConv
-    :name: stdwrap-csConv
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
-
-    Convert the charset of the string from the charset given as value to
-    the current rendering charset of the frontend (UTF-8).
+..  confval-menu::
+    :name: stdwrap-parse
+    :display: table
+    :type:
 
+    ..  _stdwrap-csConv:
 
-..  _stdwrap-parseFunc:
+    ..  confval:: csConv
+        :name: stdwrap-csConv
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-parseFunc
-~~~~~~~~~
+        Convert the charset of the string from the charset given as value to
+        the current rendering charset of the frontend (UTF-8).
 
-..  confval:: parseFunc
-    :name: stdwrap-parseFunc
-    :type: object path reference / :ref:`parsefunc` / :ref:`stdWrap`
 
-    Processing instructions for the content.
+    ..  _stdwrap-parseFunc:
 
-    ..  Note::
-        If you enter a string as value, this will be taken as a
-        reference to an object path globally in the TypoScript object tree.
-        This will be the basis configuration for parseFunc merged with any
-        properties you add here. It works exactly like references does for
-        content elements.
+    ..  confval:: parseFunc
+        :name: stdwrap-parseFunc
+        :type: object path reference / :ref:`parsefunc` / :ref:`stdWrap`
 
-    ..  rubric:: Examples
+        Processing instructions for the content.
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
-
-        page.10 {
-            parseFunc = < lib.parseFunc_RTE
-            parseFunc.tags.myTag = TEXT
-            parseFunc.tags.myTag.value = This will be inserted when &lt;myTag&gt; is found!
-        }
-
-..  _stdwrap-parseFunc-sanitization:
+        ..  Note::
+            If you enter a string as value, this will be taken as a
+            reference to an object path globally in the TypoScript object tree.
+            This will be the basis configuration for parseFunc merged with any
+            properties you add here. It works exactly like references does for
+            content elements.
 
-Sanitization
-""""""""""""
+        ..  rubric:: Examples
 
-:ref:`stdwrap-htmlSanitize` is enabled by default when
-:ref:`stdwrap-parseFunc` is invoked. This also includes the Fluid Viewhelper
-:html:`<f:format.html>`, since it invokes :ref:`stdwrap-parseFunc`
-directly using :typoscript:`lib.parseFunc_RTE`.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-The following example shows how to disable the sanitization behavior that is
-enabled by default. This is not recommended, but it can be disabled when required.
+            page.10 {
+                parseFunc = < lib.parseFunc_RTE
+                parseFunc.tags.myTag = TEXT
+                parseFunc.tags.myTag.value = This will be inserted when &lt;myTag&gt; is found!
+            }
 
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  _stdwrap-parseFunc-sanitization:
 
-    // either disable globally
-    lib.parseFunc.htmlSanitize = 0
-    lib.parseFunc_RTE.htmlSanitize = 0
+    :ref:`stdwrap-htmlSanitize` is enabled by default when
+    :ref:`stdwrap-parseFunc` is invoked. This also includes the Fluid Viewhelper
+    :html:`<f:format.html>`, since it invokes :ref:`stdwrap-parseFunc`
+    directly using :typoscript:`lib.parseFunc_RTE`.
 
-    // or disable individually per use case
-    10 = TEXT
-    10 {
-        value = <div><img src="invalid.file" onerror="alert(1)"></div>
-        parseFunc =< lib.parseFunc_RTE
-        parseFunc.htmlSanitize = 0
-    }
+    The following example shows how to disable the sanitization behavior that is
+    enabled by default. This is not recommended, but it can be disabled when required.
 
-Since any invocation of :typoscript:`stdWrap.parseFunc` triggers HTML
-sanitization automatically; unless explicitly disabled
-the following example causes a lot of generated markup to be sanitized and can be
-solved by explicitly disabling it with :typoscript:`htmlSanitize = 0`.
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        // either disable globally
+        lib.parseFunc.htmlSanitize = 0
+        lib.parseFunc_RTE.htmlSanitize = 0
 
-    10 = FLUIDTEMPLATE
-    10 {
-        templateRootPaths {
-            // ...
-        }
-        variables {
-            // ...
-        }
-        stdWrap.parseFunc {
-            // replace --- with soft-hyphen
-            short.--- = &shy;
-            // sanitization of ALL MARKUP is NOT DESIRED here
-            htmlSanitize = 0
+        // or disable individually per use case
+        10 = TEXT
+        10 {
+            value = <div><img src="invalid.file" onerror="alert(1)"></div>
+            parseFunc =< lib.parseFunc_RTE
+            parseFunc.htmlSanitize = 0
         }
-    }
-
-..  _stdwrap-htmlparser:
-
-HTMLparser
-~~~~~~~~~~
-
-..  confval:: HTMLparser
-    :name: stdwrap-htmlparser
-    :type: :ref:`data-type-boolean` / :ref:`htmlparser` / :ref:`stdWrap`
-
-    This object allows you to parse the HTML-content and perform all kinds of
-    advanced filtering on the content.
-
-    Value must be set and properties are those of :ref:`htmlparser`.
-
-    (See :ref:`t3coreapi:rte` for more information about RTE transformations)
-
-
-..  _stdwrap-split:
-
-split
-~~~~~
-
-..  confval:: split
-    :name: stdwrap-split
-    :type: :ref:`split` / :ref:`stdWrap`
-
-
-..  _stdwrap-replacement:
-
-replacement
-~~~~~~~~~~~
-
-..  confval:: replacement
-    :name: stdwrap-replacement
-    :type: :ref:`replacement` / :ref:`stdWrap`
-
-    Performs an ordered search/replace on the current content with the
-    possibility of using PCRE regular expressions. An array with numeric
-    indices defines the order of actions and thus allows multiple
-    replacements at once.
-
-
-..  _stdwrap-prioriCalc:
-
-prioriCalc
-~~~~~~~~~~
-
-..  confval:: prioriCalc
-    :name: stdwrap-prioriCalc
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-
-    Calculation of the value using operators -+\*/%^ plus respects
-    priority to + and - operators and parenthesis levels ().
-
-    . (period) is decimal delimiter.
-
-    Returns a doublevalue.
-
-    If :typoscript:`prioriCalc` is set to "intval" an integer is returned.
-
-    There is no error checking and division by zero or other invalid
-    values may generate strange results. Also you should use a proper syntax
-    because future modifications to the function used may allow for more
-    operators and features.
-
-    ..  rubric:: Examples
-
-    ..  code-block:: none
-        :caption: Example Output for different calculations
-
-        100%7 = 2
-        -5*-4 = 20
-        +6^2 = 36
-        6 ^(1+1) = 36
-        -5*-4+6^2-100%7 = 54
-        -5 * (-4+6) ^ 2 - 100%7 = 98
-        -5 * ((-4+6) ^ 2) - 100%7 = -22
-
-
-..  _stdwrap-char:
-
-char
-~~~~
 
-..  confval:: char
-    :name: stdwrap-char
-    :type: :ref:`data-type-integer` / :ref:`stdWrap`
+    Since any invocation of :typoscript:`stdWrap.parseFunc` triggers HTML
+    sanitization automatically; unless explicitly disabled
+    the following example causes a lot of generated markup to be sanitized and can be
+    solved by explicitly disabling it with :typoscript:`htmlSanitize = 0`.
 
-    Content is set to :php:`chr(*value*)`. This returns a one-character
-    string containing the character specified by ascii code. Reliable
-    results will be obtained only for character codes in the integer
-    range 0 - 127. See
-    `the PHP manual <https://php.net/manual/en/function.chr.php>`_:
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  code-block:: php
+        10 = FLUIDTEMPLATE
+        10 {
+            templateRootPaths {
+                // ...
+            }
+            variables {
+                // ...
+            }
+            stdWrap.parseFunc {
+                // replace --- with soft-hyphen
+                short.--- = &shy;
+                // sanitization of ALL MARKUP is NOT DESIRED here
+                htmlSanitize = 0
+            }
+        }
 
-        $content = chr((int)$conf['char']);
+    ..  _stdwrap-htmlparser:
 
+    ..  confval:: HTMLparser
+        :name: stdwrap-htmlparser
+        :type: :ref:`data-type-boolean` / :ref:`htmlparser` / :ref:`stdWrap`
 
-..  _stdwrap-intval:
+        This object allows you to parse the HTML-content and perform all kinds of
+        advanced filtering on the content.
 
-intval
-~~~~~~
+        Value must be set and properties are those of :ref:`htmlparser`.
 
-..  confval:: intval
-    :name: stdwrap-intval
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        (See :ref:`t3coreapi:rte` for more information about RTE transformations)
 
-    PHP function :php:`intval()` returns an integer:
 
-    ..  code-block:: php
+    ..  _stdwrap-split:
 
-        $content = intval($content);
+    ..  confval:: split
+        :name: stdwrap-split
+        :type: :ref:`split` / :ref:`stdWrap`
 
 
-..  _stdwrap-hash:
+    ..  _stdwrap-replacement:
 
-hash
-~~~~
+    ..  confval:: replacement
+        :name: stdwrap-replacement
+        :type: :ref:`replacement` / :ref:`stdWrap`
 
-..  confval:: hash
-    :name: stdwrap-hash
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        Performs an ordered search/replace on the current content with the
+        possibility of using PCRE regular expressions. An array with numeric
+        indices defines the order of actions and thus allows multiple
+        replacements at once.
 
-    Returns a hashed value of the current content. Set to one of the
-    algorithms which are available in PHP. For a list of supported
-    algorithms see https://www.php.net/manual/en/function.hash-algos.php.
 
-    ..  rubric:: Examples
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  _stdwrap-prioriCalc:
 
-        page.10 = TEXT
-        page.10 {
-           value = test@example.org
-           stdWrap.hash = md5
-           stdWrap.wrap = <img src="https://www.gravatar.com/avatar/|" />
-        }
+    ..  confval:: prioriCalc
+        :name: stdwrap-prioriCalc
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
+        Calculation of the value using operators -+\*/%^ plus respects
+        priority to + and - operators and parenthesis levels ().
 
-..  _stdwrap-round:
+        . (period) is decimal delimiter.
 
-round
-~~~~~
+        Returns a doublevalue.
 
-..  confval:: round
-    :name: stdwrap-round
-    :type: :ref:`round` / :ref:`stdWrap`
+        If :typoscript:`prioriCalc` is set to "intval" an integer is returned.
 
-    Round the value with the selected method to the given number of
-    decimals.
+        There is no error checking and division by zero or other invalid
+        values may generate strange results. Also you should use a proper syntax
+        because future modifications to the function used may allow for more
+        operators and features.
 
+        ..  rubric:: Examples
 
-..  _stdwrap-numberFormat:
+        ..  code-block:: none
+            :caption: Example Output for different calculations
 
-numberFormat
-~~~~~~~~~~~~
+            100%7 = 2
+            -5*-4 = 20
+            +6^2 = 36
+            6 ^(1+1) = 36
+            -5*-4+6^2-100%7 = 54
+            -5 * (-4+6) ^ 2 - 100%7 = 98
+            -5 * ((-4+6) ^ 2) - 100%7 = -22
 
-..  confval:: numberFormat
-    :name: stdwrap-numberFormat
-    :type: :ref:`numberformat`
 
-    Format a float value to any number format you need (e.g. useful for
-    prices).
+    ..  _stdwrap-char:
 
+    ..  confval:: char
+        :name: stdwrap-char
+        :type: :ref:`data-type-integer` / :ref:`stdWrap`
 
-..  _stdwrap-date:
+        Content is set to :php:`chr(*value*)`. This returns a one-character
+        string containing the character specified by ascii code. Reliable
+        results will be obtained only for character codes in the integer
+        range 0 - 127. See
+        `the PHP manual <https://php.net/manual/en/function.chr.php>`_:
 
-date
-~~~~
+        ..  code-block:: php
 
-..  confval:: date
-    :name: stdwrap-date
-    :type: :ref:`data-type-date-conf` / :ref:`stdWrap`
+            $content = chr((int)$conf['char']);
 
-    The content should be data-type "UNIX-time". Returns the content
-    formatted as a date. See the PHP manual (`datetime.format <https://www.php.net/manual/en/datetime.createfromformat.php>`_)
-    for the format codes.
 
+    ..  _stdwrap-intval:
 
-    ..  code-block:: php
+    ..  confval:: intval
+        :name: stdwrap-intval
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-        $content = date($conf['date'], $content);
+        PHP function :php:`intval()` returns an integer:
 
-    Properties:
+        ..  code-block:: php
 
-    **.GMT:** If set, the PHP function `gmdate() <https://www.php.net/gmdate>`_ will be
-    used instead of `date() <https://www.php.net/date>`_.
+            $content = intval($content);
 
-    ..  rubric:: Examples
 
-    Render in human readable form:
+    ..  _stdwrap-hash:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  confval:: hash
+        :name: stdwrap-hash
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-        page.10 = TEXT
-        page.10.value {
-           # format like 2017-05-31 09:08
-           field = tstamp
-           date = Y-m-d H:i
-        }
+        Returns a hashed value of the current content. Set to one of the
+        algorithms which are available in PHP. For a list of supported
+        algorithms see https://www.php.net/manual/en/function.hash-algos.php.
 
-    ..  note::
-        You should consider using the more flexible function
-        :ref:`stdwrap-formattedDate`.
+        ..  rubric:: Examples
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+            page.10 = TEXT
+            page.10 {
+               value = test@example.org
+               stdWrap.hash = md5
+               stdWrap.wrap = <img src="https://www.gravatar.com/avatar/|" />
+            }
 
-..  _stdwrap-strtotime:
 
-strtotime
-~~~~~~~~~
+    ..  _stdwrap-round:
 
-..  confval:: strtotime
-    :name: stdwrap-strtotime
-    :type: :ref:`data-type-string`
+    ..  confval:: round
+        :name: stdwrap-round
+        :type: :ref:`round` / :ref:`stdWrap`
 
-    Allows conversion of formatted dates to timestamp, e.g. to perform date calculations.
+        Round the value with the selected method to the given number of
+        decimals.
 
-    Possible values are :typoscript:`1` or any time string valid as first argument of the PHP :php:`strtotime()` function.
 
-    ..  rubric:: Examples
+    ..  _stdwrap-numberFormat:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  confval:: numberFormat
+        :name: stdwrap-numberFormat
+        :type: :ref:`numberformat`
 
-        lib.date_as_timestamp = TEXT
-        lib.date_as_timestamp {
-           value = 2015-04-15
-           strtotime = 1
-        }
+        Format a float value to any number format you need (e.g. useful for
+        prices).
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        lib.next_weekday = TEXT
-        lib.next_weekday {
-           data = GP:selected_date
-           strtotime = + 2 weekdays
-           strftime = %Y-%m-%d
-        }
+    ..  _stdwrap-date:
 
+    ..  confval:: date
+        :name: stdwrap-date
+        :type: :ref:`data-type-date-conf` / :ref:`stdWrap`
 
-..  _stdwrap-strftime:
+        The content should be data-type "UNIX-time". Returns the content
+        formatted as a date. See the PHP manual (`datetime.format <https://www.php.net/manual/en/datetime.createfromformat.php>`_)
+        for the format codes.
 
-strftime
-~~~~~~~~
 
-..  confval:: strftime
-    :name: stdwrap-strftime
-    :type: :ref:`data-type-strftime-conf` / :ref:`stdWrap`
+        ..  code-block:: php
 
-    Very similar to "date", but using a different format. See the PHP manual (`strftime <https://www.php.net/strftime>`_) for the
-    format codes.
+            $content = date($conf['date'], $content);
 
-    This formatting is useful if the locale is set in advance in the
-    :ref:`CONFIG <config>` object. See there.
+        Properties:
 
-    Properties:
+        **.GMT:** If set, the PHP function `gmdate() <https://www.php.net/gmdate>`_ will be
+        used instead of `date() <https://www.php.net/date>`_.
 
-    .charset
-        Can be set to the charset of the output string if you need to
-        convert it to UTF-8. Default is to take the intelligently guessed
-        charset from :php:`TYPO3\CMS\Core\Charset\CharsetConverter`.
+        ..  rubric:: Examples
 
-    .GMT
-        If set, the PHP function `gmstrftime()
-        <https://www.php.net/gmstrftime>`_ will be used instead of
-        `strftime() <https://www.php.net/strftime>`_.
+        Render in human readable form:
 
-    ..  note::
-        You should consider using the more flexible function
-        :ref:`stdwrap-formattedDate`.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+            page.10 = TEXT
+            page.10.value {
+               # format like 2017-05-31 09:08
+               field = tstamp
+               date = Y-m-d H:i
+            }
 
-..  _stdwrap-formattedDate:
+        ..  note::
+            You should consider using the more flexible function
+            :ref:`stdwrap-formattedDate`.
 
-formattedDate
-~~~~~~~~~~~~~
 
-..  versionadded:: 12.3
+    ..  _stdwrap-strtotime:
 
-..  confval:: formattedDate
-    :name: stdwrap-formattedDate
-    :type: :ref:`data-type-string`
+    ..  confval:: strtotime
+        :name: stdwrap-strtotime
+        :type: :ref:`data-type-string`
 
-    The function renders date and time based on formats/patterns defined by
-    the International Components for Unicode standard (ICU). ICU-based date and
-    time formatting is much more flexible in rendering as
-    :ref:`stdwrap-date` or :ref:`stdwrap-strftime`, as it ships
-    with default patterns for date and time based on the given locale (given
-    examples for locale `en-US` and timezone `America/Los_Angeles`):
+        Allows conversion of formatted dates to timestamp, e.g. to perform date calculations.
 
-    *   `FULL`, for example: `Friday, March 17, 2023 at 3:00:00 AM Pacific Daylight Time`
-    *   `LONG`, for example: `March 17, 2023 at 3:00:00 AM PDT`
-    *   `MEDIUM`, for example: `Mar 17, 2023, 3:00:00 AM`
-    *   `SHORT`, for example: `3/17/23, 3:00 AM`
+        Possible values are :typoscript:`1` or any time string valid as first argument of the PHP :php:`strtotime()` function.
 
-    TYPO3 also adds prepared custom patterns:
+        ..  rubric:: Examples
 
-    *   `FULLDATE`, for example: `Friday, March 17, 2023`
-    *   `FULLTIME`, for example: `3:00:00 AM Pacific Daylight Time`
-    *   `LONGDATE`, for example: `March 17, 2023`
-    *   `LONGTIME`, for example: `3:00:00 AM PDT`
-    *   `MEDIUMDATE`, for example: `Mar 17, 2023`
-    *   `MEDIUMTIME`, for example: `3:00:00 AM`
-    *   `SHORTDATE`, for example: `3/17/23`
-    *   `SHORTTIME`, for example: `3:00 AM`
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  note::
-        You can specify an own pattern to suit your requirements, for example:
-        `qqqq, yyyy` will result in `1st quarter, 2023`. Have a look into the
-        `available options <https://unicode-org.github.io/icu/userguide/format_parse/datetime/#datetime-format-syntax>`__.
+            lib.date_as_timestamp = TEXT
+            lib.date_as_timestamp {
+               value = 2015-04-15
+               strtotime = 1
+            }
 
-    The locale is typically fetched from the
-    :ref:`locale setting <t3coreapi:sitehandling-addingLanguages-locale>` in the
-    site configuration.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    Properties:
+            lib.next_weekday = TEXT
+            lib.next_weekday {
+               data = GP:selected_date
+               strtotime = + 2 weekdays
+               strftime = %Y-%m-%d
+            }
 
-    .locale
-        A locale other than the locale of the site language.
 
-    ..  rubric:: Example: Full German output from a date/time value
+    ..  _data-type-strftime-conf:
+    ..  _stdwrap-strftime:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  confval:: strftime
+        :name: stdwrap-strftime
+        :type: :ref:`data-type-strftime-conf` / :ref:`stdWrap`
 
-        lib.my_formatted_date = TEXT
-        lib.my_formatted_date {
-            value = 2023-03-17 3:00:00
-            formattedDate = FULL
-            # Optional, if a different locale is wanted other than the site language's locale
-            formattedDate.locale = de-DE
-        }
+        Very similar to "date", but using a different format. See the PHP manual (`strftime <https://www.php.net/strftime>`_) for the
+        format codes.
 
-    will result in "Freitag, 17. März 2023 um 03:00:00 Nordamerikanische Westküsten-Sommerzeit".
+        This formatting is useful if the locale is set in advance in the
+        :ref:`CONFIG <config>` object. See there.
 
-    ..  rubric:: Example: Full French output from a relative date value
+        Properties:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        .charset
+            Can be set to the charset of the output string if you need to
+            convert it to UTF-8. Default is to take the intelligently guessed
+            charset from :php:`TYPO3\CMS\Core\Charset\CharsetConverter`.
 
-        lib.my_formatted_date = TEXT
-        lib.my_formatted_date {
-            value = -5 days
-            formattedDate = FULL
-            formattedDate.locale = fr-FR
-        }
+        .GMT
+            If set, the PHP function `gmstrftime()
+            <https://www.php.net/gmstrftime>`_ will be used instead of
+            `strftime() <https://www.php.net/strftime>`_.
 
-    will result in "dimanche 12 mars 2023 à 11:16:44 heure d’été du Pacifique".
+        ..  note::
+            You should consider using the more flexible function
+            :ref:`stdwrap-formattedDate`.
 
-    ..  rubric:: Example: Custom format from a timestamp
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  _stdwrap-formattedDate:
 
-        lib.my_formatted_date = TEXT
-        lib.my_formatted_date {
-            value = 1679022000
-            formattedDate = Y-MM-dd'T'HH:mm:ssZ
-        }
+    ..  confval:: formattedDate
+        :name: stdwrap-formattedDate
+        :type: :ref:`data-type-string`
 
-    will return the date in the ISO 8601 format: "2023-03-17T03:00:00+00:00"
+        The function renders date and time based on formats/patterns defined by
+        the International Components for Unicode standard (ICU). ICU-based date and
+        time formatting is much more flexible in rendering as
+        :ref:`stdwrap-date` or :ref:`stdwrap-strftime`, as it ships
+        with default patterns for date and time based on the given locale (given
+        examples for locale `en-US` and timezone `America/Los_Angeles`):
 
-    ..  note::
-        The timezone will be taken from the setting `date.timezone` in your
-        :file:`php.ini`.
+        *   `FULL`, for example: `Friday, March 17, 2023 at 3:00:00 AM Pacific Daylight Time`
+        *   `LONG`, for example: `March 17, 2023 at 3:00:00 AM PDT`
+        *   `MEDIUM`, for example: `Mar 17, 2023, 3:00:00 AM`
+        *   `SHORT`, for example: `3/17/23, 3:00 AM`
 
+        TYPO3 also adds prepared custom patterns:
 
-..  _stdwrap-age:
+        *   `FULLDATE`, for example: `Friday, March 17, 2023`
+        *   `FULLTIME`, for example: `3:00:00 AM Pacific Daylight Time`
+        *   `LONGDATE`, for example: `March 17, 2023`
+        *   `LONGTIME`, for example: `3:00:00 AM PDT`
+        *   `MEDIUMDATE`, for example: `Mar 17, 2023`
+        *   `MEDIUMTIME`, for example: `3:00:00 AM`
+        *   `SHORTDATE`, for example: `3/17/23`
+        *   `SHORTTIME`, for example: `3:00 AM`
 
-age
-~~~
+        ..  note::
+            You can specify an own pattern to suit your requirements, for example:
+            `qqqq, yyyy` will result in `1st quarter, 2023`. Have a look into the
+            `available options <https://unicode-org.github.io/icu/userguide/format_parse/datetime/#datetime-format-syntax>`__.
 
-..  confval:: age
-    :name: stdwrap-age
-    :type: :ref:`data-type-boolean` or :ref:`data-type-string` / :ref:`stdWrap`
+        The locale is typically fetched from the
+        :ref:`locale setting <t3coreapi:sitehandling-addingLanguages-locale>` in the
+        site configuration.
 
-    If enabled with a "1" (number, integer) the content is seen as a date
-    (UNIX-time) and the difference from present time and the content-time
-    is returned as one of these eight variations:
+        Properties:
 
-    "xx min" or "xx hrs" or "xx days" or "xx yrs" or "xx min" or "xx hour"
-    or "xx day" or "year"
+        .locale
+            A locale other than the locale of the site language.
 
-    The limits between which layout is used are 60 minutes, 24 hours and
-    365 days.
+        ..  rubric:: Example: Full German output from a date/time value
 
-    If you set this property with a non-integer, it is used to format the
-    eight units. The first four values are the plural values and the last
-    four are singular. This is the default string:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    .. code-block:: none
-       :caption: Default string for age format
+            lib.my_formatted_date = TEXT
+            lib.my_formatted_date {
+                value = 2023-03-17 3:00:00
+                formattedDate = FULL
+                # Optional, if a different locale is wanted other than the site language's locale
+                formattedDate.locale = de-DE
+            }
 
-       min| hrs| days| yrs| min| hour| day| year
+        will result in "Freitag, 17. März 2023 um 03:00:00 Nordamerikanische Westküsten-Sommerzeit".
 
-    Set another string if you want to change the units. You may include
-    the "-signs. They are removed anyway, but they make sure that a space
-    which you might want between the number and the unit stays.
+        ..  rubric:: Example: Full French output from a relative date value
 
-    ..  rubric:: Examples
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        lib.ageFormat = TEXT
-        lib.ageFormat.stdWrap.data = page:tstamp
-        lib.ageFormat.stdWrap.age = " Minuten | Stunden | Tage | Jahre | Minute | Stunde | Tag | Jahr"
+            lib.my_formatted_date = TEXT
+            lib.my_formatted_date {
+                value = -5 days
+                formattedDate = FULL
+                formattedDate.locale = fr-FR
+            }
 
+        will result in "dimanche 12 mars 2023 à 11:16:44 heure d’été du Pacifique".
 
-..  _stdwrap-case:
+        ..  rubric:: Example: Custom format from a timestamp
 
-case
-~~~~
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  confval:: case
-    :name: stdwrap-case
-    :type: :ref:`data-type-case` / :ref:`stdWrap`
+            lib.my_formatted_date = TEXT
+            lib.my_formatted_date {
+                value = 1679022000
+                formattedDate = Y-MM-dd'T'HH:mm:ssZ
+            }
 
-    Converts case
+        will return the date in the ISO 8601 format: "2023-03-17T03:00:00+00:00"
 
-    Uses "UTF-8" for the operation.
+        ..  note::
+            The timezone will be taken from the setting `date.timezone` in your
+            :file:`php.ini`.
 
 
-..  _stdwrap-bytes:
+    ..  _stdwrap-age:
 
-bytes
-~~~~~
+    ..  confval:: age
+        :name: stdwrap-age
+        :type: :ref:`data-type-boolean` or :ref:`data-type-string` / :ref:`stdWrap`
 
-..  confval:: bytes
-    :name: stdwrap-bytes
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
-    :Default: iec, 1024
+        If enabled with a "1" (number, integer) the content is seen as a date
+        (UNIX-time) and the difference from present time and the content-time
+        is returned as one of these eight variations:
 
-    This is for number values. When the 'bytes' property is added and set
-    to 'true' then a number will be formatted in 'bytes' style with two
-    decimals like '1.53 KiB' or '1.00 MiB'.
-    Learn about common notations at
-    `Wikipedia "Kibibyte" <https://en.wikipedia.org/wiki/Kibibyte>`__.
-    IEC naming with base 1024 is the default. Use sub-properties for
-    customisation.
+        "xx min" or "xx hrs" or "xx days" or "xx yrs" or "xx min" or "xx hour"
+        or "xx day" or "year"
 
-    .labels = iec
-        This is the default. IEC labels and base 1024 are used.
-        Built in IEC labels are :typoscript:`" | Ki| Mi| Gi| Ti| Pi| Ei| Zi| Yi"`.
-        You need to append a final string like 'B' or '-Bytes' yourself.
+        The limits between which layout is used are 60 minutes, 24 hours and
+        365 days.
 
-    .labels = si
-        In this case SI labels and base 1000 are used.
-        Built in IEC labels are :typoscript:`" | k| M| G| T| P| E| Z| Y"`.
-        You need to append a final string like 'B' yourself.
+        If you set this property with a non-integer, it is used to format the
+        eight units. The first four values are the plural values and the last
+        four are singular. This is the default string:
 
-    .labels = "..."
-        Custom values can be defined as well like with
-        :typoscript:`.labels = " Byte| Kilobyte| Megabyte| Gigabyte"`. Use a
-        vertical bar to separate the labels. Enclose the whole string in
-        double quotes.
+        .. code-block:: none
+           :caption: Default string for age format
 
-    .base = 1000
-        Only with custom labels you can choose to set a base of1000. All
-        other values, including the default, mean base 1024.
+           min| hrs| days| yrs| min| hour| day| year
 
-    ..  attention::
+        Set another string if you want to change the units. You may include
+        the "-signs. They are removed anyway, but they make sure that a space
+        which you might want between the number and the unit stays.
 
-        If the value isn't a number the internal PHP function may issue a
-        warning which - depending on you error handling settings - can
-        interrupt execution. Example:
+        ..  rubric:: Examples
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            lib.ageFormat = TEXT
+            lib.ageFormat.stdWrap.data = page:tstamp
+            lib.ageFormat.stdWrap.age = " Minuten | Stunden | Tage | Jahre | Minute | Stunde | Tag | Jahr"
 
-        page.10 {
-           value = abc
-           bytes = 1
-        }
 
-        will show `0` but may raise a warning or an exception.
+    ..  _data-type-case:
+    ..  _stdwrap-case:
 
-    ..  rubric:: Examples
+    ..  confval:: case
+        :name: stdwrap-case
+        :type: string / :ref:`stdWrap`
 
-    Output value 1000 without special formatting. Shows `1000`:
+        Converts case
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        Uses "UTF-8" for the operation.
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-        }
+        ..  rubric:: Possible values:
 
-    Format value 1000 in IEC style with base=1024. Shows `0.98 Ki`:
+        ============================= ==========================================================
+        Value                         Effect
+        ============================= ==========================================================
+        :typoscript:`upper`           Convert all letters of the string to upper case
+        :typoscript:`lower`           Convert all letters of the string to lower case
+        :typoscript:`capitalize`      Uppercase the first character of each word in the string
+        :typoscript:`ucfirst`         Convert the first letter of the string to upper case
+        :typoscript:`lcfirst`         Convert the first letter of the string to lower case
+        :typoscript:`uppercamelcase`  Convert underscored `upper_camel_case` to `UpperCamelCase`
+        :typoscript:`lowercamelcase`  Convert underscored `lower_camel_case` to `lowerCamelCase`
+        ============================= ==========================================================
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  rubric:: Example
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-        }
+        Code:
 
-    Format value 1000 in IEC style with base=1024 and 'B' supplied by us.
-    Shows `0.98 KiB`:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            10 = TEXT
+            10.value = Hello world!
+            10.case = upper
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           noTrimWrap = ||B|
-        }
+        Result:
 
-    Format value 1000 in SI style with base=1000. Shows `1.00 k`:
+        ..  code-block:: text
+            :caption: Example Output
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            HELLO WORLD!
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           bytes.labels = si
-        }
 
-    Format value 1000 in SI style with base=1000 and 'b' supplied by us.
-    Shows `1.00 kb`:
+    ..  _stdwrap-bytes:
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  confval:: bytes
+        :name: stdwrap-bytes
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        :Default: iec, 1024
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           bytes.labels = si
-           noTrimWrap = ||b|
-        }
+        This is for number values. When the 'bytes' property is added and set
+        to 'true' then a number will be formatted in 'bytes' style with two
+        decimals like '1.53 KiB' or '1.00 MiB'.
+        Learn about common notations at
+        `Wikipedia "Kibibyte" <https://en.wikipedia.org/wiki/Kibibyte>`__.
+        IEC naming with base 1024 is the default. Use sub-properties for
+        customisation.
 
-    Format value 1000 with custom label and base=1000. Shows
-    `1.00 x 1000 Bytes`:
+        .labels = iec
+            This is the default. IEC labels and base 1024 are used.
+            Built in IEC labels are :typoscript:`" | Ki| Mi| Gi| Ti| Pi| Ei| Zi| Yi"`.
+            You need to append a final string like 'B' or '-Bytes' yourself.
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        .labels = si
+            In this case SI labels and base 1000 are used.
+            Built in IEC labels are :typoscript:`" | k| M| G| T| P| E| Z| Y"`.
+            You need to append a final string like 'B' yourself.
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           bytes.labels = " x 1 Byte| x 1000 Bytes"
-           bytes.base = 1000
-        }
+        .labels = "..."
+            Custom values can be defined as well like with
+            :typoscript:`.labels = " Byte| Kilobyte| Megabyte| Gigabyte"`. Use a
+            vertical bar to separate the labels. Enclose the whole string in
+            double quotes.
 
-    Format value 1000 with custom label and base=1000. Shows
-    `1.00 kilobyte (kB)`:
+        .base = 1000
+            Only with custom labels you can choose to set a base of1000. All
+            other values, including the default, mean base 1024.
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  attention::
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           bytes.labels = " byte (B)| kilobyte (kB)| megabyte (MB)| gigabyte (GB)| terabyte (TB)| petabyte (PB)| exabyte (EB)| zettabyte (ZB)| yottabyte YB"
-           bytes.base = 1000
-        }
+            If the value isn't a number the internal PHP function may issue a
+            warning which - depending on you error handling settings - can
+            interrupt execution. Example:
 
-    Format value 1000 with custom label and base=1024. Shows
-    `0.98 kibibyte (KiB)`:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            page.10 {
+               value = abc
+               bytes = 1
+            }
 
-        page = PAGE
-        page.10 = TEXT
-        page.10 {
-           value = 1000
-           bytes = 1
-           bytes.labels = " byte (B)| kibibyte (KiB)| mebibyte (MiB)| gibibyte (GiB)| tebibyte (TiB)| pepibyte (PiB)| exbibyte (EiB)| zebibyte (ZiB)| yobibyte YiB"
-           bytes.base = 1024
-        }
+            will show `0` but may raise a warning or an exception.
 
+        ..  rubric:: Examples
 
-..  _stdwrap-substring:
+        Output value 1000 without special formatting. Shows `1000`:
 
-substring
-~~~~~~~~~
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  confval:: substring
-    :name: stdwrap-substring
-    :type: [p1], [p2] / :ref:`stdWrap`
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+            }
 
-    Returns the substring with [p1] and [p2] sent as the 2nd and 3rd
-    parameter to the PHP `mb_substr <https://www.php.net/mb_substr>`__ function.
+        Format value 1000 in IEC style with base=1024. Shows `0.98 Ki`:
 
-    Uses "UTF-8" for the operation.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+            }
 
+        Format value 1000 in IEC style with base=1024 and 'B' supplied by us.
+        Shows `0.98 KiB`:
 
-..  _stdwrap-cropHTML:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-cropHTML
-~~~~~~~~
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               noTrimWrap = ||B|
+            }
 
-..  confval:: cropHTML
-    :name: stdwrap-cropHTML
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        Format value 1000 in SI style with base=1000. Shows `1.00 k`:
 
-    Crops the content to a certain length. In contrast to :typoscript:`stdWrap.crop` it
-    respects HTML tags. It does not crop inside tags and closes open tags.
-    Entities (like ">") are counted as one char. See :typoscript:`stdWrap.crop` below
-    for a syntax description and examples.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    Note that :typoscript:`stdWrap.crop` should not be used if :typoscript:`stdWrap.cropHTML` is
-    already used.
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               bytes.labels = si
+            }
 
+        Format value 1000 in SI style with base=1000 and 'b' supplied by us.
+        Shows `1.00 kb`:
 
-..  _stdwrap-stripHtml:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-stripHtml
-~~~~~~~~~
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               bytes.labels = si
+               noTrimWrap = ||b|
+            }
 
-..  confval:: stripHtml
-    :name: stdwrap-stripHtml
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        Format value 1000 with custom label and base=1000. Shows
+        `1.00 x 1000 Bytes`:
 
-    Strips all HTML tags.
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               bytes.labels = " x 1 Byte| x 1000 Bytes"
+               bytes.base = 1000
+            }
 
-..  _stdwrap-crop:
+        Format value 1000 with custom label and base=1000. Shows
+        `1.00 kilobyte (kB)`:
 
-crop
-~~~~
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  confval:: crop
-    :name: stdwrap-crop
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               bytes.labels = " byte (B)| kilobyte (kB)| megabyte (MB)| gigabyte (GB)| terabyte (TB)| petabyte (PB)| exabyte (EB)| zettabyte (ZB)| yottabyte YB"
+               bytes.base = 1000
+            }
 
-    Crops the content to a certain length.
+        Format value 1000 with custom label and base=1024. Shows
+        `0.98 kibibyte (KiB)`:
 
-    You can define up to three parameters, of which the third one is
-    optional. The syntax is:
-    [numbers of characters to keep] \| [ellipsis] \| [keep whole words]
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    numbers of characters to keep (integer): Define the number of characters
-    you want to keep. For positive numbers, the first characters from the
-    beginning of the string will be kept, for negative numbers the last
-    characters from the end will be kept.
+            page = PAGE
+            page.10 = TEXT
+            page.10 {
+               value = 1000
+               bytes = 1
+               bytes.labels = " byte (B)| kibibyte (KiB)| mebibyte (MiB)| gibibyte (GiB)| tebibyte (TiB)| pepibyte (PiB)| exbibyte (EiB)| zebibyte (ZiB)| yobibyte YiB"
+               bytes.base = 1024
+            }
 
-    ellipsis (string): The signs to be added instead of the part, which was
-    cropped of. If the number of characters was positive, the string will
-    be *prepended* with the ellipsis, if it was negative, the string will
-    be *appended* with the ellipsis.
 
-    keep whole words (boolean): If set to 0 (default), the string is always
-    cropped directly after the defined number of characters. If set to 1,
-    only complete words are kept. Then a word, which would normally be cut
-    in the middle, is removed completely.
+    ..  _stdwrap-substring:
 
-    ..  rubric:: Examples
+    ..  confval:: substring
+        :name: stdwrap-substring
+        :type: [p1], [p2] / :ref:`stdWrap`
 
-    :typoscript:`20 | ...` => max 20 characters. If more, the value will be truncated
-    to the first 20 characters and prepended with "..."
+        Returns the substring with [p1] and [p2] sent as the 2nd and 3rd
+        parameter to the PHP `mb_substr <https://www.php.net/mb_substr>`__ function.
 
-    :typoscript:`-20 | ...` => max 20 characters. If more, the value will be truncated
-    to the last 20 characters and appended with "..."
+        Uses "UTF-8" for the operation.
 
-    :typoscript:`20 | ... | 1` => max 20 characters. If more, the value will be
-    truncated to the first 20 characters and prepended with "...". If
-    the division is in the middle of a word, the remains of that word is
-    removed.
 
-    Uses "UTF-8" for the operation.
+    ..  _stdwrap-cropHTML:
 
+    ..  confval:: cropHTML
+        :name: stdwrap-cropHTML
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  _stdwrap-rawUrlEncode:
+        Crops the content to a certain length. In contrast to :typoscript:`stdWrap.crop` it
+        respects HTML tags. It does not crop inside tags and closes open tags.
+        Entities (like ">") are counted as one char. See :typoscript:`stdWrap.crop` below
+        for a syntax description and examples.
 
-rawUrlEncode
-~~~~~~~~~~~~
+        Note that :typoscript:`stdWrap.crop` should not be used if :typoscript:`stdWrap.cropHTML` is
+        already used.
 
-..  confval:: rawUrlEncode
-    :name: stdwrap-rawUrlEncode
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    Passes the content through the PHP function `rawurlencode() <https://www.php.net/rawurlencode>`_.
+    ..  _stdwrap-stripHtml:
 
+    ..  confval:: stripHtml
+        :name: stdwrap-stripHtml
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-..  _stdwrap-htmlSpecialChars:
+        Strips all HTML tags.
 
-htmlSpecialChars
-~~~~~~~~~~~~~~~~
 
-..  confval:: htmlSpecialChars
-    :name: stdwrap-htmlSpecialChars
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  _stdwrap-crop:
 
-    Passes the content through the PHP function `htmlspecialchars() <https://www.php.net/htmlspecialchars>`_.
+    ..  confval:: crop
+        :name: stdwrap-crop
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-    Additional property :typoscript:`preserveEntities` will preserve entities so only
-    non-entity characters are affected.
+        Crops the content to a certain length.
 
+        You can define up to three parameters, of which the third one is
+        optional. The syntax is:
+        [numbers of characters to keep] \| [ellipsis] \| [keep whole words]
 
-..  _stdwrap-encodeForJavaScriptValue:
+        numbers of characters to keep (integer): Define the number of characters
+        you want to keep. For positive numbers, the first characters from the
+        beginning of the string will be kept, for negative numbers the last
+        characters from the end will be kept.
 
-encodeForJavaScriptValue
-~~~~~~~~~~~~~~~~~~~~~~~~
+        ellipsis (string): The signs to be added instead of the part, which was
+        cropped of. If the number of characters was positive, the string will
+        be *prepended* with the ellipsis, if it was negative, the string will
+        be *appended* with the ellipsis.
 
-..  confval:: encodeForJavaScriptValue
-    :name: stdwrap-encodeForJavaScriptValue
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        keep whole words (boolean): If set to 0 (default), the string is always
+        cropped directly after the defined number of characters. If set to 1,
+        only complete words are kept. Then a word, which would normally be cut
+        in the middle, is removed completely.
 
-    Encodes content to be used safely inside strings in JavaScript.
-    Characters, which can cause problems inside JavaScript strings, are
-    replaced with their encoded equivalents. The resulting string is
-    already quoted with single quotes.
+        ..  rubric:: Examples
 
-    Passes the content through the core function
-    :php:`\TYPO3\CMS\Core\Utility\GeneralUtility::quoteJSvalue()`.
+        :typoscript:`20 | ...` => max 20 characters. If more, the value will be truncated
+        to the first 20 characters and prepended with "..."
 
-    ..  rubric:: Examples
+        :typoscript:`-20 | ...` => max 20 characters. If more, the value will be truncated
+        to the last 20 characters and appended with "..."
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        :typoscript:`20 | ... | 1` => max 20 characters. If more, the value will be
+        truncated to the first 20 characters and prepended with "...". If
+        the division is in the middle of a word, the remains of that word is
+        removed.
 
-        10 = TEXT
-        10.stdWrap {
-              data = GP:sWord
-              encodeForJavaScriptValue = 1
-              wrap = setSearchWord(|);
-        }
+        Uses "UTF-8" for the operation.
 
 
-..  _stdwrap-doubleBrTag:
+    ..  _stdwrap-rawUrlEncode:
 
-doubleBrTag
-~~~~~~~~~~~
+    ..  confval:: rawUrlEncode
+        :name: stdwrap-rawUrlEncode
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-..  confval:: doubleBrTag
-    :name: stdwrap-doubleBrTag
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        Passes the content through the PHP function `rawurlencode() <https://www.php.net/rawurlencode>`_.
 
-    All double line breaks are substituted with this value.
 
+    ..  _stdwrap-htmlSpecialChars:
 
-..  _stdwrap-br:
+    ..  confval:: htmlSpecialChars
+        :name: stdwrap-htmlSpecialChars
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-br
-~~
+        Passes the content through the PHP function `htmlspecialchars() <https://www.php.net/htmlspecialchars>`_.
 
-..  confval:: br
-    :name: stdwrap-br
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        Additional property :typoscript:`preserveEntities` will preserve entities so only
+        non-entity characters are affected.
 
-    Pass the value through the PHP function `nl2br() <https://www.php.net/nl2br>`__. This
-    converts each line break to a :html:`<br />` or a :html:`<br>` tag depending on doctype.
 
+    ..  _stdwrap-encodeForJavaScriptValue:
 
-..  _stdwrap-brTag:
+    ..  confval:: encodeForJavaScriptValue
+        :name: stdwrap-encodeForJavaScriptValue
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-brTag
-~~~~~
+        Encodes content to be used safely inside strings in JavaScript.
+        Characters, which can cause problems inside JavaScript strings, are
+        replaced with their encoded equivalents. The resulting string is
+        already quoted with single quotes.
 
-..  confval:: brTag
-    :name: stdwrap-brTag
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+        Passes the content through the core function
+        :php:`\TYPO3\CMS\Core\Utility\GeneralUtility::quoteJSvalue()`.
 
-    All ASCII codes of "10" (line feed, LF) are substituted with the
-    *value*, which has been provided in this property.
+        ..  rubric:: Examples
 
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  _stdwrap-encapsLines:
+            10 = TEXT
+            10.stdWrap {
+                  data = GP:sWord
+                  encodeForJavaScriptValue = 1
+                  wrap = setSearchWord(|);
+            }
 
-encapsLines
-~~~~~~~~~~~
 
-..  confval:: encapsLines
-    :name: stdwrap-encapsLines
-    :type: :ref:`encapslines` / :ref:`stdWrap`
+    ..  _stdwrap-doubleBrTag:
 
-    Lets you split the content by :php:`chr(10)` and process each line
-    independently. Used to format content made with the RTE.
+    ..  confval:: doubleBrTag
+        :name: stdwrap-doubleBrTag
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
+        All double line breaks are substituted with this value.
 
-..  _stdwrap-keywords:
 
-keywords
-~~~~~~~~
+    ..  _stdwrap-br:
 
-..  confval:: keywords
-    :name: stdwrap-keywords
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  confval:: br
+        :name: stdwrap-br
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    Splits the content by characters "," ";" and php:`chr(10)` (return), trims
-    each value and returns a comma-separated list of the values.
+        Pass the value through the PHP function `nl2br() <https://www.php.net/nl2br>`__. This
+        converts each line break to a :html:`<br />` or a :html:`<br>` tag depending on doctype.
 
 
-..  _stdwrap-innerWrap:
+    ..  _stdwrap-brTag:
 
-innerWrap
-~~~~~~~~~
+    ..  confval:: brTag
+        :name: stdwrap-brTag
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-..  confval:: innerWrap
-    :name: stdwrap-innerWrap
-    :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
+        All ASCII codes of "10" (line feed, LF) are substituted with the
+        *value*, which has been provided in this property.
 
-    Wraps the content.
 
+    ..  _stdwrap-encapsLines:
 
-..  _stdwrap-innerWrap2:
+    ..  confval:: encapsLines
+        :name: stdwrap-encapsLines
+        :type: :ref:`encapslines` / :ref:`stdWrap`
 
-innerWrap2
-~~~~~~~~~~
+        Lets you split the content by :php:`chr(10)` and process each line
+        independently. Used to format content made with the RTE.
 
-..  confval:: innerWrap2
-    :name: stdwrap-innerWrap2
-    :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
 
-    Same as :typoscript:`innerWrap` (but watch the order in which they are executed).
+    ..  _stdwrap-keywords:
 
+    ..  confval:: keywords
+        :name: stdwrap-keywords
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-..  _stdwrap-preCObject:
+        Splits the content by characters "," ";" and php:`chr(10)` (return), trims
+        each value and returns a comma-separated list of the values.
 
-preCObject
-~~~~~~~~~~
 
-..  confval:: preCObject
-    :name: stdwrap-preCObject
-    :type: :ref:`data-type-cobject`
+..  _stdwrap-properties-wrap:
 
-    :ref:`stdwrap-cObject` prepended the content.
-
-
-..  _stdwrap-postCObject:
-
-postCObject
-~~~~~~~~~~~
+Properties for wrapping data
+----------------------------
 
-..  confval:: postCObject
-    :name: stdwrap-postCObject
-    :type: :ref:`data-type-cobject`
+..  confval-menu::
+    :name: stdwrap-wrap
+    :display: table
+    :type:
 
-    :ref:`stdwrap-cObject` appended the content.
+    ..  _stdwrap-innerWrap:
 
+    ..  confval:: innerWrap
+        :name: stdwrap-innerWrap
+        :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
 
-..  _stdwrap-wrapAlign:
+        Wraps the content.
 
-wrapAlign
-~~~~~~~~~
 
-..  confval:: wrapAlign
-    :name: stdwrap-wrapAlign
-    :type: :ref:`data-type-align` / :ref:`stdWrap`
+    ..  _stdwrap-innerWrap2:
 
-    Wraps content with :typoscript:`<div style=text-align:[*value*];"> | </div>`
-    *if* align is set.
+    ..  confval:: innerWrap2
+        :name: stdwrap-innerWrap2
+        :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
 
+        Same as :typoscript:`innerWrap` (but watch the order in which they are executed).
 
-..  _stdwrap-typolink:
 
-typolink
-~~~~~~~~
+    ..  _stdwrap-preCObject:
 
-..  confval:: typolink
-    :name: stdwrap-typolink
-    :type: :ref:`typolink` / :ref:`stdWrap`
+    ..  confval:: preCObject
+        :name: stdwrap-preCObject
+        :type: :ref:`data-type-cobject`
 
-    Wraps the content with a link tag.
+        :ref:`stdwrap-cObject` prepended the content.
 
 
-..  _stdwrap-wrap:
+    ..  _stdwrap-postCObject:
 
-wrap
-~~~~
+    ..  confval:: postCObject
+        :name: stdwrap-postCObject
+        :type: :ref:`data-type-cobject`
 
-..  confval:: wrap
-    :name: stdwrap-wrap
-    :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
+        :ref:`stdwrap-cObject` appended the content.
 
-    :typoscript:`splitChar` defines an alternative splitting character (default is "\|"
-    - the vertical line)
 
-..  _stdwrap-noTrimWrap:
+    ..  _data-type-align:
+    ..  _stdwrap-wrapAlign:
 
-noTrimWrap
-~~~~~~~~~~
+    ..  confval:: wrapAlign
+        :name: stdwrap-wrapAlign
+        :type: string / :ref:`stdWrap`
+        :Allowed values: :typoscript:`left`, :typoscript:`center`, :typoscript:`right`
 
-..  confval:: noTrimWrap
-    :name: stdwrap-noTrimWrap
-    :type: "special" wrap /+.splitChar / :ref:`stdWrap`
+        Wraps content with :typoscript:`<div style=text-align:[*value*];"> | </div>`
+        *if* align is set.
 
-    This wraps the content *without* trimming the values. That means that
-    surrounding whitespaces stay included! Note that this kind of wrap
-    does not only need a special character in the middle, but that it also
-    needs the same special character to begin and end the wrap (default
-    for all three is "\|").
 
-    **Additional property:**
+    ..  _stdwrap-typolink:
 
-    :typoscript:`splitChar`
+    ..  confval:: typolink
+        :name: stdwrap-typolink
+        :type: :ref:`typolink` / :ref:`stdWrap`
 
-    Can be set to define an alternative special character. :typoscript:`stdWrap` is
-    available. Default is "\|" - the vertical line. This sub-property is
-    useful in cases when the default special character would be recognized
-    by :ref:`optionsplit` (which takes precedence over :typoscript:`noTrimWrap`).
+        Wraps the content with a link tag.
 
-    ..  rubric:: Examples
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-       page.10.noTrimWrap = | val1 | val2 |
+    ..  _stdwrap-wrap:
 
-    In this example the content with the values val1 and val2 will be
-    wrapped; including the whitespaces.
+    ..  confval:: wrap
+        :name: stdwrap-wrap
+        :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
 
-    ..  rubric:: Examples
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        :typoscript:`splitChar` defines an alternative splitting character (default is "\|"
+        - the vertical line)
 
-       page.10 {
-          noTrimWrap = ^ val1 ^ val2 ^ || ^ val3 ^ val4 ^
-          noTrimWrap.splitChar = ^
-       }
+    ..  _stdwrap-noTrimWrap:
 
-    :ref:`optionsplit` will use the "\|\|" to have two subparts in
-    the first part. In each subpart :typoscript:`noTrimWrap` will then use the "^" as
-    special character.
+    ..  confval:: noTrimWrap
+        :name: stdwrap-noTrimWrap
+        :type: "special" wrap /+.splitChar / :ref:`stdWrap`
 
+        This wraps the content *without* trimming the values. That means that
+        surrounding whitespaces stay included! Note that this kind of wrap
+        does not only need a special character in the middle, but that it also
+        needs the same special character to begin and end the wrap (default
+        for all three is "\|").
 
-..  _stdwrap-wrap2:
+        **Additional property:**
 
-wrap2
-~~~~~
+        :typoscript:`splitChar`
 
-..  confval:: wrap2
-    :name: stdwrap-wrap2
-    :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
+        Can be set to define an alternative special character. :typoscript:`stdWrap` is
+        available. Default is "\|" - the vertical line. This sub-property is
+        useful in cases when the default special character would be recognized
+        by :ref:`optionsplit` (which takes precedence over :typoscript:`noTrimWrap`).
 
-    same as :ref:`stdwrap-wrap` (but watch the order in which they are executed)
+        ..  rubric:: Examples
+        .. code-block:: typoscript
+           :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+           page.10.noTrimWrap = | val1 | val2 |
 
-..  _stdwrap-dataWrap:
+        In this example the content with the values val1 and val2 will be
+        wrapped; including the whitespaces.
 
-dataWrap
-~~~~~~~~
+        ..  rubric:: Examples
+        .. code-block:: typoscript
+           :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  confval:: dataWrap
-    :name: stdwrap-dataWrap
-    :type: mixed / :ref:`stdWrap`
+           page.10 {
+              noTrimWrap = ^ val1 ^ val2 ^ || ^ val3 ^ val4 ^
+              noTrimWrap.splitChar = ^
+           }
 
-    The content is parsed for pairs of curly braces. The content of the
-    curly braces is of the type :ref:`data-type-gettext` and is substituted with the result
-    of :ref:`data-type-gettext`.
+        :ref:`optionsplit` will use the "\|\|" to have two subparts in
+        the first part. In each subpart :typoscript:`noTrimWrap` will then use the "^" as
+        special character.
 
-    ..  rubric:: Examples
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+    ..  _stdwrap-wrap2:
 
-        page.10.dataWrap = <div id="{tsfe : id}"> | </div>
+    ..  confval:: wrap2
+        :name: stdwrap-wrap2
+        :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
 
-    This will produce a :html:`<div>` tag around the content with an id attribute
-    that contains the number of the current page.
+        same as :ref:`stdwrap-wrap` (but watch the order in which they are executed)
 
 
-..  _stdwrap-prepend:
+    ..  _stdwrap-dataWrap:
 
-prepend
-~~~~~~~
+    ..  confval:: dataWrap
+        :name: stdwrap-dataWrap
+        :type: mixed / :ref:`stdWrap`
 
-..  confval:: prepend
-    :name: stdwrap-prepend
-    :type: :ref:`data-type-cobject`
+        The content is parsed for pairs of curly braces. The content of the
+        curly braces is of the type :ref:`data-type-gettext` and is substituted with the result
+        of :ref:`data-type-gettext`.
 
-    :ref:`stdwrap-cObject` prepended to content (before)
+        ..  rubric:: Examples
 
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  _stdwrap-append:
+            page.10.dataWrap = <div id="{tsfe : id}"> | </div>
 
-append
-~~~~~~
+        This will produce a :html:`<div>` tag around the content with an id attribute
+        that contains the number of the current page.
 
-..  confval:: append
-    :name: stdwrap-append
-    :type: :ref:`data-type-cobject`
 
-    :ref:`stdwrap-cObject` appended to content (after)
+    ..  _stdwrap-prepend:
 
+    ..  confval:: prepend
+        :name: stdwrap-prepend
+        :type: :ref:`data-type-cobject`
 
-..  _stdwrap-wrap3:
+        :ref:`stdwrap-cObject` prepended to content (before)
 
-wrap3
-~~~~~
 
-..  confval:: wrap3
-    :name: stdwrap-wrap3
-    :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
+    ..  _stdwrap-append:
 
-    same as :typoscript:`wrap` (but watch the order in which they are executed)
+    ..  confval:: append
+        :name: stdwrap-append
+        :type: :ref:`data-type-cobject`
 
+        :ref:`stdwrap-cObject` appended to content (after)
 
-..  _stdwrap-orderedStdWrap:
 
-orderedStdWrap
-~~~~~~~~~~~~~~
+    ..  _stdwrap-wrap3:
 
-..  confval:: orderedStdWrap
-    :name: stdwrap-orderedStdWrap
-    :type: Array of numeric keys with / :ref:`stdWrap` each
+    ..  confval:: wrap3
+        :name: stdwrap-wrap3
+        :type: :ref:`wrap <data-type-wrap>` /+.splitChar / :ref:`stdWrap`
 
-    Execute multiple :typoscript:`stdWrap` statements in a freely selectable order. The order
-    is determined by the numeric order of the keys. This allows to use multiple
-    stdWrap statements without having to remember the rather complex sorting
-    order in which the :typoscript:`stdWrap` functions are executed.
+        same as :typoscript:`wrap` (but watch the order in which they are executed)
 
-    ..  rubric:: Examples
-
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        10 = TEXT
-        10.value = a
-        10.stdWrap.orderedStdWrap {
-           30.wrap = |.
+    ..  _stdwrap-orderedStdWrap:
 
-           10.wrap = is | working
-           10.innerWrap = &nbsp;|&nbsp;
+    ..  confval:: orderedStdWrap
+        :name: stdwrap-orderedStdWrap
+        :type: Array of numeric keys with / :ref:`stdWrap` each
 
-           20.wrap = This|solution
-           20.stdWrap.wrap = &nbsp;|&nbsp;
-        }
+        Execute multiple :typoscript:`stdWrap` statements in a freely selectable order. The order
+        is determined by the numeric order of the keys. This allows to use multiple
+        stdWrap statements without having to remember the rather complex sorting
+        order in which the :typoscript:`stdWrap` functions are executed.
 
-    In this example orderedStdWrap is executed on the value "a".
-    :typoscript:`10.innerWrap` is executed first, followed by :typoscript:`10.wrap`.
-    Then the next key is processed which is 20. Afterwards :typoscript:`30.wrap`
-    is executed on what already was created.
+        ..  rubric:: Examples
 
-    This results in "This is a working solution."
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+            10 = TEXT
+            10.value = a
+            10.stdWrap.orderedStdWrap {
+               30.wrap = |.
 
-..  _stdwrap-outerWrap:
+               10.wrap = is | working
+               10.innerWrap = &nbsp;|&nbsp;
 
-outerWrap
-~~~~~~~~~
+               20.wrap = This|solution
+               20.stdWrap.wrap = &nbsp;|&nbsp;
+            }
 
-..  confval:: outerWrap
-    :name: stdwrap-outerWrap
-    :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
+        In this example orderedStdWrap is executed on the value "a".
+        :typoscript:`10.innerWrap` is executed first, followed by :typoscript:`10.wrap`.
+        Then the next key is processed which is 20. Afterwards :typoscript:`30.wrap`
+        is executed on what already was created.
 
-    Wraps the complete content
+        This results in "This is a working solution."
 
 
-..  _stdwrap-insertData:
+    ..  _stdwrap-outerWrap:
 
-insertData
-~~~~~~~~~~
+    ..  confval:: outerWrap
+        :name: stdwrap-outerWrap
+        :type: :ref:`wrap <data-type-wrap>` / :ref:`stdWrap`
 
-..  confval:: insertData
-    :name: stdwrap-insertData
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+        Wraps the complete content
 
-    If set, then the content string is parsed like :typoscript:`dataWrap` above.
 
-    ..  rubric:: Examples
+    ..  _stdwrap-insertData:
 
-    Displays the page title:
+    ..  confval:: insertData
+        :name: stdwrap-insertData
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    .. code-block:: typoscript
-       :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        If set, then the content string is parsed like :typoscript:`dataWrap` above.
 
-       10 = TEXT
-       10.value = This is the page title: {page:title}
-       10.stdWrap.insertData = 1
+        ..  rubric:: Examples
 
-       # TEXT is already stdWrapable, so we can also use insertData right away
-       20 = TEXT
-       20.value = <link rel="preload" href="{path : EXT:site/Resources/Public/Fonts/Roboto.woff2}" as="font" type="font/woff2" crossorigin="anonymous">
-       20.insertData = 1
+        Displays the page title:
 
-..  warning::
-    Never use this on content that can be edited in the backend. This allows editors to disclose
-    normally hidden information. Never use this to insert data into wraps.
-    Use :ref:`stdwrap-dataWrap` instead.
+        .. code-block:: typoscript
+           :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
+           10 = TEXT
+           10.value = This is the page title: {page:title}
+           10.stdWrap.insertData = 1
 
-..  _stdwrap-postUserFunc:
+           # TEXT is already stdWrapable, so we can also use insertData right away
+           20 = TEXT
+           20.value = <link rel="preload" href="{path : EXT:site/Resources/Public/Fonts/Roboto.woff2}" as="font" type="font/woff2" crossorigin="anonymous">
+           20.insertData = 1
 
-postUserFunc
-~~~~~~~~~~~~
+    ..  warning::
+        Never use this on content that can be edited in the backend. This allows editors to disclose
+        normally hidden information. Never use this to insert data into wraps.
+        Use :ref:`stdwrap-dataWrap` instead.
 
-..  confval:: postUserFunc
-    :name: stdwrap-postUserFunc
-    :type: :ref:`data-type-function-name`
 
-    Calls the provided PHP function. If you specify the name with a '->'
-    in it, then it is interpreted as a call to a method in a class.
+    ..  _stdwrap-postUserFunc:
 
-    Two parameters are sent to the PHP function: As first parameter a
-    content variable, which contains the current content. This is the
-    value to be processed. As second parameter any sub-properties of
-    :typoscript:`postUserFunc` are provided to the function.
+    ..  confval:: postUserFunc
+        :name: stdwrap-postUserFunc
+        :type: :ref:`data-type-function-name`
 
-    The description of the :typoscript:`cObject` :ref:`USER <cobj-user>` contains some
-    more in-depth information.
+        Calls the provided PHP function. If you specify the name with a '->'
+        in it, then it is interpreted as a call to a method in a class.
 
-    ..  rubric:: Examples
+        Two parameters are sent to the PHP function: As first parameter a
+        content variable, which contains the current content. This is the
+        value to be processed. As second parameter any sub-properties of
+        :typoscript:`postUserFunc` are provided to the function.
 
-    You can paste this example directly into a new template record:
+        The description of the :typoscript:`cObject` :ref:`USER <cobj-user>` contains some
+        more in-depth information.
 
-    ..  literalinclude:: _StdWrap/_UserFunction.typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  rubric:: Examples
 
-    Your methods will get the parameters :php:`$content` and :php:`$conf`
-    (in that order) and need to return a string.
+        You can paste this example directly into a new template record:
 
-    ..  literalinclude:: _StdWrap/_UserFunction.php
-        :caption: EXT:site_package/Classes/UserFunctions/YourClass.php
+        ..  literalinclude:: _StdWrap/_UserFunction.typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    For :typoscript:`page.10` the content, which is present when
-    :typoscript:`postUserFunc` is executed, will be given to the PHP function
-    :php:`reverseString()`. The result will be `!DLROW OLLEH`.
+        Your methods will get the parameters :php:`$content` and :php:`$conf`
+        (in that order) and need to return a string.
 
-    The content of :typoscript:`page.20` will be processed by the function
-    :php:`reverseString()` from the class :php:`YourClass`. This also returns
-    the text `!DLROW OLLEH`, but wrapped into a link to the page with the ID 11.
-    The result will be :html:`<a href="/path/to/page/id/11">!DLROW OLLEH</a>`.
+        ..  literalinclude:: _StdWrap/_UserFunction.php
+            :caption: EXT:site_package/Classes/UserFunctions/YourClass.php
 
-    Note how in the second example :php:`$this->cObj`, the reference to the
-    calling :typoscript:`cObject`, is utilised to use functions from
-    :php:`ContentObjectRenderer` class!
+        For :typoscript:`page.10` the content, which is present when
+        :typoscript:`postUserFunc` is executed, will be given to the PHP function
+        :php:`reverseString()`. The result will be `!DLROW OLLEH`.
 
+        The content of :typoscript:`page.20` will be processed by the function
+        :php:`reverseString()` from the class :php:`YourClass`. This also returns
+        the text `!DLROW OLLEH`, but wrapped into a link to the page with the ID 11.
+        The result will be :html:`<a href="/path/to/page/id/11">!DLROW OLLEH</a>`.
 
-..  _stdwrap-postUserFuncInt:
+        Note how in the second example :php:`$this->cObj`, the reference to the
+        calling :typoscript:`cObject`, is utilised to use functions from
+        :php:`ContentObjectRenderer` class!
 
-postUserFuncInt
-~~~~~~~~~~~~~~~
 
-..  confval:: postUserFuncInt
-    :name: stdwrap-postUserFuncInt
-    :type: :ref:`data-type-function-name`
+    ..  _stdwrap-postUserFuncInt:
 
-    Calls the provided PHP function. If you specify the name with a '->'
-    in it, then it is interpreted as a call to a method in a class.
+    ..  confval:: postUserFuncInt
+        :name: stdwrap-postUserFuncInt
+        :type: :ref:`data-type-function-name`
 
-    Two parameters are sent to the PHP function: As first parameter a
-    content variable, which contains the current content. This is the
-    value to be processed. As second parameter any sub-properties of
-    postUserFuncInt are provided to the function.
+        Calls the provided PHP function. If you specify the name with a '->'
+        in it, then it is interpreted as a call to a method in a class.
 
-    The result will be rendered non-cached, outside the main
-    page-rendering. Please see the description of the :typoscript:`cObject`
-    :ref:`USER_INT <cobj-user-int>`.
+        Two parameters are sent to the PHP function: As first parameter a
+        content variable, which contains the current content. This is the
+        value to be processed. As second parameter any sub-properties of
+        postUserFuncInt are provided to the function.
 
-    Supplied by Jens Ellerbrock
+        The result will be rendered non-cached, outside the main
+        page-rendering. Please see the description of the :typoscript:`cObject`
+        :ref:`USER_INT <cobj-user-int>`.
 
+        Supplied by Jens Ellerbrock
 
-..  _stdwrap-prefixComment:
 
-prefixComment
-~~~~~~~~~~~~~
+    ..  _stdwrap-prefixComment:
 
-..  confval:: prefixComment
-    :name: stdwrap-prefixComment
-    :type: :ref:`data-type-string` / :ref:`stdWrap`
+    ..  confval:: prefixComment
+        :name: stdwrap-prefixComment
+        :type: :ref:`data-type-string` / :ref:`stdWrap`
 
-    Prefixes content with an HTML comment with the second part of input
-    string (divided by "\|") where first part is an integer telling how
-    many trailing tabs to put before the comment on a new line.
+        Prefixes content with an HTML comment with the second part of input
+        string (divided by "\|") where first part is an integer telling how
+        many trailing tabs to put before the comment on a new line.
 
-    The content is parsed through :ref:`stdwrap-insertData`.
+        The content is parsed through :ref:`stdwrap-insertData`.
 
-    ..  rubric:: Examples
+        ..  rubric:: Examples
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-        prefixComment = 2 | CONTENT ELEMENT, uid:{field:uid}/{field:CType}
+            prefixComment = 2 | CONTENT ELEMENT, uid:{field:uid}/{field:CType}
 
-    Will indent the comment with 1 tab (and the next line with 2+1 tabs)
+        Will indent the comment with 1 tab (and the next line with 2+1 tabs)
 
 
-..  _stdwrap-htmlSanitize:
+..  _stdwrap-properties-cache:
 
-htmlSanitize
-~~~~~~~~~~~~
+Properties for sanitizing and caching data
+------------------------------------------
 
-..  confval:: htmlSanitize
-    :name: stdwrap-htmlSanitize
-    :type: :ref:`data-type-boolean` / array with key "build"
+..  confval-menu::
+    :name: stdwrap-cache
+    :display: table
+    :type:
 
-    The property controls the sanitization and removal of XSS from markup. It
-    strips tags, attributes and values that are not explicitly allowed.
+    ..  _stdwrap-htmlSanitize:
 
-    * :typoscript:`htmlSanitize = [boolean]`: whether to invoke sanitization
-      (enabled per default when invoked via :typoscript:`stdWrap.parseFunc`).
-    * :typoscript:`htmlSanitize.build = [string]`: defines which specific builder
-      (must be an instance of :php:`\TYPO3\HtmlSanitizer\Builder\BuilderInterface`)
-      to be used for building a :php:`\TYPO3\HtmlSanitizer\Sanitizer` instance
-      using a particular :php:`\TYPO3\HtmlSanitizer\Behavior`. This can either be
-      a fully qualified class name or the name of a preset as defined in
-      :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['htmlSanitizer']` - per default,
-      :php:`\TYPO3\CMS\Core\Html\DefaultSanitizerBuilder` is used.
+    ..  confval:: htmlSanitize
+        :name: stdwrap-htmlSanitize
+        :type: :ref:`data-type-boolean` / array with key "build"
 
-    ..  rubric:: Examples
+        The property controls the sanitization and removal of XSS from markup. It
+        strips tags, attributes and values that are not explicitly allowed.
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+        * :typoscript:`htmlSanitize = [boolean]`: whether to invoke sanitization
+          (enabled per default when invoked via :typoscript:`stdWrap.parseFunc`).
+        * :typoscript:`htmlSanitize.build = [string]`: defines which specific builder
+          (must be an instance of :php:`\TYPO3\HtmlSanitizer\Builder\BuilderInterface`)
+          to be used for building a :php:`\TYPO3\HtmlSanitizer\Sanitizer` instance
+          using a particular :php:`\TYPO3\HtmlSanitizer\Behavior`. This can either be
+          a fully qualified class name or the name of a preset as defined in
+          :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['htmlSanitizer']` - per default,
+          :php:`\TYPO3\CMS\Core\Html\DefaultSanitizerBuilder` is used.
 
-        10 = TEXT
-        10 {
-            value = <div><img src="invalid.file" onerror="alert(1)"></div>
-            htmlSanitize = 1
-        }
+        ..  rubric:: Examples
 
-    will result in the following output:
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-    ..  code-block:: html
+            10 = TEXT
+            10 {
+                value = <div><img src="invalid.file" onerror="alert(1)"></div>
+                htmlSanitize = 1
+            }
 
-        <div><img src="invalid.file"></div>
+        will result in the following output:
 
-    The following code is equivalent to above, but with a builder specified:
+        ..  code-block:: html
 
-    ..  code-block:: typoscript
-        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+            <div><img src="invalid.file"></div>
 
-        10 = TEXT
-        10 {
-            value = <div><img src="invalid.file" onerror="alert(1)"></div>
-            htmlSanitize = 1
-            // Use either "default" for the default builder
-            htmlSanitize.build = default
-            // or use the full class name of the default builder
-            // htmlSanitize.build = TYPO3\CMS\Core\Html\DefaultSanitizerBuilder
-        }
+        The following code is equivalent to above, but with a builder specified:
 
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
-..  _stdwrap-cache:
+            10 = TEXT
+            10 {
+                value = <div><img src="invalid.file" onerror="alert(1)"></div>
+                htmlSanitize = 1
+                // Use either "default" for the default builder
+                htmlSanitize.build = default
+                // or use the full class name of the default builder
+                // htmlSanitize.build = TYPO3\CMS\Core\Html\DefaultSanitizerBuilder
+            }
 
-cache
-~~~~~
 
-..  confval:: cache
-    :name: stdwrap-cache
-    :type: :ref:`cache`
+    ..  _stdwrap-cache:
 
-    Caches rendered content in the caching framework.
+    ..  confval:: cache
+        :name: stdwrap-cache
+        :type: :ref:`cache`
 
+        Caches rendered content in the caching framework.
 
-..  _stdwrap-debug:
+..  _stdwrap-properties-debug:
 
-debug
-~~~~~
+Properties for debugging data
+-----------------------------
 
-..  confval:: debug
+..  confval-menu::
     :name: stdwrap-debug
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    :display: table
+    :type:
 
-    Prints content with :php:`HTMLSpecialChars()` and :html:`<pre></pre>`:
-    Useful for debugging which value :typoscript:`stdWrap` actually ends up with,
-    if you are constructing a website with TypoScript.
+    ..  _stdwrap-debug:
 
-.. attention::
+    ..  confval:: debug
+        :name: stdwrap-debug
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-   Only for debugging during development, otherwise output can break.
+        Prints content with :php:`HTMLSpecialChars()` and :html:`<pre></pre>`:
+        Useful for debugging which value :typoscript:`stdWrap` actually ends up with,
+        if you are constructing a website with TypoScript.
 
+    .. attention::
 
-..  _stdwrap-debugFunc:
+       Only for debugging during development, otherwise output can break.
 
-debugFunc
-~~~~~~~~~
 
-..  confval:: debugFunc
-    :name: stdwrap-debugFunc
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  _stdwrap-debugFunc:
 
-    Prints the content directly to browser with the :php:`debug()` function.
+    ..  confval:: debugFunc
+        :name: stdwrap-debugFunc
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    Set to value "2" the content will be printed in a table which looks nicer.
+        Prints the content directly to browser with the :php:`debug()` function.
 
-..  attention::
+        Set to value "2" the content will be printed in a table which looks nicer.
 
-    Only for debugging during development, otherwise output can break.
+    ..  attention::
 
+        Only for debugging during development, otherwise output can break.
 
-..  _stdwrap-debugData:
 
-debugData
-~~~~~~~~~
+    ..  _stdwrap-debugData:
 
-..  confval:: debugData
-    :name: stdwrap-debugData
-    :type: :ref:`data-type-boolean` / :ref:`stdWrap`
+    ..  confval:: debugData
+        :name: stdwrap-debugData
+        :type: :ref:`data-type-boolean` / :ref:`stdWrap`
 
-    Prints the current data-array, :php:`$cObj->data`, directly to browser. This
-    is where :typoscript:`field` gets data from.
+        Prints the current data-array, :php:`$cObj->data`, directly to browser. This
+        is where :typoscript:`field` gets data from.
 
-..  attention::
+    ..  attention::
 
-    Only for debugging during development, otherwise output can break.
+        Only for debugging during development, otherwise output can break.
 
 .. _stdwrap-examples:
 
diff --git a/Documentation/Functions/Typolink.rst b/Documentation/Functions/Typolink.rst
index 333f1374a..254369e78 100644
--- a/Documentation/Functions/Typolink.rst
+++ b/Documentation/Functions/Typolink.rst
@@ -35,7 +35,7 @@ extTarget
 
 ..  confval:: extTarget
     :name: typolink-extTarget
-    :type: :ref:`data-type-target` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
     :Default: "" (no target set)
 
     Target used for external links
@@ -48,7 +48,7 @@ fileTarget
 
 ..  confval:: fileTarget
     :name: typolink-fileTarget
-    :type: :ref:`data-type-target` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
 
     Target used for file links
 
@@ -87,7 +87,7 @@ target
 
 ..  confval:: target
     :name: typolink-target
-    :type: :ref:`data-type-target` / :ref:`stdwrap`
+    :type: string / :ref:`stdwrap`
 
     Target used for internal links
 
@@ -165,12 +165,7 @@ addQueryString
         query arguments are never added by default. This is the recommended
         behaviour.
 
-        ..  versionchanged:: 12.0
-            Before TYPO3 v12 this setting added all query parameters. To ensure
-            the previous behaviour use :typoscript:`untrusted`.
-
     :typoscript:`untrusted`
-        ..  versionadded:: 12.0
 
         Any given query parameters of the current request are added.
 
@@ -887,7 +882,7 @@ record.identifier
 
     The same identifier is used as key in the TypoScript configuration of
     the frontend rendering: :ref:`setup-config-recordLinks` and the :ref:`TSconfig
-    backend link handler configuration <t3tsconfig:pagetcemaintables-linkhandler>`
+    backend link handler configuration <pagetcemaintables-linkhandler>`
 
 ..  _typolink-handler-record-uid:
 
diff --git a/Documentation/Functions/Wrap.rst b/Documentation/Functions/Wrap.rst
new file mode 100644
index 000000000..36f49c4c3
--- /dev/null
+++ b/Documentation/Functions/Wrap.rst
@@ -0,0 +1,34 @@
+..  include:: /Includes.rst.txt
+..  _data-type-wrap:
+
+====
+Wrap
+====
+
+..  confval:: wrap
+    :name: data-type-wrap
+
+    :Syntax: <...> \| </...>
+
+    Used to wrap something. The vertical bar ("|") is the place, where
+    your content will be inserted; the parts on the left and right of the
+    vertical line are placed on the left and right side of the content.
+
+    Spaces between the wrap-parts and the divider ("|") are trimmed off
+    from each part of the wrap.
+
+    If you want to use more sophisticated data functions, then you
+    should use `stdWrap.dataWrap` instead of `wrap`.
+
+    A `wrap` is applied as one of the last of properties
+    a cObject.
+
+    ..  rubric:: Examples
+
+    This will cause the value to be wrapped in a p-tag coloring the
+    value red:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        page.10.wrap = <p class="bg-red"> | </p>
diff --git a/Documentation/Gifbuilder/Colors.rst b/Documentation/Gifbuilder/Colors.rst
new file mode 100644
index 000000000..2f4b34bb7
--- /dev/null
+++ b/Documentation/Gifbuilder/Colors.rst
@@ -0,0 +1,33 @@
+..  include:: /Includes.rst.txt
+..  index:: GIFBUILDER; +calc
+.. _gifbuilder-colors:
+
+===============================
+Colors in TypoScript GIFBUILDER
+===============================
+
+..  _data-type-GraphicColor:
+..  confval:: GraphicColor
+    :name: data-type-GraphicColor
+
+    ..  rubric:: Syntax:
+
+    [colordef] : [modifier]
+
+    Where modifier can be an integer which is added or subtracted to the three
+    RGB-channels or a floating point with an :typoscript:`*` before, which will then
+    multiply the values with that factor.
+    The color can be given as HTML-color or as a comma-separated list of
+    RGB-values (integers). An extra parameter can be given, that will modify the
+    color mathematically:
+
+    ..  rubric:: Examples
+
+    *   :typoscript:`red` (HTML color)
+    *   :typoscript:`#ffeecc` (HTML color as hexadecimal notation)
+    *   :typoscript:`255,0,255` (HTML color as decimal notation)
+
+    *Extra:*
+
+    *   :typoscript:`red : *0.8` ("red" is darkened by factor 0.8)
+    *   :typoscript:`#ffeecc : +16` ("ffeecc" is going to #fffedc because 16 is added)
diff --git a/Documentation/Gifbuilder/Examples.rst b/Documentation/Gifbuilder/Examples.rst
index c096b601a..d9da32974 100644
--- a/Documentation/Gifbuilder/Examples.rst
+++ b/Documentation/Gifbuilder/Examples.rst
@@ -9,6 +9,25 @@ Examples
 ..  contents::
     :local:
 
+..  _gifbuilder-examples-avif:
+
+Using the AVIF format
+=====================
+
+..  versionadded:: 13.3
+
+AVIF is an image format, that is supported by most modern browsers, and usually
+has a better compression (= smaller file size) than jpg files.
+
+..  important::
+
+    Before using this feature, please check whether the used operating system
+    actually supports de/encoding AVIF files. Especially Debian 11 (Bullseye)
+    and older or systems forked from that may lack AVIF support.
+
+..  literalinclude:: _snippets/_avif.typoscript
+    :caption: EXT:config/sites/my_site/setup.typoscript
+
 
 Masking semi-transparent images (Logos) onto other images
 =========================================================
diff --git a/Documentation/Gifbuilder/Index.rst b/Documentation/Gifbuilder/Index.rst
index 378b0b0ec..f295457e3 100644
--- a/Documentation/Gifbuilder/Index.rst
+++ b/Documentation/Gifbuilder/Index.rst
@@ -27,6 +27,7 @@ supported file format. PNG and JPG can be created as well today (configured with
     :glob:
 
     Examples
+    Colors
     Calc
     Properties
     ObjectNames/Index
diff --git a/Documentation/Gifbuilder/ObjectNames/Text/Index.rst b/Documentation/Gifbuilder/ObjectNames/Text/Index.rst
index 7229aafe2..a4be1b184 100644
--- a/Documentation/Gifbuilder/ObjectNames/Text/Index.rst
+++ b/Documentation/Gifbuilder/ObjectNames/Text/Index.rst
@@ -35,7 +35,7 @@ align
     *   :typoscript:`center`
     *   :typoscript:`right`
 
-
+..  _data-type-degree:
 ..  _gifbuilder-text-angle:
 
 angle
@@ -43,7 +43,7 @@ angle
 
 ..  confval:: angle
     :name: gifbuilder-text-angle
-    :type: :ref:`data-type-degree`
+    :type: integer
     :Default: 0
     :Range: -90 to 90
 
diff --git a/Documentation/Gifbuilder/Properties.rst b/Documentation/Gifbuilder/Properties.rst
index b7aa228ad..f0536904e 100644
--- a/Documentation/Gifbuilder/Properties.rst
+++ b/Documentation/Gifbuilder/Properties.rst
@@ -153,15 +153,9 @@ charRangeMap
 format
 ======
 
-..  versionchanged:: 13.0
-    The default format is now "png". Before TYPO3 v13.0 this was "gif".
-
-..  versionadded:: 13.0
-    Support for WebP has been added.
-
 ..  confval:: format
     :name: gifbuilder-properties-format
-    :type: "gif" / "jpg" / "jpeg" / "png" / "webp"
+    :type: "gif" / "jpg" / "jpeg" / "png" / "webp" / "avif"
     :Default: png
 
     File type of the output image.
@@ -170,9 +164,16 @@ format
 
     *   :ref:`$TYPO3_CONF_VARS['GFX']['jpg_quality'] <t3coreapi:typo3ConfVars_gfx_jpg_quality>` for a JPG image
     *   :ref:`$TYPO3_CONF_VARS['GFX']['webp_quality'] <t3coreapi:typo3ConfVars_gfx_webp_quality>` for a WebP image
+    *   :ref:`$TYPO3_CONF_VARS['GFX']['avif_quality'] <t3coreapi:typo3ConfVars_gfx_webp_quality>` for a AVIF image
 
     or via the :ref:`gifbuilder-properties-quality` property on a per-image basis.
 
+    ..  versionchanged:: 13.0
+        The default format is now "png". Before TYPO3 v13.0 this was "gif".
+
+    ..  versionadded:: 13.0
+        Support for WebP and AVIF have been added.
+
 
 .. _gifbuilder-properties-maxHeight:
 
@@ -231,6 +232,18 @@ quality
 
     ..  _"lossless" compression: https://developers.google.com/speed/webp/docs/compression#lossless_webp
 
+.. _gifbuilder-properties-speed:
+
+speed
+=====
+
+..  confval:: speed
+    :name: gifbuilder-properties-speed
+    :type: integer
+
+    Set the "speed" for files in format AVIF (See
+    https://www.php.net/manual/en/function.imageavif.php for more details).
+
 
 .. _gifbuilder-properties-transparentBackground:
 
diff --git a/Documentation/Gifbuilder/_snippets/_avif.typoscript b/Documentation/Gifbuilder/_snippets/_avif.typoscript
new file mode 100644
index 000000000..64888edae
--- /dev/null
+++ b/Documentation/Gifbuilder/_snippets/_avif.typoscript
@@ -0,0 +1,15 @@
+page.10 = IMAGE
+page.10 {
+  file = GIFBUILDER
+  file {
+    backColor = yellow
+    XY = 1024,199
+    format = avif
+    quality = 44
+    speed = 1
+
+    10 = IMAGE
+    10.offset = 10,10
+    10.file = 1:/my-image.jpg
+  }
+}
diff --git a/Documentation/Glossary.rst b/Documentation/Glossary.rst
index 34e76b3ac..963ecc2d4 100644
--- a/Documentation/Glossary.rst
+++ b/Documentation/Glossary.rst
@@ -7,10 +7,10 @@
 Glossary
 ========
 
-We use the terms as explained in :ref:`TypoScript Syntax <t3coreapi:typoscript-syntax-introduction>`,
+We use the terms as explained in :ref:`TypoScript Syntax <typoscript-syntax>`,
 with some modifications:
 
-The section :ref:`t3coreapi:typoscript-syntax-object-paths` differentiates between Object paths, Objects,
+We differentiates between Object paths, Objects,
 properties and values.
 
 To reuse the OOP analogy and compare with PHP:
@@ -110,7 +110,7 @@ cObject data type
    used for content elements.
 
 Top level objects
-   As described in :ref:`t3coreapi:typoscript-syntax-introduction`
+   As described in :ref:`typoscript-syntax`
    TypoScript configuration is converted into a multidimensional PHP array.
    You can view this in the :ref:`submodule-active-typoscript`. Top level
    objects are located on the top level. Top level objects are for
diff --git a/Documentation/Guide/Content/Index.rst b/Documentation/Guide/Content/Index.rst
new file mode 100644
index 000000000..7447f9e56
--- /dev/null
+++ b/Documentation/Guide/Content/Index.rst
@@ -0,0 +1,62 @@
+:navigation-title: Content records
+..  include:: /Includes.rst.txt
+..  _guide-content-records:
+
+=======================
+Reading content records
+=======================
+
+..  note::
+
+    The following chapter aims at explaining the relationship between database
+    content and frontend output via TypoScript. The TYPO3 Core and system
+    extension `fluid_styled_content` already contain definitions for the TYPO3
+    Core content element rendering. You do not have to add anything yourself.
+
+    If you wish a content element to be rendered differently or if you program
+    an extension with new content elements, it will be necessary to understand
+    this relationship to be able to design your own TypoScript properly.
+
+Obviously entering all content for the website would be terribly tiresome,
+although possible from a theoretical point of view.
+
+What we want is to have a TypoScript which gathers the content automatically.
+The example below creates a page on which, for each content element on that
+page, the headline and the text is displayed.
+
+After creating the :ref:`PAGE <page>` object, we use the :ref:`CONTENT
+<cobj-content>` object to retrieve content from the database. For each
+content element we use the :ref:`TEXT <cobj-text>` object to perform
+the actual rendering:
+
+..  literalinclude:: /Guide/Content/_snippets/_PAGE.typoscript
+
+The :ref:`CONTENT <cobj-content>` object executes an SQL query on the
+database. The query is controlled by the `select` property, which - in
+our case - defines that we want all records from the column 0 (which is the
+column called "NORMAL" in the backend), and that the result should be sorted
+according to the field called "sorting".
+
+The `select` property has a `pidInList` which can be used to
+retrieve elements from a specific page. If it is not defined
+- as in our example - elements are taken from the current page.
+
+The `renderObj` property defines how each record gets rendered. It is
+defined as :ref:`COA (Content Object Array) <cobj-coa>`, which can hold
+an arbitrary number of TypoScript objects. In this case, two :ref:`TEXT
+<cobj-text>` objects are used, which are rendered one after the other
+(remember that the order of the rendering is not controlled by the order in
+TypoScript, but by the numbers with which they are defined). The :ref:`TEXT
+<cobj-text>` object "10" will be created first and the :ref:`TEXT
+<cobj-text>` object "20" will be rendered after it.
+
+The challenge is to render all content elements like the web designer
+predetermined. Therefore, we have to create TypoScript definitions for every
+single database field (e.g. for images, image size, image position, link to
+top, index, etc.).
+
+..  include:: _Chapters/_HtmlTemplate.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_ContentElements.rst.txt
+    :show-buttons:
diff --git a/Documentation/Guide/Content/_Chapters/_ContentElements.rst.txt b/Documentation/Guide/Content/_Chapters/_ContentElements.rst.txt
new file mode 100644
index 000000000..4a882be1f
--- /dev/null
+++ b/Documentation/Guide/Content/_Chapters/_ContentElements.rst.txt
@@ -0,0 +1,65 @@
+..  _guide-content-elements:
+
+============================
+The various content elements
+============================
+
+The setup we just defined is pretty basic and will work only for content
+elements containing text. But the content elements are varied and we also need
+to render images, forms, etc. and we do not want to define everything in
+TypoScript - using HTML templates would be more convenient.
+
+The type of a content element is stored in the column
+`CType` of table "tt\_content". We can use this information
+with a :ref:`CASE <cobj-case>` object, which makes it possible to
+differentiate how the individual content element types are rendered.
+
+The following code is the default TypoScript rendering definition as taken from
+the TYPO3 Core. The default `renderObj` of a table is a TypoScript
+definition named after that table. In case of content in TYPO3 the table is
+called `tt_content` therefore the default `renderObj` is also called
+`tt_content`:
+
+..  literalinclude:: /Guide/Content/_snippets/_tt_content.typoscript
+    :caption: Content element rendering taken from typo3/sysext/frontend/ext_localconf.php
+
+The basic extension for rendering content in TYPO3 since TYPO3 v8 is
+`fluid_styled_content`. The example shows how
+`fluid_styled_content` is set up: It defines a basic content element based
+on the content object `FLUIDTEMPLATE` which is able to render html
+templates using the Fluid templating engine. For every content element,
+the basic template, layout and partial parts are defined. As you can see by
+looking at the lines starting with `10 =` there is the possibility to
+add your own templates by setting the corresponding `constant` (in the
+`Constants` section of a TypoScript record):
+
+..  literalinclude:: /Guide/Content/_snippets/_lib.contentElement.typoscript
+    :caption: Taken from typo3/sysext/fluid_styled_content/Configuration/TypoScript/Helper/ContentElement.typoscript
+
+Each content element inherits that configuration. As an example take a look at
+the content element definition of the content element of type `header`:
+
+..  literalinclude:: /Guide/Content/_snippets/_tt_content.header.typoscript
+    :caption: Taken from typo3/sysext/fluid_styled_content/Configuration/TypoScript/ContentElement/Header.typoscript
+
+First, all configuration options defined in `lib.contentElement` are
+referenced. Then the `templateName` for rendering a content element of
+type `header` is set - in this case `Header`. This tells fluid to
+look for a
+`Header.html` in the defined template path(s) (see above, by default in
+`EXT:fluid_styled_content/Resources/Private/Templates/`).
+
+To adjust how the default elements are rendered you can overwrite the templates
+in your own site package extension and set the TypoScript constants defining
+the paths (see above). In your own templates you have the data of the currently
+rendered content element available in the {data} fluid variable. For example
+take a look at how the text element is rendered:
+
+..  literalinclude:: /Guide/Content/_snippets/_Layout.html
+    :caption: Taken from typo3/sysext/fluid_styled_content/Resources/Private/Templates/Text.html
+
+The database field `bodytext` from the `tt_content` table (which is
+the main text input field for content elements of type `text`) is
+available as `{data.bodytext}` in the Fluid template. For more
+information about `fluid_styled_content` see its :doc:`manual
+<typo3/cms-fluid-styled-content:Index>`.
diff --git a/Documentation/Guide/Content/_Chapters/_HtmlTemplate.rst.txt b/Documentation/Guide/Content/_Chapters/_HtmlTemplate.rst.txt
new file mode 100644
index 000000000..71897ae34
--- /dev/null
+++ b/Documentation/Guide/Content/_Chapters/_HtmlTemplate.rst.txt
@@ -0,0 +1,30 @@
+..  include:: /Includes.rst.txt
+
+
+..  _insert-content-in-a-template:
+
+=================================
+Insert content in a HTML template
+=================================
+
+Although we now know how to render content, we do not
+have a real website yet.
+
+Again everything could be done using TypoScript. That would be pretty complex
+and error prone. Furthermore if a HTML template file is prepared by a designer
+for the website, it would be a shame not to reuse it as is as much as
+possible. It would also make further corrections to the HTML template much
+harder to apply.
+
+TYPO3 CMS provides the :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>`
+object, with which we can use Fluid template and render our website with it:
+
+..  literalinclude:: /Guide/Content/_snippets/_FLUIDTEMPLATE.typoscript
+
+In your template file you can now replace the parts that should be filled by
+TYPO3 with references to the TypoScript configuration objects you defined
+earlier.
+
+For example to render a template with the menu we defined add:
+
+..  literalinclude:: /Guide/Content/_snippets/_Fluid.html
diff --git a/Documentation/Guide/Content/_snippets/_FLUIDTEMPLATE.typoscript b/Documentation/Guide/Content/_snippets/_FLUIDTEMPLATE.typoscript
new file mode 100644
index 000000000..20e06450f
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_FLUIDTEMPLATE.typoscript
@@ -0,0 +1,14 @@
+10 = FLUIDTEMPLATE
+10 {
+  templateName = Default
+
+  templateRootPaths {
+    0 = EXT:site_package/Resources/Private/Templates/Pages/
+  }
+  partialRootPaths {
+    0 = EXT:site_package/Resources/Private/Partials/Pages/
+  }
+  layoutRootPaths {
+    0 = EXT:site_package/Resources/Private/Layouts/Pages/
+  }
+}
diff --git a/Documentation/Guide/Content/_snippets/_Fluid.html b/Documentation/Guide/Content/_snippets/_Fluid.html
new file mode 100644
index 000000000..e3e6e07a6
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_Fluid.html
@@ -0,0 +1,7 @@
+<nav>
+    <f:cObject typoscriptObjectPath="lib.textmenu" />
+</nav>
+
+<div class="container">
+    <f:cObject typoscriptObjectPath="lib.dynamicContent" data="{pageUid: '{data.uid}', colPos: '0'}" />
+</div>
diff --git a/Documentation/Guide/Content/_snippets/_Layout.html b/Documentation/Guide/Content/_snippets/_Layout.html
new file mode 100644
index 000000000..b134ac670
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_Layout.html
@@ -0,0 +1,6 @@
+<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
+<f:layout name="Default" />
+<f:section name="Main">
+    <f:format.html>{data.bodytext}</f:format.html>
+</f:section>
+</html>
diff --git a/Documentation/Guide/Content/_snippets/_PAGE.typoscript b/Documentation/Guide/Content/_snippets/_PAGE.typoscript
new file mode 100644
index 000000000..476cd60a6
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_PAGE.typoscript
@@ -0,0 +1,40 @@
+page = PAGE
+page.typeNum = 0
+
+# The CONTENT object executes a database query and loads the content.
+page.10 = CONTENT
+page.10.table = tt_content
+page.10.select {
+
+  # "sorting" is a column from the tt_content table and
+  # keeps track of the sorting order, which was specified in
+  # the backend.
+  orderBy = sorting
+
+  # Only select content from column "0" (the column called
+  # "normal") and quote the database identifier (column name)
+  # "colPos" (indicated by wrapping with {#})
+  where = {#colPos}=0
+}
+
+# For every result line from the database query (that means for every content
+# element) the renderObj is executed and the internal data array is filled
+# with the content. This ensures that we can call the .field property and we
+# get the according value.
+page.10.renderObj = COA
+page.10.renderObj {
+
+  10 = TEXT
+
+  # The field tt_content.header normally holds the headline.
+  10.stdWrap.field = header
+
+  10.stdWrap.wrap = <h1>|</h1>
+
+  20 = TEXT
+
+  # The field tt_content.bodytext holds the content text.
+  20.stdWrap.field = bodytext
+
+  20.stdWrap.wrap = <p>|</p>
+}
diff --git a/Documentation/Guide/Content/_snippets/_lib.contentElement.typoscript b/Documentation/Guide/Content/_snippets/_lib.contentElement.typoscript
new file mode 100644
index 000000000..9aa24d911
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_lib.contentElement.typoscript
@@ -0,0 +1,17 @@
+lib.contentElement = FLUIDTEMPLATE
+lib.contentElement {
+  templateName = Default
+  templateRootPaths {
+    0 = EXT:fluid_styled_content/Resources/Private/Templates/
+    10 = {$styles.templates.templateRootPath}
+  }
+  partialRootPaths {
+    0 = EXT:fluid_styled_content/Resources/Private/Partials/
+    10 = {$styles.templates.partialRootPath}
+  }
+  layoutRootPaths {
+    0 = EXT:fluid_styled_content/Resources/Private/Layouts/
+    10 = {$styles.templates.layoutRootPath}
+  }
+  # ...
+}
diff --git a/Documentation/Guide/Content/_snippets/_tt_content.header.typoscript b/Documentation/Guide/Content/_snippets/_tt_content.header.typoscript
new file mode 100644
index 000000000..1497d2102
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_tt_content.header.typoscript
@@ -0,0 +1,8 @@
+# Header Only:
+# Adds a header only.
+#
+# CType: header
+tt_content.header =< lib.contentElement
+tt_content.header {
+  templateName = Header
+}
diff --git a/Documentation/Guide/Content/_snippets/_tt_content.typoscript b/Documentation/Guide/Content/_snippets/_tt_content.typoscript
new file mode 100644
index 000000000..64c88f5f7
--- /dev/null
+++ b/Documentation/Guide/Content/_snippets/_tt_content.typoscript
@@ -0,0 +1,15 @@
+tt_content = CASE
+tt_content {
+  key {
+    # The field CType will be used to differentiate.
+    field = CType
+  }
+  # Render a error message in case no specific rendering definition is found
+  default = TEXT
+  default {
+    field = CType
+    htmlSpecialChars = 1
+    wrap = <p style="background-color: yellow; padding: 0.5em 1em;"><strong>ERROR:</strong> Content Element with uid "{field:uid}" and type "|" has no rendering definition!</p>
+    wrap.insertData = 1
+  }
+}
diff --git a/Documentation/Guide/FirstSteps/Index.rst b/Documentation/Guide/FirstSteps/Index.rst
new file mode 100644
index 000000000..8abbb320b
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/Index.rst
@@ -0,0 +1,97 @@
+:navigation-title: First steps
+..  include:: /Includes.rst.txt
+..  _guide-first-steps:
+
+===========
+First steps
+===========
+
+The basic rendering is defined in the "Setup" field of the main TypoScript record.
+
+TypoScript essentially consists of objects, which have certain
+properties. Some of these properties can accept other objects, others
+stand for functions or simple values.
+
+The :ref:`PAGE <page>` object is responsible for the
+rendering of a website page in the frontend:
+
+..  literalinclude:: _snippets/_mypage.typoscript
+
+The :ref:`PAGE <page>` object on the one hand offers numerous named properties
+(like :typoscript:`typeNum`). On the other hand it also has an endless number of
+numbered objects (a so-called content array). The names of these
+objects only consist of numbers and the objects are sorted
+accordingly when they are rendered, from the smallest number to the
+largest. The order of the lines in the TypoScript record is
+irrelevant:
+
+..  literalinclude:: _snippets/_mypage2.typoscript
+
+Every entry is stored in a multidimensional PHP array. Every object
+and every property, therefore, is unique. We could define an arbitrary
+number of PAGE objects; however, the :typoscript:`typeNum` has to be unique. For
+every :typoscript:`typeNum`, there can be only one :ref:`PAGE <page>` object.
+
+In the example, for the parameter :typoscript:`typeNum = 98`, a different output
+mode is created. By using :typoscript:`typeNum`, various output types can be
+defined. If :typoscript:`typeNum` is not set explicitly, it defaults to "0".
+Typically, :typoscript:`typeNum = 0` is used for the HTML output.
+
+When a page is requested with just :code:`index.php?id=1`, :typoscript:`typeNum = 0`
+will be assumed and the output will be HTML. To get the print output, the request
+will have to pass a "type" attribute, i.e. :code:`index.php?id=1&type=98`.
+
+It is thus possible to generate many different outputs depending on one's
+needs (XML, JSON, PDF, etc.). TypoScript configuration can be copied between
+those various views, changing only what's specific for each of them.
+
+The previous example would look like this as a PHP array:
+
+..  literalinclude:: _snippets/_mypage.php
+
+Empty spaces at the start and end of values are removed by TYPO3 CMS
+automatically (using the PHP :php:`trim()` function).
+
+The :typoscript:`=` sign corresponds to a simple assignment. Here is an
+overview of the various operators:
+
+..  literalinclude:: _snippets/_mypage3.typoscript
+
+Object types are always written with capital letters; parameters and
+functions typically in camel case (first word lower case, next word
+starts with a capital letter, no space between words). There are some
+exceptions to this.
+
+With the :typoscript:`.` as a separator parameter, functions and child objects are
+referenced and can be assigned values accordingly:
+
+..  code-block:: typoscript
+
+    page.10.stdWrap.wrap = <h1>|</h1>
+
+The :doc:`TypoScript Reference (TSref) <Index>` is the ultimate
+resource to find out which objects, functions and properties exist.
+
+Things can get more complicated when objects are nested inside
+each other and many properties are used:
+
+..  literalinclude:: _snippets/_mypage4.typoscript
+
+To make things clearer, TypoScript code can be structured using curly braces
+(:typoscript:`{}`) at each nesting level:
+
+..  literalinclude:: _snippets/_mypage5.typoscript
+
+..  important::
+
+    The opening curly brace must always be on the same line as the property.
+
+Parenthesis (:typoscript:`()`) are used for writing text values on more
+than one line.
+
+Using this style of notation reduces the danger of typographic errors
+and makes the script easier to read. In addition it reduces the repetition
+of variable names making it easier to rename an object.
+
+The full reference for the syntax is found in the
+:ref:`TypoScript Syntax and In-depth Study <typoscript-syntax>`.
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage.php b/Documentation/Guide/FirstSteps/_snippets/_mypage.php
new file mode 100644
index 000000000..e363b203c
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage.php
@@ -0,0 +1,15 @@
+<?php
+
+$TypoScript['page'] = 'PAGE';
+$TypoScript['page.']['typeNum'] = 0;
+$TypoScript['page.']['10'] = 'TEXT';
+$TypoScript['page.']['10.']['value'] = 'This is rendered first.';
+$TypoScript['page.']['20'] = 'TEXT';
+$TypoScript['page.']['20.']['value'] = 'This is rendered in the middle.';
+$TypoScript['page.']['30'] = 'TEXT';
+$TypoScript['page.']['30.']['value'] = 'This gets rendered last.';
+
+$TypoScript['print'] = 'PAGE';
+$TypoScript['print.']['typeNum'] = 98;
+$TypoScript['print.']['10'] = 'TEXT';
+$TypoScript['print.']['10.']['value'] = 'This is the print version.';
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage.typoscript b/Documentation/Guide/FirstSteps/_snippets/_mypage.typoscript
new file mode 100644
index 000000000..af7f5daec
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage.typoscript
@@ -0,0 +1,11 @@
+# The object page is defined as PAGE object.
+page = PAGE
+
+# PAGE objects have the property typeNum.
+page.typeNum = 0
+
+# page has an object "10" of type TEXT. It is a TEXT object.
+page.10 = TEXT
+
+# TEXT objects in turn have a property called "value".
+page.10.value = Hello World
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage2.typoscript b/Documentation/Guide/FirstSteps/_snippets/_mypage2.typoscript
new file mode 100644
index 000000000..f5daa9e58
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage2.typoscript
@@ -0,0 +1,22 @@
+# Create a PAGE object.
+page = PAGE
+page.typeNum = 0
+
+page.30 = TEXT
+page.30.value = This gets rendered last.
+
+# Rendering will first output object number 10, then 20 and 30.
+# An object with number 25 would logically be output between 20 and 30.
+page.20 = TEXT
+page.20.value = This is rendered in the middle.
+
+# This is the first output object
+page.10 = TEXT
+page.10.value = This is rendered first.
+
+# Here we create a second PAGE object, which we can use for the
+# print view.
+print = PAGE
+print.typeNum = 98
+print.10 = TEXT
+print.10.value = This is the print version.
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage3.typoscript b/Documentation/Guide/FirstSteps/_snippets/_mypage3.typoscript
new file mode 100644
index 000000000..e66093014
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage3.typoscript
@@ -0,0 +1,21 @@
+# The object test is an object of type TEXT.
+# "=" means "set value".
+test = TEXT
+test.value = Holla
+
+# "<" means "copy object".
+# page.10 returns "Holla"
+page.10 < test
+
+# Change the original object.
+# The change has no effect on page.10; it still returns "Holla".
+test.value = Hello world
+
+# "=<" means "create an object reference (link the object)".
+test.value = Holla
+page.10 =< test
+
+# Change the object which is referenced.
+# Changes DO have an effect on page.10.
+# page.10 will return "Hello world".
+test.value = Hello world
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage4.typoscript b/Documentation/Guide/FirstSteps/_snippets/_mypage4.typoscript
new file mode 100644
index 000000000..0738e7139
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage4.typoscript
@@ -0,0 +1,15 @@
+page = PAGE
+page.typeNum = 0
+page.10 = TEXT
+page.10.value = Hello world
+page.10.stdWrap.typolink.parameter = http://www.typo3.org/
+page.10.stdWrap.typolink.additionalParams = &parameter=value
+
+# The function name "ATagParams" does not use the standardized
+# "camelCase".
+page.10.stdWrap.typolink.ATagParams = class="externalwebsite"
+page.10.stdWrap.typolink.extTarget = _blank
+page.10.stdWrap.typolink.title = The website of TYPO3
+page.10.stdWrap.postCObject = TEXT
+page.10.stdWrap.postCObject.value = This text also appears in the link text
+page.10.stdWrap.postCObject.stdWrap.wrap = |, because the postCObject is executed before the typolink function.
diff --git a/Documentation/Guide/FirstSteps/_snippets/_mypage5.typoscript b/Documentation/Guide/FirstSteps/_snippets/_mypage5.typoscript
new file mode 100644
index 000000000..f6bab9fe6
--- /dev/null
+++ b/Documentation/Guide/FirstSteps/_snippets/_mypage5.typoscript
@@ -0,0 +1,30 @@
+page = PAGE
+page {
+  typeNum = 0
+
+  10 = TEXT
+  10 {
+    value = Hello world
+    stdWrap {
+      typolink {
+        parameter = http://www.typo3.org/
+        additionalParams = &parameter=value
+
+        # The function name "ATagParams" does not use the standardized
+        # "camelCase".
+        ATagParams = class="externalwebsite"
+
+        extTarget = _blank
+        title = The website of TYPO3
+      }
+
+      postCObject = TEXT
+      postCObject {
+        value = This text also appears in the link text
+        stdWrap.wrap (
+                  |, because the postCObject is executed before the typolink function.
+        )
+      }
+    }
+  }
+}
diff --git a/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.png b/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.png
new file mode 100644
index 000000000..db41db309
Binary files /dev/null and b/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.png differ
diff --git a/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.rst.txt b/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.rst.txt
new file mode 100644
index 000000000..13da89691
--- /dev/null
+++ b/Documentation/Guide/Images/AutomaticScreenshots/RootlevelFlag.rst.txt
@@ -0,0 +1,7 @@
+..  Automatic screenshot: Remove this line if you want to manually change this file
+
+..  figure:: /Images/AutomaticScreenshots/RootlevelFlag.png
+   :alt: The Rootlevel flag in the tab Options a template record
+   :class: with-shadow
+
+   The :guilabel:`Rootlevel` flag in the tab :guilabel:`Options` a template record
diff --git a/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.png b/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.png
new file mode 100644
index 000000000..c54acb226
Binary files /dev/null and b/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.png differ
diff --git a/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.rst.txt b/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.rst.txt
new file mode 100644
index 000000000..3c5908f9f
--- /dev/null
+++ b/Documentation/Guide/Images/AutomaticScreenshots/TemplateAnalyzerStructure.rst.txt
@@ -0,0 +1,7 @@
+..  Automatic screenshot: Remove this line if you want to manually change this file
+
+..  figure:: /Images/AutomaticScreenshots/TemplateAnalyzerStructure.png
+   :alt: The template structure as seen with the Template Analyzer
+   :class: with-shadow
+
+   The template structure as seen with the Template Analyzer
diff --git a/Documentation/Guide/Images/ManualScreenshots/ModuleNameTypoScript.png b/Documentation/Guide/Images/ManualScreenshots/ModuleNameTypoScript.png
new file mode 100644
index 000000000..38cd585dd
Binary files /dev/null and b/Documentation/Guide/Images/ManualScreenshots/ModuleNameTypoScript.png differ
diff --git a/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFound.png b/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFound.png
new file mode 100644
index 000000000..0d92981ed
Binary files /dev/null and b/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFound.png differ
diff --git a/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png b/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png
new file mode 100644
index 000000000..3001d23ab
Binary files /dev/null and b/Documentation/Guide/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png differ
diff --git a/Documentation/Guide/Images/ManualScreenshots/ThePageIsNotConfigured.png b/Documentation/Guide/Images/ManualScreenshots/ThePageIsNotConfigured.png
new file mode 100644
index 000000000..17981ce9a
Binary files /dev/null and b/Documentation/Guide/Images/ManualScreenshots/ThePageIsNotConfigured.png differ
diff --git a/Documentation/Guide/Index.rst b/Documentation/Guide/Index.rst
new file mode 100644
index 000000000..db4f948fb
--- /dev/null
+++ b/Documentation/Guide/Index.rst
@@ -0,0 +1,29 @@
+:navigation-title: Getting started
+..  include:: /Includes.rst.txt
+..  _guide:
+
+=====================================================
+Getting started: A quick introduction into TypoScript
+=====================================================
+
+Learn the fundamentals of TypoScript in just 45 minutes.
+
+Furthermore, you can find a full reference of all object types and properties of
+TypoScript in the menu  on the left, including the
+:ref:`TypoScript Syntax <typoscript-syntax>` chapter.
+
+----
+
+..  toctree::
+    :maxdepth: 1
+    :titlesonly:
+
+    Overview/Index
+    FirstSteps/Index
+    Page/Index
+    Content/Index
+    Menu/Index
+    UsingFluidStyledContent/Index
+    TypoScriptObjects/Index
+    TypoScriptFunctions/Index
+    NextSteps/Index
diff --git a/Documentation/Guide/Menu/Index.rst b/Documentation/Guide/Menu/Index.rst
new file mode 100644
index 000000000..89b36707c
--- /dev/null
+++ b/Documentation/Guide/Menu/Index.rst
@@ -0,0 +1,38 @@
+..  include:: /Includes.rst.txt
+..  _guide-menu:
+
+=============================
+Create a menu with TypoScript
+=============================
+
+Until now, we learned how the page *content* is rendered; however, the
+page *navigation* is missing.
+
+TYPO3 provides a special data processor, the :ref:`menu data processor <MenuProcessor>`
+to pass data to render a menu to the Fluid template.
+
+Configure the data processor in TypoScript:
+
+..  literalinclude:: _menu.typoscript
+    :caption: TypoScript Setup
+
+And render the menu in your Fluid template. You need at least a
+:ref:`Minimal site package (see site package tutorial) <t3sitepackage:minimal-design>`
+to keep your templates in its private resources folder, for example
+:path:`/packages/site_package/Resources/Private/Templates`:
+
+..  literalinclude:: _MenuTemplate.html
+    :caption: /packages/site_package/Resources/Private/Templates/Pages/Default.html
+
+Find more examples on how to configure and render menus with TypoScript and
+Fluid in chapter
+:ref:`Main menu of the Site Package Tutorial <t3sitepackage:main-menu-creation>`.
+
+You can find more examples on how to output menus of different styles, including
+multi-level menus, breadcrumbs, language menus, and sitemaps in the chapter
+about the :ref:`menu data processor <MenuProcessor>`.
+
+..  note::
+    Before data processors were introduced it was common to use the TypoScript
+    object :ref:`HMENU <t3tsref:cobj-hmenu>` to render a menu. It is still
+    possible doing so and you might see it in older examples.
diff --git a/Documentation/Guide/Menu/_MenuTemplate.html b/Documentation/Guide/Menu/_MenuTemplate.html
new file mode 100644
index 000000000..13171cf65
--- /dev/null
+++ b/Documentation/Guide/Menu/_MenuTemplate.html
@@ -0,0 +1,18 @@
+<header>
+    <ul class="navbar-nav">
+        <f:for each="{myMainMenu}" as="menuItem">
+            <li class="nav-item">
+                <a class="nav-link {f:if(condition: menuItem.active, then:'active')}"
+                   href="{menuItem.link}"
+                   target="{menuItem.target}"
+                   title="{menuItem.title}"
+                >
+                    {menuItem.title}
+                </a>
+            </li>
+        </f:for>
+    </ul>
+</header>
+<main>
+    <p>Hello World!</p>
+</main>
diff --git a/Documentation/Guide/Menu/_menu.typoscript b/Documentation/Guide/Menu/_menu.typoscript
new file mode 100644
index 000000000..2e61e314c
--- /dev/null
+++ b/Documentation/Guide/Menu/_menu.typoscript
@@ -0,0 +1,12 @@
+page = PAGE
+page {
+  10 = PAGEVIEW
+  10 {
+    paths.10 = EXT:my_site_package/Resources/Private/Templates/Pages/
+    # ...
+    dataProcessing {
+      10 = menu
+      10.as = myMainMenu
+    }
+  }
+}
diff --git a/Documentation/Guide/NextSteps/Index.rst b/Documentation/Guide/NextSteps/Index.rst
new file mode 100644
index 000000000..df301096b
--- /dev/null
+++ b/Documentation/Guide/NextSteps/Index.rst
@@ -0,0 +1,20 @@
+..  include:: /Includes.rst.txt
+..  _guide-next-steps:
+
+==========
+Next steps
+==========
+
+Armed with this basic knowledge of TypoScript, you may want
+to continue your exploration of TYPO3 CMS by following the
+:doc:`Sitepackage Tutorial <t3sitepackage:Index>`, which will
+guide you through the creation of a whole website template
+using TypoScript.
+
+To learn more about the structure and syntax of TypoScript,
+you can refer to the :ref:`TypoScript Syntax and In-depth Study <typoscript-syntax>`
+reference.
+
+Finally - as was mentioned again and again throughout this tutorial -
+the ultimate resource about TypoScript objects, functions and
+data types is the :doc:`TypoScript Reference <Index>`.
diff --git a/Documentation/Guide/Overview/Index.rst b/Documentation/Guide/Overview/Index.rst
new file mode 100644
index 000000000..db090a83a
--- /dev/null
+++ b/Documentation/Guide/Overview/Index.rst
@@ -0,0 +1,47 @@
+:navigation-title: Quick overview
+..  include:: /Includes.rst.txt
+
+..  _guide-overview:
+
+=============================
+TypoScript - A quick overview
+=============================
+
+This introduction is designed to give you a
+comprehensive understanding of how TypoScript works.
+In other words the goal is not to just help you make it work,
+but to make sure that you end up knowing why and how
+it works.
+
+At the end of this tutorial, you will not have a complete
+TYPO3 CMS-powered website, but you should feel confident about
+how to get there.
+
+A common workflow used by beginners is to try arbitrary
+properties on objects until things somehow begin to work.
+However understanding how TypoScript really works
+allows you to proceed more efficiently and waste less time
+in painful trial and error.
+
+Going through this tutorial is helpful for understanding
+other tutorials, like the :ref:`Site package tutorial <t3sitepackage:start>`.
+
+..  contents::
+
+..  include:: _Chapters/_BackendConfiguration.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_Prerequisites.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_WhyTypoScript.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_MainTemplate.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_TheTermTemplate.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_TypoScriptAnArray.rst.txt
+    :show-buttons:
diff --git a/Documentation/Guide/Overview/_Chapters/_BackendConfiguration.rst.txt b/Documentation/Guide/Overview/_Chapters/_BackendConfiguration.rst.txt
new file mode 100644
index 000000000..a5b42d777
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_BackendConfiguration.rst.txt
@@ -0,0 +1,15 @@
+..  _guide-backend-configuration:
+
+=====================
+Backend configuration
+=====================
+
+TypoScript influences many aspects of a TYPO3 site:
+
+TypoScript can be used in the TSconfig field of a backend user or a
+backend user group or in the TSconfig field of a page. It will then
+change the look and behavior of forms in the *backend*.
+
+The *frontend* rendering in contrast is defined by the TypoScript
+used in TypoScript records. This document covers only frontend
+rendering.
diff --git a/Documentation/Guide/Overview/_Chapters/_MainTemplate.rst.txt b/Documentation/Guide/Overview/_Chapters/_MainTemplate.rst.txt
new file mode 100644
index 000000000..fe63b2d5c
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_MainTemplate.rst.txt
@@ -0,0 +1,26 @@
+..  _guide-main-template:
+..  _guide-main-typoscript-record:
+
+==========================
+The main TypoScript record
+==========================
+
+The TypoScript code used to define how pages are rendered is
+located in the "main" TypoScript record. In this record a so-called
+"rootlevel flag" is set.
+
+..  include:: /Images/AutomaticScreenshots/RootlevelFlag.rst.txt
+
+When the frontend renders a page, TYPO3 CMS searches along the page tree up
+to the root page to find a "main" TypoScript record. Normally, there are
+additional TypoScript records besides the "main" TypoScript record.
+For now, we will assume we are only using the "main" TypoScript record.
+
+TypoScript syntax is very straightforward. On the left side, objects
+and properties are defined. On the right side are the assigned values.
+Both objects and properties can contain other objects. Object properties
+are defined by using the dot "." notation.
+
+The following is a typical example of TypoScript syntax:
+
+..  literalinclude:: /Guide/Overview/_snippets/_page1.typoscript
diff --git a/Documentation/Guide/Overview/_Chapters/_Prerequisites.rst.txt b/Documentation/Guide/Overview/_Chapters/_Prerequisites.rst.txt
new file mode 100644
index 000000000..09e1cf56e
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_Prerequisites.rst.txt
@@ -0,0 +1,28 @@
+..  _guide-prerequisites:
+
+=============
+Prerequisites
+=============
+
+It is assumed that you have a running TYPO3 installation.
+See :ref:`TYPO3 Getting Started Tutorial, installing TYPO3 with DDEV <t3start:installation-ddev-tutorial>`.
+
+and that you have been through the
+:ref:`TYPO3 - Getting Started Tutorial <t3start:start>` in order
+to have a general idea of how the TYPO3 CMS backend operates.
+
+A few more elements that you need to know before starting:
+
+*   all content elements are stored in a database table called `tt_content`
+
+*   each content element has a database field called `CType` in which
+    the type of the content element is stored
+
+*   the `tt_content` table also has a field called `pid` which refers
+    to the page the content element is on
+
+*   in general, each TYPO3 CMS table has a field called `uid` which
+    contains the primary key (unique id for each record)
+
+*   you will probably find useful to have a database access to check
+    how information is stored as we proceed along this tutorial
diff --git a/Documentation/Guide/Overview/_Chapters/_TheTermTemplate.rst.txt b/Documentation/Guide/Overview/_Chapters/_TheTermTemplate.rst.txt
new file mode 100644
index 000000000..4e51f922a
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_TheTermTemplate.rst.txt
@@ -0,0 +1,51 @@
+
+..  _guide-template:
+
+===================
+The term "template"
+===================
+
+Sometimes the term "template" is used as a synonym for the TypoScript record
+or the combined TypoScript configuration from all sources. This has historic
+reasons. Until TYPO3 v11 TypoScript could be edited in a backend module
+called "Template". In the beginning of TYPO3 sites were build almost
+exclusively with TypoScript while it slowly evolved to be mainly a configuration
+language.
+
+As a Fluid template is also called "template" the terms took on a double meaning
+in TYPO3. With TYPO3 v12 we speak about TypoScript records, TypoScript files
+and the complete TypoScript configuration. However you will still find the
+outdated term "TypoScript template" or just "template" in places.
+
+..  _guide-troubleshooting:
+
+Troubleshooting
+===============
+
+Common mistakes made in the TypoScript configuration can cause a message like this:
+
+..  figure:: /Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png
+    :alt: Error message "No TypoScript record found!"
+
+If you turn on the :ref:`debug mode <t3coreapi:troubleshooting-debug-mode>`
+you will get more detailed information:
+
+..  figure:: /Images/ManualScreenshots/NoTypoScriptTemplateFound.png
+   :alt: Error message "No TypoScript record found!"
+
+`No TypoScript record found!`: This warning appears if no TypoScript record,
+with the `root level` flag enabled, is found in the page tree.
+
+..  figure:: /Images/ManualScreenshots/ThePageIsNotConfigured.png
+   :alt: Error message "The page is not configured!"
+
+`The page is not configured! [type=0][]`. This means that there is no TypoScript
+object of type PAGE with typeNum=0 configured.`: This warning appears if the
+TypoScript Configuration of the current page contains no :ref:`PAGE <guide-page>`
+definition.
+
+The following TypoScript setup code is enough to remove this warning:
+
+..  literalinclude:: /Guide/Overview/_snippets/_page1.typoscript
+
+Do not worry about this code for now, it will be explained later.
diff --git a/Documentation/Guide/Overview/_Chapters/_TypoScriptAnArray.rst.txt b/Documentation/Guide/Overview/_Chapters/_TypoScriptAnArray.rst.txt
new file mode 100644
index 000000000..2cd05cb3a
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_TypoScriptAnArray.rst.txt
@@ -0,0 +1,51 @@
+..  _guide-typoscript-array:
+
+===========================
+TypoScript is just an array
+===========================
+
+Internally, TypoScript is parsed and stored as a PHP array.
+For example:
+
+..  literalinclude:: /Guide/Overview/_snippets/_page.typoscript
+
+will be converted to the following PHP array:
+
+..  literalinclude:: /Guide/Overview/_snippets/_page.php
+
+Upon evaluation, a ":ref:`PAGE <page>`" object will be created
+first, and the parameter :php:`$data['page.']` will be assigned to it.
+The ":ref:`PAGE <page>`" object will then search for all properties, which
+it knows about. In this case, it will find a numeric entry ("10"), which
+has to be evaluated. A new object of type ":ref:`TEXT <cobj-text>`"
+with the parameter :php:`$data['page.']['10.']` will be created.
+The ":ref:`TEXT <cobj-text>`" object knows the parameters :typoscript:`value` and
+:typoscript:`stdWrap`. It will set the content of :typoscript:`value` accordingly. The
+parameters from :typoscript:`stdWrap` will be passed to the ":ref:`stdWrap <stdwrap>`" function.
+There the property 'wrap' is known, and the text "Hello world" will be inserted
+at the pipe (`|`) position and returned.
+
+It is important to be aware of this relationship in order to
+understand the behaviour of TypoScript.
+For example, if the above TypoScript is extended
+with the following line:
+
+..  code-block:: typoscript
+
+    page.10.myFunction = Magic!
+
+the following entry will be added to the PHP array:
+
+..  code-block:: php
+
+    $data['page.']['10.']['myFunction'] = 'Magic!';
+
+However, the ":ref:`TEXT <cobj-text>`" object does not know
+any property called "myFunction". Consequently, the entry will have no effect.
+
+..  important::
+
+    No semantic error checking is done. If you define objects or
+    properties which do not exist, you will not see any error message.
+    Instead, those specific lines of TypoScript simply do nothing. This
+    should be considered, especially while troubleshooting.
diff --git a/Documentation/Guide/Overview/_Chapters/_WhyTypoScript.rst.txt b/Documentation/Guide/Overview/_Chapters/_WhyTypoScript.rst.txt
new file mode 100644
index 000000000..c6d52f370
--- /dev/null
+++ b/Documentation/Guide/Overview/_Chapters/_WhyTypoScript.rst.txt
@@ -0,0 +1,29 @@
+
+
+..  _guide-why-typoscript:
+
+===============
+Why TypoScript?
+===============
+
+Strictly speaking, TypoScript is a configuration language. We cannot
+program with it, but can configure a TYPO3 CMS website in a
+very comprehensive way. With TypoScript, we define the rendering of the
+website, including navigation, generic content, and how individual
+content elements are rendered on a page.
+
+TYPO3 CMS is a content management system that clearly separates content
+and design. TypoScript is the glue that joins these two together again.
+TypoScript reads content which is stored in the database, prepares it
+for display and then renders it in the frontend.
+
+To render a website, we only need to define what content to display and
+how it will be rendered.
+
+* The "what" is controlled by the backend - where pages and content
+  are generated.
+* The "how" is controlled by TypoScript.
+
+With TypoScript, we can define how the individual content elements are
+rendered in the frontend. For example, we can use TypoScript to add a
+:html:`<div>` tag to an element, or the :html:`<h1>` tag to a headline.
diff --git a/Documentation/Guide/Overview/_snippets/_page.php b/Documentation/Guide/Overview/_snippets/_page.php
new file mode 100644
index 000000000..a740c114d
--- /dev/null
+++ b/Documentation/Guide/Overview/_snippets/_page.php
@@ -0,0 +1,14 @@
+<?php
+
+$data = [
+    'page' => 'PAGE',
+    'page.' => [
+        '10' => 'TEXT',
+        '10.' => [
+            'value' => 'Hello World',
+            'stdWrap.' => [
+                'wrap' => '<h2>|</h2>',
+            ],
+        ],
+    ],
+];
diff --git a/Documentation/Guide/Overview/_snippets/_page.typoscript b/Documentation/Guide/Overview/_snippets/_page.typoscript
new file mode 100644
index 000000000..8af14356b
--- /dev/null
+++ b/Documentation/Guide/Overview/_snippets/_page.typoscript
@@ -0,0 +1,4 @@
+page = PAGE
+page.10 = TEXT
+page.10.value = Hello World
+page.10.stdWrap.wrap = <h2>|</h2>
diff --git a/Documentation/Guide/Overview/_snippets/_page1.typoscript b/Documentation/Guide/Overview/_snippets/_page1.typoscript
new file mode 100644
index 000000000..b043dddf1
--- /dev/null
+++ b/Documentation/Guide/Overview/_snippets/_page1.typoscript
@@ -0,0 +1,3 @@
+page = PAGE
+page.10 = TEXT
+page.10.value = Hello World
diff --git a/Documentation/Guide/Page/Index.rst b/Documentation/Guide/Page/Index.rst
new file mode 100644
index 000000000..4b7546e9d
--- /dev/null
+++ b/Documentation/Guide/Page/Index.rst
@@ -0,0 +1,129 @@
+:navigation-title: Page
+..  include:: /Includes.rst.txt
+..  _guide-page:
+
+================================
+Configure the PAGE in TypoScript
+================================
+
+A TypoScript object of type :ref:`PAGE <t3tsref:object-type-page>` is needed
+to display anything in the frontend of TYPO3.
+
+The :typoscript:`PAGE` object is used to define a certain view of the content that was
+entered in the backend.
+
+To display an HTML representation of your content usually a Fluid template
+is used to define the output of the HTML body while the `PAGE` object can
+additionally define meta data for the HTML head or even the HTTP response.
+
+By default the top level variable `page` is used to define the main
+:typoscript:`PAGE` object. The following would display the empty skeleton of
+an HTML page:
+
+..  code-block:: typoscript
+
+    page = PAGE
+
+If this line is missing, you get the error message
+"No page configured for type=0.".
+
+See also :ref:`Troubleshooting <t3tsref:guide-troubleshooting>`.
+
+..  contents:: Overview
+
+..  _guide-page-body:
+
+Displaying the page body with TypoScript
+========================================
+
+Numeral indexes on the `PAGE` object are used to output the actual content of
+the page. Many integrators like to use the index 10.
+
+As we already saw in section :ref:`guide-first-steps`, the following code outputs
+"Hello World!":
+
+..  literalinclude:: _hello-world.typoscript
+    :caption: TypoScript setup
+
+In a more common use case you want to load the page content from a Fluid
+template:
+
+..  literalinclude:: _fluid-template.typoscript
+    :caption: TypoScript setup
+
+You need at least a
+:ref:`Minimal site package (see site package tutorial) <t3sitepackage:minimal-design>`
+to keep your templates in its private resources folder, for example
+:path:`/packages/site_package/Resources/Private/Templates`:
+
+..  literalinclude:: _Default.html
+    :caption: /packages/site_package/Resources/Private/Templates/Pages/Default.html
+
+..  note::
+    Learn more about building site packages (website themes) with TypoScript and
+    Fluid templates in the :ref:`TYPO3 site package tutorial <t3sitepackage:start>`.
+
+..  _guide-page-loading-css:
+
+Loading CSS in TypoScript
+=========================
+
+You can write inline CSS using property
+:confval:`cssInline.[array] <t3tsref:page-cssinline>`, or place your CSS file
+in the public resources of your :ref:`Minimal site package <t3sitepackage:minimal-design>`:
+
+..  literalinclude:: _css-loading.typoscript
+    :caption: TypoScript setup
+
+..  _guide-page-loading-js:
+
+Loading JavaScript in TypoScript
+================================
+
+You can write inline JavaScript using property
+:confval:`jsFooterInline.[array] <t3tsref:page-jsfooterinline>`, or place your JavaScript file
+in the public resources of your :ref:`Minimal site package <t3sitepackage:minimal-design>`:
+
+..  literalinclude:: _javascript-loading.typoscript
+    :caption: TypoScript setup
+
+..  warning::
+    If you are using inline JavaScript **never** pass any unescaped user input
+    directly to the JavaScript.
+
+    See also :ref:`Preventing Cross-site scripting (XSS)
+    in TypoScript <t3coreapi:security-typoscript-xss>`.
+
+..  _guide-page-favicon:
+
+Favicon / shortcut icon definition in the TypoScript PAGE
+=========================================================
+
+Use property :confval:`shortcutIcon <t3tsref:page-shortcuticon>` to define
+the favicon:
+
+..  literalinclude:: _favicon.typoscript
+    :caption: TypoScript setup
+
+You need to have a
+:ref:`Minimal site package (see site package tutorial) <t3sitepackage:minimal-design>`
+and put the favicon file in the public resources folder of that site package.
+If you followed the instruction from the site package tutorial that would be
+path :path:`/packages/site_package/Resources/Public/Icons`.
+
+..  _guide-page-tracking-code:
+
+Tracking code: Add content to the end of your page
+==================================================
+
+You can use the property :confval:`footerData.[array] <t3tsref:page-footerdata>`
+to enter some HTML code just before the closing `</body>` tag:
+
+..  literalinclude:: _tracking-code.typoscript
+    :caption: TypoScript setup
+
+..  warning::
+    The HTML is output directly. Never use any unescaped user input.
+
+    See also :ref:`Preventing Cross-site scripting (XSS)
+    in TypoScript <t3coreapi:security-typoscript-xss>`.
diff --git a/Documentation/Guide/Page/_Default.html b/Documentation/Guide/Page/_Default.html
new file mode 100644
index 000000000..4fe1c867b
--- /dev/null
+++ b/Documentation/Guide/Page/_Default.html
@@ -0,0 +1,3 @@
+<main>
+    <p>Hello World!</p>
+</main>
diff --git a/Documentation/Guide/Page/_css-loading.typoscript b/Documentation/Guide/Page/_css-loading.typoscript
new file mode 100644
index 000000000..e65be66d9
--- /dev/null
+++ b/Documentation/Guide/Page/_css-loading.typoscript
@@ -0,0 +1,16 @@
+page = PAGE
+page {
+  10 = TEXT
+  10.value = <div class="myTodo">TODO: Add Fluid template </div>
+  cssInline {
+    10 = TEXT
+    10.value (
+      .myTodo {
+        border: 2px solid #ee7600;
+      }
+    )
+  }
+  includeCSS {
+    styles = EXT:site_package/Resources/Public/Css/styles.css
+  }
+}
diff --git a/Documentation/Guide/Page/_favicon.typoscript b/Documentation/Guide/Page/_favicon.typoscript
new file mode 100644
index 000000000..8942cd731
--- /dev/null
+++ b/Documentation/Guide/Page/_favicon.typoscript
@@ -0,0 +1,6 @@
+page = PAGE
+page {
+  shortcutIcon = EXT:site_package/Ressources/Public/Icons/favicon.ico
+  10 = TEXT
+  10.value = TODO: Add Fluid template
+}
diff --git a/Documentation/Guide/Page/_fluid-template.typoscript b/Documentation/Guide/Page/_fluid-template.typoscript
new file mode 100644
index 000000000..1ceb8f032
--- /dev/null
+++ b/Documentation/Guide/Page/_fluid-template.typoscript
@@ -0,0 +1,12 @@
+page = PAGE
+page {
+  10 = PAGEVIEW
+  10 {
+    paths {
+      100 = EXT:my_site_package/Resources/Private/PageView/
+    }
+    dataProcessing {
+      10 = page-content
+    }
+  }
+}
diff --git a/Documentation/Guide/Page/_hello-world.typoscript b/Documentation/Guide/Page/_hello-world.typoscript
new file mode 100644
index 000000000..be6c0a040
--- /dev/null
+++ b/Documentation/Guide/Page/_hello-world.typoscript
@@ -0,0 +1,5 @@
+page = PAGE
+page {
+  10 = TEXT
+  10.value = Hello World!
+}
diff --git a/Documentation/Guide/Page/_javascript-loading.typoscript b/Documentation/Guide/Page/_javascript-loading.typoscript
new file mode 100644
index 000000000..e4f31744d
--- /dev/null
+++ b/Documentation/Guide/Page/_javascript-loading.typoscript
@@ -0,0 +1,14 @@
+page = PAGE
+page {
+  10 = TEXT
+  10.value = <div class="myTodo">TODO: Add Fluid template </div>
+  jsFooterInline {
+    10 = TEXT
+    10.value (
+      alert("Hello World! ");
+    )
+  }
+  includeCSS {
+    includeJSFooter = EXT:site_package/Resources/Public/JavaScript/main.js
+  }
+}
diff --git a/Documentation/Guide/Page/_tracking-code.typoscript b/Documentation/Guide/Page/_tracking-code.typoscript
new file mode 100644
index 000000000..a046b6fd5
--- /dev/null
+++ b/Documentation/Guide/Page/_tracking-code.typoscript
@@ -0,0 +1,12 @@
+page = PAGE
+page {
+  10 = TEXT
+  10.value = TODO: Add Fluid template
+  footerData {
+    10 = TEXT
+    10.value (
+      <!-- Enter some tracking code supplied by your provider -->
+      <p>My tracking code</p>
+    )
+  }
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/GetText/Index.rst b/Documentation/Guide/TypoScriptFunctions/GetText/Index.rst
new file mode 100644
index 000000000..8f9af1a4d
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/GetText/Index.rst
@@ -0,0 +1,56 @@
+:navigation-title: getText / data
+..  include:: /Includes.rst.txt
+..  _using-gettext:
+
+===========================
+Using the getText data type
+===========================
+
+There's one particular data type which might leave you wondering, because it
+may seem to behave rather like a function. This is
+:ref:`getText <data-type-gettext>`.
+
+The `data` property of :ref:`stdWrap <stdwrap>` has this
+particular data type. It makes it possible retrieve values from a large number
+of sources, including:
+
+*   global TYPO3 CMS arrays
+*   GET/POST vars
+*   database
+*   localized strings
+*   page rootline
+
+Here are some examples:
+
+..  code-block:: typoscript
+
+    10 = TEXT
+    10.data = field:abstract
+
+Creates a text object that contains the value of the "abstract" field from the
+current page:
+
+..  code-block:: typoscript
+
+    10 = TEXT
+    10.data = leveltitle:0
+
+Creates a text object that contains the title of the page on level 0 of the
+current branch, i.e. the website root for that branch:
+
+..  code-block:: typoscript
+
+    10 = TEXT
+    10.data = LLL:EXT:myext/Resources/Private/Language/locallang.xlf:siteTitle
+
+Creates a text object that contains the value of the "siteTitle" string in the
+given localization, appropriately translated for the current language.
+
+As you can see, the base syntax is a keyword, then a colon (`:`) and then some
+values that makes with regards to the chosen keyword. Although such a tool may
+appear to be a function, it is not considered one as it is entirely defined on
+the right side of the assignment and is thus not a property of any given
+TypoScript object.
+
+This is just a very quick overview. As usual, the :ref:`TypoScript Reference
+<data-type-gettext>` is your friend.
diff --git a/Documentation/Guide/TypoScriptFunctions/If/Index.rst b/Documentation/Guide/TypoScriptFunctions/If/Index.rst
new file mode 100644
index 000000000..4f25bca4a
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/If/Index.rst
@@ -0,0 +1,29 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-function-if:
+
+==
+if
+==
+
+The :ref:`if <if>` function is perhaps the most difficult
+of all TypoScript functions. It does not work like the "if" construct
+known from most programming language and is thus very open to misuse.
+Hopefully the examples below will help you get it right.
+
+Generally the `if` function returns `true`,
+if **all** conditions are fulfilled. This resembles a boolean AND combination.
+If what we would like returned is a `false` value,
+we can use the :code:`negate` option to negate the result:
+
+..  literalinclude:: _if.typoscript
+
+With the use of `if` it is also possible to compare values. For this
+purpose we use `value` property:
+
+..  literalinclude:: _if2.typoscript
+
+Because the properties of the `if` function implement
+:ref:`stdWrap functions <guide-using-stdwrap>`, all kinds of variables can be compared:
+
+..  literalinclude:: _if3.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/If/_if.typoscript b/Documentation/Guide/TypoScriptFunctions/If/_if.typoscript
new file mode 100644
index 000000000..983842fcc
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/If/_if.typoscript
@@ -0,0 +1,10 @@
+10 = TEXT
+10 {
+
+  # Content of the TEXT object.
+  value = The L parameter is passed as GET variable.
+
+  # Results in "true" and leads to rendering of the upper value, if the
+  # GET/POST parameter is passed with a value, which is not 0.
+  stdWrap.if.isTrue.data = GP:L
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/If/_if2.typoscript b/Documentation/Guide/TypoScriptFunctions/If/_if2.typoscript
new file mode 100644
index 000000000..ae87305ce
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/If/_if2.typoscript
@@ -0,0 +1,13 @@
+10 = TEXT
+10 {
+
+  # WARNING: This value resembles the value of the TEXT object, not that of the "if"!
+  value = 3 is bigger than 2.
+
+  # Compare parameter of the "if" function.
+  stdWrap.if.value = 2
+
+  # Please note: The sorting order is "backwards",
+  # returning the sentence "3 is bigger than 2".
+  stdWrap.if.isGreaterThan = 3
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/If/_if3.typoscript b/Documentation/Guide/TypoScriptFunctions/If/_if3.typoscript
new file mode 100644
index 000000000..8b185372f
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/If/_if3.typoscript
@@ -0,0 +1,11 @@
+10 = TEXT
+10 {
+  # Value of the TEXT object.
+  value = The record can be shown, because the starting date has passed.
+
+  # Condition of the if clause (number of seconds since January 1st, 1970).
+  stdWrap.if.value.data = date:U
+
+  # Condition backwards again: Start time isLessThan date:U.
+  stdWrap.if.isLessThan.field = starttime
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/ImgResource/Index.rst b/Documentation/Guide/TypoScriptFunctions/ImgResource/Index.rst
new file mode 100644
index 000000000..b8e5c3f20
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ImgResource/Index.rst
@@ -0,0 +1,23 @@
+..  include:: /Includes.rst.txt
+..  _guide-imgresource:
+
+===========
+imgResource
+===========
+
+The :ref:`imgResource <imgresource>` function relates to modifications of
+pictures. Its main usage is the property `file` of the
+:ref:`IMAGE <cobj-image>` object.
+
+This, for example, allows an image to be resized:
+
+..  literalinclude:: _temp.myImage.typoscript
+
+It is also possible to set minimum or maximum dimensions:
+
+..  literalinclude:: _temp.myImage2.typoscript
+
+`imgResource` also provides direct access to
+ImageMagick/GraphicsMagick features:
+
+..  literalinclude:: _temp.myImage3.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage.typoscript b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage.typoscript
new file mode 100644
index 000000000..784ad787f
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage.typoscript
@@ -0,0 +1,6 @@
+temp.myImage = IMAGE
+temp.myImage {
+  file = toplogo.gif
+  file.width = 200
+  file.height = 300
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage2.typoscript b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage2.typoscript
new file mode 100644
index 000000000..9b48a8f2e
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage2.typoscript
@@ -0,0 +1,12 @@
+temp.myImage = IMAGE
+temp.myImage {
+  file = toplogo.gif
+
+  # maximum size
+  file.maxW = 200
+  file.maxH = 300
+
+  # minimum size
+  file.minW = 100
+  file.minH = 120
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage3.typoscript b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage3.typoscript
new file mode 100644
index 000000000..0bdde67f9
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ImgResource/_temp.myImage3.typoscript
@@ -0,0 +1,5 @@
+temp.myImage = IMAGE
+temp.myImage {
+  file = toplogo.gif
+  file.params = -rotate 90
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/Index.rst b/Documentation/Guide/TypoScriptFunctions/Index.rst
new file mode 100644
index 000000000..fe965f0d0
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Index.rst
@@ -0,0 +1,31 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-functions:
+
+====================
+TypoScript functions
+====================
+
+TypoScript functions can be considered as a set of common properties. Whenever
+an object has a property corresponding to a given function, you are assured to
+have that set of properties available.
+
+This chapter gives you a brief overview of the most common functions available
+in TypoScript. See chapter :ref:`Functions <functions>` for a complete list.
+
+The most used function is the "standard wrap", usually known as "stdWrap".
+
+..  toctree::
+    :caption: The functions
+    :maxdepth: 1
+    :titlesonly:
+
+    StdWrap/Index
+    GetText/Index
+    ImgResource/Index
+    Select/Index
+    Split/Index
+    If/Index
+    Typolink/Index
+    ParseFunc/Index
+
diff --git a/Documentation/Guide/TypoScriptFunctions/ParseFunc/Index.rst b/Documentation/Guide/TypoScriptFunctions/ParseFunc/Index.rst
new file mode 100644
index 000000000..e4e2e62e6
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ParseFunc/Index.rst
@@ -0,0 +1,24 @@
+..  include:: /Includes.rst.txt
+
+
+..  _guide-function-parsefunc:
+
+=========
+parseFunc
+=========
+
+This function parses the main part of the content, i.e., the content which has
+been entered in the Rich Text Editor. The function is responsible for the fact
+that the content is not rendered exactly as it was entered in the RTE. Some
+default parsing rules are implemented in the core, like parsing link tags via
+:ref:`typolink` function.
+
+You can also use :typoscript:`parseFunc` for your own processing. In the following
+example, every occurrence of "COMP" is replaced by "My company name":
+
+..  literalinclude:: _parseFunc.typoscript
+
+The various possibilities of changing the default behavior can be found by
+using the TypoScript object browser. All possibilities of how parseFunc can
+alter the rendering can be found in the
+:ref:`TypoScript Reference <parsefunc>`.
diff --git a/Documentation/Guide/TypoScriptFunctions/ParseFunc/_parseFunc.typoscript b/Documentation/Guide/TypoScriptFunctions/ParseFunc/_parseFunc.typoscript
new file mode 100644
index 000000000..bda961bc2
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/ParseFunc/_parseFunc.typoscript
@@ -0,0 +1,3 @@
+page.stdWrap.parseFunc.short {
+  COMP = My company name
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/Select/Index.rst b/Documentation/Guide/TypoScriptFunctions/Select/Index.rst
new file mode 100644
index 000000000..4043d8a48
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Select/Index.rst
@@ -0,0 +1,17 @@
+..  include:: /Includes.rst.txt
+..  _guide-function-select:
+
+======
+select
+======
+
+The :ref:`select <select>` function generates a SQL SELECT query, which
+is used to read records from the database. `select` automatically checks
+whether the records might be "hidden", "deleted", or if they have a "start and
+end date". If `pidInList` is used (meaning a list of pages is rendered),
+the function also checks if the current user is allowed to see all records.
+
+With the help of the select function, it is possible to show the content of a
+page on all pages. For example:
+
+..  literalinclude:: _temp.leftContent.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/Select/_temp.leftContent.typoscript b/Documentation/Guide/TypoScriptFunctions/Select/_temp.leftContent.typoscript
new file mode 100644
index 000000000..c8e207f5a
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Select/_temp.leftContent.typoscript
@@ -0,0 +1,22 @@
+temp.leftContent = CONTENT
+temp.leftContent {
+
+  table = tt_content
+  select {
+
+    # The page with ID = 123 is the source.
+    pidInList = 123
+
+    # Sorting is the same as in the backend.
+    orderBy = sorting
+
+    # Only select the content of the left column.
+    where = {#colPos}=1
+
+    # Define the field with the language ID in tt_content.
+    languageField = sys_language_uid
+  }
+}
+
+# Replace the mark ###LEFT### with the output of temp.leftContent.
+marks.LEFT < temp.leftContent
diff --git a/Documentation/Guide/TypoScriptFunctions/Split/Index.rst b/Documentation/Guide/TypoScriptFunctions/Split/Index.rst
new file mode 100644
index 000000000..4bc8cf60d
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Split/Index.rst
@@ -0,0 +1,18 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-function-split:
+
+=====
+split
+=====
+
+The :ref:`split <split>` function can be used to split given data at a predefined
+character and process the single pieces afterwards. At every
+iteration, the current index key `SPLIT-COUNT` is stored (starting
+with 0).
+
+By using `split`, we could, for example, read a table field and wrap
+every single line with a certain code (e.g. generate an HTML table,
+which can be used to show the same content on more than one page):
+
+..  literalinclude:: _split.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/Split/_split.typoscript b/Documentation/Guide/TypoScriptFunctions/Split/_split.typoscript
new file mode 100644
index 000000000..fd3329a0f
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Split/_split.typoscript
@@ -0,0 +1,31 @@
+20 = TEXT
+
+# The content of the field "bodytext" is imported (from $cObj->data-array).
+20.stdWrap.field = bodytext
+20.stdWrap.split {
+
+  # The separation character is defined (char = 10 is the newline character).
+  token.char = 10
+
+  # We define which element will be used.
+  # By using optionSplit we can distinguish between elements.
+  # Corresponding elements with the numbers must be defined!
+  # For rendering, the numbers 1 and 2 are used in alternation.
+  # In this example, the classes "odd" and "even" are used so we
+  # can zebra style a table.
+  cObjNum = |*|1||2|*|
+
+  # The first element is defined (which is referenced by cObjNum).
+  # The content is imported using stdWrap->current.
+  1.current = 1
+
+  # The element is wrapped.
+  1.wrap = <tr class="odd"><td> | </td></tr>
+
+  # The 2nd element is determined and wrapped.
+  2.current = 1
+  2.wrap = <tr class="even"><td> | </td></tr>
+}
+
+# A general wrap to create a valid table markup.
+20.stdWrap.wrap = <table> | </table>
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/Index.rst b/Documentation/Guide/TypoScriptFunctions/StdWrap/Index.rst
new file mode 100644
index 000000000..c666f1d53
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/Index.rst
@@ -0,0 +1,31 @@
+:navigation-title: stdWrap
+..  include:: /Includes.rst.txt
+..  _guide-using-stdwrap:
+
+=======================
+Using stdWrap correctly
+=======================
+
+The :ref:`stdWrap <stdwrap>` function is one of the most powerful and
+most widely used of all TypoScript. Most properties actually support `stdWrap`
+turning each of them into some kind of Swiss army knife.
+
+`stdWrap` is very rich, having itself a large number of properties. This
+chapter is intended to give you a feel for `stdWrap` so that you may get
+familiar with it and be ready to explore it in greater depth using the
+:ref:`TypoScript Reference <stdwrap>`.
+
+..  contents:: Details of stdWrap
+
+..  include:: _Chapters/_HeedTheOrder.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_ModifyTheOrder.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_TheDataType.rst.txt
+    :show-buttons:
+
+..  include:: _Chapters/_CObject.rst.txt
+    :show-buttons:
+
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_CObject.rst.txt b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_CObject.rst.txt
new file mode 100644
index 000000000..52b5ea64d
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_CObject.rst.txt
@@ -0,0 +1,12 @@
+..  _guide-stdwrap-cobject:
+
+=======
+cObject
+=======
+
+The `stdWrap` property ":ref:`cObject <stdwrap-cobject>`" can be
+used to replace the content with a TypoScript object. This can be a
+:ref:`COA <cobj-coa>`, a plugin or a text like in this
+example:
+
+..  literalinclude:: /Guide/TypoScriptFunctions/StdWrap/_snippets/_cObject.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_HeedTheOrder.rst.txt b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_HeedTheOrder.rst.txt
new file mode 100644
index 000000000..dbc36790e
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_HeedTheOrder.rst.txt
@@ -0,0 +1,24 @@
+..  _guide-stdwrap-order:
+
+==============
+Heed the order
+==============
+
+The single most important thing to know about `stdWrap` is that all
+properties are parsed/executed exactly in the order in which they appear in the
+:ref:`TypoScript Reference <stdwrap>`, no matter in which order you
+have set them in your TypoScript record.
+
+Let's consider this example:
+
+..  literalinclude:: /Guide/TypoScriptFunctions/StdWrap/_snippets/_order.typoscript
+
+It results in the following:
+
+..  code-block:: html
+
+    <strong>Tool: TYPO3</strong>
+
+The `case` property is executed before the `noTrimWrap` property.
+Hence only "typo3" was changed to uppercase and not the "Tool:" with which it
+is wrapped.
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_ModifyTheOrder.rst.txt b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_ModifyTheOrder.rst.txt
new file mode 100644
index 000000000..7357f4090
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_ModifyTheOrder.rst.txt
@@ -0,0 +1,25 @@
+..  _guide-stdwrap-recursively:
+
+================
+Modify the order
+================
+
+There is a way around this ordering restriction. `stdWrap` has a property
+called `orderedStdWrap` in which several `stdWrap` properties can
+be called in numerical order. Thus:
+
+..  literalinclude:: /Guide/TypoScriptFunctions/StdWrap/_snippets/_orderedStdWrap.typoscript
+
+results in:
+
+..  code-block:: html
+
+    <strong>TOOL: TYPO3</strong>
+
+because we explicitly specified that `noTrimWrap` should happen before
+`case`.
+
+It should be noted that `stdWrap` itself has a `stdWrap` property,
+meaning that it can be called recursively. In most case `orderedStdWrap`
+will do the job and is much easier to understand making code easier to
+maintain.
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_TheDataType.rst.txt b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_TheDataType.rst.txt
new file mode 100644
index 000000000..a3c44a140
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_Chapters/_TheDataType.rst.txt
@@ -0,0 +1,15 @@
+
+..  _guide-data-types:
+
+=============
+The data type
+=============
+
+While writing TypoScript, it is crucial to know what kind of data type
+you are handling. It is common to see beginners try to combine functions
+arbitrarily, until the anticipated result is finally achieved by accident.
+
+The :ref:`TypoScript reference <stdWrap>` is very clear about
+which properties exist and what their data type is, so please refer
+to that essential resource while writing your TypoScript configuration.
+
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_cObject.typoscript b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_cObject.typoscript
new file mode 100644
index 000000000..b3f556fcd
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_cObject.typoscript
@@ -0,0 +1,5 @@
+10.typolink.title.cObject = TEXT
+10.typolink.title.cObject {
+  value = Copyright
+  case = upper
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_order.typoscript b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_order.typoscript
new file mode 100644
index 000000000..ff923304f
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_order.typoscript
@@ -0,0 +1,6 @@
+10 = TEXT
+10 {
+  value = typo3
+  noTrimWrap = |<strong>Tool: |</strong>|
+  case = upper
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_orderedStdWrap.typoscript b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_orderedStdWrap.typoscript
new file mode 100644
index 000000000..03d7ced87
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/StdWrap/_snippets/_orderedStdWrap.typoscript
@@ -0,0 +1,8 @@
+10 = TEXT
+10 {
+  value = typo3
+  orderedStdWrap {
+    10.noTrimWrap = |<strong>Tool: |</strong>|
+    20.case = upper
+  }
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/Typolink/Index.rst b/Documentation/Guide/TypoScriptFunctions/Typolink/Index.rst
new file mode 100644
index 000000000..b5150101c
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Typolink/Index.rst
@@ -0,0 +1,46 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-function-typolink:
+
+========
+typolink
+========
+
+:ref:`typolink <typolink>` is the TYPO3 CMS function
+that allows us to generate all kinds of links.
+If possible one should always use this function to generate links
+as they will be processed by TYPO3 CMS. This is a prerequisite,
+for example, for the anti-spam protection of email addresses.
+
+Please resist the urge to a straight `<a href="...">...</a>` construct
+in your TypoScript and Fluid templates.
+
+Basically `typolink` links the specified text according to
+the defined parameters. One example:
+
+..  literalinclude:: _temp.link.typoscript
+
+The example above will generate this HTML code:
+
+..  code-block:: html
+
+    <a href="http://www.example.com/" target="_blank" class="linkclass" rel="noreferrer">Example link</a>
+
+`typolink`, in a way, almost works like a wrap: the content which is
+defined for example by the `value` property, will be wrapped by the HTML anchor tag.
+If no content is defined, it will be generated automatically. With a
+link to a page, the page title will be used. With an external URL, the
+URL will be shown.
+
+The above example can actually be shortened, because the
+`parameter` property can take a series of values separated
+by a white space:
+
+..  literalinclude:: _temp.link2.typoscript
+
+The exact syntax for `parameter` property is fully described,
+as usual, in the :ref:`TypoScript Reference <typolink>`.
+
+It is even possible to define links that open in JavaScript popups:
+
+..  literalinclude:: _temp.link3.typoscript
diff --git a/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link.typoscript b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link.typoscript
new file mode 100644
index 000000000..947359cb8
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link.typoscript
@@ -0,0 +1,19 @@
+temp.link = TEXT
+temp.link {
+
+  # This is the defined text.
+  value = Example link
+
+  # Here comes the typolink function.
+  typolink {
+
+    # This is the destination of the link...
+    parameter = http://www.example.com/
+
+    # with a target ("_blank" opens a new window)...
+    extTarget = _blank
+
+    # and add a class to the link so we can style it.
+    ATagParams = class="linkclass"
+  }
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link2.typoscript b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link2.typoscript
new file mode 100644
index 000000000..96b26f2d8
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link2.typoscript
@@ -0,0 +1,10 @@
+temp.link2 = TEXT
+temp.link2 {
+
+  # Again the defined text.
+  value = Example link
+
+  # The parameter with the summary of the parameters of the first
+  # example (explanation follows below).
+  typolink.parameter = www.example.com _blank linkclass
+}
diff --git a/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link3.typoscript b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link3.typoscript
new file mode 100644
index 000000000..57922d552
--- /dev/null
+++ b/Documentation/Guide/TypoScriptFunctions/Typolink/_temp.link3.typoscript
@@ -0,0 +1,19 @@
+temp.link3 = TEXT
+temp.link3 {
+
+  # The link text.
+  value = Open a popup window.
+
+  stdWrap.typolink {
+    # The first parameter is the page ID of the target page,
+    # second parameter is the size of the popup window.
+    parameter = 10 500x400
+
+    # The title attribute of the link.
+    title = Click here to open a popup window.
+
+    # The parameters of the popup window.
+    JSwindow_params = menubar=0, scrollbars=0, toolbar=0, resizable=1
+
+  }
+}
diff --git a/Documentation/Guide/TypoScriptObjects/DatabaseQueries/Index.rst b/Documentation/Guide/TypoScriptObjects/DatabaseQueries/Index.rst
new file mode 100644
index 000000000..3b394fb8d
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/DatabaseQueries/Index.rst
@@ -0,0 +1,30 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-cobjects-database-queries:
+
+==================================
+Objects executing database queries
+==================================
+
+*   :ref:`CONTENT <cobj-content>` can be used to access arbitrary tables
+    of TYPO3 CMS internals. This does not only include table "tt\_content", but
+    extension tables can also be referenced. The :ref:`select <select>`
+    function makes it possible to generate complex SQL queries.
+
+*   :ref:`RECORDS <cobj-records>` can be used to reference specific data
+    records. This is very helpful if the same text has to be present on all
+    pages. By using RECORDS, a single content element can be defined and shown.
+    Thus, an editor can edit the content without having to copy the element
+    repetitively. This object is also used by the content element type "Insert
+    records".
+
+    In the following example, the email address from an address record is
+    rendered and linked as email at the same time:
+
+    ..  literalinclude:: _RECORDS.typoscript
+
+*   :ref:`HMENU <cobj-hmenu>` imports the page tree and offers
+    comfortable ways to generate a menu of pages or a sitemap. Special menus
+    include the breadcrumb trail, simple list of pages or subpages, a page
+    browser (providing "Previous" and "Next" buttons for a set of pages) and a
+    language selector.
diff --git a/Documentation/Guide/TypoScriptObjects/DatabaseQueries/_RECORDS.typoscript b/Documentation/Guide/TypoScriptObjects/DatabaseQueries/_RECORDS.typoscript
new file mode 100644
index 000000000..fd1a9ec45
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/DatabaseQueries/_RECORDS.typoscript
@@ -0,0 +1,11 @@
+page.80 = RECORDS
+page.80 {
+  source = 1
+  tables = tt_address
+  conf.tt_address = COA
+  conf.tt_address {
+    20 = TEXT
+    20.stdWrap.field = email
+    20.stdWrap.typolink.parameter.field = email
+  }
+}
diff --git a/Documentation/Guide/TypoScriptObjects/FurtherObjects/Index.rst b/Documentation/Guide/TypoScriptObjects/FurtherObjects/Index.rst
new file mode 100644
index 000000000..1b5a00378
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/FurtherObjects/Index.rst
@@ -0,0 +1,42 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-cobjects-further-cobjects:
+
+===============
+Further objects
+===============
+
+*   :ref:`CASE <cobj-case>` allows case differentiation. In the core this
+    object is used for rendering different content elements according to their
+    type.
+
+*   :ref:`COA <cobj-coa>` (content object array) allows us to combine an
+    arbitrary number of objects.
+
+*   :ref:`COA\_INT <cobj-coa-int>` is a COA object, but non-cached. This
+    element will be regenerated upon each call. This is useful with time and date
+    or user-dependent data, for example.
+
+*   :ref:`LOAD\_REGISTER <cobj-load-register>` /
+    :ref:`RESTORE\_REGISTER <cobj-restore-register>` objects allow us to
+    fill the global array `$GLOBALS['TSFE']->register[]` with content.
+    These objects return nothing. Single values and complete TypoScript
+    objects can be used. In doing so, the register works as a stack: With
+    every call, a further element is stacked. With
+    `RESTORE_REGISTER`, the element on top can be removed.
+    Values in the register can be used with the
+    :ref:`getText <data-type-gettext-register>` data type.
+
+*   :ref:`USER <cobj-user>` and USER\_INT are for user-defined functions.
+    Every frontend plugin from a TYPO3 CMS extension is such an object.
+    :ref:`USER\_INT <cobj-user-int>` is the non-cached variant.
+
+*   :ref:`IMG\_RESOURCE <cobj-img-resource>` is used by the
+    :ref:`IMAGE <cobj-image>` object. The resource returned is
+    normally the `src` attribute of the `<img>` tag.
+    If images are scaled, this object serves as
+    a calculation basis for the new files, which are stored in the
+    :file:`_processed_` folder of each file storage.
+
+*   :ref:`GIFBUILDER <gifbuilder>` is used for generating image files
+    dynamically. Various texts and images can be combined, and much more.
diff --git a/Documentation/Guide/TypoScriptObjects/Index.rst b/Documentation/Guide/TypoScriptObjects/Index.rst
new file mode 100644
index 000000000..e83eccd54
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/Index.rst
@@ -0,0 +1,25 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-cobjects:
+
+==================
+TypoScript objects
+==================
+
+As we already saw there is quite a variety of TypoScript objects. Each object
+has a number of properties. These can be simple data types or functions, which
+have their own set of properties. Using properties that don't exist will have
+no effect.
+
+The :doc:`TypoScript Reference <Index>` lists all data types, functions
+and objects with their properties. This chapter offers a short overview of the
+most common objects to give you an idea of what is available.
+
+
+**Some most common objects:**
+
+..  toctree::
+
+   DatabaseQueries/Index
+   RenderingContent/Index
+   FurtherObjects/Index
diff --git a/Documentation/Guide/TypoScriptObjects/RenderingContent/Index.rst b/Documentation/Guide/TypoScriptObjects/RenderingContent/Index.rst
new file mode 100644
index 000000000..5441c6731
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/RenderingContent/Index.rst
@@ -0,0 +1,34 @@
+..  include:: /Includes.rst.txt
+
+..  _guide-cobjects-rendering-content:
+
+=========================
+Objects rendering content
+=========================
+
+-   :ref:`IMAGE <cobj-image>` for the rendering of an image:
+
+    ..  literalinclude:: _IMAGE.typoscript
+
+    The result is an image based on file :file:`logo.gif` with width of 200 pixels
+    and a link to the page 1.
+
+-   :ref:`TEXT <cobj-text>` is for the rendering of standard text or the
+    content of fields:
+
+    ..  literalinclude:: _lib.slogan.typoscript
+
+-   :ref:`FILES <cobj-files>` is used to retrieve information about one
+    or more files and perform some rendering with it:
+
+    ..  literalinclude:: _lib.banner.typoscript
+
+    This code will probably look pretty abstract to you right now. What it does
+    is to reference the images that were related to a given page in the "media"
+    field. It takes each of these images and resizes them to a maximum width of
+    500 pixels. Each image is wrapped in a `<div>` tag.
+
+-   :ref:`FLUIDTEMPLATE <cobj-fluidtemplate>` renders a template with the
+    template engine Fluid with variables and data that you define - as previously
+    discussed in the ":ref:`insert-content-in-a-template`" chapter.
+
diff --git a/Documentation/Guide/TypoScriptObjects/RenderingContent/_IMAGE.typoscript b/Documentation/Guide/TypoScriptObjects/RenderingContent/_IMAGE.typoscript
new file mode 100644
index 000000000..81f36bcef
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/RenderingContent/_IMAGE.typoscript
@@ -0,0 +1,6 @@
+lib.logo = IMAGE
+lib.logo {
+  file = fileadmin/logo.gif
+  file.width = 200
+  stdWrap.typolink.parameter = 1
+}
diff --git a/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.banner.typoscript b/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.banner.typoscript
new file mode 100644
index 000000000..bfa9f7bec
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.banner.typoscript
@@ -0,0 +1,15 @@
+lib.banner = FILES
+lib.banner {
+  references {
+    table = pages
+    fieldName = media
+    uid.data = page:uid
+  }
+  renderObj = IMAGE
+  renderObj {
+    file.import.data = file:current:uid
+    file.treatIdAsReference = 1
+    file.width = 500
+    wrap = <div class="banner">|</div>
+  }
+}
diff --git a/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.slogan.typoscript b/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.slogan.typoscript
new file mode 100644
index 000000000..c6de9410e
--- /dev/null
+++ b/Documentation/Guide/TypoScriptObjects/RenderingContent/_lib.slogan.typoscript
@@ -0,0 +1,3 @@
+lib.slogan = TEXT
+lib.slogan.value = Inspiring people to share
+lib.slogan.wrap = <div class="highlight">|</div>
diff --git a/Documentation/Guide/UsingFluidStyledContent/Index.rst b/Documentation/Guide/UsingFluidStyledContent/Index.rst
new file mode 100644
index 000000000..bcf5d065c
--- /dev/null
+++ b/Documentation/Guide/UsingFluidStyledContent/Index.rst
@@ -0,0 +1,47 @@
+:navigation-title: fluid_styled_content
+..  include:: /Includes.rst.txt
+..  _using-fluid-styled-content:
+
+============================
+Using fluid\_styled\_content
+============================
+
+It is worth taking a deeper look at the TypoScript of the system extension
+:composer:`typo3/cms-fluid-styled-content`. It comes with
+more than 900 lines of TypoScript code containing definitions for each type of
+content element.
+
+Although it may seem daunting, it is very instructive to review all this code,
+as there is much to learn by example. To view the raw code, place yourself on
+the root page of your website and move to the
+:guilabel:`Site Management > TypoScript` module. Then
+choose the submodule :guilabel:`Included TypoScript` from the drop-down.
+
+You should see a list of all used TypoScript records and files and how they possibly
+include one another. All TypoScript is evaluated by TYPO3 CMS from top to
+bottom.
+
+..  figure:: /Images/ManualScreenshots/IncludedTypoScript.png
+    :alt: Screenshot of the module Site Management > TypoScript > Included TypoScript
+
+    Click on the :guilabel:`{ }`,  "show code", button to see the code
+
+With a click on the :guilabel:`{ }`,  "show code", button, you can view the content
+of that TypoScript file.
+
+As the TypoScript is split up in several files you can also use the
+:guilabel:`{ + }`,  "show resolved code", button to show the code including all
+its includes.
+
+You will see that the set `set:typo3/fluid-styled-content` adds rendering
+definitions for all
+content elements. When rendering special content like file relations or menus
+the concept of data processors is used. You can find out more about data
+processors in the :doc:`manual of fluid_styled_content
+<typo3/cms-fluid-styled-content:Index>`.
+
+HTML purists may find that the set `set:typo3/fluid-styled-content` generates
+too much markup.
+
+It is perfectly possible to trim down this setup or write one's own entirely.
+However this is not recommended for beginners.
diff --git a/Documentation/Images/AutomaticScreenshots/Input1.png b/Documentation/Images/AutomaticScreenshots/Input1.png
new file mode 100644
index 000000000..66448f717
Binary files /dev/null and b/Documentation/Images/AutomaticScreenshots/Input1.png differ
diff --git a/Documentation/Images/AutomaticScreenshots/Input1.rst.txt b/Documentation/Images/AutomaticScreenshots/Input1.rst.txt
new file mode 100644
index 000000000..bbd084dfe
--- /dev/null
+++ b/Documentation/Images/AutomaticScreenshots/Input1.rst.txt
@@ -0,0 +1,4 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. figure:: /Images/AutomaticScreenshots/Input1.png
+   :class: with-shadow
\ No newline at end of file
diff --git a/Documentation/Images/AutomaticScreenshots/RootlevelFlag.png b/Documentation/Images/AutomaticScreenshots/RootlevelFlag.png
new file mode 100644
index 000000000..db41db309
Binary files /dev/null and b/Documentation/Images/AutomaticScreenshots/RootlevelFlag.png differ
diff --git a/Documentation/Images/AutomaticScreenshots/RootlevelFlag.rst.txt b/Documentation/Images/AutomaticScreenshots/RootlevelFlag.rst.txt
new file mode 100644
index 000000000..90de54e87
--- /dev/null
+++ b/Documentation/Images/AutomaticScreenshots/RootlevelFlag.rst.txt
@@ -0,0 +1,7 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. figure:: /Images/AutomaticScreenshots/RootlevelFlag.png
+   :alt: The Rootlevel flag in the tab Options a template record
+   :class: with-shadow
+
+   The :guilabel:`Rootlevel` flag in the tab :guilabel:`Options` a template record
\ No newline at end of file
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.png b/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.png
new file mode 100644
index 000000000..9308ce029
Binary files /dev/null and b/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.png differ
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.rst.txt b/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.rst.txt
new file mode 100644
index 000000000..f295f3870
--- /dev/null
+++ b/Documentation/Images/AutomaticScreenshots/WebList/ExportDialog.rst.txt
@@ -0,0 +1,4 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. figure:: /Images/AutomaticScreenshots/WebList/ExportDialog.png
+   :class: with-shadow
\ No newline at end of file
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.png b/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.png
new file mode 100644
index 000000000..2b7978dac
Binary files /dev/null and b/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.png differ
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.rst.txt b/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.rst.txt
new file mode 100644
index 000000000..3f908e3cb
--- /dev/null
+++ b/Documentation/Images/AutomaticScreenshots/WebList/NoExportButtons.rst.txt
@@ -0,0 +1,6 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. figure:: /Images/AutomaticScreenshots/WebList/NoExportButtons.png
+   :class: with-shadow
+
+   The list module without export buttons after activating the single-table mode
\ No newline at end of file
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.png b/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.png
new file mode 100644
index 000000000..178d6adce
Binary files /dev/null and b/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.png differ
diff --git a/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.rst.txt b/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.rst.txt
new file mode 100644
index 000000000..ae0d2eeda
--- /dev/null
+++ b/Documentation/Images/AutomaticScreenshots/WebList/WithExportButtons.rst.txt
@@ -0,0 +1,6 @@
+.. Automatic screenshot: Remove this line if you want to manually change this file
+
+.. figure:: /Images/AutomaticScreenshots/WebList/WithExportButtons.png
+   :class: with-shadow
+
+   The list module with export buttons after activating the single-table mode
\ No newline at end of file
diff --git a/Documentation/Images/ManualScreenshots/Access/AccessDefaultActions.png b/Documentation/Images/ManualScreenshots/Access/AccessDefaultActions.png
new file mode 100644
index 000000000..56a5a20a6
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Access/AccessDefaultActions.png differ
diff --git a/Documentation/Images/ManualScreenshots/Access/AccessDefaultPermissions.png b/Documentation/Images/ManualScreenshots/Access/AccessDefaultPermissions.png
new file mode 100644
index 000000000..1428dfc35
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Access/AccessDefaultPermissions.png differ
diff --git a/Documentation/Images/ManualScreenshots/AdminPanel/UserTsAdminPanel.png b/Documentation/Images/ManualScreenshots/AdminPanel/UserTsAdminPanel.png
new file mode 100644
index 000000000..00e80c701
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/AdminPanel/UserTsAdminPanel.png differ
diff --git a/Documentation/Images/ManualScreenshots/BackendLayouts/PageModule.png b/Documentation/Images/ManualScreenshots/BackendLayouts/PageModule.png
new file mode 100644
index 000000000..b0341d07e
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/BackendLayouts/PageModule.png differ
diff --git a/Documentation/Images/ManualScreenshots/BackendLayouts/PageProperties.png b/Documentation/Images/ManualScreenshots/BackendLayouts/PageProperties.png
new file mode 100644
index 000000000..99aa03d5c
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/BackendLayouts/PageProperties.png differ
diff --git a/Documentation/Images/ManualScreenshots/BackendUsers/TSconfigUserInput.png b/Documentation/Images/ManualScreenshots/BackendUsers/TSconfigUserInput.png
new file mode 100644
index 000000000..b92e38836
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/BackendUsers/TSconfigUserInput.png differ
diff --git a/Documentation/Images/ManualScreenshots/ColorPalettes/ColorPalette.png b/Documentation/Images/ManualScreenshots/ColorPalettes/ColorPalette.png
new file mode 100644
index 000000000..14821e5fe
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/ColorPalettes/ColorPalette.png differ
diff --git a/Documentation/Images/ManualScreenshots/Configuration/UserTSconfigOverview.png b/Documentation/Images/ManualScreenshots/Configuration/UserTSconfigOverview.png
new file mode 100644
index 000000000..9fe143cea
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Configuration/UserTSconfigOverview.png differ
diff --git a/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/ContentObjectsHmenuSpecialBrowse.png b/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/ContentObjectsHmenuSpecialBrowse.png
deleted file mode 100644
index 43f1572e2..000000000
Binary files a/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/ContentObjectsHmenuSpecialBrowse.png and /dev/null differ
diff --git a/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/MenuObjectsCommonPropertiesSubmenuObjSuffixes.png b/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/MenuObjectsCommonPropertiesSubmenuObjSuffixes.png
deleted file mode 100644
index 2e5ceb489..000000000
Binary files a/Documentation/Images/ManualScreenshots/FrontendOutput/Hmenu/MenuObjectsCommonPropertiesSubmenuObjSuffixes.png and /dev/null differ
diff --git a/Documentation/Images/ManualScreenshots/IncludedTypoScript.png b/Documentation/Images/ManualScreenshots/IncludedTypoScript.png
new file mode 100644
index 000000000..23938b900
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/IncludedTypoScript.png differ
diff --git a/Documentation/Images/ManualScreenshots/Info/FunctionMenuInfoModule.png b/Documentation/Images/ManualScreenshots/Info/FunctionMenuInfoModule.png
new file mode 100644
index 000000000..b9904ce27
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Info/FunctionMenuInfoModule.png differ
diff --git a/Documentation/Images/ManualScreenshots/Info/PageTsModWebInfoFieldDefinitions.png b/Documentation/Images/ManualScreenshots/Info/PageTsModWebInfoFieldDefinitions.png
new file mode 100644
index 000000000..f791c1743
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Info/PageTsModWebInfoFieldDefinitions.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/BackendLayoutID.png b/Documentation/Images/ManualScreenshots/List/BackendLayoutID.png
new file mode 100644
index 000000000..10603cfcf
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/BackendLayoutID.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/BackendLayoutsExcluded.png b/Documentation/Images/ManualScreenshots/List/BackendLayoutsExcluded.png
new file mode 100644
index 000000000..969a7095d
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/BackendLayoutsExcluded.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/FileListPrimaryActions.png b/Documentation/Images/ManualScreenshots/List/FileListPrimaryActions.png
new file mode 100644
index 000000000..5fc3a195a
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/FileListPrimaryActions.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/NewRecordWizardNewOrder.png b/Documentation/Images/ManualScreenshots/List/NewRecordWizardNewOrder.png
new file mode 100644
index 000000000..199ebd8b9
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/NewRecordWizardNewOrder.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PageCopyWithSuffix.png b/Documentation/Images/ManualScreenshots/List/PageCopyWithSuffix.png
new file mode 100644
index 000000000..c34f5364a
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PageCopyWithSuffix.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PageTsModWebListAllowedNewTables.png b/Documentation/Images/ManualScreenshots/List/PageTsModWebListAllowedNewTables.png
new file mode 100644
index 000000000..3b96446f3
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PageTsModWebListAllowedNewTables.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PageTsModWebListListOnlyInSingleTableView.png b/Documentation/Images/ManualScreenshots/List/PageTsModWebListListOnlyInSingleTableView.png
new file mode 100644
index 000000000..48836c8d4
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PageTsModWebListListOnlyInSingleTableView.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewContentElementExample2.png b/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewContentElementExample2.png
new file mode 100644
index 000000000..24079df00
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewContentElementExample2.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewRecordHideInside.png b/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewRecordHideInside.png
new file mode 100644
index 000000000..2ee0acb09
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PageTsModWizardsNewRecordHideInside.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PagesContextMenu.png b/Documentation/Images/ManualScreenshots/List/PagesContextMenu.png
new file mode 100644
index 000000000..a36878b9e
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PagesContextMenu.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PagesDoktypeDifferentLabels.png b/Documentation/Images/ManualScreenshots/List/PagesDoktypeDifferentLabels.png
new file mode 100644
index 000000000..802efef4a
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PagesDoktypeDifferentLabels.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PanelModified.png b/Documentation/Images/ManualScreenshots/List/PanelModified.png
new file mode 100644
index 000000000..7e3adbe36
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PanelModified.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PanelNormal.png b/Documentation/Images/ManualScreenshots/List/PanelNormal.png
new file mode 100644
index 000000000..6233d6f48
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PanelNormal.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/PanelUserDB.png b/Documentation/Images/ManualScreenshots/List/PanelUserDB.png
new file mode 100644
index 000000000..a5bfa4755
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/PanelUserDB.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/SelectFlagIcon.png b/Documentation/Images/ManualScreenshots/List/SelectFlagIcon.png
new file mode 100644
index 000000000..8275488dc
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/SelectFlagIcon.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/SelectInvalidValue.png b/Documentation/Images/ManualScreenshots/List/SelectInvalidValue.png
new file mode 100644
index 000000000..843266ee9
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/SelectInvalidValue.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/SelectInvalidValueDifferentLabel.png b/Documentation/Images/ManualScreenshots/List/SelectInvalidValueDifferentLabel.png
new file mode 100644
index 000000000..ec3647743
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/SelectInvalidValueDifferentLabel.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/SelectNoInvalidValue.png b/Documentation/Images/ManualScreenshots/List/SelectNoInvalidValue.png
new file mode 100644
index 000000000..bf4ddd5fb
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/SelectNoInvalidValue.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/TSconfigPageInput.png b/Documentation/Images/ManualScreenshots/List/TSconfigPageInput.png
new file mode 100644
index 000000000..cf7c82226
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/TSconfigPageInput.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/TcaTypeGroupSuggest.png b/Documentation/Images/ManualScreenshots/List/TcaTypeGroupSuggest.png
new file mode 100644
index 000000000..6f2f2f9de
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/TcaTypeGroupSuggest.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/listModuleWithExportButtons.png b/Documentation/Images/ManualScreenshots/List/listModuleWithExportButtons.png
new file mode 100644
index 000000000..5957d2abd
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/listModuleWithExportButtons.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/listModuleWithoutExportButtons.png b/Documentation/Images/ManualScreenshots/List/listModuleWithoutExportButtons.png
new file mode 100644
index 000000000..df65fab59
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/listModuleWithoutExportButtons.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/optionsPageTreeBackgroundColor.png b/Documentation/Images/ManualScreenshots/List/optionsPageTreeBackgroundColor.png
new file mode 100644
index 000000000..bfeb612a7
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/optionsPageTreeBackgroundColor.png differ
diff --git a/Documentation/Images/ManualScreenshots/List/optionsPageTreeLabel.png b/Documentation/Images/ManualScreenshots/List/optionsPageTreeLabel.png
new file mode 100644
index 000000000..9dd79a266
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/List/optionsPageTreeLabel.png differ
diff --git a/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFound.png b/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFound.png
new file mode 100644
index 000000000..97959f322
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFound.png differ
diff --git a/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png b/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png
new file mode 100644
index 000000000..3001d23ab
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/NoTypoScriptTemplateFoundDebuggingOff.png differ
diff --git a/Documentation/Images/ManualScreenshots/Page/FunctionMenuPageModule.png b/Documentation/Images/ManualScreenshots/Page/FunctionMenuPageModule.png
new file mode 100644
index 000000000..ffa73fc66
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Page/FunctionMenuPageModule.png differ
diff --git a/Documentation/Images/ManualScreenshots/Template/FunctionMenuTemplateModule.png b/Documentation/Images/ManualScreenshots/Template/FunctionMenuTemplateModule.png
new file mode 100644
index 000000000..3592c78f1
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/Template/FunctionMenuTemplateModule.png differ
diff --git a/Documentation/Images/ManualScreenshots/ThePageIsNotConfigured.png b/Documentation/Images/ManualScreenshots/ThePageIsNotConfigured.png
new file mode 100644
index 000000000..17981ce9a
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/ThePageIsNotConfigured.png differ
diff --git a/Documentation/Images/ManualScreenshots/UserSettings/UserSettings.png b/Documentation/Images/ManualScreenshots/UserSettings/UserSettings.png
new file mode 100644
index 000000000..98ac264b4
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/UserSettings/UserSettings.png differ
diff --git a/Documentation/Images/ManualScreenshots/View/WebViewTSConfigPreview.png b/Documentation/Images/ManualScreenshots/View/WebViewTSConfigPreview.png
new file mode 100644
index 000000000..00bf6c53c
Binary files /dev/null and b/Documentation/Images/ManualScreenshots/View/WebViewTSConfigPreview.png differ
diff --git a/Documentation/Index.rst b/Documentation/Index.rst
index 5f6b9a5af..f398e78ca 100644
--- a/Documentation/Index.rst
+++ b/Documentation/Index.rst
@@ -3,7 +3,7 @@
 ..  _start:
 
 ====================
-TypoScript Reference
+TypoScript Explained
 ====================
 
 :Version:
@@ -25,37 +25,53 @@ TypoScript Reference
 ----
 
 This document is a complete reference of all object types and properties of
-TypoScript as used in frontend TypoScript configuration.
+TypoScript as used in frontend TypoScript and backend TypoScript, also called TSconfig.
 
-Furthermore, you can find a quick guide to TypoScript configuration at
-:ref:`t3ts45:start`, insights into TYPO3 backend configuration with
-TypoScript in the :ref:`TSconfig <t3tsconfig:start>` documentation and
-explanations of TypoScript syntax in the ":ref:`TypoScript Syntax <t3coreapi:typoscript-syntax-start>`"
-chapter of TYPO3 Explained.
+You can find a quick guide to TypoScript configuration at
+:ref:`guide` and
+explanations of TypoScript syntax in the ":ref:`TypoScript Syntax <typoscript-syntax>`"
+chapter.
 
 ----
 
 **Table of Contents:**
 
-.. toctree::
-   :maxdepth: 2
-   :titlesonly:
-
-   Introduction/Index
-   UsingSetting/Index
-   DataTypes/Index
-   TopLevelObjects/Index
-   ContentObjects/Index
-   DataProcessing/Index
-   Functions/Index
-   Conditions/Index
-   AppendixA/Index
-
-.. Meta Menu
-
-.. toctree::
-   :hidden:
-
-   Glossary
-   About
-   Sitemap
+..  toctree::
+    :caption: About TypoScript
+    :maxdepth: 1
+    :titlesonly:
+
+    Introduction/Index
+    Guide/Index
+    UsingSetting/Index
+    UsingSettingTSconfig/Index
+    Syntax/Index
+
+..  toctree::
+    :caption: Frontend TypoScript
+    :maxdepth: 1
+    :titlesonly:
+
+    TopLevelObjects/Page/Index
+    ContentObjects/Index
+    DataProcessing/Index
+    TopLevelObjects/Config
+    TopLevelObjects/Index
+    Functions/Index
+    Conditions/Index
+
+..  toctree::
+    :caption: Backend TypoScript
+    :maxdepth: 1
+    :titlesonly:
+
+    PageTsconfig/Index
+    UserTsconfig/Index
+
+..  toctree::
+    :caption: Appendix
+    :hidden:
+
+    AppendixA/Index
+    Glossary
+    Sitemap
diff --git a/Documentation/Introduction/Index.rst b/Documentation/Introduction/Index.rst
index 6ff837678..f79b26226 100644
--- a/Documentation/Introduction/Index.rst
+++ b/Documentation/Introduction/Index.rst
@@ -1,103 +1,64 @@
+:navigation-title: Introduction
 .. include:: /Includes.rst.txt
+..  _typoscript-syntax-typoscript-templates:
+..  _typoscript-syntax-typoscript-templates-usage:
+..  _introduction:
 
-.. _introduction:
-.. _typoscript-syntax-typoscript-templates:
+============================
+Introduction into TypoScript
+============================
 
-============
-Introduction
-============
+TypoScript is a configuration language used to configure both the frontend
+output and the backend of a a TYPO3 web site.
 
-What is to be rendered on a page in the frontend,
-the menu structure, how content objects are displayed, etc. can be
-defined with TypoScript - often it is used in
-combination with the Fluid templating engine.
+TypoScript is not a programming language but a means of configuring the
+website.
 
-This document is a **reference**, used to lookup TypoScript templating
-:ref:`basic data types <data-types>`, :ref:`object types <cobject>`,
-:ref:`functions <functions>` and :ref:`conditions <conditions>`. This
-reference is not intended to give you a full introduction into the topic
-TypoScript.
+..  contents::
 
+..  _introduction-frontend-typoscript:
 
-What is TypoScript?
+Frontend TypoScript
 ===================
 
-TypoScript can have 2 meanings:
+Frontend TypoScript is mainly used to configure which data should be send to the
+Fluid templates.
 
-* **TypoScript syntax** is used in TypoScript templates and in
-  TSconfig
-* **TypoScript templates** are used to configure
-  the TYPO3 frontend rendering.
+It can also be used to define settings send to Extbase plugins, metadata for
+a whole page etc.
 
-Additionally, in TypoScript templates, you must differentiate between
+In the beginning of TYPO3, TypoScript was used as templating language. In modern
+project it is not common to do that anymore.
 
-* TypoScript **constants** (using the TypoScript constant syntax)
-* and Typoscript **setup**
+For an introduction see
+`Getting started: A quick introduction into TypoScript <https://docs.typo3.org/permalink/t3tsref:guide>`_.
 
-Though TypoScript does include "functions" and "objects" and "conditions"
-it is not a programming language. Think of it more as a configuration
-language. The results of the TypoScript setup are used to build a PHP
-array.
+..  _about-tsconfig:
 
-Basically think of TypoScript as a means to "configure" the **frontend**,
-while TSconfig is used to configure the **backend** (with a few exceptions
-to this principle)
+Backend TypoScript / TSconfig
+=============================
 
-Please read the following for an introduction:
+Backend TypoScript, also called TSconfig, can be used to configure the output
+of certain forms etc in the TYPO3 backend.
 
-* :ref:`TypoScript Syntax <t3coreapi:typoscript-syntax-start>`
-  chapter in "TYPO3 Explained" for an introduction to the TypoScript
-  syntax
-* :ref:`t3ts45:start` for an introduction to TypoScript Templating
-* The chapter :ref:`using-and-setting` describes how to use, set
-  and extend TypoScript.
+..  _about-page-tsconfig:
 
+Page TSconfig
+-------------
 
-.. _typoscript-syntax-typoscript-templates-usage:
+Page TSconfig can be made available globally, on a per site or per page level.
 
-Templating methods in TYPO3
-===========================
+For the possibilities see the
+`Page TSconfig Reference <https://docs.typo3.org/permalink/t3tsref:pagetoplevelobjects>`_.
 
+..  _about-user-tsconfig:
 
-TypoScript templates are used to drive frontend rendering.
+User TSconfig
+-------------
 
-A minimal amount of TypoScript will *always* be necessary to
-tell TYPO3 CMS which templating method to use.
-It could be any of the following.
-
-Best practice:
-
-- **Fluid templates:** Configure TYPO3 to use `Fluid <https://typo3.org/fluid>`__
-  for templating. This allows to use external HTML templates, but
-  with fluid-style variables with curly braces. A content object type
-  :ref:`cobj-fluidtemplate` is available, which uses Fluid
-  from inside TypoScript.
-
-  * See :ref:`t3sitepackage:start` for a complete walkthrough of creating a
-    sitepackage, which is the basis for a custom theme for your site.
-  * See :ref:`t3coreapi:adding-your-own-content-elements` for an
-    introduction on how to create your own content element types using
-    TypoScript :ref:`cobj-template`, Fluid and data processors.
-
-Other methods:
-
-
-- **External Templating Engines:** Any other templating system can be
-  used. It will be provided via an extension. In such a case TypoScript
-  may be used to delegate the rendering to that system.
-
-- **Custom PHP:** Configure TYPO3 to call your own PHP code which
-  generates content in any way you may prefer. This might include using
-  third party templating engines!
-
-- **TS content objects:** Build the page entirely using TypoScript
-  content objects. All these objects are highly configurable.
-
-Outdated methods:
-
-
-- **HTML templates:** Configure TYPO3 CMS to facilitate external HTML-
-  templates with markers and subparts using the :ref:`cobj-template`
-  content object type. This method is considered outdated and no
-  longer recommended.
+User TSconfig can be made available globally for certain user groups or certain
+users. It cannot be set for just one site or page. It can however override
+:ref:`about-page-tsconfig`.
 
+For the possibilities see the
+`User TSconfig reference <https://docs.typo3.org/permalink/t3tsref:usertoplevelobjects>`_.
diff --git a/Documentation/PageTsconfig/ColorPalettes.rst b/Documentation/PageTsconfig/ColorPalettes.rst
new file mode 100644
index 000000000..ad2572ec5
--- /dev/null
+++ b/Documentation/PageTsconfig/ColorPalettes.rst
@@ -0,0 +1,69 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    Page TSconfig; colorPalettes
+    colorPalettes
+..  _pagecolorpalettes:
+
+
+=============
+colorPalettes
+=============
+
+..  versionadded:: 13.0
+
+TYPO3 provides a :ref:`color picker component <t3tca:columns-color>` that
+supports color palettes, or swatches. The colors can be configured and assigned
+to palettes. This way, for example, colors defined in a corporate design can be
+selected by a simple click. Multiple color palettes can be configured.
+
+..  figure:: /Images/ManualScreenshots/ColorPalettes/ColorPalette.png
+    :alt: Example of a color palette
+    :class: with-shadow
+
+    Example of a color palette
+
+Basic syntax
+============
+
+First, define the colors by name and RGB value:
+
+..  code-block:: typoscript
+    :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+    colorPalettes {
+      colors {
+        typo3 {
+          value = #ff8700
+        }
+        blue {
+          value = #0080c9
+        }
+        darkgrey {
+          value = #515151
+        }
+        valid {
+          value = #5abc55
+        }
+        error {
+          value = #dd123d
+        }
+      }
+    }
+
+Then assign the colors to your palettes:
+
+..  code-block:: typoscript
+    :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+    colorPalettes {
+      palettes {
+        main = typo3
+        key_colors = typo3, blue, darkgrey
+        messages = valid, error
+      }
+    }
+
+Now you can assign a color palette to one field, to all fields of a table or
+as a global configuration, see
+:ref:`TCEFORM.colorPalette <pageTsConfigTceFormColorPalette>`.
diff --git a/Documentation/PageTsconfig/Index.rst b/Documentation/PageTsconfig/Index.rst
new file mode 100644
index 000000000..eb4650405
--- /dev/null
+++ b/Documentation/PageTsconfig/Index.rst
@@ -0,0 +1,34 @@
+..  include:: /Includes.rst.txt
+..  index:: ! Page TSconfig
+..  _pagetsconfig:
+..  _pagetoplevelobjects:
+
+=======================
+Page TSconfig Reference
+=======================
+
+The page TSconfig primarily concerns configuration of the modules in
+the TYPO3 backend, the most important section is :ref:`mod <pagemod>`.
+
+The TSconfig for a page is accumulated from the root and extends
+to cover the whole branch of sub pages as well (unless values are
+overridden further out).
+
+Note that the page TSconfig can be overridden on a user and group basis by
+user TSconfig again, for details, see section
+:ref:`Overriding page TSconfig in user TSconfig <userrelationshiptovaluessetinpagetsconfig>`.
+
+
+..  toctree::
+    :maxdepth: 5
+    :titlesonly:
+
+    ColorPalettes
+    Mod
+    Options
+    Rte
+    TcaDefaults
+    TceForm
+    TceMain
+    Templates
+    Tx
diff --git a/Documentation/PageTsconfig/Mod.rst b/Documentation/PageTsconfig/Mod.rst
new file mode 100644
index 000000000..1e8e6e517
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod.rst
@@ -0,0 +1,29 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    Page TSconfig; mod
+    mod
+..  _pagemod:
+
+
+===
+mod
+===
+
+Configuration for backend modules. This is the part of page TSconfig
+with the most options, most sections affect the main TYPO3 editing modules
+like :guilabel:`Web > Page` and :guilabel:`Web > List`.
+
+Properties
+==========
+
+..  toctree::
+    :maxdepth: 1
+    :glob:
+
+    Mod/Shared
+    Mod/WebInfo
+    Mod/WebLayout
+    Mod/WebList
+    Mod/WebView
+    Mod/Wizards
diff --git a/Documentation/PageTsconfig/Mod/Shared.rst b/Documentation/PageTsconfig/Mod/Shared.rst
new file mode 100644
index 000000000..5a3273a8e
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/Shared.rst
@@ -0,0 +1,154 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    mod; SHARED
+    Modules; All
+..  _pagesharedotionsformodules:
+..  _mod-shared:
+
+======
+SHARED
+======
+
+..  youtube:: xJtsLlEtY5U
+
+..  contents::
+    :local:
+
+..  index::
+    colPos_list
+    Columns; Disable
+
+colPos_list
+===========
+
+..  confval:: colPos_list
+    :name: mod-share-colPos-list
+    :type: comma separated list of integers
+    :default: ''
+    :Path: mod.SHARED.colPos_list
+
+    This setting controls which areas or columns of the backend layouts are
+    editable. Columns configured in the :ref:`Backend Layout <backend-layouts>`,
+    which are not listed here, will be displayed with placeholder area.
+
+    The default backend layout only has one column, which has the id 0.
+
+..  _example_for_backend_layout:
+
+Example: Make a column in a backend layout not editable
+-------------------------------------------------------
+
+Assuming the current page uses the following backend layout:
+
+..  literalinclude:: /PageTsconfig/Mod/WebLayout/_BackendLayout.tsconfig
+    :caption: config/sites/my-site/page.tsconfig
+
+And we want to make the area "Jumbotron" (colPos = 1) not editable.
+
+As long as :confval:`mod-share-colPos-list` is empty all areas are allowed.
+We therefore have to list all colPos, which should still be allowed. In this
+that would be the columns left (colPos = 0) and right (colPos = 2).
+
+..  literalinclude:: /PageTsconfig/Mod/_snippets/_mod.SHARED.colPos_list.tsconfig
+    :caption: config/sites/my-site/page.tsconfig
+
+..  index::
+    defaultLanguageFlag
+    Localization; Default language flag
+..  _pageTsConfigSharedDefaultLanguageLabel:
+
+defaultLanguageFlag
+===================
+
+..  warning::
+
+    Note that this option has largely been superseded by site configuration since **TYPO3 v10** and will only
+    work in the Backend for a "NullSite". For instance, a global sysfolder in the page tree without an
+    attached site configuration. Once a page tree has a site configuration, the default language icon is
+    set from the site configuration's language settings and this option will have no effect at all.
+
+..  confval:: defaultLanguageFlag
+    :name: mod-share-defaultLanguageFlag
+    :type: string
+
+    Country flag shown for the "Default" language in the backend, used in Web > List and Web > Page module.
+    Values as listed in the "Select flag icon" of a language record in the backend are allowed, including
+    the value "multiple".
+
+    ..  figure:: /Images/ManualScreenshots/List/SelectFlagIcon.png
+        :alt: The flag selector of a language record in the backend
+
+        The flag selector of a language record in the backend
+
+Example: Show a German flag on a NullSite
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This will show the German flag, and the text "deutsch" on hover.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.SHARED {
+        defaultLanguageFlag = de
+        defaultLanguageLabel = deutsch
+    }
+
+..  index::
+    defaultLanguageLabel
+    Localization; Default language label
+
+defaultLanguageLabel
+====================
+
+..  warning::
+
+    Note that this option has largely been superseded by site configuration since **TYPO3 v10** and will only
+    work in the backend for a "NullSite". For instance a global sysfolder in the page tree without an
+    attached site configuration. Once a page tree has a site configuration, the default language label is
+    set from the site configuration's language settings and this option will have no effect at all.
+
+..  confval:: defaultLanguageLabel
+    :name: mod-share-defaultLanguageLabel
+    :type: string
+
+    Alternate label for "Default" when language labels are shown in the interface.
+
+    Used in Web > List and Web > Page module.
+
+..  index::
+    disableLanguages
+    Localization; disable languages
+
+disableLanguages
+================
+
+..  warning::
+
+    Note that this option has largely been superseded by site configuration since **TYPO3 v10** and will only
+    work in the Backend for a "NullSite". For instance, a global sysfolder in the page tree without an
+    attached site configuration. Once a page tree has a site configuration, the language settings
+    from the site configuration are applied and this option will have no effect at all.
+
+..  confval:: disableLanguages
+    :name: mod-share-disableLanguages
+    :type: string
+
+    Comma-separated list of language UIDs which will be disabled in the given page tree.
+
+..  index::
+    disableSysNoteButton
+    Buttons; disable sys_note
+
+disableSysNoteButton
+====================
+
+..  confval:: disableSysNoteButton
+    :name: mod-share-disableSysNoteButton
+    :type: boolean
+
+    Disables the `sys_note` creation button in the modules' top button bar
+    in the :guilabel:`Page`, :guilabel:`List` and :guilabel:`Info`
+    modules.
+
+
diff --git a/Documentation/PageTsconfig/Mod/WebInfo.rst b/Documentation/PageTsconfig/Mod/WebInfo.rst
new file mode 100644
index 000000000..06198038e
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebInfo.rst
@@ -0,0 +1,67 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    mod; web_info
+    Modules; Info
+
+========
+web_info
+========
+
+Configuration options of the "Web > Info" module.
+
+..  contents::
+    :local:
+
+..  index::
+    fieldDefinitions
+    Pagetree overview; Available fields
+..  _fieldDefinitions-webinfo:
+
+fieldDefinitions
+================
+
+..  confval:: fieldDefinitions
+    :name: mod-web-info-fieldDefinitions
+    :type: array
+
+    The available fields in the "Pagetree overview" module under the Info module, by default ship with the entries
+    "Basic settings", "Record overview", and "Cache and age".
+
+    ..  figure:: /Images/ManualScreenshots/Info/PageTsModWebInfoFieldDefinitions.png
+        :alt: Default entries of Pagetree Overview
+
+        Default entries of Pagetree Overview
+
+    By using page TsConfig it is possible to change the available fields and add additional entries to the select box.
+
+    Next to using a list of fields from the `pages` table you can add counters for records in a given table by prefixing a
+    table name with `table_` and adding it to the list of fields.
+
+    The string `###ALL_TABLES###` is replaced with a list of all table names an editor has access to.
+
+..  _fieldDefinitions-webinfo-example:
+
+Example: Override the field definitions in the info module
+----------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_info.fieldDefinitions {
+        0 {
+            # Basic settings
+            label = LLL:EXT:info/Resources/Private/Language/locallang_webinfo.xlf:pages_0
+            fields = title,uid,slug,alias,starttime,endtime,fe_group,target,url,shortcut,shortcut_mode
+        }
+        1 {
+            # Record overview
+            label = LLL:EXT:info/Resources/Private/Language/locallang_webinfo.xlf:pages_1
+            fields = title,uid,###ALL_TABLES###
+        }
+        2 {
+            # Cache and age
+            label = LLL:EXT:info/Resources/Private/Language/locallang_webinfo.xlf:pages_2
+            fields = title,uid,table_tt_content,table_fe_users
+        }
+    }
diff --git a/Documentation/PageTsconfig/Mod/WebLayout.rst b/Documentation/PageTsconfig/Mod/WebLayout.rst
new file mode 100644
index 000000000..0bec091a6
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout.rst
@@ -0,0 +1,332 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    mod; web_layout
+    Modules; Page
+..  _pagewebpage:
+
+==========
+web_layout
+==========
+
+Configuration options of the "Web > Page" module.
+
+..  contents::
+    :local:
+
+..  index::
+    Localization; Inconsistent language mode
+    Localization; Independently translated content
+    allowInconsistentLanguageHandling
+
+..  _mod-web-layout-allowInconsistentLanguageHandling:
+
+allowInconsistentLanguageHandling
+=================================
+
+..  confval:: allowInconsistentLanguageHandling
+    :name: mod-web-layout-allowInconsistentLanguageHandling
+    :type: boolean
+
+    By default, TYPO3 will not allow you to mix translated content and independent content in the page module.
+    Content elements violating this behavior will be marked in the page module and there is no UI control (yet)
+    allowing you to create independent content elements in a given language.
+
+    If you want to go back to the old, inconsistent behavior, you can toggle it back on using this switch.
+
+..  _mod-web-layout-allowInconsistentLanguageHandling-example:
+
+Example: Allow inconsistent language modes
+------------------------------------------
+
+Allows to set TYPO3s page module back to inconsistent language mode
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_layout.allowInconsistentLanguageHandling = 1
+
+
+..  index:: BackendLayouts
+
+..  _mod-web-layout-backendLayouts:
+
+BackendLayouts
+==============
+
+..  confval:: BackendLayouts
+    :type: array
+    :no-index:
+
+    Backend Layouts were initially introduced in order to customize the view of
+    the :guilabel:`Page` module in TYPO3 Backend for a page, but has then since grown also in
+    Frontend rendering to select for example Fluid template files via TypoScript for a page,
+    commonly used via :confval:`data:pagelayout <t3tsref:data-pagelayout>`.
+
+    See also the dedicated chapter :ref:`backend-layouts`.
+
+..  _mod-web-layout-backendLayouts-example:
+
+Example: Define a backend layout
+--------------------------------
+
+..  literalinclude:: WebLayout/_backendLayouts-example.tsconfig
+    :language: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+..  index::
+    defaultLanguageLabel
+    Localization; Default language label
+
+..  _mod-web-layout-defaultLanguageLabel:
+
+defaultLanguageLabel
+====================
+
+..  warning::
+
+    Note that this option has largely been superseded by site configuration since **TYPO3 v10** and will only
+    work in the Backend for a "NullSite". For instance, a global sysfolder in the page tree without an
+    attached site configuration. Once a page tree has a site configuration, the default language label is
+    set from the site configuration's language settings and this option will have no effect at all.
+
+..  confval:: defaultLanguageLabel
+    :name: mod-web-layout-defaultLanguageLabel
+    :type: string
+
+    Alternate label for "Default" when language labels are shown in the interface.
+
+    Overrides the same property from :ref:`mod.SHARED <pageTsConfigSharedDefaultLanguageLabel>` if set.
+
+..  index::
+    defLangBinding
+    Localization; Show default content element
+
+..  _mod-web-layout-defLangBinding:
+
+defLangBinding
+==============
+
+..  confval:: defLangBinding
+    :name: mod-web-layout-defLangBinding
+    :type: boolean
+    :Default: 0
+
+    If set, translations of content elements are bound to the default record in the display. This means that
+    within each column with content elements any translation found for exactly the shown default content
+    element will be shown in the language column next to.
+
+    This display mode should be used depending on how the frontend is configured to display localization.
+    The frontend must display localized pages by selecting the default content elements and for each
+    one overlay with a possible translation if found.
+
+..  index::
+    hideRestrictedCols
+    Page columns; Hide restricted
+
+..  _mod-web-layout-hideRestrictedCols:
+
+hideRestrictedCols
+==================
+
+..  confval:: hideRestrictedCols
+    :name: mod-web-layout-hideRestrictedCols
+    :type: boolean
+    :Default: false
+
+    If activated, only columns will be shown in the backend that the editor is
+    allowed to access. All columns with access restriction are hidden in that case.
+
+    By default columns with restricted access are rendered with a message
+    telling *that* the user doesn't have access. This may be useless and
+    distracting or look repelling. Instead, all columns an editor doesn't have
+    access to can be hidden:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        mod.web_layout.hideRestrictedCols = 1
+
+    ..  attention::
+
+        This setting will break your layout if you are using backend layouts.
+
+
+..  index::
+    localization.enableCopy
+    Localization; Free mode
+    Localization; Copy content elements
+
+..  _mod-web-layout-localization-enableCopy:
+
+localization.enableCopy
+=======================
+
+..  confval:: localization.enableCopy
+    :name: mod-web-layout-localization-enableCopy
+    :type: boolean
+    :Default: 1
+
+    Enables the creation of copies of content elements into languages in the translation wizard ("free mode").
+
+..  _mod-web-layout-localization-enableCopy-example:
+
+Example: Disable free mode button for localization
+--------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_layout {
+        localization.enableCopy = 0
+    }
+
+
+..  index::
+    localization.enableTranslate
+    Localization; Connected mode
+    Localization; Translate content elements
+
+..  _mod-web-layout-localization-enableTranslate:
+
+localization.enableTranslate
+============================
+
+..  confval:: localization.enableTranslate
+    :name: mod-web-layout-localization-enableTranslate
+    :type: boolean
+    :Default: 1
+
+    Enables simple translations of content elements in the translation wizard ("connected mode").
+
+..  _mod-web-layout-localization-enableTranslate-example:
+
+Example: Disable "connected mode" button for translation
+--------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_layout {
+        localization.enableTranslate = 0
+    }
+
+..  index::
+    web_layout.menu.functions
+    Module menu; Pages
+..  _pageblindingfunctionmenuoptions-weblayout:
+
+menu.functions
+==============
+
+..  confval:: menu.functions
+    :name: mod-web-layout-menu-functions
+    :type: array
+
+    Disable elements of the "Function selector" in the document header of the module.
+
+    ..  figure:: /Images/ManualScreenshots/Page/FunctionMenuPageModule.png
+        :alt: The function menu of the Page module
+
+    The function keys are numerical:
+
+    Columns
+        1
+    Languages
+        2
+
+    ..  warning::
+
+        Blinding Function Menu items is not hardcore access control! All it
+        does is hide the possibility of accessing that module functionality
+        from the interface. It might be possible for users to hack their way
+        around it and access the functionality anyways. You should use the
+        option of blinding elements mostly to remove otherwise distracting options.
+
+..  _pageblindingfunctionmenuoptions-weblayout-example:
+
+Example: Disable "Languages" from the function menu
+---------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Disables "Languages" from function menu
+    mod.web_layout.menu.functions {
+        2 = 0
+    }
+
+
+..  index::
+    noCreateRecordsLink
+    Buttons; Create new record
+
+noCreateRecordsLink
+===================
+
+..  confval:: noCreateRecordsLink
+    :name: mod-web-layout-noCreateRecordsLink
+    :type: boolean
+    :Default: 0
+
+    If set, the link in the bottom of the page, "Create new record", is hidden.
+
+..  index::
+    preview
+    Content elements; Preview definition
+..  _pageweblayoutpreview:
+
+tt_content.preview
+==================
+
+..  confval:: tt_content.preview
+    :name: mod-web-layout-tt-content-preview
+    :type: boolean
+
+    It is possible to render previews of your own content elements in the page module.
+    By referencing a Fluid template you can create a visual representation of your content element,
+    making it easier for an editor to understand what is going on on the page.
+
+    The syntax is as follows:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        mod.web_layout.tt_content.preview.[CTYPE].[list_type value] = EXT:site_mysite/Resources/Private/Templates/Preview/ExamplePlugin.html
+
+    This way you can even switch between previews for your plugins by supplying `list` as CType.
+
+    ..  note::
+
+        This only works if the registered preview renderer for the content type
+        uses Fluid rendering and the rendering is not overridden by using
+        an event listener for the event :php:`\TYPO3\CMS\Backend\View\Event\PageContentPreviewRenderingEvent`.
+
+        Have a look at :php:`\TYPO3\CMS\Backend\Preview\StandardContentPreviewRenderer`
+        and the various methods for customizing the preview rendering:
+
+        #.  :ref:`Register a preview renderer <t3coreapi:ConfigureCE-Preview>`
+        #.  Register an event listener for :ref:`PageContentPreviewRenderingEvent <t3coreapi:PageContentPreviewRenderingEvent>`
+
+        For checking for event listeners, see the list
+        :guilabel:`System > Configuration > Event Listeners (PSR-14)` (available with installed EXT:lowlevel).
+
+
+..  _pageweblayoutpreview-example:
+
+Example: Define previews for custom content elements
+----------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_layout.tt_content {
+        preview.custom_ce = EXT:site_mysite/Resources/Private/Templates/Preview/CustomCe.html
+        preview.table = EXT:site_mysite/Resources/Private/Templates/Preview/Table.html
+        preview.list.tx_news = EXT:site_mysite/Resources/Private/Templates/Preview/TxNews.html
+    }
+
+..  toctree::
+    :glob:
+
+    WebLayout/*
diff --git a/Documentation/PageTsconfig/Mod/WebLayout/BackendLayout.rst b/Documentation/PageTsconfig/Mod/WebLayout/BackendLayout.rst
new file mode 100644
index 000000000..e2785f759
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout/BackendLayout.rst
@@ -0,0 +1,148 @@
+..  include:: /Includes.rst.txt
+
+..  _backend-layouts:
+
+===============
+Backend layouts
+===============
+
+Backend layouts were initially introduced to display editable versions of the
+webpages in the backend (in the :guilabel:`Page` module). However, they have now
+increased their functionality and can be used for frontend rendering as well. Using
+TypoScript, the Fluid template for a webpage is chosen depending on which backend
+layout a page has. (The TypoScript :confval:`data:pagelayout <t3tsref:data-pagelayout>`
+function retrieves the backend layout).
+
+..  figure:: /Images/ManualScreenshots/BackendLayouts/PageModule.png
+
+    A page module with a backend layout that has 3 content areas.
+
+Backend layouts contain content areas that are organized in rows and columns. Content
+areas can span multiple rows and columns, but they cannot be nested. For nested layouts in the
+backend, use an extension like :composer:`b13/container`.
+
+The page TSconfig for the backend layout above can be found in the site package
+tutorial: :ref:`Create backend page layouts <t3sitepackage:backend-page-layouts>`.
+
+For further examples, see `backend layouts in the bootstrap
+package (GitHub) <https://github.com/benjaminkott/bootstrap_package/tree/master/Configuration/TsConfig/Page/Mod/WebLayout/BackendLayouts>`__.
+
+..  confval-menu::
+
+..  confval:: BackendLayouts.[backendLayout]
+    :name: mod-web-layout-BackendLayouts
+    :type: array:guilabel:`Page` module
+    :Path: mod.web_layout.BackendLayouts
+
+    ..  confval:: title
+        :name: mod-web-layout-BackendLayouts-backendLayout-title
+        :type: string or language identifier
+
+        The title of a backend layout. It will be displayed in the page
+        properties in the backend.
+
+        ..  figure:: /Images/ManualScreenshots/BackendLayouts/PageProperties.png
+            :caption: Choose the backend layout in the page properties
+
+    ..  confval:: icon
+        :name: mod-web-layout-BackendLayouts-backendLayout-icon
+        :type: string, extension path to an image file
+
+        The icon in the page properties.
+
+        ..  code-block:: tsconfig
+            :caption: EXT:bootstrap_package/Configuration/TsConfig/Page/Mod/WebLayout/BackendLayouts/subnavigation_right_2_columns.tsconfig
+
+            mod.web_layout.BackendLayouts.subnavigation_right_2_columns {
+                icon = EXT:bootstrap_package/Resources/Public/Icons/BackendLayouts/subnavigation_right_2_columns.svg
+            }
+
+    ..  confval:: config.backend_layout
+
+        ..  confval:: colCount
+            :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout.colCount
+            :type: integer
+
+            The total number of columns in the backend layout.
+
+        ..  confval:: rowCount
+            :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout.rowCount
+            :type: integer
+
+            The total number of rows in the backend layout.
+
+        ..  confval:: rows.[row].columns.[col]
+
+            ..  confval:: name
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-name
+                :type: string or language identifier
+
+                The name of the input area where content elements can be added. Will be
+                displayed in the :guilabel:`Page` module.
+
+            ..  confval:: colPos
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-colPos
+                :type: integer, 0 - maxInt
+
+                If content elements have been  added to this area, the value of `colPos`
+
+            ..  confval:: identifier
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-identifier
+                :type: string
+
+                An identifier that can be used by the page content
+                DataProcessor to identify the content elements in this
+                area.
+
+                It is a more meaningful representation than just :confval:`colPos <mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-colPos>`,
+                such as "main", "sidebar" and "footerArea".
+
+            ..  confval:: slideMode
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-slideMode
+                :type: string, "" (empty string), "slide", "collect", "collectReverse"
+
+                An identifier that can be used by the page content
+                DataProcessor to identify content elements in this
+                area.
+
+                `slide`
+                    If no content is found, check the parent pages for more content
+                `collect`
+                    Use all content from this page and the parent pages as one collection
+                `collectReverse`
+                    The same as "collect", but in the opposite order
+
+            ..  confval:: colspan
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-colspan
+                :type: integer, 1 - :confval:`mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout.colCount`
+
+                Can be used if the content element area should span multiple
+                columns as in the "Jumbotron" example above.
+
+            ..  confval:: rowspan
+                :name: mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout-rows-row-columns-col-rowspan
+                :type: integer, 1 - :confval:`mod-web-layout-BackendLayouts-backendLayout-title-config-backend_layout.rowCount`
+
+                Can be used if the content element area spans multiple
+                rows.
+
+Example: Use a backend layout in the page content data processor
+================================================================
+
+Define the backend layout via page TSconfig, like in the site below:
+
+..  literalinclude:: _BackendLayout.tsconfig
+    :caption: config/sites/my-site/page.tsconfig
+
+Configure the output with TypoScript, using the :ref:`PAGEVIEW <t3tsref:cobj-pageview>`
+content object and the `page-content` DataProcessor.
+
+..  todo: Link Dataprocessor
+
+..  literalinclude:: _BackendLayout.typoscript
+    :caption: config/sites/my-site/setup.typoscript
+
+Use the column identifiers in a Fluid template:
+
+..  literalinclude:: _Default.html
+    :caption: EXT:my_sitepackage/Resources/Private/Templates/Pages/Default.html
diff --git a/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.tsconfig b/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.tsconfig
new file mode 100644
index 000000000..698538b84
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.tsconfig
@@ -0,0 +1,41 @@
+mod.web_layout.BackendLayouts {
+    default {
+        title = Default
+        config {
+            backend_layout {
+                colCount = 2
+                rowCount = 2
+                rows {
+                    1 {
+                        columns {
+                            1 {
+                                name = Jumbotron
+                                colPos = 1
+                                identifier = jumbotron
+                                slideMode = slide
+                                colspan = 2
+                            }
+                        }
+                    }
+
+                    2 {
+                        columns {
+                            1 {
+                                name = Left
+                                colPos = 0
+                                identifier = left
+                            }
+
+                            2 {
+                                name = Right
+                                colPos = 2
+                                identifier = right
+                                slideMode = collectReverse
+                            }
+                        }
+                    }
+                }
+            }
+        }
+    }
+}
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.typoscript b/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.typoscript
new file mode 100644
index 000000000..3c00eb533
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout/_BackendLayout.typoscript
@@ -0,0 +1,9 @@
+page = PAGE
+page {
+    10 = PAGEVIEW
+    10 {
+        paths.10 = EXT:my_sitepackage/Resources/Private/Templates/
+        dataProcessing.10 = page-content
+        dataProcessing.10.as = myContent
+    }
+}
diff --git a/Documentation/PageTsconfig/Mod/WebLayout/_Default.html b/Documentation/PageTsconfig/Mod/WebLayout/_Default.html
new file mode 100644
index 000000000..e01923a7b
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout/_Default.html
@@ -0,0 +1,13 @@
+<f:render partial="Jumbotron" arguments="{jumbotronContent: myContent.jumbotron}"/>
+<main>
+	<f:for each="{myContent.left.records}" as="contentElement">
+	   <f:cObject
+			typoscriptObjectPath="{contentElement.mainType}"
+			data="{contentElement.rawRecord}"
+			table="{contentElement.mainType}"
+		 />
+	</f:for>
+</main>
+<aside>
+    <f:render partial="Aside" arguments="{content: myContent.right}"/>
+</aside>
diff --git a/Documentation/PageTsconfig/Mod/WebLayout/_backendLayouts-example.tsconfig b/Documentation/PageTsconfig/Mod/WebLayout/_backendLayouts-example.tsconfig
new file mode 100644
index 000000000..547f5f8cf
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebLayout/_backendLayouts-example.tsconfig
@@ -0,0 +1,33 @@
+mod.web_layout.BackendLayouts {
+    exampleKey {
+        title = Example
+        icon = EXT:example_extension/Resources/Public/Images/BackendLayouts/default.gif
+        config {
+            backend_layout {
+                colCount = 1
+                rowCount = 2
+                rows {
+                    1 {
+                        columns {
+                            1 {
+                                name = LLL:EXT:frontend/Resources/Private/Language/locallang_ttc.xlf:colPos.I.3
+                                colPos = 3
+                                colspan = 1
+                            }
+                        }
+                    }
+                    2 {
+                        columns {
+                            1 {
+                                name = Main
+                                colPos = 0
+                                colspan = 1
+                                identifier = main
+                            }
+                        }
+                    }
+                }
+            }
+        }
+    }
+}
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Mod/WebList.rst b/Documentation/PageTsconfig/Mod/WebList.rst
new file mode 100644
index 000000000..670722fbc
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebList.rst
@@ -0,0 +1,758 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    mod; web_list
+    Modules; List
+..  _pageweblist:
+
+========
+web_list
+========
+
+Configuration options of the "Web > List" module.
+
+..  contents::
+    :local:
+
+..  index::
+    allowedNewTables
+    Buttons; Create new
+..  _pageTsConfigWebListAllowedNewTables:
+
+allowedNewTables
+================
+
+..  confval:: allowedNewTables
+    :name: mod-web-list-allowedNewTables
+    :type: list of table names
+
+    If this list is set, then only tables listed here will have a link to "create new" in the page and sub pages.
+    This also affects the "Create new record" content element wizard.
+
+    This is the opposite of :ref:`deniedNewTables property <pageTsConfigWebListDeniedNewTables>`.
+
+    ..  note::
+
+        Technically records can be created (e.g. by copying/moving), so this is not a security feature.
+        The point is to reduce the number of options for new records visually.
+
+..  _pageTsConfigWebListAllowedNewTable-example:
+
+Example: Only allow records of type pages or sys_category in the new record wizard
+----------------------------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        # Only pages and sys_category table elements will be linked to in the new record wizard
+        allowedNewTables = pages, sys_category
+    }
+
+..  figure:: /Images/ManualScreenshots/List/PageTsModWebListAllowedNewTables.png
+    :alt: The New record screen after modifying the allowed elements
+
+    The New record screen after modifying the allowed elements
+
+
+..  index:: clickTitleMode
+..  _pageTsConfigWebList-clickTitleMode:
+
+clickTitleMode
+==============
+
+..  confval:: clickTitleMode
+    :name: mod-web-list-clickTitleMode
+    :type: string
+    :Default: edit
+
+    Keyword which defines what happens when a user clicks a record title in the list.
+
+    The following values are possible:
+
+    edit
+        Edits record
+
+    info
+        Shows information
+
+    show
+        Shows page in the frontend
+
+..  index::
+    csvDelimiter
+    CSV Exports; Delimiter
+..  _pageTsConfigWebList-csvDelimiter:
+
+csvDelimiter
+============
+
+..  confval:: csvDelimiter
+    :name: mod-web-list-csvDelimiter
+    :type: string
+    :Default: `,`
+
+    Defines the default delimiter for CSV downloads (Microsoft Excel expects
+    `;` to be set). The value set will be displayed as default delimiter in the
+    download dialog in the list module.
+
+Example: Use semicolon as delimiter CSV downloads
+-------------------------------------------------
+
+..  include:: /CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt
+
+..  include:: /Images/AutomaticScreenshots/WebList/ExportDialog.rst.txt
+
+
+..  index::
+    csvQuote
+    CSV Downloads; Quoting character
+..  _pageTsConfigWebList-csvQuote:
+
+csvQuote
+========
+
+..  confval:: csvQuote
+    :name: mod-web-list-csvQuote
+    :type: string
+    :Default: `"`
+
+    Defines the default quoting character for CSV downloads. The value set will
+    be displayed as default quoting in the download dialog in the list module.
+
+..  _pageTsConfigWebList-csvQuote-example:
+
+Example: Use single quotes as quoting character for CSV downloads
+-----------------------------------------------------------------
+
+..  include:: /CodeSnippets/PageTSconfig/Mod/CsvExport.rst.txt
+
+..  include:: /Images/AutomaticScreenshots/WebList/ExportDialog.rst.txt
+
+..  index::
+    deniedNewTables
+    Buttons; Create new
+..  _pageTsConfigWebListDeniedNewTables:
+
+deniedNewTables
+===============
+
+..  confval:: deniedNewTables
+    :name: mod-web-list-deniedNewTables
+    :type: list of table names
+
+    If this list is set, then the tables listed here won't have a link to "create new record" in the page
+    and sub pages. This also affects the "Create new record" content element wizard.
+
+    This is the opposite of :ref:`allowedNewTables property <pageTsConfigWebListAllowedNewTables>`.
+
+    If `allowedNewTables` and `deniedNewTables` contain a common subset, `deniedNewTables` takes precedence.
+
+Hide "Create new record" links in tables sys_category and tt_content
+--------------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        deniedNewTables = sys_category, tt_content
+    }
+
+
+..  index:: disableSearchBox
+..  _pageTsConfigWebList-disableSearchBox:
+
+disableSearchBox
+======================
+
+..  confval:: disableSearchBox
+    :name: mod-web-list-disableSearchBox
+    :type: boolean
+
+    If set, the checkbox "Show search" in the list module is hidden.
+
+
+..  index:: disableSingleTableView
+..  _pageTsConfigWebList-disableSingleTableView:
+
+disableSingleTableView
+======================
+
+..  confval:: disableSingleTableView
+    :name: mod-web-list-disableSingleTableView
+    :type: boolean
+
+    If set, then the links on the table titles which shows a single table
+    listing will not be available - including sorting links on columns
+    titles, because these links jumps to the table-only view.
+
+
+..  index:: displayColumnSelector
+..  _pageTsConfigWebList-displayColumnSelector:
+
+displayColumnSelector
+=====================
+
+..  confval:: displayColumnSelector
+    :name: mod-web-list-displayColumnSelector
+    :type: boolean
+    :Default: `true`
+
+    The column selector is enabled by default and can be disabled with this
+    option. The column selector is displayed at the top of each record list in
+    the :guilabel:`List` module. It can be used to compare different fields of
+    the listed records.
+
+..  _pageTsConfigWebList-displayRecordDownload:
+
+displayRecordDownload
+=====================
+
+..  confval:: displayRecordDownload
+    :name: mod-web-list-displayRecordDownload
+    :type: boolean
+    :Default: `1`
+
+    The "Download" functionality is available in the :guilabel:`Web > List`
+    module via the "Download" button in the relevant
+    table header row. It is available in both the list and the single table
+    view and can be managed using this option.
+
+    As well as the general option, it is also possible to set this option on
+    a table basis using the
+    :typoscript:`mod.web_list.table.<tablename>.displayRecordDownload` option.
+    If this option is set, it takes precedence over the general option.
+
+    ..  code-block:: typoscript
+        :caption: packages/my_sitepackage/Configuration/Sets/MySet/page.tsconfig
+
+        # Page TSconfig
+        mod.web_list {
+            # Disable "Export" button in List module header
+            noExportRecordsLinks = 1
+
+            # Generally disable "Download" button
+            displayRecordDownload = 0
+
+            # Enable "Download" button for table "tt_content"
+            table.tt_content.displayRecordDownload = 1
+        }
+
+
+..  _pageTsConfigWebList-displayColumnSelector-example:
+
+Example: Hide the column selector
+---------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.displayColumnSelector = 0
+
+..  _pageTsConfigWebList-downloadPresets:
+
+downloadPresets
+===============
+
+..  confval:: downloadPresets.[table]
+    :name: mod-web-list-downloadPresets
+    :type: array of presets
+
+    ..  versionadded:: 13.2
+        A new function has been introduced that makes it possible to select the data columns
+        to be exported from a list of configurable presets.
+
+    This property adds presets of preselected fields to the download area in
+    the :guilabel:`Web > List` backend module.
+
+    Those presets can be configured via page TSconfig, and can also be
+    overridden via user TSconfig (for example, to expand certain presets
+    only to specific users).
+
+    Each entry of :typoscript:`mod.web_list.downloadPresets`
+    defines the table name on the first level, followed by
+    any number of presets.
+
+    Each preset contains a :typoscript:`label` (the displayed name of the preset,
+    which can be a locallang key), a comma-separated list of each column that
+    should be included in the export as :typoscript:`columns` and optionally
+    an :typoscript:`identifier`. In case :typoscript:`identifier` is not provided,
+    the identifier is generated as hash of the :typoscript:`label` and
+    :typoscript:`columns`.
+
+    Since any table can be configured for a preset, any extension
+    can deliver a defined set of presets through the
+    :file:`EXT:my_extension/Configuration/page.tsconfig` file and
+    their table name(s).
+
+    Additionally, the list of presets can be manipulated via the PSR-14 event
+    :ref:`\TYPO3\CMS\Backend\RecordList\Event\BeforeRecordDownloadPresetsAreDisplayedEvent <t3coreapi:BeforeRecordDownloadPresetsAreDisplayedEvent>`.
+
+..  _pageTsConfigWebList-downloadPresets-example:
+
+Example: Create download presets for table page
+-----------------------------------------------
+
+..  literalinclude:: _WebList/_downloadPresets.tsconfig
+    :caption: EXT:my_extension/Configuration/page.tsconfig
+
+This can be manipulated with user TSconfig by adding the :typoscript:`page.`
+prefix. User TSconfig is loaded after page TSconfig, so you can overwrite
+the existing default settings using the same TypoScript path.
+
+..  literalinclude:: _WebList/_downloadPresets.tsconfig
+    :caption: EXT:my_extension/Configuration/user.tsconfig
+
+..  index::
+    enableClipBoard
+    Buttons; Show clipboard
+    Clipboard; Enable
+
+..  _pageTsConfigWebList-enableClipBoard:
+
+enableClipBoard
+===============
+
+..  confval:: enableClipBoard
+    :name: mod-web-list-enableClipBoard
+    :type: list of keywords
+    :Default: `selectable`
+
+    Determines whether the checkbox "Show clipboard" in the list module is
+    shown or hidden. If it is hidden, you can predefine it to be always
+    activated or always deactivated.
+
+    The following values are possible:
+
+    activated
+        The option is activated and the checkbox is hidden.
+
+    deactivated
+        The option is deactivated and the checkbox is hidden.
+
+    selectable
+        The checkbox is shown so that the option can be selected by the user.
+
+..  index::
+    enableDisplayBigControlPanel
+    List module; Extended view
+..  _pageTsConfigWebList-enableDisplayBigControlPanel:
+
+enableDisplayBigControlPanel
+============================
+
+..  versionchanged:: 11.3
+    The checkbox :guilabel:`Extended view` was removed with TYPO3 v11.3.
+    Therefore the option :typoscript:`mod.web_list.enableDisplayBigControlPanel`
+    has no effect anymore.
+
+..  index::
+    hideTables
+    List module; Hide tables
+..  _pageTsConfigWebList-hideTables:
+
+hideTables
+==========
+
+..  confval:: hideTables
+    :name: mod-web-list-hideTables
+    :type: list of table names, or *
+
+    Hide these tables in record listings (comma-separated)
+
+    If `*` is used, all tables will be hidden
+
+
+..  index::
+    hideTranslations
+    List module; Hide translations
+    Localization; Hide translations in List module
+..  _pageTsConfigWebList-hideTranslations:
+
+hideTranslations
+================
+
+..  confval:: hideTranslations
+    :name: mod-web-list-hideTranslations
+    :type: list of table names, or *
+
+    For tables in this list all their translated records in additional website languages will be hidden
+    in the List module.
+
+    Use `*` to hide all records of additional website languages in all tables or set
+    single table names as comma-separated list.
+
+..  _pageTsConfigWebList-hideTranslations-example-all:
+
+Example: Hide all translated records
+------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.hideTranslations = *
+
+..  _pageTsConfigWebList-hideTranslations-example:
+
+Example: Hide translated records in tables tt_content and tt_news
+-----------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.hideTranslations = tt_content, tt_news
+
+..  index::
+    itemsLimitPerTable
+    List module; Items per table
+..  _pageTsConfigWebList-itemsLimitPerTable:
+
+itemsLimitPerTable
+==================
+
+..  confval:: itemsLimitPerTable
+    :name: mod-web-list-itemsLimitPerTable
+    :type:  positive integer
+    :Default: 20
+
+    Set the default maximum number of items to show per table.
+    The number must be between `0` and `10000`. If below or above this range,
+    the nearest valid number will be used.
+
+    If a value is defined in the `$TCA[<table>]['interface']['maxDBListItems']`
+    of the table, it will override this TSconfig option.
+    For example, the `maxDBListItems` for the `pages` table is `30` by default.
+
+..  _pageTsConfigWebList-itemsLimitPerTable-example:
+
+Example: Limit items per table in overview to 10
+------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        itemsLimitPerTable = 10
+    }
+
+..  index::
+    itemsLimitSingleTable
+    List module; Items per table in single table view
+..  _pageTsConfigWebList-itemsLimitSingleTable:
+
+itemsLimitSingleTable
+=====================
+
+..  confval:: itemsLimitSingleTable
+    :name: mod-web-list-itemsLimitSingleTable
+    :type:  positive integer
+    :Default: 100
+
+    Set the default maximum number of items to show in single table view.
+    The number must be between `0` and `10000`. If below or above this range,
+    the nearest valid number will be used.
+
+    If a value is defined in the `$TCA[<table>]['interface']['maxSingleDBListItems']`
+    of the table, it will override this TSconfig option.
+    For example, the `maxSingleDBListItems` for the `pages` table is `50` by default.
+
+..  _pageTsConfigWebList-itemsLimitSingleTable-example:
+
+Example: Limit items in single table view to 10
+-----------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        itemsLimitSingleTable = 10
+    }
+
+..  index::
+    listOnlyInSingleTableView
+    List module; Records in single table view only
+..  _pageTsConfigWebList-listOnlyInSingleTableView:
+
+listOnlyInSingleTableView
+=========================
+
+..  confval:: listOnlyInSingleTableView
+    :name: mod-web-list-listOnlyInSingleTableView
+    :type:  boolean
+    :Default: 0
+
+    If set, the default view will not show the single records inside a
+    table anymore, but only the available tables and the number of records
+    in these tables. The individual records will only be listed in the
+    single table view, that means when a table has been clicked. This is
+    very practical for pages containing many records from many tables!
+
+..  _pageTsConfigWebList-listOnlyInSingleTableView-example:
+
+Example: Only list records of tables in single-table mode
+---------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        listOnlyInSingleTableView = 1
+    }
+
+    The result will be that records from tables are only listed in the single-table mode:
+
+..  figure:: /Images/ManualScreenshots/List/PageTsModWebListListOnlyInSingleTableView.png
+    :alt: The list module after activating the single-table mode
+
+    The list module after activating the single-table mode
+
+..  index::
+    newPageWizard.override
+    Pages; New wizard
+..  _pageTsConfigWebList-newPageWizard-override:
+
+newPageWizard.override
+======================
+
+..  confval:: newPageWizard.override
+    :name: mod-web-list-newPageWizard-override
+    :type: string
+
+    If set to an extension key, then the specified module or route will be used for creating
+    new elements on the page.
+
+
+..  index::
+    noCreateRecordsLink
+    Buttons; Create new record
+..  _pageTsConfigWebList-noCreateRecordsLink:
+
+noCreateRecordsLink
+===================
+
+..  confval:: noCreateRecordsLink
+    :name: mod-web-list-noCreateRecordsLink
+    :type:  boolean
+    :Default: 0
+
+    If set, the link "Create new record" is hidden.
+
+..  _pageTsConfigWebList-noCreateRecordsLink-example:
+
+Example: Hide the "Create new record" link.
+-------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list {
+        noCreateRecordsLink = 1
+    }
+
+
+..  index::
+    noExportRecordsLinks
+    Buttons; Export
+..  _pageTsConfigWebList-noExportRecordsLinks:
+
+noExportRecordsLinks
+====================
+
+..  confval:: noExportRecordsLinks
+    :name: mod-web-list-noExportRecordsLinks
+    :type:  boolean
+    :Default: 0
+
+    ..  versionchanged:: 13.1.0, 12.4.11
+        Up until these versions this option also hid the
+        :guilabel:`Download` button used for CSV export.
+
+    If set, the :guilabel:`Download` button is hidden
+    in the :guilabel:`Web > List` module.
+
+    This option is for example important to disable batch
+    download of sensitive data via t3d exports.
+
+    ..  include:: /Images/AutomaticScreenshots/WebList/WithExportButtons.rst.txt
+
+    ..  include:: /Images/AutomaticScreenshots/WebList/NoExportButtons.rst.txt
+
+    ..  note::
+        This option only hides the buttons in the list module. Bulk export of
+        data is still possible via the context menu of the page tree.
+
+..  _pageTsConfigWebList-noExportRecordsLinks-example:
+
+Example: Hide the "Download" and "Export" links
+-----------------------------------------------
+
+..  include:: /CodeSnippets/PageTSconfig/Mod/noExportRecordsLinks.rst.txt
+
+..  index::
+    noViewWithDokTypes
+    Buttons; View page
+..  _pageTsConfigWebList-noViewWithDokTypes:
+
+noViewWithDokTypes
+==================
+
+..  confval:: noViewWithDokTypes
+    :name: mod-web-list-noViewWithDokTypes
+    :type:  string (comma-separated list of integers)
+    :Default: `254,255`
+
+    Hide view icon for the defined :ref:`doktypes <t3coreapi:list-of-page-types>`.
+
+..  index::
+    table.[tableName].hideTable
+    List module; Hide tables
+..  _pageTsConfigWebList-table-tableName-hideTable:
+
+table.[tableName].hideTable
+===========================
+
+..  confval:: table.[tableName].hideTable
+    :name: mod-web-list-table-tableName-hideTable
+    :type:  boolean
+    :Default: 0
+
+    If set to non-zero, the table is hidden. If it is zero, table is shown
+    even if table name is listed in "hideTables" list.
+
+..  _pageTsConfigWebList-table-tableName-hideTable-example:
+
+Example: Hide table tt_content
+------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.table.tt_content.hideTable = 1
+
+
+..  index::
+    table.[tableName].displayColumnSelector
+    List module; columns selector
+..  _pageTsConfigWebList-table-tableName-displayColumnSelector:
+
+table.[tableName].displayColumnSelector
+=======================================
+
+..  confval:: table.[tableName].displayColumnSelector
+    :name: mod-web-list-table-tableName-displayColumnSelector
+    :type:  boolean
+
+    If set to false, the column selector in the title row of the specified
+    table gets hidden. If the column selctors have been disabled globally
+    this option can be used to enable it for a specific table.
+
+..  _pageTsConfigWebList-table-tableName-displayColumnSelector-example-disable:
+
+Example: Hide the column selector for tt_content
+------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.table.tt_content.displayColumnSelector = 0
+
+..  _pageTsConfigWebList-table-tableName-displayColumnSelector-example-enable:
+
+Example: Hide the column selector for all tables but sys_category
+-----------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_list.displayColumnSelector = 0
+    mod.web_list.table.sys_category.displayColumnSelector = 1
+
+
+..  index::
+    tableDisplayOrder
+    List module; Order tables
+..  _pageTsConfigWebList-tableDisplayOrder:
+
+tableDisplayOrder
+=================
+
+..  confval:: tableDisplayOrder.[tableName]
+    :name: mod-web-list-tableDisplayOrder
+    :type: array
+
+    Flexible configuration of the order in which tables are displayed.
+
+    The keywords `before` and `after` can be used to specify an order relative
+    to other table names.
+
+    ..  code-block:: typoscript
+
+        mod.web_list.tableDisplayOrder.<tableName> {
+            before = <tableA>, <tableB>, ...
+            after = <tableA>, <tableB>, ...
+        }
+
+..  index::
+    searchLevel.items
+    Items; Search level
+..  _pageTsConfigWebList-searchLevel-items:
+
+searchLevel.items
+=================
+
+..  confval:: searchLevel.items
+    :name: mod-web-list-searchLevel-items
+    :type: array
+
+    Sets labels for each level label in the search level select box
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        mod.web_list.searchLevel.items {
+            -1 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.infinite
+            0 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.0
+            1 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.1
+            2 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.2
+            3 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.3
+            4 = EXT:core/Resources/Private/Language/locallang_core.xlf:labels.searchLevel.4
+        }
+
+..  index::
+    searchLevel.items
+    Items; Search level
+
+..  _pageTsConfigWebList-searchLevel-default:
+
+searchLevel.default
+===================
+
+..  confval:: searchLevel.default
+    :name: mod-web-list-searchLevel-default
+    :type: integer
+
+    ..  versionadded:: 13.2
+
+    This option allows to define one of the available level options
+    as the default level to use.
+
+    When searching for records in the :guilabel:`Web > List` module as well as
+    the database browser, it is possible to select the search levels (page tree
+    levels to respect in the search).
+
+    An editor is therefore able to select between the current page, a couple of
+    defined levels (e.g. 1, 2, 3) as well as the special "infinite levels".
+
+    Those options can already be extended using the TSconfig option
+    :confval:`mod-web-list-searchLevel-items`.
+
+..  _pageTsConfigWebList-searchLevel-default-example:
+
+Example: Set the default search level to "infinite levels"
+----------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+    mod.web_list.searchLevel.default = -1
+
diff --git a/Documentation/PageTsconfig/Mod/WebView.rst b/Documentation/PageTsconfig/Mod/WebView.rst
new file mode 100644
index 000000000..a36ae3298
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/WebView.rst
@@ -0,0 +1,87 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    mod; web_view
+    Modules; View
+..  _pagewebview:
+
+========
+web_view
+========
+
+Configuration options of the "Web > View" module.
+
+..  contents::
+    :local:
+
+..  index::
+    previewFrameWidths
+    Preview; Frame widths
+    Preview; Tablet
+    Preview; Mobile
+
+previewFrameWidths
+==================
+
+..  confval:: previewFrameWidths
+    :name: mod-web-view-previewFrameWidths
+    :type: array
+
+    Configure available presets in view module.
+
+    <key>.label
+        Label for the preset
+
+    <key>.type
+        Category of the preset, must be one of 'desktop', 'tablet' or 'mobile'
+
+    <key>.width
+        Width of the preset
+
+    <key>.height
+        Height of the preset
+
+Example: Define a new preview preset
+------------------------------------
+
+With this configuration a new preset '1014' with size 1024x768 will be configured with a label
+loaded from an xlf file and the category 'desktop'.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_view.previewFrameWidths {
+        1024.label = LLL:EXT:viewpage/Resources/Private/Language/locallang.xlf:computer
+        1024.type = desktop
+        1024.width = 1024
+        1024.height = 768
+    }
+
+..  figure:: /Images/ManualScreenshots/View/WebViewTSConfigPreview.png
+    :alt: Dropdown menu Width with added frame size called myPreview
+
+    Dropdown menu Width with added frame size called myPreview
+
+
+..  index::
+    View module; type parameter
+
+type
+====
+
+..  confval:: type
+    :name: mod-web-view-type
+    :type: positive integer
+
+    Enter the value of the `&type=` parameter passed to the webpage.
+
+Example: Show pages of type 42 in the preview
+---------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.web_view {
+        # Frontend link will be something like index.php?id=123&type=42
+        type = 42
+    }
diff --git a/Documentation/PageTsconfig/Mod/Wizards.rst b/Documentation/PageTsconfig/Mod/Wizards.rst
new file mode 100644
index 000000000..f304863cf
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/Wizards.rst
@@ -0,0 +1,281 @@
+..  include:: /Includes.rst.txt
+..  index:: Wizards
+
+..  _page-mod-wizard:
+
+=======
+wizards
+=======
+
+The `wizards` section allows to customize the *New record wizard* and the
+*New content element wizard*.
+
+..  contents::
+    :local:
+
+..  index:: Wizards; new content element
+..  _pagenewcontentelementwizard:
+
+newContentElement.wizardItems
+=============================
+
+..  versionchanged:: 13.0
+    New content elements added via TCA to the
+    :ref:`items <t3tca:columns-select-properties-items>` of field :sql:`CType`
+    of table :sql:`tt_content` are automatically added to the New Content Element
+    Wizard. The following page TSconfig can be used to override values set via
+    TCA.
+
+..  confval-menu::
+    :display: tree
+
+    ..  confval:: newContentElement.wizardItems
+        :name: mod-wizards-newContentElement-wizardItems
+        :type: array
+        :Path: mod.wizards.newContentElement.wizardItems
+
+        In the New Content Element Wizard, content element types are grouped
+        together by type. Each such group can be configured independently. The
+        four default groups are: `default`, `special`, `forms` and `plugins`.
+
+        ..  versionchanged:: 13.0
+            The group `common` was renamed to `default`. A permanent migration is in
+            place.
+
+        ..  confval:: removeItems
+            :name: mod-wizards-newContentElement-wizardItems-removeItems
+            :type: comma separated list of groups
+            :Path: mod.wizards.newContentElement.wizardItems.removeItems
+
+            ..  versionchanged:: 13.0
+
+            With this setting one or several groups with all their content
+            elements can be hidden in the New Content Element Wizard.
+
+            .. code-block:: typoscript
+
+                # This will remove the "menu" group
+                mod.wizards.newContentElement.wizardItems.removeItems := addToList(menu)
+
+        ..  confval:: [group].before
+            :name: mod-wizards-newContentElement-wizardItems-group-before
+            :type: string
+            :Path: mod.wizards.newContentElement.wizardItems.[group].before
+
+            Sorts [group] in front of the group given.
+
+        ..  confval:: [group].after
+            :name: mod-wizards-newContentElement-wizardItems-group-after
+            :type: string
+            :Path: mod.wizards.newContentElement.wizardItems.[group].after
+
+            Sorts [group] after the group given.
+
+        ..  confval:: [group].header
+            :name: mod-wizards-newContentElement-wizardItems-group-header
+            :type: string | localized string
+            :Path: mod.wizards.newContentElement.wizardItems.[group].header
+
+            Name of the group.
+
+        ..  confval:: [group].show
+            :name: mod-wizards-newContentElement-wizardItems-group-show
+            :type: string, comma-separated list of items
+            :Path: mod.wizards.newContentElement.wizardItems.[group].show
+
+            ..  versionchanged:: 13.0
+                The configuration of the New Content Element Wizard has been
+                changed to automatically registering the groups and elements
+                from the TCA configuration.
+
+                The previously used option to show / hide elements
+                :typoscript:`mod.wizards.newContentElement.wizardItems.<group>.show` is
+                not evaluated anymore.
+
+                All configured groups and elements are automatically shown. Removing these
+                groups and elements from the New Content Element Wizard can be done via
+                the option :confval:`removeItems <mod-wizards-newContentElement-wizardItems-removeItems>` and
+                :confval:`[group].removeItems <mod-wizards-newContentElement-wizardItems-group-removeItems>`
+                options.
+
+        ..  confval:: [group].elements
+            :name: mod-wizards-newContentElement-wizardItems-group-elements
+            :type: array
+            :Path: mod.wizards.newContentElement.wizardItems.[group].elements
+
+            List of items in the group.
+
+            ..  confval:: [name]
+                :name: mod-wizards-newContentElement-wizardItems-group-elements-name
+                :type: array
+                :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name]
+
+                Configuration for a single item.
+
+                ..  confval:: iconIdentifier
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-iconIdentifier
+                    :type: string
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].iconIdentifier
+
+                    The icon identifier of the icon you want to display.
+
+                ..  confval:: iconOverlay
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-iconOverlay
+                    :type: string
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].iconOverlay
+
+                    The icon identifier of the overlay icon you want to use.
+
+                ..  confval:: title
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-title
+                    :type: string | localized string
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].title
+
+                    Name of the item.
+
+                ..  confval:: description
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-description
+                    :type: string | localized string
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].description
+
+                    Description text for the item.
+
+                ..  confval:: tt_content_defValues
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-tt_content_defValues
+                    :type: array
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].tt_content_defValues
+
+                    Default values for tt_content fields.
+
+                ..  confval:: saveAndClose
+                    :name: mod-wizards-newContentElement-wizardItems-group-elements-name-saveAndClose
+                    :type: bool
+                    :Path: mod.wizards.newContentElement.wizardItems.[group].elements.[name].saveAndClose
+                    :Default: `false`
+
+                    If `true`, directs the user back to the :guilabel:`Page` module
+                    directly instead of showing the FormEngine.
+
+        ..  confval:: [group].removeItems
+            :name: mod-wizards-newContentElement-wizardItems-group-removeItems
+            :type: Comma separated list
+            :Path: mod.wizards.newContentElement.wizardItems.[group].removeItems
+
+            ..  versionchanged:: 13.0
+
+            Comma separated list of content elements that should be hidden in
+            [group].
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/page.tsconfig
+
+                mod.wizards.newContentElement.wizardItems {
+                    special.removeItems := addToList(html)
+                }
+
+..  _pageexample1:
+
+Example: Add a new element to the "common" group
+------------------------------------------------
+
+..  literalinclude:: _newContentElementWizard.tsconfig
+    :language: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+..  _pageexample2:
+
+Example: Create a new group and add an element to it
+----------------------------------------------------
+
+..  literalinclude:: _newContentElementWizardGroup.tsconfig
+    :language: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+With the second example, the bottom of the new content element wizard shows:
+
+..  figure:: /Images/ManualScreenshots/List/PageTsModWizardsNewContentElementExample2.png
+    :alt: Added entry in the new content element wizard
+
+    Added entry in the new content element wizard
+
+..  index::
+    Wizards; record
+    New Record wizard; order
+..  _mod-wizards-newRecord-order:
+
+newRecord.order
+===============
+
+..  confval:: newRecord.order
+    :name: mod-wizards-newRecord-order
+    :type: list of values
+
+    Define an alternate order for the groups of records in the new records
+    wizard. Pages and content elements will always be on top, but the
+    order of other record groups can be changed.
+
+    Records are grouped by extension keys, plus the special key "system"
+    for records provided by the TYPO3 Core.
+
+..  _mod-wizards-newRecord-order-example:
+
+Example: Place the tt_news group at the top of the new record dialog
+--------------------------------------------------------------------
+
+Place the tt_news group at the top (after pages and content
+elements), other groups follow unchanged:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.wizards.newRecord.order = tt_news
+
+..  figure:: /Images/ManualScreenshots/List/NewRecordWizardNewOrder.png
+    :alt: The position of News changed after modifying the New record screen
+
+    The position of News changed after modifying the New record screen
+
+
+..  index::
+    Wizards; record
+    New Record wizard; After page button
+    New Record wizard; Inside page button
+..  _mod-wizards-newRecord-pages:
+
+newRecord.pages
+===============
+
+..  confval:: newRecord.pages
+    :name: mod-wizards-newRecord-pages
+    :type: boolean
+
+    Use the following sub-properties to show or hide the specified links.
+    Setting any of these properties to 0 will hide the corresponding link,
+    but setting to 1 will leave it visible.
+
+    show.pageAfter
+        Show or hide the link to create new pages after the selected page.
+
+    show.pageInside
+        Show or hide the link to create new pages inside the selected page.
+
+    show.pageSelectPosition
+        Show or hide the link to create new pages at a selected position.
+
+..  _mod-wizards-newRecord-pages-example:
+
+Example: Hide the "Page (inside)" link in the "New Record" dialog
+-----------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    mod.wizards.newRecord.pages.show {
+        # Hide the "Page (inside)" link.
+        pageInside = 0
+    }
+
+..  figure:: /Images/ManualScreenshots/List/PageTsModWizardsNewRecordHideInside.png
+    :alt: The modified New record screen without Page (inside)
+
+    The modified new record screen without page (inside)
diff --git a/Documentation/PageTsconfig/Mod/_WebList/_downloadPresets.tsconfig b/Documentation/PageTsconfig/Mod/_WebList/_downloadPresets.tsconfig
new file mode 100644
index 000000000..2f27fe123
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/_WebList/_downloadPresets.tsconfig
@@ -0,0 +1,14 @@
+mod.web_list.downloadPresets {
+    pages {
+        minimum {
+            label = Quick overview
+            columns = uid, title, crdate, slug
+        }
+
+        fullExport {
+            identifier = uid-title
+            label = LLL:EXT:myext/Resources/Private/Language/locallang.xlf:preset2.label
+            columns = uid, title
+        }
+    }
+}
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Mod/_WebList/_downloadPresetsUser.tsconfig b/Documentation/PageTsconfig/Mod/_WebList/_downloadPresetsUser.tsconfig
new file mode 100644
index 000000000..5d7c7ad15
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/_WebList/_downloadPresetsUser.tsconfig
@@ -0,0 +1,13 @@
+page.mod.web_list.downloadPresets {
+    pages {
+        minimum {
+            label = Quick overview (customized)
+            columns = uid, title, crdate, slug
+        }
+
+        fullExport {
+            label = Short with URL
+            columns = uid, title, slug
+        }
+    }
+}
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Mod/_newContentElementWizard.tsconfig b/Documentation/PageTsconfig/Mod/_newContentElementWizard.tsconfig
new file mode 100644
index 000000000..328fb33ed
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/_newContentElementWizard.tsconfig
@@ -0,0 +1,10 @@
+# Add a new element (header) to the "common" group
+mod.wizards.newContentElement.wizardItems.common.elements.header {
+    iconIdentifier = content-header
+    title = Header
+    description = Adds a header element only
+    tt_content_defValues {
+        CType = header
+    }
+}
+mod.wizards.newContentElement.wizardItems.common.show := addToList(header)
diff --git a/Documentation/PageTsconfig/Mod/_newContentElementWizardGroup.tsconfig b/Documentation/PageTsconfig/Mod/_newContentElementWizardGroup.tsconfig
new file mode 100644
index 000000000..58f64b789
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/_newContentElementWizardGroup.tsconfig
@@ -0,0 +1,19 @@
+# Create a new group and add a (pre-filled) element to it
+mod.wizards.newContentElement.wizardItems.myGroup {
+    header = LLL:EXT:cms/layout/locallang.xlf:advancedFunctions
+    elements.customText {
+        iconIdentifier = content-text
+        title = Introductory text for national startpage
+        description = Use this element for all national startpages
+        tt_content_defValues {
+            CType = text
+            bodytext (
+                    <h2>Section Header</h2>
+                    <p class="bodytext">Lorem ipsum dolor sit amet, consectetur, sadipisci velit ...</p>
+            )
+            header = Section Header
+            header_layout = 100
+        }
+    }
+}
+mod.wizards.newContentElement.wizardItems.myGroup.show = customText
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Mod/_snippets/_mod.SHARED.colPos_list.tsconfig b/Documentation/PageTsconfig/Mod/_snippets/_mod.SHARED.colPos_list.tsconfig
new file mode 100644
index 000000000..3b359d5dc
--- /dev/null
+++ b/Documentation/PageTsconfig/Mod/_snippets/_mod.SHARED.colPos_list.tsconfig
@@ -0,0 +1 @@
+mod.SHARED.colPos_list = 0,2
\ No newline at end of file
diff --git a/Documentation/PageTsconfig/Options.rst b/Documentation/PageTsconfig/Options.rst
new file mode 100644
index 000000000..643660515
--- /dev/null
+++ b/Documentation/PageTsconfig/Options.rst
@@ -0,0 +1,86 @@
+..  include:: /Includes.rst.txt
+
+..  _pageoptions:
+
+=======
+options
+=======
+
+Various options for the page affecting the Core at various points.
+
+Properties
+==========
+
+..  contents::
+    :depth: 2
+    :local:
+
+..  index::
+    options.backendLayout
+    Backend; Layout
+..  _pagebackendlayout:
+
+backendLayout.exclude
+---------------------
+
+..  confval:: backendLayout.exclude
+    :name: options-backendLayout-exclude
+    :type: list of identifiers / uids
+
+    Exclude a list of backend layouts from being selectable when assigning a backend layout
+    to a page record.
+
+    Use the uid/identifier of the record in the default data provider.
+
+..  _pagebackendlayout-example:
+
+Example: Exclude two backend layouts from drop down selector
+------------------------------------------------------------
+
+..  figure:: /Images/ManualScreenshots/List/BackendLayoutID.png
+    :alt: Two backend layout records shown in list module
+
+    Before: Two backend layout records shown in list module
+
+..  code-block:: typoscript
+   :caption: EXT:site_package/Configuration/page.tsconfig
+
+   # Exclude two backend layouts from drop down selector
+   options.backendLayout.exclude = 1,2
+
+..  figure:: /Images/ManualScreenshots/List/BackendLayoutsExcluded.png
+    :alt: Drop down without backend layouts
+
+    After: Drop down without backend layouts
+
+..  index::
+   options.backendLayout
+   Backend; Layout
+..  _pagedefaultuploadfolder:
+
+defaultUploadFolder
+-------------------
+
+..  confval:: defaultUploadFolder
+    :name: options-defaultUploadFolder
+    :type: string
+
+    Identical to the user TSconfig setting
+    :ref:`options.defaultUploadFolder <useroptions-defaultUploadFolder>`,
+    this allows the setting of a default upload folder per page.
+
+    If specified and the given folder exists, this setting will override the
+    value defined in user TSconfig.
+
+    The syntax is "storage_uid:file_path".
+
+Example: Set default upload
+---------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Set default upload folder to "fileadmin/page_upload" on PID 1
+    [traverse(page, "uid") == 1]
+        options.defaultUploadFolder = 1:/page_upload/
+    [END]
diff --git a/Documentation/PageTsconfig/Rte.rst b/Documentation/PageTsconfig/Rte.rst
new file mode 100644
index 000000000..ee6d19f2c
--- /dev/null
+++ b/Documentation/PageTsconfig/Rte.rst
@@ -0,0 +1,588 @@
+..  include:: /Includes.rst.txt
+..  index::
+    RTE
+    Rich text editor
+    see: Rich text editor; RTE
+..  _pageTsRte:
+
+===
+RTE
+===
+
+The `RTE` prefix key is used for configuration of the Rich Text Editor.
+Please refer to the :ref:`RTE chapter <t3coreapi:rte>` in Core API document
+for more general information on RTE configuration and data processing.
+
+The order in which the configuration for the RTE is loaded is (the first one which
+is set will be used, see :ref:`example <pageTsRteOverridePreset>` below):
+
+1.  preset defined for a specific field via page TSconfig
+2.  :ref:`richtextConfiguration <t3tca:columns-text-properties-richtextConfiguration>`
+    defined for a specific field via TCA
+3.  general preset defined via page TSconfig (:typoscript:`RTE.default.preset`)
+4.  default (the preset "default", e.g. as defined by EXT:rte_ckeditor or overridden
+    in :file:`ext_localconf.php`)
+
+The full property path building is a bit more complex than for other
+property segments. The goal is that global options can be set that can
+also be overridden in more specific situations:
+
+Configure all RTE for all tables, fields and types:
+    `RTE.default`
+
+Configure RTE for a specific field in a table
+    `RTE.config.[tableName].[fieldName]`
+
+Configure RTE for a specific field in a table for a specific :ref:`record type <t3tca:types>`
+    `RTE.config.[tableName].[fieldName].types.[type]`
+
+Configuring RTE via page TSconfig is general and not specific to a
+particular rich-text editor. However, TYPO3 comes with EXT:rte_ckeditor, so this one
+will usually be used. This page covers only the general configuration, for
+more information about configuring EXT:rte_ckeditor, see the
+:ref:`rte_ckeditor configuration <ext_rte_ckeditor:configuration>`.
+
+..  contents::
+    :local:
+
+..  _pageTsRte-examples:
+
+Examples
+========
+
+..  _pageTsRte-example-disable:
+
+Example: Disable RTE
+--------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Disable all RTEs
+    RTE.default.disabled = 1
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Disable all RTEs
+    RTE.default.disabled = 1
+    # Enable RTE for the tt_content bodytext field only
+    RTE.config.tt_content.bodytext.disabled = 0
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Disable all RTEs
+    RTE.default.disabled = 1
+    # Enable RTE for the tt_content bodytext field only
+    RTE.config.tt_content.bodytext.disabled = 0
+    # But disable RTE for tt_content bodytext again if the record type is "text"
+    RTE.config.tt_content.bodytext.types.text.disabled = 1
+
+..  _pageTsRteOverridePreset:
+
+Example: Override preset
+------------------------
+
+Refer to the description of the order above for details of which setting has priority over which.
+
+Summary:
+
+*   Setting the preset via page TSconfig *for a specific field* overrides all,
+    else
+*   TCA richtextConfiguration (for a specific field) overrides the page TSconfig
+    default preset (:typoscript:`RTE.default.preset`)
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # set a default preset to use as fallback
+    RTE.default.preset = custom_preset_default
+
+    # Override preset for field "description" in table "tt_address"
+    RTE.config.tt_address.description.preset = custom_preset_fancy
+
+..  _pageTsRte-properties:
+
+Properties
+==========
+
+..  contents::
+    :depth: 2
+    :local:
+
+..  index:: RTE; disable
+
+disabled
+--------
+
+..  confval:: disabled
+    :name: rte-disabled
+    :type: boolean
+
+    If set, the editor is disabled. This option is evaluated in :php:`\TYPO3\CMS\Backend\Form\FormEngine`
+    where it determines whether the RTE is rendered or not. Note that a backend user can also ultimately
+    disable RTE's in his user settings.
+
+..  index::
+    RTE; Configuration
+    RTE; config
+
+
+buttons
+-------
+
+..  _buttons-link-options-removeitems:
+
+buttons.link.options.removeItems
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.options.removeItems
+    :name: rte-buttons-link-options-removeItems
+    :type: list of strings
+
+    List of tab items to remove from the dialog of the link button.
+    Possible tab items are: page, file, url, email, folder, telephone.
+
+    Note: More tabs may be provided by extensions.
+
+..  _buttons-link-targetselector-disabled:
+
+buttons.link.targetSelector.disabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.targetSelector.disabled
+    :name: rte-buttons-link-targetselector-disabled
+    :type: boolean
+    :Default: 0
+
+    If set, the selection of link target is removed from the link
+    insertion/update dialog.
+
+..  _buttons-link-pageidselector-enabled:
+
+buttons.link.pageIdSelector.enabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.pageIdSelector.enabled
+    :name: rte-buttons-link-pageidselector-enabled
+    :type: boolean
+    :Default: 0
+
+    If set, the specification of a page id, without using the page tree,
+    is enabled in the link insertion/update dialog.
+
+    Note: This feature is intended for authors who have to deal with a
+    very large page tree. Note that the feature is disabled by default.
+
+..  _buttons-link-queryparametersselector-enabled:
+
+buttons.link.queryParametersSelector.enabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.queryParametersSelector.enabled
+    :name: rte-buttons-link-queryparametersselector-enabled
+    :type: boolean
+    :Default: 0
+
+    If set, an additional field is enabbled in the link insertion/update
+    dialogue allowing authors to specify query parameters to be added on
+    the link
+
+..  _buttons-link-relattribute-enabled:
+
+buttons.link.relAttribute.enabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.relAttribute.enabled
+    :name: rte-buttons-link-relattribute-enabled
+    :type: boolean
+    :Default: 0
+
+    If set, an additional field is enabled in the link insertion/update
+    dialogue allowing authors to specify a rel attribute to be added to
+    the link.
+
+..  _buttons-link-properties-class-allowedclasses:
+
+buttons.link.properties.class.allowedClasses
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.properties.class.allowedClasses
+    :name: rte-buttons-link-properties-class-allowedclasses
+    :type: list of id-strings
+
+    Classes available in the Insert/Modify link dialogue.
+
+..  _buttons-link-properties-class-required:
+
+buttons.link.properties.class.required
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.properties.class.required
+    :name: rte-buttons-link-properties-class-required
+    :type: boolean
+
+    If set, a class must be selected for any link. Therefore, the empty
+    option is removed from the class selector.
+
+..  _buttons-link-type-properties-class-required:
+
+buttons.link.[ *type* ].properties.class.required
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.[type].properties.class.required
+    :name: rte-buttons-link-type-properties-class-required
+    :type: boolean
+
+    If set, a class must be selected for any link of the given type.
+    Therefore, the empty option is removed from the class selector.
+    Possible types are: page, file, url, email, folder, telephone.
+
+..  _buttons-link-properties-target-default:
+
+buttons.link.properties.target.default
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.properties.target.default
+    :name: rte-buttons-link-properties-target-default
+    :type: string
+
+    This sets the default target for new links in the RTE.
+
+
+..  _buttons-link-type-properties-target-default:
+
+buttons.link.[ *type* ].properties.target.default
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: buttons.link.[type].properties.target.default
+    :name: rte-buttons-link-type-properties-target-default
+    :type: string
+
+    Specifies a default target for links of the given type.
+    Possible types are: page, file, url, mail, spec. More types may be
+    provided by extensions.
+
+..  index::
+    RTE; Content language direction
+    RTE config; contentsLanguageDirection
+..  _rte-config-contentsLanguageDirection:
+
+config.contentsLanguageDirection
+--------------------------------
+
+..  confval:: config.contentsLanguageDirection
+    :name: rte-config-contentsLanguageDirection
+    :type: string
+
+    The configuration `contentsLangDirection` of the ckeditor is used to define the
+    direction of the content. It is filled by the direction defined in the site
+    language of the current element.
+
+    As fallback the following page TsConfig configuration can be used:
+
+    ..  code-block:: typoscript
+        :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+        # always use right to left
+        RTE.config.contentsLanguageDirection = rtl
+
+        # except for the following language:
+        [siteLanguage("locale").getName() == "en-US"]
+            RTE.config.contentsLanguageDirection = ltr
+        [END]
+
+..  index::
+    RTE; Server processing
+    RTE; proc
+..  _rte-config-proc:
+
+proc
+----
+
+The `proc` section allows customization of the server processing of the content, see
+the :ref:`transformation section <t3coreapi:transformations-tsconfig>` of the RTE chapter in
+the core API document for more general information on server processing.
+
+The `proc` properties are in :code:`\TYPO3\CMS\Core\Html\RteHtmlParser` and
+are universal for all RTEs. The main objective of these options is to allow for minor
+configuration of the transformations. For instance you may disable the mapping between
+:code:`<b>-<strong>` and :code:`<i>-<em>` tags which is done by the `ts_transform` transformation.
+
+Notice how many properties relate to specific transformations only! Also notice that the meta-transformations
+`ts_css` imply other transformations.
+
+This means that options limited to `ts_transform` will also work for `ts_css` of course.
+
+
+..  index::
+    RTE; Classes allowed
+..  _rte-proc-allowedClasses:
+
+allowedClasses
+~~~~~~~~~~~~~~
+
+..  confval:: proc.allowedClasses
+    :name: rte-proc-allowedClasses
+    :type: string with comma separated values
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    Direction: From RTE to database, saving a record.
+
+    Allowed general class names when content is stored in database. Could be a list matching the
+    number of defined classes you have. Class names are case insensitive.
+
+    This might be a really good idea to do, because when pasting in content from MS word for
+    instance there are a lot of `<SPAN>` and `<P>` tags which may have class names in. So by
+    setting a list of allowed classes, such foreign class names are removed.
+
+    If a class name is not found in this list, the default is to remove the class.
+
+..  index::
+    RTE; HTML tags allowed
+    RTE; Tags allowed
+..  _rte-proc-allowTags:
+
+allowTags
+~~~~~~~~~
+
+..  confval:: proc.allowTags
+    :name: rte-proc-allowTags
+    :type: string with comma separated values
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    Tags to allow. Notice, this list is  *added* to the default list,
+    which you see here:
+
+    b,i,u,a,img,br,div,center,pre,figure,figcaption,font,hr,sub,sup,p,strong,em,li,ul,ol,blockquote,strike,span,abbr,acronym,dfn
+
+..  index::
+    RTE; Tags outside paragraphs
+..  _rte-proc-allowTagsOutside:
+
+allowTagsOutside
+~~~~~~~~~~~~~~~~
+
+..  confval:: proc.allowTagsOutside
+    :name: rte-proc-allowTagsOutside
+    :type: string with comma separated values
+    :Default: `address, article, aside, blockquote, footer, header, hr, nav, section, div`
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    Enter tags which are allowed outside of `<P>` and `<DIV>` sections when converted back to database.
+
+
+Example: Allow only hr tags outside of p and div
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Allow only hr tags outside of p and div
+    RTE.default.proc.allowTagsOutside = hr
+
+..  index::
+    RTE; block elements
+..  _rte-proc-blockElementList:
+
+blockElementList
+~~~~~~~~~~~~~~~~
+
+..  confval:: proc.blockElementList
+    :name: rte-proc-blockElementList
+    :type: string with comma separated values
+
+    Comma-separated list of uppercase tags (e.g. :code:`P,HR`) that overrides the list of HTML
+    elements that will be treated as block elements by the RTE transformations.
+
+..  index::
+    RTE; tags denyed
+..  _rte-proc-denyTags:
+
+denyTags
+~~~~~~~~
+
+..  confval:: proc.denyTags
+    :name: rte-proc-denyTags
+    :type: string with comma separated values
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    Tags from above list to disallow.
+
+..  index::
+    RTE; HTMLparser DB entry
+..  _rte-proc-entryHTMLparser_db:
+
+entryHTMLparser_db
+~~~~~~~~~~~~~~~~~~
+
+..  confval:: proc.entryHTMLparser_db
+    :name: rte-proc-entryHTMLparser_db
+    :type: boolean / :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies to all kinds of processing.
+
+    Allows to enable / disable the :ref:`HTMLparser <t3tsref:htmlparser>` *before* the
+    content is processed with the predefined processors (e.g. ts_images or ts_transform).
+
+..  index::
+    RTE; HTMLparser RTE entry
+..  _rte-proc-entryHTMLparser_rte:
+
+entryHTMLparser_rte
+~~~~~~~~~~~~~~~~~~~
+
+..  confval:: proc.entryHTMLparser_rte
+    :name: rte-proc-entryHTMLparser_rte
+    :type: boolean / :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies to all kinds of processing.
+
+    Allows to enable / disable the :ref:`HTMLparser <t3tsref:htmlparser>` *before* the
+    content is processed with the predefined processors (e.g. ts_images or ts_transform).
+
+..  index::
+    RTE; HTMLparser DB exit
+..  _rte-proc-exitHTMLparser_db:
+
+exitHTMLparser_db
+~~~~~~~~~~~~~~~~~
+
+..  confval:: proc.exitHTMLparser_db
+    :name: rte-proc-exitHTMLparser_db
+    :type: boolean / :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies to all kinds of processing.
+
+    Allows to enable / disable the :ref:`HTMLparser <t3tsref:htmlparser>` *after* the
+    content is processed with the predefined processors (e.g. ts_images or ts_transform).
+
+..  index::
+    RTE; HTMLparser RTE exit
+..  _rte-proc-exitHTMLparser_rte:
+
+exitHTMLparser_rte
+~~~~~~~~~~~~~~~~~~
+
+..  confval:: proc.exitHTMLparser_rte
+    :name: rte-proc-exitHTMLparser_rte
+    :type: boolean / :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies to all kinds of processing.
+
+    Allows to enable / disable the :ref:`HTMLparser <t3tsref:htmlparser>` *after* the
+    content is processed with the predefined processors (e.g. ts_images or ts_transform).
+
+
+..  index::
+    RTE; HTMLparser DB
+..  _pageTsRteProcHtmlParserDb:
+
+HTMLparser_db
+~~~~~~~~~~~~~
+
+..  confval:: proc.HTMLparser_db
+    :name: rte-proc-HTMLparser_db
+    :type: :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    These are additional options to the HTML parser calls which strips of tags when the content is prepared
+    *from the RTE to the database*, saving a record. It is possible to configure additional rules like which other
+    tags to preserve, which attributes to preserve, which values are allowed as attributes of a certain tag etc.
+
+    For the detailed list of properties, see the :ref:`section of the TypoScript reference <t3tsref:htmlparser>`.
+
+    ..  note::
+
+        This configuration is similar in frontend TypoScript and Page TSconfig.
+        This is why single properties can be looked up in the TypoScript reference.
+
+        Also note the :ref:`HTMLparser <t3tsref:htmlparser>` options :code:`keepNonMatchedTags`
+        and :code:`htmlSpecialChars` are *not* observed. They are preset internally.
+
+..  _pageTsRteProcHtmlParserDb-Sanitization:
+
+Sanitization
+^^^^^^^^^^^^
+
+..  versionadded:: 9.5.29/10.4.19
+
+An HTML sanitizer is available to sanitize and remove XSS from markup. It
+strips tags, attributes and values that are not explicitly allowed.
+
+Sanitization for persisting data is disabled by default and can be enabled
+globally by using the corresponding feature flag in the :ref:`configuration
+files <t3coreapi:configuration-files>`
+:file:`config/system/settings.php` or
+:file:`config/system/additional.php`:
+
+..  code-block:: php
+
+    $GLOBALS['TYPO3_CONF_VARS']['SYS']['features']['security.backend.htmlSanitizeRte'] = true;
+
+It can then be disabled per use case with a custom processing instruction:
+
+..  code-block:: yaml
+    :caption: EXT:site_package/Configuration/Processing.yaml
+
+    processing:
+      allowTags:
+        # ...
+      HTMLparser_db:
+        # ...
+        # disable individually per use case
+        htmlSanitize: false
+
+        # This is the default configuration,
+        # the feature flag has to be enabled
+        htmlSanitize:
+          # use default builder as configured in
+          # $GLOBALS['TYPO3_CONF_VARS']['SYS']['htmlSanitizer']
+          build: default
+
+
+..  index::
+    RTE; HTMLparser RTE
+..  _rte-proc-HTMLparser_rte:
+
+HTMLparser_rte
+~~~~~~~~~~~~~~
+
+..  confval:: proc.HTMLparser_rte
+    :name: rte-proc-HTMLparser_rte
+    :type: :ref:`HTMLparser <t3tsref:htmlparser>`
+
+    Applies for `ts_transform` and `css_transform` only.
+
+    These are additional options to the HTML parser calls which strips of tags when the content is prepared
+    *from the database to the RTE* rendering. It is possible to configure additional rules like which other
+    tags to preserve, which attributes to preserve, which values are allowed as attributes of a certain tag etc.
+
+    For the detailed list of properties, see the :ref:`section of the TypoScript reference <t3tsref:htmlparser>`.
+
+    ..  note::
+
+       This configuration is similar in frontend TypoScript and Page TSconfig.
+       This is why single properties can be looked up in the TypoScript reference.
+
+       Also note the :ref:`HTMLparser <t3tsref:htmlparser>` options :code:`keepNonMatchedTags`
+       and :code:`htmlSpecialChars` are *not* observed. They are preset internally.
+
+..  index::
+    RTE; Transformations overruled
+..  _rte-proc-:
+
+overruleMode
+~~~~~~~~~~~~
+
+..  confval:: proc.overruleMode
+    :name: rte-proc-overruleMode
+    :type: Comma list of RTE transformations
+
+    This can overrule the RTE transformation set from TCA. Notice, this is a  *comma list* of transformation keys.
diff --git a/Documentation/PageTsconfig/TcaDefaults.rst b/Documentation/PageTsconfig/TcaDefaults.rst
new file mode 100644
index 000000000..6ac0cdc84
--- /dev/null
+++ b/Documentation/PageTsconfig/TcaDefaults.rst
@@ -0,0 +1,40 @@
+..  include:: /Includes.rst.txt
+..  index::
+    TCAdefaults
+    Records; Default values
+..  _pageTsTcaDefaults:
+
+===========
+TCAdefaults
+===========
+
+This allows to set or override the `default` values of `TCA` fields that is available
+for various TCA types, for instance for :ref:`type=input <t3tca:columns-input-properties-default>`.
+
+The full path of a setting include the table and the field name: `TCAdefaults.[table name].[field]`
+
+This key is also available on :ref:`User TSconfig level <userTsTcaDefaults>`, the order of default
+values when creating new records in the backend is this:
+
+#.  Value from `$GLOBALS['TCA']`
+#.  Value from :ref:`user TSconfig <userTsTcaDefaults>`
+#.  Value from page TSconfig (these settings)
+#.  Value from "defVals" GET variables
+#.  Value from previous record based on
+    :ref:`useColumnsForDefaultValues <t3tca:ctrl-reference-usecolumnsfordefaultvalues>`
+
+..  note::
+    `TCAdefaults` is not applied to :ref:`FlexForm <t3coreapi:flexforms>` values.
+    These can only be addressed via :xml:`<default>` elements within the
+    FlexForm data structure.
+
+..  _pageTsTcaDefaults-example:
+
+Example: Do not hide newly created pages by default
+===================================================
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCAdefaults.pages.hidden = 0
+
diff --git a/Documentation/PageTsconfig/TceForm.rst b/Documentation/PageTsconfig/TceForm.rst
new file mode 100644
index 000000000..20b551a18
--- /dev/null
+++ b/Documentation/PageTsconfig/TceForm.rst
@@ -0,0 +1,1264 @@
+..  include:: /Includes.rst.txt
+..  index::
+    TCEFORM
+    Records; editing options
+..  _tceform:
+..  _pagetceformconfobj:
+..  _pagetceformflexformsheet:
+
+=======
+TCEFORM
+=======
+
+Allows detailed configuration of how editing forms are rendered for a page
+tree branch and for individual tables if you like. You can enable and
+disable options, blind options in selector boxes etc.
+
+See the core API document section :ref:`FormEngine <t3coreapi:FormEngine>` for more
+details on how records are rendered in the backend.
+
+..  _tceform-apply-properties:
+
+Applying properties
+===================
+
+The properties listed below apply to various contexts which are explained per
+property. The full property path thus depends on the property and where it should
+apply. In general, a more specific property path overrides a less specific one:
+
+Some properties apply to single fields, those can be usually set per table or
+per table and record type. This leads to the property paths
+`TCEFORM.[tableName].[fieldName].[propertyName]` to configure the field for all types
+and `TCEFORM.[tableName].[fieldName].types.[typeName].[propertyName]` to configure a field for a specific
+type, see the :ref:`TCA type section <t3tca:types>` for details on types.
+
+While all that property path munging looks messy at first, it should become more
+clear when reading through the single properties below and looking at the examples.
+
+..  youtube:: B3IQq7pIJ_o
+
+..  _tceformApplyPropertiesFlexForm:
+
+Applying properties to FlexForm fields
+--------------------------------------
+
+Other properties also apply to :ref:`FlexForm <t3coreapi:flexforms>` fields, in this case the full property
+path including the data structure key has to be set:
+
+..  code-block:: typoscript
+
+     # TCEFORM.[tableName].[fieldName].[dataStructureKey].[flexSheet].[flexFieldName with escaped dots].[propertyName]
+     TCEFORM.tt_content.pi_flexform.sfregister_create.sDEF.settings\.fields\.selected.addItems.ZZZ = ZZZ
+
+The sheet name (sDEF) must be given only if the FlexForm has a sheet.
+
+The `[dataStructureKey]` represents the key of a FlexForm in
+:php:`$GLOBALS['TCA'][<tableName>]['columns'][<field>]['config']['ds']`. This key will be split into up to
+two parts. By default the first part will be used as identifier of the FlexForm in TSconfig. The second part
+will override the identifier if it is not empty, `list` or `*`. For example the identifier of the key
+`myext_pi1,list` will be `myext_pi1` and of the key `*,my_CType` it will be `my_CType`. See section
+:ref:`Pointing to a data structure <t3tca:columns-flex-ds-pointer>` of the TCA reference for details.
+
+The flexFieldName is the name of the property in the FlexForm. If it contains
+dots ('.'), these must be escaped with backslash.
+
+Some properties apply to whole FlexForm sheets, their property path is
+`TCEFORM.[tableName].[fieldName].[dataStructureKey].[flexSheet].[propertyName]`.
+
+..  _tceform-properties:
+
+Properties
+==========
+
+..  contents::
+    :depth: 2
+    :local:
+
+..  index::
+    Records; select items added
+..  _tceform-addItems:
+
+addItems
+--------
+
+..  confval:: addItems
+    :name: tceform-addItems
+    :type: localized string
+
+    Change the list of items in :ref:`TCA type=select <t3tca:columns-select>` fields. Using this property,
+    items can be added to the list. Note that the added elements might be removed if the selector represents
+    records: If the select box is a relation to another table. In that case only existing records
+    will be preserved.
+
+    The subkey :typoscript:`icon` will allow to add your own icons to new values.
+
+    The subkey :typoscript:`group` can be used to insert a new element into an
+    existing select item group by settings the value to the group identifier.
+    The grouping is usually displayed in select fields with groups available.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.header_layout.addItems`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header_layout.types.textpic.addItems`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.addItems`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+    ..  warning::
+        Do not add page types this way (using `TCEFORM.pages.doktype.addItems`), instead the proper
+        PHP API should be used to do this, see :ref:`Core APIs <t3coreapi:page-types>` for details.
+
+..  _tceform-addItems-example:
+
+Example: Add header layout option
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.header_layout {
+        # Add another header_layout option:
+        addItems.1525215969 = Another header layout
+        # Add another one with localized label, icon and group
+        addItems.1525216023 = LLL:EXT:my_ext/Resources/Private/Language/locallang.xlf:header_layout
+        addItems.1525216023.icon = EXT:my_ext/icon.png
+        addItems.1525216023.group = special
+    }
+
+    Instead of adding files by path, icon identifiers should be used.
+
+..  index::
+    Records; labels changed
+..  _tceform-altLabels:
+
+altLabels
+---------
+
+..  confval:: altLabels
+    :name: tceform-altLabels
+    :type: localized string
+
+    This property applies to :ref:`TCA type=select <t3tca:columns-select>`,
+    :ref:`TCA type=check <t3tca:columns-check>` and :ref:`TCA type=radio <t3tca:columns-radio>`.
+
+    This property allows you to enter alternative labels for the items in the list. For a single checkbox or radio
+    button, use `default`, for multiple checkboxes and radiobuttons, use an integer for their position starting at 0.
+
+    This property is available for various levels:
+
+    table level:
+        `TCEFORM.[tableName].[fieldName].altLabels`
+
+    table and record type level:
+        `TCEFORM.[tableName].[fieldName].types.[typeName].altLabels`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.altLabels`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-altLabels-example:
+
+Example: Override labels for document types
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.doktype {
+        # Set a different item label
+        altLabels.1 = STANDARD Page Type
+        altLabels.254 = Folder (for various elements)
+        # Sets the default label for Recycler via "locallang":
+        altLabels.255 = LLL:EXT:my_ext/Resources/Private/Language/locallang_tca.xlf:recycler
+    }
+
+..  figure:: /Images/ManualScreenshots/List/PagesDoktypeDifferentLabels.png
+    :alt: The Page types with modified labels
+
+    The Page types with modified labels
+
+..  note::
+
+    If the item has an **empty** value, the syntax is slightly different and an additional dot must be provided,
+    like on this example:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.space_before_class.altLabels.. = foo
+
+Note the *double dot* after `altLabels`.
+
+..  _tceform-page_tsconfig_id:
+
+PAGE_TSCONFIG_ID
+----------------
+
+..  confval:: PAGE_TSCONFIG_ID
+    :name: tceform-PAGE_TSCONFIG_ID
+    :type: integer
+
+    This option allows to provide a value for dynamic SQL-WHERE parameters. The
+    value is defined for a specific field of a table. For usage with flexform
+    fields, the entire path to a sub-field must be provided.
+
+..  note::
+
+    This value can be used for the TCA property :ref:`foreign_table_where <t3tca:columns-select-properties-foreign-table-where>`
+    and for the `addWhere` part of the :ref:`suggest wizard <pagetceformsuggest>`.
+
+..  _tceform-page_tsconfig_id-example:
+
+Example: Substitute a marker in a plugin FlexForm
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.myField.PAGE_TSCONFIG_ID = 22
+
+In this example, the value will substitute the marker in a plugin FlexForm.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tx_myext_table.myfield.PAGE_TSCONFIG_ID = 22
+
+This example might be used for a record in an extension. It refers to a
+table called `tx_myext_table` and the field `myfield`. Here the marker will
+be substituted by the value `22`.
+
+..  _tceform-page_tsconfig_idlist:
+
+PAGE_TSCONFIG_IDLIST
+--------------------
+
+..  confval:: PAGE_TSCONFIG_IDLIST
+    :name: tceform-PAGE_TSCONFIG_IDLIST
+    :type: list of integers
+
+    See above.
+
+..  _tceform-page_tsconfig_idlist-example:
+
+Example: Substitute a list of IDs in a plugin FlexForm
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.myField.PAGE_TSCONFIG_IDLIST = 20,21,22
+
+In this example, the value will substitute the marker in a plugin FlexForm.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tx_myext_table.myfield.PAGE_TSCONFIG_IDLIST = 20,21,22
+
+This example might be used for a record in an extension. It refers to a
+table called `tx_myext_table` and the field `myfield`. Here the marker will
+be substituted by the list of integers.
+
+
+..  _tceform-page_tsconfig_str:
+
+PAGE_TSCONFIG_STR
+-----------------
+
+..  confval:: PAGE_TSCONFIG_STR
+    :name: tceform-PAGE_TSCONFIG_STR
+    :type: string
+
+    See above.
+
+..  _tceform-page_tsconfig_str-example:
+
+Example: Substitute a string in a plugin FlexForm
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.myField.PAGE_TSCONFIG_STR = %hello%
+
+In this example, the value will substitute the marker in a plugin FlexForm.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tx_myext_table.myfield.PAGE_TSCONFIG_STR = %hello%
+
+This example might be used for a record in an extension. It refers to a
+table called `tx_myext_table` and the field `myfield`. Here the marker will
+be substituted by the given value.
+
+
+..  index::
+     Records; field configuration
+..  _pageTsConfigTceFormColorPalette:
+
+colorPalette
+------------
+
+..  versionadded:: 13.0
+
+..  confval:: colorPalette
+    :name: tceform-colorPalette
+    :type: string
+
+     Assign a :ref:`color palette <pagecolorpalettes>` to a specific field of a
+     table, for all fields within a table or a global configuration affecting all
+     color pickers within :ref:`FormEngine <t3coreapi:FormEngine>`. If no palette
+     is defined, FormEngine falls back to all configured colors.
+
+..  _pageTsConfigTceFormColorPalette-example:
+
+Example: Assign a palette to a field
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+    # Assign a palette to a specific field
+    TCEFORM.tx_myext_table.myfield.colorPalette = messages
+
+    # Assign a palette to all color pickers used in a table
+    TCEFORM.tx_myext_table.colorPalette = key_colors
+
+    # Assign global palette
+    TCEFORM.colorPalette = main
+
+
+..  index::
+     Records; field configuration
+..  _pageTsConfigTceFormConfig:
+
+config
+------
+
+..  confval:: config
+    :name: tceform-config
+
+     This setting allows to override TCA field configuration. This will influence configuration settings in
+     :php:`$GLOBALS['TCA'][<tableName>]['columns'][<fieldName>]['config'][<key>]`, see
+     :ref:`TCA reference <t3tca:columns-properties-config>` for details.
+
+     Not all configuration options can be overridden, the properties are restricted and depend on the
+     :ref:`field type <t3tca:columns-types>`. The array
+     :code:`typo3/sysext/backend/Classes/Form/Utility/FormEngineUtility.php->$allowOverrideMatrix`
+     within :ref:`FormEngine code <t3coreapi:FormEngine>` defines details:
+
+     ..  code-block:: php
+
+          'input' => ['size', 'max', 'readOnly'],
+          'number' => ['size', 'readOnly'],
+          'email' => ['size', 'readOnly'],
+          'link' => ['size', 'readOnly'],
+          'password' => ['size', 'readOnly'],
+          'datetime' => ['size', 'readOnly'],
+          'color' => ['size', 'readOnly'],
+          'uuid' => ['size', 'enableCopyToClipboard'],
+          'text' => ['cols', 'rows', 'wrap', 'max', 'readOnly'],
+          'json' => ['cols', 'rows', 'readOnly'],
+          'check' => ['cols', 'readOnly'],
+          'select' => ['size', 'autoSizeMax', 'maxitems', 'minitems', 'readOnly', 'treeConfig', 'fileFolderConfig'],
+          'category' => ['size', 'maxitems', 'minitems', 'readOnly', 'treeConfig'],
+          'group' => ['size', 'autoSizeMax', 'maxitems', 'minitems', 'readOnly', 'elementBrowserEntryPoints'],
+          'folder' => ['size', 'autoSizeMax', 'maxitems', 'minitems', 'readOnly', 'elementBrowserEntryPoints'],
+          'inline' => ['appearance', 'behaviour', 'foreign_label', 'foreign_selector', 'foreign_unique', 'maxitems', 'minitems', 'size', 'autoSizeMax', 'symmetric_label', 'readOnly'],
+          'file' => ['appearance', 'behaviour', 'maxitems', 'minitems', 'readOnly'],
+          'imageManipulation' => ['ratios', 'cropVariants'],
+
+     The reason that not all properties can be changed is that
+     internally, the :ref:`DataHandler <t3coreapi:datahandler-basics>` performs database
+     operations which require finalized :ref:`TCA <t3tca:start>` definitions
+     that are accessed without this TSconfig getting interpreted. This mismatch
+     would then lead to inconsistencies.
+
+     An `input` or `text` TCA field can *not* enable the
+     :ref:`RTE <typo3/cms-rte-ckeditor:introduction>` via the
+     :typoscript:`config.enableRichtext` option due to similar reasons in respect
+     to the DataHandler.
+
+     Also, if for example the :typoscript:`max` definition of a field is made
+     larger than the TCA definition of that field, you may need to to change
+     the file :file:`ext_tables.sql` (see :ref:`t3coreapi:ext_tables-sql`)
+     to adjust column definitions, especially when using the
+     :ref:`Auto-generated structure <t3coreapi:auto-generated-db-structure>`.
+
+     The property :typoscript:`config` is available for these levels:
+
+     table level, example:
+          :typoscript:`TCEFORM.tt_content.header.config.max`
+
+     table and record type level, example:
+          :typoscript:`TCEFORM.tt_content.header.types.textpic.config.max`
+
+     Flex form field level, example:
+          No current TYPO3 version allows to override the configuration of
+          Flex form fields, even though this was previously documented here.
+          This may change in future versions.
+
+     ..  todo: Removed, because this is broken in every known TYPO3 version.
+     ..  todo: Maybe re-enable this, if it gets fixed in a future release
+          :typoscript:`TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.myInputField.config.max`
+
+          Where :typoscript:`sDEF` is the sheet name and :typoscript:`myext_pi1` the name
+          of the plugin.
+
+..  index::
+    Records; tree configuration
+..  _pageTsConfigTceFormConfigTreeConfig:
+
+config.treeConfig
+-----------------
+
+..  confval:: config.treeConfig
+    :name: tceform-config-treeConfig
+    :type: int
+
+    The `treeConfig` sub properties of :ref:`TCEFORM.config <pageTsConfigTceFormConfig>` are dedicated to the TCA config type
+    `select` with :ref:`renderType=selectTree <t3tca:columns-select-rendertype-selectTree>`. A couple of
+    :ref:`treeConfig <t3tca:columns-select-properties-treeconfig>` properties can be overriden on page TSconfig level, see their detailed description
+    in the :ref:`TCA reference <t3tca:columns-select-properties-treeconfig>`:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        config.treeConfig.startingPoints = 1,42
+        config.treeConfig.appearance.expandAll = 1
+        config.treeConfig.appearance.maxLevels = 2
+        config.treeConfig.appearance.nonSelectableLevels = 1
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.myField.config.treeConfig.startingPoints`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header.types.config.treeConfig.startingPoints`
+
+    Flex form field level, example:
+        No current TYPO3 version allows to override the configuration of
+        Flex form fields, even though this was previously documented here.
+        This may change in future versions.
+
+    ..  todo: Removed, because this is broken in every known TYPO3 version.
+    ..  todo: Maybe re-enable this, if it gets fixed in a future release
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.config.treeConfig.startingPoints`
+
+        Where `sDEF` is the sheet name and :typoscript:`myext_pi1` the name
+        of the plugin. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+
+..  index::
+    Records; field description
+..  _tceform-description:
+
+description
+-----------
+
+..  include:: /Images/AutomaticScreenshots/Input1.rst.txt
+
+..  confval:: description
+    :name: tceform-description
+    :type: string
+
+    This property sets or overrides the TCA property
+    :ref:`TCA description <t3tca:columns-properties-description>`, which allows to
+    define a description for a TCA field, next to its label.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.tt_content.header.description = override description
+
+    As already known from other properties, this can also be configured for a
+    specific language.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.tt_content.header.description.de = override description for DE
+
+    The option can be used on a per record type basis, too.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.tt_content.header.types.textpic.description = override description for textpic
+
+    Also referencing language labels is supported.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.tt_content.header.description = LLL:EXT:my_ext/Resources/Private/Language/locallang.xlf:override_description
+
+..  index::
+    Records; field disabled
+..  _tceform-disabled:
+
+disabled
+--------
+
+..  confval:: disabled
+    :name: tceform-disabled
+    :type: boolean
+
+    If set, the field is not displayed in the backend form of the record.
+    However, the field can still be set by other means. For example if
+    this property is set:
+    :typoscript:`TCEFORM.tt_content.colPos.disabled = 1` the :guilabel:`Column` field
+    will not be displayed in the content elements form. The
+    content element can still be moved to another column which internally also
+    sets the field :sql:`colPos`. Fields with the TSconfig property
+    :tsconfig:`TCEFORM.<table>.<field>.disabled` therefore show the same
+    behaviour as fields of the TCA type :ref:`passthrough <t3tca:columns-passthrough>`.
+
+    table level, example:
+        `TCEFORM.tt_content.header.disabled`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header.types.textpic.disabled`
+
+    Flex form sheet level. If set, the entire tab is not rendered, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.disabled`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.disabled`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-disabled-example:
+
+Example: Disable editing of the page title
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.title {
+        # The title field of the pages table is not editable
+        disabled = 1
+    }
+
+..  index::
+    Records; select items  disable "INVALID VALUE"
+..  _pageFormEngineDisableNoMatchingElement:
+
+disableNoMatchingValueElement
+-----------------------------
+
+..  confval:: disableNoMatchingValueElement
+    :name: tceform-disableNoMatchingValueElement
+    :type: boolean
+
+    This property applies only to items in :ref:`TCA type=select <t3tca:columns-select>` fields.
+    If a selector box value is not available among the options in the box, the default behavior
+    of TYPO3 is to preserve the value and to show a label which warns about this special state:
+
+    ..  figure:: /Images/ManualScreenshots/List/SelectInvalidValue.png
+        :alt: A missing selector box value is indicated by a warning message
+
+        A missing selector box value is indicated by a warning message
+
+    If disableNoMatchingValueElement is set, the element "INVALID VALUE" will not be added to the list.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.header_layout.disableNoMatchingValueElement`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header_layout.types.textpic.disableNoMatchingValueElement`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.disableNoMatchingValueElement`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _pageFormEngineDisableNoMatchingElement-example:
+
+Example: Disable "INVALID VALUE ..." label
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.doktype {
+        # "INVALID VALUE ..." label will never show up
+        disableNoMatchingValueElement = 1
+    }
+
+Now the selector box will default to the first element in the selector box:
+
+..  figure:: /Images/ManualScreenshots/List/SelectNoInvalidValue.png
+    :alt: Instead of show a warning message the system choose the first element in the selector box
+
+    Instead of show a warning message the system choose the first element in the selector box
+
+
+..  index::
+    Records; fileFolderConfig
+..  _fileFolderConfig:
+
+fileFolderConfig
+----------------
+
+..  confval:: fileFolderConfig
+    :name: tceform-fileFolderConfig
+    :type: array
+
+    The special :ref:`fileFolder configuration options
+    <t3tca:columns-select-properties-fileFolderConfig>`
+    for TCA columns of type :ref:`TCA type=select <t3tca:columns-select>` can
+    be used to fill a select field with files (images / icons) from a defined
+    folder.
+
+    The `fileFolderConfig` TCA configuration can be overridden with page
+    TSconfig, allowing administrators to use different folders or different file
+    extensions, per site.
+
+    The same sub properties as in the `fileFolderConfig` TCA configuration are
+    available:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        fileFolderConfig {
+            folder = 'EXT:styleguide/Resources/Public/Icons'
+            allowedExtensions = 'svg'
+            depth = 1
+        }
+
+    This property is available for various levels:
+
+    table level:
+        `TCEFORM.[tableName].[fieldName].fileFolderConfig.folder`
+
+    table and record type level:
+        `TCEFORM.[tableName].[fieldName].types.[typeName].fileFolderConfig.folder`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.fileFolderConfig.folder`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  index::
+    Records; select items user function
+..  _itemsProcFunc:
+
+itemsProcFunc
+-------------
+
+..  confval:: itemsProcFunc
+    :name: tceform-itemsProcFunc
+    :type: custom
+
+    This property applies only to items in :ref:`TCA type=select <t3tca:columns-select>` fields. The properties of
+    this key is passed on to the :ref:`itemsProcFunc <t3tca:columns-select-properties-itemsprocfunc>` in the
+    parameter array by the key "TSconfig".
+
+    This property is available for various levels:
+
+    table level:
+        `TCEFORM.[tableName].[fieldName].itemsProcFunc`
+
+    table and record type level:
+        `TCEFORM.[tableName].[fieldName].types.[typeName].itemsProcFunc`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.itemsProcFunc`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  index::
+    Records; select items remove
+..  _tceform-keepItems:
+
+keepItems
+---------
+
+..  confval:: keepItems
+    :name: tceform-keepItems
+    :type: list of values
+
+    Change the list of items in :ref:`TCA type=select <t3tca:columns-select>` fields. Using this property,
+    all items except those defined here are removed.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.header_layout.keepItems`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header_layout.types.textpic.keepItems`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.keepItems`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-keepItems-example:
+
+Example: Show only standard and spacer pages
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.doktype {
+        # Show only standard and "Spacer" page types
+        keepItems = 1, 199
+    }
+
+..  index::
+    Records; Field label
+
+..  _tceform_label:
+
+label
+-----
+
+..  confval:: label
+    :name: tceform-label
+    :type: localized string
+
+    This allows you to enter alternative labels for any field. The value can be a `LLL:` reference
+    to a localization file, the system will then look up the selected backend user language and tries
+    to fetch the localized string if available. However, it is also possible to override these by
+    appending the language key and hard setting a value, for example `label.de = Neuer Feldname`.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.[tableName].[fieldName].label`
+
+    table and record type level, example:
+        `TCEFORM.[tableName].[fieldName].types.[typeName].label`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.label`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform_label-example:
+
+Example: Override the label of a field
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.title {
+        label = LLL:EXT:my_ext/Resources/Private/Language/locallang.xlf:table.column
+        label.default = New Label
+        label.de = Neuer Feldname
+    }
+
+
+..  index::
+    Records; label for no matching value
+..  _tceform-noMatchingValue_label:
+
+noMatchingValue_label
+---------------------
+
+..  confval:: noMatchingValue_label
+    :name: tceform-noMatchingValue_label
+    :type: localized string
+
+    This property applies only to items in :ref:`TCA type=select <t3tca:columns-select>` fields, it allows defining
+    a different label of the :ref:`noMatchingValue <pageFormEngineDisableNoMatchingElement>` element.
+
+    It is possible to use the placeholder `%s` to insert the value. If the property is set to empty,
+    the label will be blank.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.header_layout.noMatchingValue_label`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header_layout.types.textpic.noMatchingValue_label`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.noMatchingValue_label`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-noMatchingValue_label-example:
+
+Example: Replace "INVALID VALUE ..." label with another string
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.doktype {
+        # Different "INVALID VALUE ..." label:
+        noMatchingValue_label = VALUE "%s" was not available!
+    }
+
+..  figure:: /Images/ManualScreenshots/List/SelectInvalidValueDifferentLabel.png
+    :alt:  An invalid selector box value is indicated by a warning message
+
+    An invalid selector box value is indicated by a warning message
+
+
+..  index::
+    Records; select items remove
+..  _tceform-removeItems:
+
+removeItems
+-----------
+
+..  confval:: removeItems
+    :name: tceform-removeItems
+    :type: list of values
+
+    Change the list of items in :ref:`TCA type=select <t3tca:columns-select>` fields. Using this property,
+    single items can be removed, leaving all others.
+
+    This property is available for various levels:
+
+    table level, example:
+        `TCEFORM.tt_content.header_layout.removeItems`
+
+    table and record type level, example:
+        `TCEFORM.tt_content.header_layout.types.textpic.removeItems`
+
+    Flex form field level, example:
+        `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.settings\.myfield.removeItems`
+
+        Where `sDEF` is the sheet name. For a description
+        see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-removeItems-example:
+
+Example: Remove "Recycler" and "Spacer" page types
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.doktype {
+        # Remove "Recycler" and "Spacer" page types
+        removeItems = 199, 255
+    }
+
+..  index::
+    FlexForm; Sheet description
+..  _tceform-sheetDescription:
+
+sheetDescription
+----------------
+
+..  confval:: sheetDescription
+    :name: tceform-sheetDescription
+    :type: localized string
+
+    Specifies a description for the sheet shown in the FlexForm.
+
+    This property is only available on flex form sheet level, for example
+    `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.sheetDescription`.
+
+    Where `sDEF` is the sheet name. For a description
+    see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+
+..  index::
+    FlexForm; Sheet short description
+..  _tceform-sheetShortDescr:
+
+sheetShortDescr
+---------------
+
+..  confval:: sheetShortDescr
+    :name: tceform-sheetShortDescr
+    :type: localized string
+
+    Specifies a short description of the sheet used as link title in the tab-menu.
+
+    This property is only available on flex form sheet level, example:
+    `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.sheetShortDescription`.
+
+    Where `sDEF` is the sheet name. For a description
+    see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  index::
+    FlexForm; Sheet title
+..  _tceform-sheetTitle:
+
+sheetTitle
+----------
+
+..  confval:: sheetTitle
+    :name: tceform-sheetTitle
+    :type: localized string
+
+    Set the title of the sheet / tab in a FlexForm configuration.
+
+    This property is only available on flex form sheet level, example:
+    `TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF.sheetTitle`.
+
+    Where `sDEF` is the sheet name. For a description
+    see the section :ref:`tceformApplyPropertiesFlexForm` on this page.
+
+..  _tceform-sheetTitle-example:
+
+Example: Rename the first tab of the FlexForm plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.tt_content.pi_flexform.myext_pi1.sDEF {
+        # Rename the first tab of the FlexForm plug-in configuration
+        sheetTitle = LLL:my_ext/Resource/Private/Language/locallang.xlf:tt_content.pi_flexform.myext_pi1.sDEF
+    }
+
+..  index::
+    Records; Suggest wizard
+    Suggest wizard
+..  _pagetceformsuggest:
+
+suggest
+-------
+
+Configuration of the suggest wizard that is available and often enabled
+for :ref:`TCA type=group <t3tca:columns-group>` fields.
+
+..  figure:: /Images/ManualScreenshots/List/TcaTypeGroupSuggest.png
+    :alt: A configured suggest wizard
+
+    A configured suggest wizard
+
+The properties listed below are available on various levels. A more specific setting overrides
+a less specific one:
+
+Configuration of all suggest wizards in all tables for all target query tables:
+    `TCEFORM.suggest.default`
+
+Configuration of all suggest wizards in all tables looking up records from a specific target table:
+    `TCEFORM.suggest.[queryTable]`
+
+Configuration of one suggest wizard field in one table for all target query tables:
+    `TCEFORM.[tableName].[fieldName].suggest.default`
+
+Configuration of one suggest wizard field in one table for a specific target query table:
+    `TCEFORM.[tableName].[fieldName].suggest.[queryTable]`
+
+Configuration of one suggest wizard field in a flex form field of one table for all target query tables:
+    `TCEFORM.[tableName].[fieldName].[dataStructureKey].[sheetName].[flexFieldName].suggest.default`
+
+Configuration of one suggest wizard field in a flex form field of one table for a specific target query table:
+    `TCEFORM.[tableName].[fieldName].[dataStructureKey].[sheetName].[flexFieldName].suggest.[queryTable]`
+
+..  index::
+    Suggest wizard; Search fields additional
+..  _tceform-suggest-additionalSearchFields:
+
+suggest.additionalSearchFields
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.additionalSearchFields
+    :name: tceform-suggest-additionalSearchFields
+    :type: string
+
+    Comma-separated list of fields the suggest wizard should also search in. By default the wizard looks only in the
+    fields listed in the :ref:`label <t3tca:ctrl-reference-label>` and :ref:`label_alt <t3tca:ctrl-reference-label-alt>`
+    of TCA :ref:`ctrl properties <t3tca:ctrl-reference>`.
+
+
+..  index::
+    Suggest wizard;  Where statement
+..  _tceform-suggest-addWhere:
+
+suggest.addWhere
+~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.addWhere
+    :name: tceform-suggest-addWhere
+    :type: string
+
+    Additional WHERE clause (with AND at the beginning).
+
+    Markers possible for replacement:
+
+    *   ###THIS_UID###
+    *   ###CURRENT_PID###
+    *   :ref:`###PAGE_TSCONFIG_ID### <page_tsconfig_id>`
+    *   :ref:`###PAGE_TSCONFIG_IDLIST### <page_tsconfig_idlist>`
+    *   :ref:`###PAGE_TSCONFIG_STR### <page_tsconfig_str>`
+
+..  _tceform-suggest-addWhere-example:
+
+Example: limit storage_pid to the children of a certain page
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.storage_pid.suggest.default {
+        addWhere = AND pages.pid=###PAGE_TSCONFIG_ID###
+    }
+
+..  index::
+    Suggest wizard; CSS class
+..  _tceform-suggest-cssClass:
+
+suggest.cssClass
+~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.cssClass
+    :name: tceform-suggest-cssClass
+    :type: string
+
+    Add a CSS class to every list item of the result list.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.suggest.pages {
+            # Configure all suggest wizards which list records from table "pages"
+            # to add the CSS class "pages" to every list item of the result list.
+            cssClass = pages
+        }
+
+
+..  index::
+    Suggest wizard; hide
+..  _tceform-suggest-hide:
+
+suggest.hide
+~~~~~~~~~~~~
+
+..  confval:: suggest.hide
+    :name: tceform-suggest-hide
+    :type: boolean
+
+    Hide the suggest field. Works only for single fields.
+
+..  _tceform-suggest-hide-example:
+
+Example: Hide the suggest field for the storage_pid
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.storage_pid.suggest.default {
+        hide = 1
+    }
+
+
+..  index::
+    Suggest wizard; Characters max
+..  _tceform-suggest-maxPathTitleLength:
+
+suggest.maxPathTitleLength
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.maxPathTitleLength
+    :name: tceform-suggest-maxPathTitleLength
+    :type: positive integer
+
+    Maximum number of characters to display when a path element is too long.
+
+..  _tceform-suggest-maxPathTitleLength-example:
+
+Example: Limit the suggest field to 30 characters
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.suggest.default {
+        maxPathTitleLength = 30
+    }
+
+..  index::
+    Suggest wizard; Characters min
+..  _tceform-suggest-minimumCharacters:
+
+suggest.minimumCharacters
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.minimumCharacters
+    :name: tceform-suggest-minimumCharacters
+    :type: positive integer
+    :Default: 2
+
+    Minimum number of characters needed to start the search. Works only for single fields.
+
+..  _tceform-suggest-minimumCharacters-example:
+
+Example: Start the suggest search after 3 characters
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.storage_pid.suggest.default {
+        minimumCharacters = 3
+    }
+
+
+..  index::
+    Suggest wizard; pid levels
+..  _tceform-suggest-pidDepth:
+
+suggest.pidDepth
+~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.pidDepth
+    :name: tceform-suggest-pidDepth
+    :type: positive integer
+
+    Expand pidList by this number of levels. Only has an effect, if pidList has a value.
+
+..  _tceform-suggest-pidDepth-example:
+
+Example: Set search depth for suggest field
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.suggest.default {
+        pidList = 6,7
+        pidDepth = 4
+    }
+
+..  index::
+    Suggest wizard; pid list
+..  _tceform-suggest-pidList:
+
+suggest.pidList
+~~~~~~~~~~~~~~~
+
+..  confval:: suggest.pidList
+    :name: tceform-suggest-pidList
+    :type: list of values
+
+    Limit the search to certain pages (and their subpages). When pidList is empty all pages will be included
+    in the search as long as the backend user is allowed to see them.
+
+..  _tceform-suggest-pidList-example:
+
+Example: Limit suggest search to records on certain pages
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.suggest.default {
+        # sets the pidList for a suggest fields in all tables
+        pidList = 1,2,3,45
+    }
+
+
+..  index::
+    Suggest wizard; receiver php class
+..  _tceform-suggest-receiverClass:
+
+suggest.receiverClass
+~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.receiverClass
+    :name: tceform-suggest-receiverClass
+    :type: Fully Qualified PHP class name
+    :Default: :php:`\TYPO3\CMS\Backend\Form\Element\SuggestDefaultReceiver`
+
+    PHP class alternative receiver class - the file that holds the class should be derived
+    from :code:`\TYPO3\CMS\Backend\Form\Element\SuggestDefaultReceiver`.
+
+..  index::
+    Suggest wizard; rendering user function
+..  _tceform-suggest-renderFunc:
+
+suggest.renderFunc
+~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.renderFunc
+    :name: tceform-suggest-renderFunc
+    :type: string
+
+    User function to manipulate the displayed records in the result.
+
+..  index::
+    Suggest wizard; Where statement
+..  _tceform-suggest-searchCondition:
+
+suggest.searchCondition
+~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.searchCondition
+    :name: tceform-suggest-searchCondition
+    :type: string
+
+    Additional WHERE clause (no AND needed to prepend).
+
+..  _tceform-suggest-searchCondition-example:
+
+Example: Only search on pages with doktype=1
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        TCEFORM.pages.storage_pid.suggest.default {
+            # Configure the suggest wizard for the field "storage_pid" in table "pages"
+            # to search only for pages with doktype=1
+            searchCondition = doktype=1
+        }
+
+..  index::
+    Suggest wizard; Search whole phrase
+..  _tceform-suggest-searchWholePhrase:
+
+suggest.searchWholePhrase
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  confval:: suggest.searchWholePhrase
+    :name: tceform-suggest-searchWholePhrase
+    :type: boolean
+    :Default: 0
+
+    Whether to do a `LIKE=%mystring%` (searchWholePhrase = 1) or a
+    `LIKE=mystring%` (to do a real find as you type).
+
+..  _tceform-suggest-searchWholePhrase-example:
+
+Example: Search only for whole phrases
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEFORM.pages.storage_pid.suggest.default {
+        # Configure the suggest wizard for the field "storage_pid" in table "pages" to search only for whole phrases
+        searchWholePhrase = 1
+    }
diff --git a/Documentation/PageTsconfig/TceMain.rst b/Documentation/PageTsconfig/TceMain.rst
new file mode 100644
index 000000000..12672a321
--- /dev/null
+++ b/Documentation/PageTsconfig/TceMain.rst
@@ -0,0 +1,643 @@
+..  include:: /Includes.rst.txt
+..  index:: TCEMAIN
+..  _pagetcemain:
+..  _pagetcemain-properties:
+
+=======
+TCEMAIN
+=======
+
+Configuration for the TYPO3 Core Engine (DataHandler). For general information, see
+the :ref:`according section of TYPO3 Explained <t3coreapi:tce>`.
+
+Properties
+==========
+
+..  contents::
+    :depth: 2
+    :local:
+
+..  index:: Clear cache; On saving record
+..  _pagetcemain-clearcachecmd:
+
+clearCacheCmd
+-------------
+
+..  confval:: clearCacheCmd
+    :name: tcemain-clearCacheCmd
+    :type: List of integers, `all`, `pages` or tags
+
+    This allows you to have the frontend cache for additional pages cleared when saving
+    to some page or branch of the page tree.
+
+    It it possible to trigger clearing of all caches or just the pages cache. It is also
+    possible to target precise pages either by referring to their ID numbers or to tags
+    that are attached to them.
+
+    Attaching tags to page cache is described in the :ref:`TypoScript Reference <t3tsref:stdwrap-addpagecachetags>`.
+
+..  _pagetcemain-clearcachecmd-example:
+
+Example: Clear the cache for certain pages when a record is changed
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN {
+        # Clear the cache for page uid 12 and 23 when saving a record in this page
+        clearCacheCmd = 12, 23
+        # Clear all frontent page caches of pages
+        clearCacheCmd = pages
+        # Clear ALL caches
+        clearCacheCmd = all
+        # Clear cache for all pages tagged with tag "pagetag1"
+        clearCacheCmd = cacheTag:pagetag1
+    }
+
+..  note::
+
+    In order for the :typoscript:`pages` and :typoscript:`all` commands to work for non-admin users,
+    make sure to set :typoscript:`options.clearCache.pages = 1` or :typoscript:`options.clearCache.all = 1` accordingly
+    in the user TSconfig.
+
+..  index:: Clear cache; Disable
+..  _pagetcemain-clearcache-disable:
+
+clearCache_disable
+------------------
+
+..  confval:: clearCache_disable
+    :name: tcemain-clearCache_disable
+    :type: boolean
+
+    If set, then the automatic clearing of page cache when records are edited etc. is disabled.
+    This also disables the significance of the two options
+    :ref:`clearCache_pageSiblingChildren <pagetcemain-clearcache-pagesiblingchildren>`
+    and :ref:`clearCache_pageGrandParent <pagetcemain-clearcache-pagegrandparent>`
+
+..  index:: Clear cache; On saving child page
+..  _pagetcemain-clearcache-pagegrandparent:
+
+clearCache_pageGrandParent
+--------------------------
+
+..  confval:: clearCache_pageGrandParent
+    :name: tcemain-clearCache_pageGrandParent
+    :type: boolean
+
+    If set, then the grand parent of a page being edited will have the page cache cleared.
+
+..  index:: Clear cache; On saving sibling page
+..  _pagetcemain-clearcache-pagesiblingchildren:
+
+clearCache_pageSiblingChildren
+------------------------------
+
+..  confval:: clearCache_pageSiblingChildren
+    :name: tcemain-clearCache_pageSiblingChildren
+    :type: boolean
+
+    If set, then children of all siblings of a page being edited will have the page cache cleared.
+
+    Default is that when a page record is edited, the cache for itself, the parent, and siblings (same level) is cleared.
+
+..  index:: Copy record; Disable hide
+..  _pagetcemaintables-disablehideatcopy:
+
+disableHideAtCopy
+-----------------
+
+..  confval:: disableHideAtCopy
+    :name: tcemain-disableHideAtCopy
+    :type: boolean
+
+    Disables the :ref:`hideAtCopy TCA feature <t3tca:ctrl-reference-hideatcopy>` if
+    configured for the table.
+
+..  _pagetcemaintables-disablehideatcopy-example:
+
+Example: Do not hide pages when they are copy-pasted
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.table.pages {
+       # Pages will *not* have "(copy)" appended:
+       disablePrependAtCopy = 1
+       # Pages will *not* be hidden upon copy:
+       disableHideAtCopy = 1
+    }
+
+These settings adjust that a page which is copied will neither have "(copy X)" appended nor be hidden.
+
+The last page in this tree, labeled "Test", is used as original to be copied. The first sub page was
+copied using the settings from the above example: It is labeled "Test" and is visible exactly like
+the original page. The page "Test (copy 2)" in the middle was in contrast copied in default mode:
+The page is hidden and the "(copy X)" suffix is added, if another page with the same named existed already.
+
+..  figure:: /Images/ManualScreenshots/List/PageCopyWithSuffix.png
+    :alt: Hidden page with added suffix after copying its original page
+
+    Hidden page with added suffix after copying its original page
+
+Example: Apply disableHideAtCopy as default to all tables
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.default {
+      disableHideAtCopy = 1
+    }
+
+
+..  index:: Copy record; Disable prepend string (copy)
+..  _pagetcemaintables-disableprependatcopy:
+
+disablePrependAtCopy
+--------------------
+
+..  confval:: disablePrependAtCopy
+    :name: tcemain-disablePrependAtCopy
+    :type: boolean
+
+    Disable the :ref:`prependAtCopy TCA feature <t3tca:ctrl-reference-prependatcopy>` if
+    configured for the table.
+
+    The word "prepend" is misleading. The "(copy)" label is actually *appended* to the record title.
+
+..  _pagetcemaintables-disableprependatcopy-example:
+
+Example: Do not append the "(copy)" label to newly copied pages
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.table.pages {
+       # Pages will *not* have "(copy)" appended:
+       disablePrependAtCopy = 1
+       # Pages will *not* be hidden upon copy:
+       disableHideAtCopy = 1
+    }
+
+These settings adjust that a page which is copied will neither have "(copy X)" appended nor be hidden.
+
+The last page in this tree, labeled "Test", is used as original to be copied. The first sub page was
+copied using the settings from the above example: It is labeled "Test" and is visible exactly like
+the original page. The page "Test (copy 2)" in the middle was in contrast copied in default mode:
+The page is hidden and the "(copy X)" suffix is added, if another page with the same named existed already.
+
+..  figure:: /Images/ManualScreenshots/List/PageCopyWithSuffix.png
+    :alt: Hidden page with added suffix after copying its original page
+
+    Hidden page with added suffix after copying its original page
+
+Example: Apply disablePrependAtCopy as default to all tables
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.default {
+      disablePrependAtCopy = 1
+    }
+
+
+..  index:: Link handler
+..  _pagetcemaintables-linkhandler:
+
+linkHandler
+-----------
+
+..  confval:: linkHandler
+    :name: tcemain-linkHandler
+    :type: array of link handler configurations
+
+    Contains an array of link handler configurations.
+
+    ..  attention::
+        The keys in this array
+        uniquely identify the type of link and are used in the TYPO3 link format,
+        for example `t3://record?identifier=my_content&uid=123`. Therefore the key
+        must never be changed or all existing links in the content will stop working.
+
+    :typoscript:`handler`
+        Fully qualified name of the class containing the backend link handler.
+
+    :typoscript:`configuration`
+        Configuration for the link handler, depends on the :typoscript:`handler`.
+        For :php:`TYPO3\CMS\Backend\LinkHandler\RecordLinkHandler`
+        :typoscript:`configuration.table` must be defined.
+
+    :typoscript:`scanBefore` / :typoscript:`scanAfter`
+        Define the order in which handlers are queried when determining
+        the responsible tab for editing an existing link.
+
+    :typoscript:`displayBefore` / :typoscript:`displayAfter`
+        Define the order of how the various tabs are displayed in the
+        link browser.
+
+..  _pagetcemaintables-linkhandler-example:
+
+Example: Display an additional tab in the linkbrowser
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following page TSconfig display an additional tab with the `label` as
+title in the linkbrowser. It then saves the link in the format
+`t3://record?identifier=my_content&uid=123`. To render the link in the
+frontend you need to define the same key in the TypoScript setup
+:ref:`config.recordLinks <t3tsref:setup-config-recordLinks>`.
+
+..  seealso::
+    For a complete example see also the :ref:`Record link tutorial
+    in TYPO3 Explained <t3coreapi:TableRecordLinkBrowserTutorials>`.
+
+..  code-block:: typoscript
+    :caption: Page TSconfig definition for identifier `my_content`
+
+    TCEMAIN.linkHandler.my_content {
+        handler = TYPO3\CMS\Backend\LinkHandler\RecordLinkHandler
+        label = LLL:EXT:my_extension/Resources/Private/Language/locallang.xlf:link.customTab
+        configuration {
+            table = tx_myextension_content
+        }
+        scanBefore = page
+    }
+
+..  index:: Page permissions
+..  _pagetcemain-permissions-user-group:
+
+permissions
+-----------
+
+..  index:: Page permissions; copyFromParent
+..  _pagetcemain-permissions-copyFromParent:
+
+Value copyFromParent
+~~~~~~~~~~~~~~~~~~~~
+
+The value :typoscript:`copyFromParent` can be set for each of the
+page TSconfig :typoscript:`TCEMAIN.permissions.*` sub keys. If this value is
+set, the page access permissions are copied from the parent page.
+
+Example: Inherit the group id of the parent page
+""""""""""""""""""""""""""""""""""""""""""""""""
+
+..  code-block:: php
+    :caption: config/system/settings.php | typo3conf/system/settings.php
+
+    $GLOBALS['TYPO3_CONF_VARS']['BE']['defaultPageTSconfig'] .= '
+        TCEMAIN.permissions.groupid = copyFromParent
+        TCEMAIN.permissions.group = 31
+        TCEMAIN.permissions.everybody = 0
+    ';
+
+By default all new pages created by users will inherit the group of the parent
+page. Members of this group get all permissions. Users not in the group get no
+permissions.
+
+When an administrator creates a new page she can use the module
+:guilabel:`System > Access` to set a different owner group for this new page.
+
+All subpages created to this new page will now automatically have the new pages
+group. The administrator does not have to set custom TSconfig to achieve this.
+
+This behaviour is similar to the "group sticky bit" in Unix for directories.
+
+..  index:: Page permissions; everybody
+
+..  _pagetcemain-permissions-everybody:
+
+everybody
+~~~~~~~~~
+
+..  confval:: permissions.everybody
+    :name: tcemain-permissions-everybody
+    :type: list of strings or integer 0-31
+    :Default: 0
+
+    Default permissions for everybody who is not the owner user or member of
+    the owning group, key list: `show`, `edit`, `delete`, `new`, `editcontent`.
+
+    Alternatively, it is allowed to set an integer between 0 and 31, indicating
+    which bits corresponding to the key list should be set: `show = 1`,
+    `edit = 2`, `delete = 4`, `new = 8`, `editcontent = 16`.
+
+    It also possible to set the value
+    :ref:`copyFromParent <pagetcemain-permissions-copyFromParent>` to inherit
+    the value from the parent page.
+
+..  _pagetcemain-permissions-everybody-example:
+
+Example: Set permissions defaults so that everybody can see the page
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.permissions {
+      # Everybody can at least see the page, normally everybody can do nothing
+      everybody = show
+    }
+
+The page "Community" was created with the settings from the example
+above. Compared to the two other pages created with default
+permissions you can see the effect: "Everybody" has read access:
+
+..  figure:: /Images/ManualScreenshots/Access/AccessDefaultActions.png
+    :alt: Page with altered permissions for backend users, groups and everybody
+
+    Page with altered permissions for backend users, groups and everybody
+
+..  index:: Page permissions; Group
+
+..  _pagetcemain-permissions-group:
+
+group
+~~~~~
+
+..  confval:: permissions.group
+    :name: tcemain-permissions-group
+    :type: list of strings or integer 0-31
+    :Default: show,edit,new,editcontent
+
+    Default permissions for group members, key list: `show`, `edit`, `new`,
+    `editcontent`.
+
+   Alternatively, it is allowed to set an integer between 0 and 31, indicating
+   which bits corresponding to the key list should be set: `show = 1`,
+   `edit = 2`, `delete = 4`, `new = 8`, `editcontent = 16`.
+
+   It also possible to set the value
+   :ref:`copyFromParent <pagetcemain-permissions-copyFromParent>` to inherit
+   the value from the parent page.
+
+
+..  _pagetcemain-permissions-group-example:
+
+Example: Set permission defaults so that the group can do anything with the new page
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.permissions {
+        # Group can do anything, normally "delete" is disabled
+        group = 31
+    }
+
+The page "Community" was created with the settings from the example
+above. Compared to the two other pages created with default
+permissions you can see the effect: The Backend Group can now also
+delete the page by default:
+
+..  figure:: /Images/ManualScreenshots/Access/AccessDefaultActions.png
+    :alt: Page with altered permissions for backend users, groups and everybody
+
+    Page with altered permissions for backend users, groups and everybody
+
+..  index:: Page permissions; Group id
+..  _pagetcemain-permissions-groupid:
+
+groupid
+~~~~~~~
+
+..  confval:: permissions.groupid
+    :name: tcemain-permissions-groupid
+    :type: positive integer or string
+
+    By default the owner group of a newly created page is set to the main group
+    of the backend user creating the page.
+
+    By setting the value of this property to
+    :ref:`copyFromParent <pagetcemain-permissions-copyFromParent>` the owner
+    group is copied from the newly created pages parent page.
+
+    The owner group of a newly created page can be hardcoded by setting this
+    property to a positive integer greater then zero.
+
+..  _pagetcemain-permissions-groupid-example:
+
+Example: Set default user group for permissions on new pages
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN {
+        # Owner be_groups UID for new pages
+        permissions.groupid = 3
+    }
+
+In this instance, backend group with UID 3 is "test_group". With the configuration
+above a new page would be created with this group setting instead of the default,
+even if a user who is not member of that group creates the page:
+
+..  figure:: /Images/ManualScreenshots/Access/AccessDefaultPermissions.png
+    :alt: Page with altered permissions for backend users and groups
+
+    Page with altered permissions for backend groups
+
+..  index:: Page permissions; User
+..  _pagetcemain-permissions-actions:
+
+user
+~~~~
+
+..  confval:: permissions.user
+    :name: tcemain-permissions-user
+    :type: list of strings or integer 0-31
+    :Default: show,edit,delete,new,editcontent
+
+    Default permissions for owner user, key list: `show`, `edit`, `delete`,
+    `new`, `editcontent`.
+
+    Alternatively, it is allowed to set an integer between 0 and 31, indicating
+    which bits corresponding to the key list should be set: `show = 1`,
+    `edit = 2`, `delete = 4`, `new = 8`, `editcontent = 16`.
+
+    It also possible to set the value
+    :ref:`copyFromParent <pagetcemain-permissions-copyFromParent>` to inherit
+    the value from the parent page.
+
+..  _pagetcemain-permissions-actions-example:
+
+Example: Set permission defaults so that the pages owner can do anything
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN.permissions {
+        # User can do anything, this is identical to the default value
+        user = 31
+    }
+
+..  index:: Page permissions; User id
+..  _pagetcemain-permissions-userid:
+
+userid
+~~~~~~
+
+..  confval:: permissions.userid
+    :name: tcemain-permissions-userid
+    :type: positive integer or string
+
+   By default the owner of a newly created page is the user that created or
+   copied the page.
+
+   By setting the value of this property to
+   :ref:`copyFromParent <pagetcemain-permissions-copyFromParent>` the owner
+   group is copied from the newly created pages parent page.
+
+   When this property is set to a positive integer the owner of new pages is
+   hardcoded to the user of that uid.
+
+..  _pagetcemain-permissions-userid-example:
+
+Example: Set default user for permissions on new pages
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCEMAIN {
+        # Owner be_users UID for new pages
+        permissions.userid = 2
+    }
+
+In this instance, backend user with UID 2 is "test". With the configuration
+above a new page would be created with this owner setting instead of the default,
+even if another user creates the page:
+
+..  figure:: /Images/ManualScreenshots/Access/AccessDefaultPermissions.png
+    :alt: Page with altered permissions for backend users
+
+    Page with altered permissions for backend users
+
+..  index:: Page preview
+..  _pagetcemain-preview:
+
+preview
+-------
+
+..  confval:: preview
+    :name: tcemain-preview
+    :type: array
+
+    Configure preview link generated for the save+view button and other frontend view related buttons
+    in the backend. This allows to have different preview URLs depending on the record type. A common
+    use case is to have previews for blog or news records, and this feature allows you to define a different
+    preview page for content elements as well, which might be handy if those are stored in a sysfolder.
+
+    ..  code-block:: typoscript
+       :caption: EXT:site_package/Configuration/page.tsconfig
+
+       TCEMAIN.preview {
+           disableButtonForDokType = 199, 254, 255
+           <table name> {
+               previewPageId = 123
+               useDefaultLanguageRecord = 0
+               fieldToParameterMap {
+                   uid = tx_myext_pi1[showUid]
+               }
+               additionalGetParameters {
+                   tx_myext_pi1.special = HELLO # results in tx_myext_pi1[special]
+               }
+           }
+       }
+
+    The :typoscript:`previewPageId` is the uid of the page to use for preview. If this setting is omitted the
+    current page will be used. If the current page is not a normal page, the root page will be chosen.
+
+    The :typoscript:`disableButtonForDokType` setting allows you to disable the preview button for a given list
+    of :ref:`doktypes <t3coreapi:list-of-page-types>`. If none are configured, this defaults to: 199, 254, 255 (Spacer,
+    Folder and Recycler).
+
+    The :typoscript:`useDefaultLanguageRecord` defaults to `1` and ensures that translated records will use the
+    uid of the default record for the preview link. You may disable this, if your extension can deal
+    with the uid of translated records.
+
+    The :typoscript:`fieldToParameterMap` is a mapping which allows you to select fields of the record to be
+    included as GET-parameters in the preview link. The key specifies the field name and the value specifies
+    the GET-parameter name.
+
+    Finally :typoscript:`additionalGetParameters` allow you to add arbitrary GET-parameters and even override others.
+    If the plugin on your target page shows a list of records by default you will also need something like
+    :typoscript:`tx_myext_pi1.action = show` to ensure the record details are displayed.
+
+    The core automatically sets the "no_cache" and the "L" parameter. The language matches the language of
+    the current record. You may override each parameter by using the :typoscript:`additionalGetParameters` configuration
+    option.
+
+    ..  note::
+
+        Make sure not to set :typoscript:`options.saveDocView.<table name> = 0`, otherwise the save+view button
+        will not be displayed when editing records of your table.
+
+    ..  attention::
+
+        The configuration has to be defined for the page containing the records and :typoscript:`previewPageId`
+        (for example sysfolder holding the records is located outside of your root)
+
+..  index:: Copy record; Table based configuration
+..  _pagetcemaintables:
+..  _pagetcemain-table-table-name:
+
+table
+-----
+
+Processing options for tables. The table name is added, for instance `TCEMAIN.table.pages.disablePrependAtCopy = 1`
+or `TCEMAIN.table.tt_content.disablePrependAtCopy = 1`.
+
+It is also possible to set a default value for all tables, for example
+`TCEMAIN.default.disablePrependAtCopy = 1`.
+
+..  index:: Localization; Translate to message
+..  _pagetcemain-translatetomessage:
+
+translateToMessage
+------------------
+
+..  confval:: translateToMessage
+    :name: tcemain-translateToMessage
+    :type: string
+    :Default: `Translate to %s:`
+
+    Defines the string that will be prepended to some field values if you copy an element to another
+    language version. This applies to all fields where the TCA columns property
+    :ref:`l10n_mode <t3tca:columns-properties-l10n-mode>` is set to :php:`prefixLangTitle`.
+
+    The special string "%s" will be replaced with the language title.
+
+    You can globally disable the prepending of the string by setting `translateToMessage` to
+    an empty string. You can disable the message to a certain field by setting the `l10n_mode`
+    to an empty string.
+
+..  _pagetcemain-translatetomessage-example:
+
+Example: Set a German prefix for newly translated records
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: PageTSconfig
+
+    TCEMAIN {
+        translateToMessage = Bitte in "%s" übersetzen:
+    }
+
+
+..  _pagetcemain-translatetomessage-example-disable:
+
+Example: Disable the "[Translate to ...]" prefix
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: PageTSconfig
+
+    TCEMAIN {
+        translateToMessage =
+    }
diff --git a/Documentation/PageTsconfig/Templates.rst b/Documentation/PageTsconfig/Templates.rst
new file mode 100644
index 000000000..ef8e9ca04
--- /dev/null
+++ b/Documentation/PageTsconfig/Templates.rst
@@ -0,0 +1,140 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    Page TSconfig; templates
+    templates
+..  _pagetemplates:
+
+=========
+templates
+=========
+
+All Fluid templates rendered by backend controllers can be overridden with own
+templates on a per-file basis. The feature is available for basically all core
+backend modules, as well as the backend main frame templates. Exceptions are
+email templates and templates of the install tool.
+
+..  caution::
+
+    While this feature is powerful and allows overriding nearly any backend
+    template, **it should be used with care**: Fluid templates of the Core
+    extensions are not considered API. The Core development needs the freedom to
+    add, change and delete Fluid templates any time, even for bugfix releases.
+    Template overrides are similar to an XCLASS in PHP - the Core can not
+    guarantee integrity on this level across versions.
+
+..  _pagetemplates-syntax:
+
+Basic syntax
+============
+
+The various combinations are best explained by example:
+
+The linkvalidator extension (its composer name is `typo3/cms-linkvalidator`)
+comes with a backend module in the :guilabel:`Web` main section. The page tree
+is displayed for this module and linkvalidator has two main views and templates:
+
+:file:`Resources/Private/Templates/Backend/Report.html` for the
+:guilabel:`Report` view and another for the :guilabel:`Check link` view. To
+override the :file:`Backend/Report.html` file with a custom template, this
+definition can be added to the :file:`Configuration/page.tsconfig` file of an
+extension:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Left pattern (before equal sign): templates."composer-name"."something-unique"
+    # Right pattern (after equal sign): "overriding-extension-composer-name":"entry-path"
+    templates.typo3/cms-linkvalidator {
+        1643293191 = my-vendor/my-extension:Resources/Private/TemplateOverrides
+    }
+
+If the target extension, identified by its composer name
+`my-vendor/my-extension`, provides the
+:file:`Resources/Private/TemplateOverrides/Templates/Backend/Report.html` file,
+this file is used instead of the default template file from the
+linkvalidator extension.
+
+All core extensions follow the general structure for templates, layouts and
+partials file. If an extension needs to override a partial that
+is located in :file:`Resources/Private/Partials/SomeName/SomePartial.html`, and
+an override has been specified like above to
+:file:`my-vendor/my-extension:Resources/Private/TemplateOverrides`, the system
+looks for the
+:file:`Resources/Private/TemplateOverrides/Partials/SomeName/SomePartial.html`
+file. Similar is the case for layouts.
+
+..  note::
+
+    The path part of the override definition can be set the way an integrator
+    prefers, :file:`Resources/Private/TemplateOverrides` is just an idea here and
+    hopefully not a bad one, further details rely on additional needs. For
+    instance, it is probably a good idea to include the composer or extension
+    name of the source extension into the path (linkvalidator in our example) -
+    or when using overrides based on page or group IDs, to include them in the
+    path.
+
+    The sub-path of the source extension is automatically added by the
+    system when it is searching for override files. If a layout file is located
+    at :file:`Resources/Private/Layouts/ExtraLarge/Main.html` and an override
+    definition uses the :file:`Resources/Private/TemplateOverrides` path, the
+    system will look up
+    :file:`Resources/Private/TemplateOverrides/Layouts/ExtraLarge/Main.html`.
+
+Template overriding is based on the existence of files: Two files are never
+merged. An override definition either takes effect because it actually provides
+a file at the correct position with the correct file name, or it does not and
+the default is used. This can become impractical for large template files. In
+such cases it might be an option to request a split of a large template file
+into smaller partial files so an extension can override a specific partial only.
+
+..  attention::
+
+    When multiple override paths are defined and more than one of them contains
+    overrides for a specific template, the override definition with the highest
+    numerical value wins:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        templates.typo3/cms-linkvalidator {
+            23 = other-vendor/other-extension:Resources/Private/TemplateOverrides/Linkvalidator
+        }
+
+    ..  code-block:: typoscript
+        :caption: EXT:another_extension/Configuration/page.tsconfig
+
+        templates.typo3/cms-linkvalidator {
+            2300 = my-vendor/my-extension:Resources/Private/MyOverrideIsBigger
+        }
+
+..  _pagetemplates-combinations:
+
+Combinations of overrides
+=========================
+
+Due to the nature of TSconfig and its two types page TSconfig and user TSconfig,
+various combinations are possible:
+
+*   Define "global" overrides with page TSconfig in
+    :file:`Configuration/page.tsconfig` of an extension. This works for all
+    modules, regardless of whether the module renders a page tree or not.
+
+*   Define page level overrides via the :guilabel:`TSconfig` field of page
+    records. As always with page TSconfig, subpages and subtrees inherit these
+    settings from their parent pages.
+
+*   Define overrides on user or (better) group level. As always, user TSconfig can
+    override page TSconfig by prefixing any setting available as page TSconfig with
+    :typoscript:`page.` in user TSconfig. A user TSconfig template override starts
+    with :typoscript:`page.templates.` instead of :typoscript:`templates.`.
+
+..  _pagetemplates-third-party-modules:
+
+Usage in own modules
+====================
+
+Extensions with backend modules that use the simplified backend module template
+API automatically enable the general backend template override feature.
+Extension authors do not need to further prepare their extensions to enable
+template overrides by other extensions.
diff --git a/Documentation/PageTsconfig/Tx.rst b/Documentation/PageTsconfig/Tx.rst
new file mode 100644
index 000000000..03268784e
--- /dev/null
+++ b/Documentation/PageTsconfig/Tx.rst
@@ -0,0 +1,15 @@
+..  include:: /Includes.rst.txt
+..  index::
+    page TSconfig; Extensions
+    page TSconfig; tx_*
+
+..  _page-tsconfig-extension-namespace:
+
+====
+tx_*
+====
+
+The `tx_` prefix key is not used in the Core itself, and is just a
+reserved space for extensions to never collide with core options, a
+use case could be `tx_news` for the news extension. Extension developers
+should create a key like that: `tx_[extension key with no underscore]`
diff --git a/Documentation/Syntax/CodeBlocks/Index.rst b/Documentation/Syntax/CodeBlocks/Index.rst
new file mode 100644
index 000000000..a3afe2bd7
--- /dev/null
+++ b/Documentation/Syntax/CodeBlocks/Index.rst
@@ -0,0 +1,55 @@
+.. include:: /Includes.rst.txt
+.. index::
+   TypoScript; Operator "{ }"
+   TypoScript; Code blocks
+.. _typoscript-syntax-syntax-code-blocks:
+.. _typoscript-syntax-syntax-curly-brackets:
+
+===========
+Code blocks
+===========
+
+Curly braces can be used to structure identifier paths in a more efficient way:
+Without repeating upper parts of a path in each line. This allows nesting.
+
+Example without braces:
+
+.. include:: /CodeSnippets/TypoScriptSyntax/CodeBlock1.rst.txt
+
+This can be written as:
+
+.. include:: /CodeSnippets/TypoScriptSyntax/CodeBlock2.rst.txt
+
+Curly braces can be nested to further improve readability. This is also
+the same as above:
+
+.. include:: /CodeSnippets/TypoScriptSyntax/CodeBlock3.rst.txt
+
+Some rules apply during parsing:
+
+- Everything on the same line after the opening :typoscript:`{` and closing
+  :typoscript:`}` brace is considered a comment, even if the comment markers
+  :typoscript:`#`, :typoscript:`//` and :typoscript:`/* ... */` are missing.
+
+- The closing brace :typoscript:`}` must be on a single line in order to close a block.
+  The following construct is invalid, the closing brace is interpreted as part of
+  the value, so the TypoScript and TSconfig backend modules will mumble with a
+  "missing closing brace" warning:
+
+  .. include:: /CodeSnippets/TypoScriptSyntax/CodeBlockInvalidClosingBrace.rst.txt
+
+- Conditions can not be placed within blocks, they are always "global" level
+  and stop any brace nesting. The following construct is invalid, the TypoScript and
+  TSconfig backend modules will mumble with a "missing closing brace" warning:
+
+  .. include:: /CodeSnippets/TypoScriptSyntax/CodeBlockInvalidCondition.rst.txt
+
+- Nesting is per-file / per-text-snippet: It does not "swap" into included files. This
+  was the case with the old TypoScript parser. It has been a nasty side-effect, leading
+  to hard to debug problems. File includes with :typoscript:`@import`
+  within curly braces are not relative (anymore).
+
+  A construct like this is invalid, the TypoScript and TSconfig backend modules will mumble
+  with a "missing closing brace" warning:
+
+  .. include:: /CodeSnippets/TypoScriptSyntax/CodeBlockInvalidImport.rst.txt
diff --git a/Documentation/Syntax/Comments/Index.rst b/Documentation/Syntax/Comments/Index.rst
new file mode 100644
index 000000000..657be0c56
--- /dev/null
+++ b/Documentation/Syntax/Comments/Index.rst
@@ -0,0 +1,37 @@
+.. include:: /Includes.rst.txt
+.. index::
+   TypoScript; Comments
+   TypoScript; Operator "//"
+   TypoScript; Operator "#"
+   TypoScript; Single line comments
+   TypoScript; Operator "/*"
+   TypoScript; Comment blocks
+.. _typoscript-syntax-syntax-comments:
+.. _typoscript-syntax-syntax-comment-blocks:
+
+========
+Comments
+========
+
+TypoScript supports single line comments as well as multiline comment blocks.
+
+.. note::
+    ..  versionchanged:: 12.0
+
+    Comment handling has been relaxed significantly with the rewritten TypoScript
+    parser in TYPO3 v12. The parser is much less picky detecting comments, they
+    can be placed almost everywhere since v12, :typoscript:`*/` no longer needs
+    to be on a single line, and comments are auto-closed at the end of a single
+    text snippets.
+
+:typoscript:`//` and :typoscript:`#` indicate a comment. Everything until the end
+of the line will be ignored by the parser. :typoscript:`/*` indicates a multiline
+comment start, :typoscript:`*/` stops it.
+
+When using :typoscript:`//`, :typoscript:`#` and :typoscript:`/*` after an assignment
+:typoscript:`=`, this is *not* considered a comment, but part of the value! Same is
+true for multiline assignments.
+
+Some examples:
+
+.. include:: /CodeSnippets/TypoScriptSyntax/Comments.rst.txt
diff --git a/Documentation/Syntax/Conditions/Index.rst b/Documentation/Syntax/Conditions/Index.rst
new file mode 100644
index 000000000..6f6fa9d96
--- /dev/null
+++ b/Documentation/Syntax/Conditions/Index.rst
@@ -0,0 +1,196 @@
+:navigation-title: Conditions
+
+..  include:: /Includes.rst.txt
+..  index::
+    TypoScript; Operator "["
+    TypoScript; Conditions
+    TypoScript; [GLOBAL] condition
+    TypoScript; Symfony expression language
+..  _typoscript-syntax-conditions:
+..  _typoscript-syntax-implementing-custom-conditions:
+..  _typoscript-syntax-conditions-examples:
+
+===================================
+Conditions in the TypoScript syntax
+===================================
+
+TypoScript can contain :code:`if` and :code:`if / else` control structures. They
+are called `conditions`, their "body" is only considered if a condition criteria
+evaluates to true. Examples of condition criteria are:
+
+-   Is a user logged in?
+-   Is it Monday?
+-   Is the page called in a certain language?
+
+Conditions are a TypoScript syntax construct. They are thus available in both
+frontend TypoScript and backend TSconfig. However, condition criteria are based
+on prepared variables and functions, and those are different in frontend
+TypoScript and backend TSconfig. For example, the :typoscript:`frontend` variable does
+not exist in TSconfig, it is (obviously) impossible to have a backend TSconfig
+condition that checks for a logged in frontend user.
+
+..  contents:: Table of contents
+
+..  _typoscript-syntax-conditions-usage:
+
+Basic usage of TypoScript conditions
+====================================
+
+..  literalinclude:: _codesnippets/_basic.typoscript
+    :captions: packages/my_site_package/Configuration/TypoScript/setup.typoscript
+
+..  _typoscript-syntax-conditions-syntax:
+
+Syntax and rules
+================
+
+These general rules apply:
+
+..  _typoscript-syntax-conditions-confinements:
+..  _typoscript-syntax-conditions-braces:
+..  _typoscript-syntax-syntax-square-brackets:
+..  _typoscript-syntax-syntax-conditions:
+
+General condition syntax
+------------------------
+
+Conditions are encapsulated in :typoscript:`[` and :typoscript:`]`
+
+..  _typoscript-syntax-the-global-condition:
+..  _typoscript-syntax-global-condition:
+..  _typoscript-syntax-else-condition:
+..  _typoscript-syntax-end-condition:
+
+`[GLOBAL]`, `[ELSE]` and `[END]`
+--------------------------------
+
+:typoscript:`[ELSE]` negates a previous condition criteria and can contain
+a new body until :typoscript:`[END]` or :typoscript:`[GLOBAL]`. :typoscript:`[ELSE]`
+is considered if the condition criteria did *not* evaluate to true.
+
+:typoscript:`[END]` and :typoscript:`[GLOBAL]` stop a given condition scope.
+This is similar to a closing curly brace :code:`}` in programming languages like PHP.
+
+..  literalinclude:: _codesnippets/_condition.typoscript
+    :captions: packages/my_site_package/Configuration/TypoScript/setup.typoscript
+
+Conditions automatically stop at the end of a text snippet (file or record), even
+without :typoscript:`[END]` or :typoscript:`[GLOBAL]`. Another snippet on the same
+level is in "global" scope automatically. The backend TypoScript and
+TSconfig modules may mumble about a not properly closed condition, though.
+
+..  versionchanged:: 12.0
+
+    :typoscript:`[END]` and :typoscript:`[GLOBAL]` behave exactly the same. Both
+    are kept for historical reasons (for now).
+
+    Conditions automatically stop at the end of a text snippet (file or record).
+
+..  _typoscript-syntax-end-condition-and:
+..  _typoscript-syntax-end-condition-or:
+
+Combining multiple TypoScript conditions with `and` or `or`
+-----------------------------------------------------------
+
+Multiple condition criteria can be combined using :typoscript:`or` or :typoscript:`||`,
+as well as :typoscript:`and` or :typoscript:`&&`
+
+..  literalinclude:: _codesnippets/_andor.typoscript
+    :captions: packages/my_site_package/Configuration/TypoScript/setup.typoscript
+
+Single criteria can be negated using :typoscript:`!`
+
+..  _typoscript-syntax-end-condition-constants:
+
+TypoScript constant usage in Conditions
+---------------------------------------
+
+Conditions can use constants. They are available in frontend TypoScript "setup" and
+in TSconfig from "site settings". A simple example if this constant
+:typoscript:`myPageUid = 42` is set:
+
+..  code-block:: typoscript
+
+    [traverse(page, "uid") == {$myPageUid}]
+        page.10.value = Page uid is 42
+    [end]
+
+..  note::
+
+    Using the `Null coalescing operator ?? <https://docs.typo3.org/permalink/t3tsref:typoscript-syntax-syntax-null-coalescing>`_
+    with constants used within conditions is not possible.
+
+..  _typoscript-syntax-end-condition-nesting:
+
+Nesting conditions via TypoScript imports
+-----------------------------------------
+
+Conditions can *not* be nested within code blocks.
+
+..  code-block:: typoscript
+
+    # Invalid: Conditions must not be used within code blocks
+    # someIdentifier {
+    #    someProperty = foo
+    #    [frontend.user.isloggedIn]
+    #       someProperty = bar
+    #    [GLOBAL]
+    # }
+
+..  versionchanged:: 12.0
+
+Conditions *can* be nested into each other, if they are located in
+different snippets (files or records), see example below. They can *not* be nested
+within the same code snippet.
+
+A second condition that is *not* :typoscript:`[ELSE]`, :typoscript:`[END]`
+or :typoscript:`[GLOBAL]` *stops* a previous condition and starts a new one.
+This is the main reason conditions can *not* be nested within one text snippet.
+
+:typoscript:`@import` *can* be nested
+inside conditions. This allows conditional includes and is a new feature of the
+TYPO3 v12 parser.
+
+..  _typoscript-syntax-end-condition-null-save:
+
+Using the null-safe operator in conditions
+------------------------------------------
+
+..  versionadded:: 12.1
+
+Using the null-safe operator is possible when accessing properties on objects
+which might not be available in some context, for example `TSFE` in the
+backend:
+
+..  code-block:: typoscript
+
+    # Previously
+    # [getTSFE() && getTSFE().id == 123]
+
+    # Now
+    [getTSFE()?.id == 123]
+
+..  _typoscript-syntax-syntax-value:
+
+Allowed criteria in TypoScript conditions
+=========================================
+
+For a reference of allowed condition criteria, please refer to the according
+chapter in the :ref:`frontend TypoScript Reference <conditions>` and
+the :ref:`backend TSconfig Reference <tsconfig-conditions>`. These references
+come with examples for single condition criteria as well.
+
+The TSconfig and TypoScript backend modules show lists of existing conditions
+and allow simulating criteria verdicts to analyze their impact on the
+resulting TypoScript tree.
+
+..  _typoscript-syntax-conditions-expression-language:
+
+TypoScript conditions and the Symfony expression language
+=========================================================
+
+Condition criteria are based on
+the `Symfony expression language <https://symfony.com/doc/current/components/expression_language/syntax.html>`__.
+The Core allows extending the Symfony expression language with own variables and
+functions, see :ref:`symfony expression language API <t3coreapi:sel-within-typoscript-conditions>`
+for more details.
diff --git a/Documentation/Syntax/Conditions/_codesnippets/_andor.typoscript b/Documentation/Syntax/Conditions/_codesnippets/_andor.typoscript
new file mode 100644
index 000000000..b1152e02a
--- /dev/null
+++ b/Documentation/Syntax/Conditions/_codesnippets/_andor.typoscript
@@ -0,0 +1,7 @@
+[frontend.user.isLoggedIn || ip('127.0.0.1')]
+  page.20 = TEXT
+  page.20 {
+    value = A frontend user is logged in, or the browser IP is 127.0.0.1
+    stdWrap.case = upper
+  }
+[GLOBAL]
diff --git a/Documentation/Syntax/Conditions/_codesnippets/_basic.typoscript b/Documentation/Syntax/Conditions/_codesnippets/_basic.typoscript
new file mode 100644
index 000000000..656dee48c
--- /dev/null
+++ b/Documentation/Syntax/Conditions/_codesnippets/_basic.typoscript
@@ -0,0 +1,10 @@
+page = PAGE
+page.10 = TEXT
+page.10.value = HELLO WORLD!
+
+[frontend.user.isLoggedIn]
+  page.20 = TEXT
+  page.20 {
+    value = A frontend user is logged in.
+  }
+[GLOBAL]
diff --git a/Documentation/Syntax/Conditions/_codesnippets/_condition.typoscript b/Documentation/Syntax/Conditions/_codesnippets/_condition.typoscript
new file mode 100644
index 000000000..6ad4082d8
--- /dev/null
+++ b/Documentation/Syntax/Conditions/_codesnippets/_condition.typoscript
@@ -0,0 +1,5 @@
+[date("j") == 9]
+  page.10.value = It is the 9th day of the month!
+[ELSE]
+  page.10.value = It is NOT the 9th day of the month!
+[END]
diff --git a/Documentation/Syntax/Conditions/_codesnippets/_not.typoscript b/Documentation/Syntax/Conditions/_codesnippets/_not.typoscript
new file mode 100644
index 000000000..e8ab4525e
--- /dev/null
+++ b/Documentation/Syntax/Conditions/_codesnippets/_not.typoscript
@@ -0,0 +1,14 @@
+page = PAGE
+page.10 = TEXT
+page.10.value = You are logged in
+
+# This is hard to read
+[frontend.user.isLoggedIn]
+[ELSE]
+  page.10.value = You are *not* logged in
+[END]
+
+# This is faster to read
+[!frontend.user.isLoggedIn]
+  page.10.value = You are *not* logged in
+[END]
diff --git a/Documentation/Syntax/FileImports/Index.rst b/Documentation/Syntax/FileImports/Index.rst
new file mode 100644
index 000000000..0bd7c98a8
--- /dev/null
+++ b/Documentation/Syntax/FileImports/Index.rst
@@ -0,0 +1,234 @@
+.. include:: /Includes.rst.txt
+.. index:: TypoScript; Includes
+.. _typoscript-syntax-includes:
+
+============
+File imports
+============
+
+..  deprecated:: 13.4
+    The old school :typoscript:`<INCLUDE_TYPOSCRIPT:` syntax has been deprecated
+    and will be removed with TYPO3 v14.0. See :ref:`t3tsref/13:typoscript-syntax-includes-migration`.
+
+To structure and reuse single TypoScript snippets and not stuffing everything
+into one file or record, the syntax allows loading TypoScript content from sub files.
+
+The keyword :typoscript:`@import` is a syntax construct and
+thus available in both frontend TypoScript and backend TSconfig.
+
+:typoscript:`@import` allows including additional files using wildcards on the file
+level. Wildcards in paths are not allowed.
+
+The TypoScript parser allows to place :typoscript:`@import` within condition
+bodies, which allows conditional imports with :typoscript:`@import`.
+
+:typoscript:`@import` is not allowed to be placed within code blocks
+and breaks any curly braces level, resetting current scope
+to top level.
+
+.. _typoscript-syntax-import:
+
+@import
+=======
+
+This keyword allows including files inspired by a syntax similar to :code:`SASS`.
+It is restricted, but still allows wildcards on file level. Single files *must* end
+with :file:`.typoscript` if included in frontend Typoscript. In backend TSconfig,
+single files *should* end with :file:`.tsconfig`, but *may* end with
+:typoscript:`.typoscript` as well (for now).
+
+The include logic is a bit more restrictive with TYPO3 v12, previous versions
+have been slightly more relaxed in this regard. See
+:doc:`this changelog <ext_core:Changelog/12.0/Breaking-97816-TypoScriptSyntaxChanges>`
+for more details.
+
+The following rules apply:
+
+* Multiple files are imported in alphabetical order.
+  If a special loading order is desired it is common to prefix the filenames with
+  numbers that increase for files that shall be loaded later.
+
+* Recursion is allowed: Imported files can have :typoscript:`@import` statements.
+
+* The :typoscript:`@import` statement does not take a condition clause as the old
+  :typoscript:`<INCLUDE_TYPOSCRIPT condition="">` statement did. That kind of condition
+  should be considered a conceptual mistake. It should not be used.
+
+* .. versionchanged:: 12.0
+
+  It is allowed to put :typoscript:`@import` within a condition. This example imports
+  the additional file only if a frontend user is logged in:
+
+  .. code-block:: typoscript
+
+      [frontend.user.isLoggedIn]
+          @import './userIsLoggedIn.typoscript'
+      [END]
+
+* Both the old syntax :typoscript:`<INCLUDE_TYPOSCRIPT>` and the new one :typoscript:`@import`
+  can be used at the same time.
+
+* Directory imports are not recursive, meaning that a directory import does
+  not automatically travel down its subdirectories.
+
+* Quoting the filename is necessary with the new syntax. Either double quotes
+  (") or single quotes (') can be used.
+
+* Wildcards :typoscript:`*` are only allowed on file level, not on directory level.
+  Only a single wildcard character is allowed.
+
+* Includes relative to the current file location are allowed using :typoscript:`./`
+  as prefix.
+
+* Includes must start with :typoscript:`EXT:` if not relative. Loading files
+  outside of extensions is not possible.
+
+* Directory traversal using :typoscript:`../` is not allowed.
+
+Some examples:
+
+.. code-block:: typoscript
+
+    # Import a single file
+    @import 'EXT:my_extension/Configuration/TypoScript/randomfile.typoscript'
+
+    # Import multiple files in a single directory, sorted by file name
+    @import 'EXT:my_extension/Configuration/TypoScript/*.typoscript'
+
+    # It's possible to omit the file ending. For frontend TypoScript, ".typoscript" is
+    # appended automatically, backend TSconfig allows both ".typoscript" and ".tsconfig"
+    @import 'EXT:my_extension/Configuration/TypoScript/'
+
+    # Import files starting with "foo", ending with ".typoscript" (frontend)
+    @import 'EXT:my_extension/Configuration/TypoScript/foo*'
+
+    # Import files ending with ".setup.typoscript"
+    @import 'EXT:my_extension/Configuration/TypoScript/*.setup.typoscript'
+
+    # Import "bar.typoscript" relative to current file
+    @import './bar.typoscript'
+
+    # Import all ".setup.typoscript" files in sub directory relative to current file
+    @import './subDirectory/*.setup.typoscript'
+
+
+.. _typoscript-syntax-includes-alternatives:
+
+Alternatives to using file imports
+==================================
+
+The following features can make file inclusion unnecessary:
+
+*   :ref:`Automatic global inclusion of user TSconfig of extensions <usersettingdefaultusertsconfig>`
+*   :ref:`Automatic global inclusion of page TSconfig of extensions <pagesettingdefaultpagetsconfig>`
+*   :ref:`Automatic page TSconfig on site level <include-static-page-tsconfig-per-site>`
+*   :ref:`TypoScript provider for sites and sets <t3coreapi:site-sets-typoscript>`
+    automatically loads TypoScript per site when the site set is included in the
+    site configuration.
+
+
+.. index:: TypoScript; Includes by conditions
+.. _typoscript-syntax-includes-conditions:
+.. _typoscript-syntax-includes-best-practices:
+.. _typoscript-syntax-includes-migration:
+
+Migration from `<INCLUDE_TYPOSCRIPT:` to `@import`
+==================================================
+
+..  important::
+    :typoscript:`@import` does not support recursively including all `.typoscript`
+    files from sub directories. You need to list each directory with its own
+    :typoscript:`@import` statement.
+    See :ref:`typoscript-syntax-includes-migration-recursive`.
+
+..  important::
+    :typoscript:`@import` supports the file endings `.typoscript` and `.tsconfig`
+    only. All other file names will be ignored. Rename all TypoScript files to
+    these endings.
+
+Most usages of :typoscript:`<INCLUDE_TYPOSCRIPT:` can be turned into :typoscript:`@import`
+easily. A few examples:
+
+..  code-block:: diff
+
+    -<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_extension/Configuration/TypoScript/myMenu.typoscript">
+    +@import 'EXT:my_extension/Configuration/TypoScript/myMenu.typoscript'
+
+     # Including .typoscript files in a single (non recursive!) directory
+    -<INCLUDE_TYPOSCRIPT: source="DIR:EXT:my_extension/Configuration/TypoScript/" extensions="typoscript">
+    +@import 'EXT:my_extension/Configuration/TypoScript/*.typoscript'
+
+    # Including .typoscript and .ts files in a single (non recursive!) directory
+    -<INCLUDE_TYPOSCRIPT: source="DIR:EXT:my_extension/Configuration/TypoScript/" extensions="typoscript,ts">
+    +@import 'EXT:my_extension/Configuration/TypoScript/*.typoscript'
+     # Rename all files ending from .ts to .typoscript
+
+     # Including a file conditionally
+    -<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_extension/Configuration/TypoScript/user.typoscript" condition="[frontend.user.isLoggedIn]">
+    +[frontend.user.isLoggedIn]
+    +    @import 'EXT:my_extension/Configuration/TypoScript/user.typoscript'
+    +[END]
+
+There are a few more use cases that cannot be transitioned so easily since
+:typoscript:`@import` is a bit more restrictive.
+
+As one restriction :typoscript:`@import` cannot include files from arbitrary directories
+like :file:`fileadmin/`, but only from extensions by using the :typoscript:`EXT:`
+prefix. Instances that use :typoscript:`<INCLUDE_TYPOSCRIPT:` with :typoscript:`source="FILE:./someDirectory/..."`
+should move these TypoScript files into a project or site extension. Such instances are also encouraged to
+look into the TYPO3 v13 :ref:`Site sets <t3coreapi:site-sets>` feature and eventually transition towards it along the way.
+
+:typoscript:`@import` allows to import files with the file ending `.typoscript`
+and `.tsconfig`. If you used any of the outdated file endings like `.ts` or
+`.txt` rename those files before switching to the :typoscript:`@import` syntax.
+
+.. _typoscript-syntax-includes-migration-recursive:
+
+Migrating recursive TypoScript file inclusion
+---------------------------------------------
+
+If you have such a tree of TypoScript files:
+
+..  directory-tree::
+    :show-file-icons: true
+
+    *   EXT:my_sitepackage/Configuration/TypoScript/
+
+        *   Setup
+
+            *   Extensions
+
+                *   Solr
+
+                    *   indexing.typoscript
+                    *   searchPlugin.typoscript
+
+                *   news.typoscript
+                *   tt_address.typoscript
+
+            *   ContentElements
+
+                *   file1.typoscript
+                *   file2.typoscript
+                *   file3.typoscript
+
+            *   myProject.typoscript
+            *   someSettings.typoscript
+
+        *   setup.typoscript
+
+Each directory **must** be listed separately for inclusion when migrating to
+the `@import` statement:
+
+..  code-block:: diff
+    :caption: EXT:my_sitepackage/Configuration/TypoScript/setup.typoscript (Difference)
+
+    -<INCLUDE_TYPOSCRIPT: source="FILE:EXT:my_sitepackage/Configuration/TypoScript/Setup">
+
+    +@import 'EXT:my_sitepackage/Configuration/TypoScript/Setup'
+    +@import 'EXT:my_sitepackage/Configuration/TypoScript/Extensions'
+    +@import 'EXT:my_sitepackage/Configuration/TypoScript/Extensions/Solr'
+    +@import 'EXT:my_sitepackage/Configuration/TypoScript/ContentElements'
+
+The need for recursive includes may also be mitigated by restructuring
+TypoScript based functionality using :ref:`Site sets <t3coreapi:site-sets>`.
diff --git a/Documentation/Syntax/Identifiers/Index.rst b/Documentation/Syntax/Identifiers/Index.rst
new file mode 100644
index 000000000..765bac7d3
--- /dev/null
+++ b/Documentation/Syntax/Identifiers/Index.rst
@@ -0,0 +1,33 @@
+.. include:: /Includes.rst.txt
+.. index::
+    TypoScript; Identifier
+.. _typoscript-syntax-basics:
+.. _typoscript-syntax-syntax-object-path:
+
+===========
+Identifiers
+===========
+
+TypoScript is line based. Each line normally contains three parts:
+
+.. code-block:: text
+
+   [Identifier] [Operator] [Value]
+
+
+In this example we have the identifier :typoscript:`myIdentifier` with the sub identifier
+:typoscript:`mySubIdentifier`, the assignment operator :typoscript:`=` and the value :typoscript:`myValue`.
+
+.. include:: /CodeSnippets/TypoScriptSyntax/Identifiers1.rst.txt
+
+The identifier path (in above example :typoscript:`myIdentifier.mySubIdentifier`) is
+a dotted path of single identifiers, and the first block of non-whitespace characters
+on a line until an operator, a curly open brace, or a whitespace. The dot (:typoscript:`.`)
+is used to separate single identifiers, creating a hierarchy.
+
+When a dot is part of a single identifier name (this may, for instance, sometimes happen when configuring
+FlexForm details), it must be quoted with a backlash. The example below results in the
+identifier :typoscript:`myIdentifier` with the sub identifier :typoscript:`my.identifier.with.dots`
+having the assigned value :typoscript:`myValue`:
+
+.. include:: /CodeSnippets/TypoScriptSyntax/Identifiers2.rst.txt
diff --git a/Documentation/Syntax/Index.rst b/Documentation/Syntax/Index.rst
new file mode 100644
index 000000000..7d408571c
--- /dev/null
+++ b/Documentation/Syntax/Index.rst
@@ -0,0 +1,26 @@
+:navigation-title: Syntax
+
+..  include:: /Includes.rst.txt
+..  index:: TypoScript; Syntax
+..  _typoscript-syntax:
+..  _syntax:
+
+=================
+TypoScript syntax
+=================
+
+This chapter is about the syntax of TypoScript: The rules you must obey in order to
+store configuration in this structure.
+
+..  toctree::
+    :titlesonly:
+    :glob:
+
+    Identifiers/Index
+    CodeBlocks/Index
+    Operators/Index
+    Comments/Index
+    Conditions/Index
+    FileImports/Index
+    StringFormats/Index
+    TSconfig/Index
diff --git a/Documentation/Syntax/Operators/Index.rst b/Documentation/Syntax/Operators/Index.rst
new file mode 100644
index 000000000..27533e877
--- /dev/null
+++ b/Documentation/Syntax/Operators/Index.rst
@@ -0,0 +1,356 @@
+:navigation-title: Operators
+
+..  include:: /Includes.rst.txt
+..  index:: TypoScript; Operator
+..  _typoscript-syntax-syntax-operator:
+
+==================================
+Operators in the TypoScript syntax
+==================================
+
+TypoScript syntax comes with a couple of operators to assign
+values, copy from other identifier paths, and to manipulate values.
+Let's have a closer look at them.
+
+..  contents:: Operators in TypoScript
+
+..  index::
+    TypoScript; Operator "="
+    TypoScript; Value assignment
+..  _typoscript-syntax-syntax-equal-operator:
+..  _typoscript-syntax-syntax-value-assignment:
+
+Value assignment with "="
+=========================
+
+This most common operator assigns a single line value to an identifier path.
+Everything after the :typoscript:`=` character until the end of the line is
+considered to be the value. The value is trimmed, leading and trailing whitespaces
+are removed.
+
+Values are parsed for constant references. With a value assignment like
+:typoscript:`foo = someText {$someConstant} furtherText`, the parser will
+look up the constant reference :typoscript:`{$someConstant}` and tries to
+substitute it with a defined constant value. If such a constant does not
+exist, it falls back to the string literal including the :typoscript:`{$` and
+:typoscript:`}` characters.
+
+A couple of examples:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorAssignment.rst.txt
+
+..  caution::
+    The TypoScript parser looks for valid operators first, then parses things
+    behind it. Consider this example:
+
+    ..  code-block:: typoscript
+
+        lib.nav.wrap =<ul id="nav">|</ul>
+
+    This is ambiguous: The above :typoscript:`=<ul` could be interpreted both as
+    an assignment :typoscript:`=` of the value :typoscript:`<ul`, or as a
+    :ref:`reference <typoscript-syntax-syntax-object-referencing>`
+    :typoscript:`=<` to the identifier :typoscript:`ul`.
+
+    Before TYPO3 v12.0 the TypoScript parser interpreted this as an assignment,
+    since TYPO3 v12.0 it is treated as a reference.
+
+    The above example aims for an assignment, though, which can be achieved by
+    adding a whitespace between :typoscript:`=` and :typoscript:`<`:
+
+    ..  code-block:: typoscript
+
+        lib.nav.wrap = <ul id="nav">|</ul>
+
+..  index::
+    TypoScript; Operator "( )"
+    TypoScript; Multi-line values
+..  _typoscript-syntax-syntax-round-brackets:
+..  _typoscript-syntax-syntax-multiline-values:
+
+Multiline assignment with "(" and ")"
+=====================================
+
+Opening and closing parenthesis are used to assign multi-line values. This allows
+defining values that span several lines and thus include line breaks.
+
+The end parenthesis :typoscript:`)` is important: If it is not found, the parser
+considers all following lines until the end of the TypoScript text snipped to be part
+of the value. This includes comments, :typoscript:`[GLOBAL]` conditions and :typoscript:`@import`
+file includes: They are not a syntax construct and are considered part of the value assignment.
+
+However, the value is parsed for constants (text looking like :typoscript:`{$myIdentifier.mySubIdentifier}`:
+The parser will try to substitute them to their assigned constant value. The "TypoScript" and
+"Page TSconfig" backend modules may show a warning if a reference to a constant can't be resolved.
+If a constant reference can't be resolved, the value falls back to its string literal.
+Since multi-line values are sometimes used to output JavaScript, and JavaScript also uses a
+syntax construct like :typoscript:`{$...}`, this may lead to false positive warnings in those
+backend modules.
+
+A couple of examples:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorMultiLine.rst.txt
+
+
+..  index::
+    TypoScript; Operator ">"
+    TypoScript; Object unsetting
+..  _typoscript-syntax-syntax-bigger-than-operator:
+..  _typoscript-syntax-syntax-unsetting-operator:
+
+Unset with ">"
+==============
+
+This can be used to unset a previously defined identifier path value, and
+all of its sub identifiers:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorUnset.rst.txt
+
+
+..  index::
+    TypoScript; Operator "<"
+    TypoScript; Object copying
+..  _typoscript-syntax-syntax-smaller-than-operator:
+..  _typoscript-syntax-syntax-object-copying:
+
+Copy with "<"
+=============
+
+The :typoscript:`<` character is used to copy one identifier path to another.
+The whole current identifier state is copied: both value and sub identifiers.
+It overrides any old sub identifiers and values at that position.
+
+The copy operator is useful to follow the
+`DRY - Don't repeat yourself <https://en.wikipedia.org/wiki/Don%27t_repeat_yourself>`__
+principle. It allows maintaining a configuration set at a central place, and copies are
+used at further places when needed again.
+
+The result of the below TypoScript is two independent sets which are duplicates.
+They are not references to each other but actual copies:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorCopy1.rst.txt
+
+The copy operator is allowed within code blocks as well:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorCopy2.rst.txt
+
+In the above example, the copied identifier path is referred to with its full path
+:typoscript:`myIdentifier.10`. When copying on the same level, it is allowed
+to use a relative path, indicated by a prepended dot. The following produces
+the same result as above:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorCopy3.rst.txt
+
+Using the copy operator creates a copy of the source path at exactly this point
+in the parsing process. Changing the source afterwards does not change the
+target, and changing the target afterwards does not change the source:
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorCopy4.rst.txt
+
+
+..  index::
+    TypoScript; Operator "=<"
+    TypoScript; References
+..  _typoscript-syntax-syntax-equal-smaller-than-operator:
+..  _typoscript-syntax-syntax-object-referencing:
+
+References with "=<"
+====================
+
+..  note::
+
+    The reference operator :typoscript:`=<` is not a general syntax construct.
+    Even though the TypoScript and TSconfig backend modules show usages of
+    the operator, they are only resolved in frontend TypoScript for the
+    special :typoscript:`tt_content` path: You can use :typoscript:`=<`
+    in frontend TypoScript for example with
+    :typoscript:`tt_content.text =< lib.contentElement`, and you are encouraged
+    to do so in this special case for performance reasons, but this operator
+    does not work anywhere else.
+
+In the context of frontend TypoScript, it is possible to create
+references from one identifier path to another within the :typoscript:`tt_content`
+path. References mean that multiple positions can copy the same source
+identifier path without making an actual copy. This allows changes to the
+source identifier afterwards, which changes the targets as well. References can
+be convenient for this special case, but should be used with caution.
+
+..  include:: /CodeSnippets/TypoScriptSyntax/OperatorReference.rst.txt
+
+..  index::
+    TypoScript; Operator ":="
+    TypoScript; Value modifications
+..  _typoscript-syntax-syntax-colon-equal-operator:
+..  _typoscript-syntax-syntax-value-modification:
+
+Value modifications with ":="
+=============================
+
+This operator assigns a value to an identifier path by calling a
+predefined function which modifies the existing value in different ways.
+This is very useful when a value should be modified without completely
+redefining it again.
+
+A modifier is referenced by its modifier name, plus arguments in
+parenthesis. These predefined functions are available:
+
+`prependString()`
+    Add a string to the beginning of the existing value.
+
+    ..  code-block:: typoscript
+
+        foo = cd
+        foo := prependString(ab)
+        # foo is "abcd"
+
+`appendString()`
+    Add a string to the end of the existing value.
+
+    ..  code-block:: typoscript
+
+        foo = ab
+        foo := appendString(cd)
+        # foo is "abcd"
+
+`removeString()`
+    Remove a string from the existing value.
+
+    ..  code-block:: typoscript
+
+        foo = foobarfoo
+        foo := removeString(foo)
+        # foo is "bar"
+
+`replaceString()`
+    Replace old with new value. Separate these using :code:`|`.
+
+    ..  code-block:: typoscript
+
+        foo = abcd
+        foo := replaceString(bc|123)
+        # foo is "a123d"
+
+`addToList()`
+    Add values to the end of a list of existing values. There is no check for
+    duplicate values, and the list is not sorted in any way.
+
+    ..  code-block:: typoscript
+
+        foo = 123,456
+        foo := addToList(789)
+        # foo is "123,456,789"
+
+        foo =
+        foo := addToList(123)
+        # foo is "123" (no leading comma added on empty existing value)
+
+`removeFromList()`
+    Remove a comma-separated list of values from an existing comma-separated
+    list of values. Empty values are removed as well.
+
+    ..  code-block:: typoscript
+
+        foo = foo,123,bar,456,foo,,789
+        foo:= removeFromList(foo,bar)
+        # foo is "123,456,789"
+
+`uniqueList()`
+    Remove duplicate entries from a comma-separated list of values.
+
+    ..  code-block:: typoscript
+
+        foo = 123,456,abc,456,456
+        foo := uniqueList()
+        # foo is "123,456,abc"
+
+`reverseList()`
+    Reverses the order of entries in a comma-separated list of values.
+
+    ..  code-block:: typoscript
+
+        foo = 123,456,abc,456
+        foo := reverseList()
+        # foo is "456,abc,456,123"
+
+`sortList()`
+    Sorts the entries in a comma-separated list of values. There are optional
+    sorting parameters, multiple can be separated using :typoscript:`,`:
+
+    ascending (default)
+        Sort the items in ascending order: First numbers from small to big, then
+        letters in alphabetical order.
+
+    descending
+        Sort the items in descending order: First letters in descending order, then
+        numbers from big to small.
+
+    numeric
+        Apply numeric sorting: Numbers from small to big, letters sorted after "0".
+
+    ..  code-block:: typoscript
+
+        foo = 10,100,0,20,abc
+        foo := sortList()
+        # foo is "0,10,20,100,abc"
+
+        foo = 10,0,100,-20
+        foo := sortList(numeric)
+        # foo is "-20,0,10,100"
+
+        foo = 10,100,0,20,-20
+        foo := sortList(numeric,descending)
+        # foo is "100,20,10,0,-20"
+
+`getEnv()`
+    Access a $_ENV value. Resolves to empty value if not set.
+
+    ..  code-block:: typoscript
+
+        # $_ENV['foo'] = 'fooValue'
+        foo := getEnv(foo);
+        # foo is "fooValue"
+
+`myCustomFunction()`
+    ..  versionchanged:: 12.0
+
+    The PSR-14 event :php:`\TYPO3\CMS\Core\TypoScript\AST\Event\EvaluateModifierFunctionEvent`
+    is available to define custom TypoScript functions. The event replaces the hook
+    :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/class.t3lib_tsparser.php']['preParseFunc']`.
+
+    The section :ref:`EvaluateModifierFunctionEvent <t3coreapi:EvaluateModifierFunctionEvent>`
+    provides an example and the API.
+
+
+..  _typoscript-syntax-syntax-null-coalescing:
+
+Null coalescing operator `??` for TypoScript constants
+======================================================
+
+..  versionadded:: 13.1
+
+TypoScript constants expressions support a null coalescing
+operator (`??`) as a way for providing a migration path from a legacy constant
+name to a newer name, while providing full backwards compatibility for the
+legacy constant name, if still defined.
+
+Example that evaluates to `$config.oldThing` if set, otherwise the newer setting
+`$myext.thing` would be used:
+
+..  code-block:: typoscript
+    :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
+
+    plugin.tx_myext.settings.example = {$config.oldThing ?? $myext.thing}
+
+The null coalescing operator cannot be used in conditions. Use
+`or <https://docs.typo3.org/permalink/t3tsref:typoscript-syntax-end-condition-or>`_
+instead:
+
+..  code-block:: typoscript
+    :caption: EXT:my_extension/Configuration/TypoScript/setup.typoscript
+
+    # Wrong
+    # [{$config.oldThing ?? $myext.thing} == 5]
+
+    # Right
+    [{$config.oldThing}  == 5 or {$myext.thing} == 5]
+
diff --git a/Documentation/Syntax/StringFormats/Index.rst b/Documentation/Syntax/StringFormats/Index.rst
new file mode 100644
index 000000000..7e0d3af9b
--- /dev/null
+++ b/Documentation/Syntax/StringFormats/Index.rst
@@ -0,0 +1,175 @@
+:navigation-title: String formats
+..  include:: /Includes.rst.txt
+..  _data-types:
+..  _data-types-reference:
+..  _string-formats:
+
+=========================
+TypoScript string formats
+=========================
+
+The values assigned to properties in TypoScript are internally handled as
+strings.
+
+Some properties expect a certain format of string. These formats are described
+in this chapter.
+
+Enforcing these string formats is up to the implementation of the property using
+them. They are therefore no real constructs of the TypoScript syntax.
+
+..  contents::
+    :local:
+
+..  index:: Simple data types; boolean
+..  _data-type-boolean:
+
+boolean
+=======
+
+..  confval:: boolean
+    :name: data-type-boolean
+
+    Possible values for boolean variables are `1` and `0`
+    meaning TRUE and FALSE.
+
+    Everything else is `evaluated to one of these values by PHP`__:
+    Non-empty strings (except `0` [zero]) are treated as TRUE,
+    empty strings are evaluated to FALSE.
+
+    __ https://www.php.net/manual/en/language.types.boolean.php
+
+    ..  rubric:: Examples
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        dummy.enable = 0   # false, preferred notation
+        dummy.enable = 1   # true,  preferred notation
+        dummy.enable =     # false, because the value is empty
+
+..  index:: Simple data types; date-conf
+..  _data-type-date-conf:
+
+date-conf
+=========
+
+..  confval:: date-conf
+    :name: data-type-date-conf
+
+    Used to format a date, see PHP function :php:`date()`. See the
+    documentation of `allowed date time formats in
+    PHP <https://www.php.net/manual/en/datetime.format.php>`__.
+
+    ..  rubric:: Example
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        page.10.date-conf = d-m-y
+
+
+..  index:: Simple data types; function name
+..  _data-type-function-name:
+
+function name
+=============
+
+..  confval:: function name
+    :name: data-type-function-name
+
+    Indicates a function or method in a class to call. See more information at
+    the :ref:`USER cObject <cobj-user>`.
+
+    ..  rubric:: Examples
+
+    Method name in a namespaced class:
+
+    ..  code-block:: typoscript
+
+        lib.someThing = USER_INT
+        lib.someThing.userFunc = MyVendor\MyExtension\SomeNamespace\SomeClass->someFunction
+
+    ..  literalinclude:: _FunctionName.php
+        :language: php
+        :caption: EXT:my_extension/Classes/SomeNamespace/SomeClass.php
+
+..  index:: Simple data types; integer
+..  _data-type-positive-integer:
+..  _data-type-integer:
+
+integer
+=======
+
+..  confval:: integer
+    :name: data-type-integer
+
+    ..  rubric:: Examples
+
+    42, -8, -9, 0
+
+    Positive integers expect to be greater or equal zero.
+
+
+..  index:: Simple data types; path
+..  _data-type-path:
+
+path
+====
+
+..  confval:: path
+    :name: data-type-path
+
+    Path relative to the root directory from which we operate.
+    Also resolves `EXT:` syntax.
+
+    ..  rubric:: Example
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        page.10.settings.somePath = fileadmin/stuff/
+
+
+..  index:: Simple data types; resource
+..  _data-type-resource:
+
+resource
+========
+
+..  confval:: resource
+    :name: data-type-resource
+
+    If the value contains a "/", it is expected to be a reference (absolute or
+    relative) to a file in the file system. There is no support for wildcard
+    characters in the name of the reference.
+
+    ..  rubric:: Example
+
+    Reference to a file in the file system:
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        page.10.settings.someFile = fileadmin/picture.gif
+
+..  index:: Simple data types; string
+..  _data-type-string:
+
+string
+======
+
+..  confval:: string
+    :name: data-type-string
+
+    Any property in TypoScript is a string technically. String can be defined
+    in a single line or with multiple lines, using the
+    :ref:`typoscript-syntax-syntax-multiline-values`.
+
+    ..  rubric:: Example
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+        page.10.value = The quick brown fox jumps over the lazy dog.
+
+    ..  include:: /CodeSnippets/TypoScriptSyntax/OperatorUnset.rst.txt
diff --git a/Documentation/DataTypes/_FunctionName.php b/Documentation/Syntax/StringFormats/_FunctionName.php
similarity index 100%
rename from Documentation/DataTypes/_FunctionName.php
rename to Documentation/Syntax/StringFormats/_FunctionName.php
diff --git a/Documentation/Syntax/TSconfig/Index.rst b/Documentation/Syntax/TSconfig/Index.rst
new file mode 100644
index 000000000..5ce467aa7
--- /dev/null
+++ b/Documentation/Syntax/TSconfig/Index.rst
@@ -0,0 +1,20 @@
+:navigation-title: TSconfig differences
+
+..  include:: /Includes.rst.txt
+..  _tsconfig-syntax:
+
+==================================================================
+Differences in the syntax between TSconfig and frontend TypoScript
+==================================================================
+
+While the objects, properties and conditions are different,
+the *syntax* of TSconfig is basically the same as it is for
+TypoScript in frontend TypoScript templates.
+
+Please note the following differences:
+
+*   There are differences in the :ref:`conditions <conditions>` that can be used.
+
+..  note::
+    :ref:`Site settings <t3coreapi:sitehandling-settings>` can be used with the
+    TypoScript constant syntax in TSconfig.
diff --git a/Documentation/TopLevelObjects/Config.rst b/Documentation/TopLevelObjects/Config.rst
index e8295070c..4a7d81722 100644
--- a/Documentation/TopLevelObjects/Config.rst
+++ b/Documentation/TopLevelObjects/Config.rst
@@ -1,3 +1,5 @@
+:navigation-title: Config
+
 ..  include:: /Includes.rst.txt
 ..  index::
     config
@@ -7,38 +9,23 @@
 ..  _config-datatype:
 ..  _top-level-objects-config:
 
-===============
-CONFIG & config
-===============
-
-..  contents:: Table of content
-    :depth: 1
-
-..  _top-level-objects-config-about:
-
-The 'config' top-level-object
-=============================
-
-Internally TYPO3 always creates an array `config` with various configuration
-values which are evaluated during the rendering process and treated in some
-special, predefined and predictive way. This is what we mean when we say the
-property `config`, actually the array `'config'` is of type CONFIG. It is a
-"top-level-object" because it is not subordinate to any other configuration
-setting.
+==================================
+`config`: TypoScript configuration
+==================================
 
-In PHP you can refer to the array within :file:`typo3/sysext/frontend/Classes/`
-files by writing :php:`$GLOBALS['TSFE']->config['config']`.
-
-This typoscript "top level object" `config` provides access to the internal
-array. This means, that configuration settings can be made easily. For example:
+The `config` top-level object does not have to be initialized. Configuration
+can be set like this:
 
 ..  code-block::
+    :caption: config/sites/my_site/setup.typoscript
 
     # TypoScript
-    config.debug = 1
+    config {
+        headerComment = Made with ❤ by your TYPO3 Documentation Team
+    }
 
-    # will produce, in php
-    $GLOBALS['TSFE']->config['config']['debug'] // with value 1
+..  contents:: Table of content
+    :depth: 1
 
 ..  _setup-config-xmlprologue:
 ..  _setup-config-typolinklinkaccessrestrictedpages-ATagParams:
@@ -97,63 +84,61 @@ Properties of 'config'
         :type: :ref:`data-type-string`
         :Special value: "auto"
 
-        If set, the string is prepended to all relative links that TYPO3 generates.
+        If set, this string is prepended to all relative links that TYPO3 generates.
 
-        :typoscript:`config.absRefPrefix = auto` lets TYPO3 autodetect
-        the site root based on path prefixes and not based on host name variables
-        from the server, making this value safe for multi-domain environments.
+        :typoscript:`config.absRefPrefix = auto` means TYPO3 auto-detects
+        the site root from path prefixes rather than host name variables
+        on the server, making this value safe for multi-domain environments.
 
-        If the option :ref:`config.forceAbsoluteUrls <setup-config-forceAbsoluteUrls>`
-        is enabled, :typoscript:`absRefPrefix` is overridden.
+        If :ref:`config.forceAbsoluteUrls <setup-config-forceAbsoluteUrls>`
+        is enabled :typoscript:`absRefPrefix` is overridden.
 
         Using an URI in :typoscript:`absRefPrefix` will require additional conditions
         if you use different domains for your deployment stages in CI environments.
 
         If you are working on a server where you have different domain names or
         different path segments leading to the same page (e.g. for internal and
-        external access), you may do yourself a favor and set :typoscript:`absRefPrefix` to
+        external access), set :typoscript:`absRefPrefix` to
         the URL and path of your site, e.g. :samp:`https://example.org/`. If you do not,
-        you risk to render pages to cache from the internal network and thereby
-        prefix image references and links with a wrong path or a path not accessible
-        from outside.
+        you risk rendering pages to cache from the internal network and thereby
+        prefixing image references and links with incorrect or inaccessible paths.
 
     ..  confval:: additionalHeaders
         :name: config-additionalheaders
         :type: numerically indexed array of "HTTP header entries".
         :Example: :ref:`setup-config-additionalheaders`
 
-        By means of :typoscript:`config.additionalHeaders` as series of additional HTTP headers
-        can be configured. An entry has the following structure:
+        :typoscript:`config.additionalHeaders` allows additional HTTP headers
+        to be configured. An entry has the following structure:
 
         :typoscript:`10.header = the header string`
             This value is required.
 
         :typoscript:`10.replace = 0 | 1`
-            Optional, boolean, default is `1`.
-            If `1`, the header will replace an existing one that has the same name.
+            Optional, boolean. Default value is `1`.
+            If `1` the header will replace an existing header with the same name.
 
         :typoscript:`10.httpResponseCode = 201`
-            Optional, integer, a http status code that the page should return.
+            Optional, integer. The http status code that the page should return.
 
-        By default TYPO3 sends a "Content-Type" header with the defined
-        encoding. It then sends cache headers, if configured via
-        :ref:`setup-config-sendcacheheaders`.
-        Then additional headers are send, plus finally a "Content-Length"
-        header, if enabled via :ref:`setup-config-enablecontentlengthheader`.
+        By default, TYPO3 sends a "Content-Type" header with the defined
+        encoding. It then sends cache headers if configured via
+        :ref:`setup-config-sendcacheheaders` and then any additional headers.
+        Finally, a "Content-Length" header is sent, if enabled via
+        :ref:`setup-config-enablecontentlengthheader`.
 
     ..  confval:: admPanel
         :name: config-admPanel
         :type: boolean
 
-        :typoscript:`config.admPanel = 1` can
-        be used to enable the admin panel. See :ref:`Configuration in
-        the Admin Panel manual <ext_adminpanel:typoscript-config-admpanel>`.
+        :typoscript:`config.admPanel = 1` enables the admin panel. See
+        :ref:`Configuration in the Admin Panel manual <ext_adminpanel:typoscript-config-admpanel>`.
 
     ..  confval:: ATagParams
         :name: config-ATagParams
         :type: *<A>-params*
 
-        Additional parameters to all links in TYPO3 (excluding menu-links).
+        Additional parameters for all links in TYPO3 (excluding menu-links).
 
     ..  confval:: cache
         :name: config-cache
@@ -162,14 +147,14 @@ Properties of 'config'
 
         Determine the maximum cache lifetime of a page.
 
-        The maximum cache lifetime of a page can not only be determined by the
-        start and stop times of content elements on the page itself, but also
-        by arbitrary records on any other page. However, the page has to be
-        configured so that TYPO3 knows the start and stop times of which
-        records to include. Otherwise, the cache entry will be used although a
-        start/stop date already passed by.
+        The maximum cache lifetime of a page can be determined by
+        start and stop times of content elements on that page, as well as
+        arbitrary records on any other page. The page needs to be
+        configured so that TYPO3 knows which records' start and stop times to
+        take into account. Otherwise, the cache entry might be used although a
+        start/stop date has already passed by.
 
-        To include records of type <table name> on page <pid> into the cache
+        To include records of type <table name> on page <pid> in the cache
         lifetime calculation of page <page-id>, add the following TypoScript:
 
         ..  code-block:: typoscript
@@ -177,21 +162,21 @@ Properties of 'config'
 
             config.cache.<page-id> = <table name>:<storage-pid>
 
-        Multiple record sources can be added as comma-separated list, see the
-        examples.
+        Multiple record sources can be added as a comma-separated list. See
+        :ref:`examples <setup-config-cache>`.
 
-        You can use the keyword "all" instead of a <page-id> to consider
-        records for the cache lifetime of all pages.
+        Use the keyword "all" instead of a <page-id> to take all records
+        from all pages into account for the cache lifetime calculation.
 
-        You can use the keyword "current" instead of a <storage-pid> to consider
-        records on the current page for the cache life of itself.
+        Use the keyword "current" instead of a <storage-pid> to take only records
+        on the current page into account for the cache lifetime calculation.
 
     ..  confval:: cache_clearAtMidnight
         :name: config-cache-clearAtMidnight
         :type: :ref:`data-type-boolean`
         :Default: `0`
 
-        With this setting the cache always expires at midnight of the day, the
+        This setting ensures that the cache expires at midnight on the day that the
         page is scheduled to expire.
 
 
@@ -200,10 +185,10 @@ Properties of 'config'
         :type: :ref:`data-type-integer`
         :Default: `86400` *(= 24 hours)*
 
-        The number of second a page may remain in cache.
+        The number of seconds a page can remain in the cache.
 
-        This value is overridden by the value set in the page-record
-        `field="cache_timeout"` if this value is greater than zero.
+        This value is overridden by the value in the page record
+        `field="cache_timeout"` if that value is greater than zero.
 
     ..  confval:: compressCss
         :name: config-compressCss
@@ -211,21 +196,21 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-compresscss`
 
-        If set, CSS files referenced in :typoscript:`page.includeCSS` and the like will be
-        minified and compressed. Does not work on files, which are referenced
+        If set, CSS files referenced in :typoscript:`page.includeCSS`, etc,  will be
+        minified and compressed. It has no effect on files which are referenced
         in :typoscript:`page.headerData`.
 
-        Minification will remove all excess space. The more significant
-        compression step (using gzip compression) requires
+        Minification will remove excess space. A higher level of compression
+        (using gzip) requires
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['compressionLevel']` to be enabled in the
-        Install Tool. For this to work you also need to activate the gzip-
-        related compressionLevel options in :file:`.htaccess`, as otherwise the
+        Install Tool. For it to work you also need to activate gzip-
+        related compressionLevel options in :file:`.htaccess`, otherwise the
         compressed files will not be readable by the user agent.
 
         ..  include:: _includes/_concat-compress.rst.txt
 
         TYPO3 comes with a built-in compression handler, but you can
-        also register your own one using
+        also register your own using
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['cssCompressHandler']`.
 
         ..  code-block:: php
@@ -242,11 +227,11 @@ Properties of 'config'
 
         Enabling this option together with
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['compressionLevel']` in the Install Tool
-        delivers Frontend JavaScript files referenced in :typoscript:`page.includeJS` and
-        the like using GZIP compression. Does not work on files, which are
+        wil compress frontend JavaScript files referenced in :typoscript:`page.includeJS`, etc,
+        using GZIP compression. It has no effect on files which are
         referenced in :typoscript:`page.headerData`.
 
-        Please note that this requires :file:`.htaccess` to be adjusted, as otherwise
+        Please note that this requires :file:`.htaccess` to be modified, otherwise
         the files will not be readable by the user agent. Please see the
         description of :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['compressionLevel']` in the
         Install Tool.
@@ -254,7 +239,7 @@ Properties of 'config'
         ..  include:: _includes/_concat-compress.rst.txt
 
         TYPO3 comes with a built-in compression handler, but you can
-        also register your own one using
+        also register your own using
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['jsCompressHandler']`.
 
         ..  code-block:: php
@@ -269,16 +254,16 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-concatenatecss`
 
-        Setting :typoscript:`config.concatenateCss` merges Stylesheet files referenced in
-        the Frontend in page.includeCSS and the like together. Files are merged
-        only, if their media attribute has the same value, e.g. if it is "all"
-        for several files. Does not work on files, which are referenced in
+        Setting :typoscript:`config.concatenateCss` merges frontend stylesheet
+        files referenced in page.includeCSS, etc. Files are merged
+        only if their media attribute has the same value, e.g. if it is "all"
+        for several files. It has no effect on files which are referenced in
         :typoscript:`page.headerData`.
 
         ..  include:: _includes/_concat-compress.rst.txt
 
         TYPO3 comes with a built-in concatenation handler, but you
-        can also register your own one using
+        can also register your own using
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['cssConcatenateHandler']`.
 
         ..  code-block:: php
@@ -293,16 +278,17 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-concatenateJs`
 
-        Setting :typoscript:`config.concatenateJs` merges JavaScript files referenced in
-        the Frontend in :typoscript:`page.includeJS` and the like together. Does not work
-        on files, which are referenced in :typoscript:`page.headerData`.
+        Setting :typoscript:`config.concatenateJs` merges frontend JavaScript
+        files referenced in :typoscript:`page.includeJS`, etc. It has no effect
+        on files which are referenced in :typoscript:`page.headerData`.
 
-        If all files to be concatenated are marked with the async flag, the async attribute is assigned to the script tag.
+        If all the files are marked with an async flag, an async attribute is
+        assigned to the script tag.
 
         ..  include:: _includes/_concat-compress.rst.txt
 
         TYPO3 comes with a built-in concatenation handler, but you
-        can also register your own one using
+        can also register your own using
         :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['jsConcatenateHandler']`.
 
         ..  code-block:: php
@@ -317,32 +303,32 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref: `setup-config-contentObjectExceptionHandler`
 
-        Exceptions which occur during rendering of content objects (typically plugins)
-        will be caught by default in production context and an error message
-        is shown along with the rendered output.
+        Exceptions which occur during the rendering of content objects (typically plugins)
+        are caught by default in a production context. An error message
+        is displayed with the rendered output.
 
-        If this is done, the page will remain available while the section of the page
-        that produces an error (i.e. throws an exception) will show a configurable error message.
-        By default this error message contains a random code which references
-        the exception and is also logged by the :ref:`logging framework <t3coreapi:logging>`
+        If there is an exception, the page will remain available while the section of the page
+        that produces the error (i.e. throws an exception) will show a configurable error message.
+        By default the error message contains a random code referencing
+        the exception and the error is logged by the :ref:`logging framework <t3coreapi:logging>`
         for developer reference.
 
         ..  important::
 
-            Instead of breaking the whole page when an exception occurs, an error message
-            is shown for the part of the page that is broken.
-            Be aware, it is possible that a page with an error message gets cached.
+            Instead of a whole page breaking when an exception occurs, an error message
+            is displayed just in the part of the page that is broken.
+            Be aware that a page displaying an error message can get cached.
 
-        To get rid of the error message not only the actual error needs to be fixed,
-        but the cache must be cleared for this page.
+        To get rid of the error message, the error needs to be fixed
+        and the cache must be cleared for the page.
 
     ..  confval:: debug
         :name: config-debug
         :type: :ref:`data-type-boolean`
 
-        If set, then debug information in the TypoScript code is sent.
-        This applies e.g. to menu objects and the parsetime output.
-        The parsetime will be sent as HTTP response header `X-TYPO3-Parsetime`.
+        If set, debug information for the TypoScript code is sent.
+        This applies to menu objects and parse-time output.
+        The parse-time will be sent in HTTP response header `X-TYPO3-Parsetime`.
 
     ..  confval:: disableAllHeaderCode
         :name: config-disableAllHeaderCode
@@ -350,19 +336,19 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-disableallheadercode`
 
-        If this is not set or set to `0`, the :ref:`page` object automatically
+        If this is not set or set to `0`, the :ref:`page`
         outputs a HTML skeleton, see :ref:`page_output`.
 
-        To disable this default behaviour set :typoscript:`disableAllHeaderCode = 1`.
-        The page outputs only the result of the cObject array
-        (1,2,3,4...) of the :ref:`page` object.
+        To disable the default behaviour set :typoscript:`disableAllHeaderCode = 1`.
+        The page then consists of only the cObject array
+        (1,2,3,4...) output of the :ref:`page`.
 
-        Use this feature in templates supplying other content-types than HTML.
-        That could be an image, a RSS-feed, an ajax request in a format like
-        XML or JSON.
+        Use this feature for templates for content types other than HTML,
+        for example images, RSS-feeds or ajax requests in an
+        XML or JSON format.
 
-        This property can also be used to generate the complete HTML page,
-        including the :html:`<html>` and :html:`<body>` tags manually.
+        This property can also be used to generate complete HTML pages,
+        including the :html:`<html>` and :html:`<body>` tags.
 
     ..  confval:: disableBodyTag
         :name: config-disableBodyTag
@@ -371,36 +357,37 @@ Properties of 'config'
 
         If this option is set, the TYPO3 core will not generate the
         opening :html:`<body ...>` part of the body tag. The closing :html:`</body>`
-        is not affected and will still be issued.
+        is not affected and will still be generated.
 
-        :typoscript:`disableBodyTag` takes precedence over the :ref:`page` properties
+        :typoscript:`disableBodyTag` takes precedence over
         :typoscript:`bodyTagCObject`, :typoscript:`bodyTag` and
-        :typoscript:`bodyTagAdd`. With :typoscript:`config.disableBodyTag = 1` the others are
-        ignored and don't have any effect.
+        :typoscript:`bodyTagAdd` in the :ref:`page` properties. If
+        :typoscript:`config.disableBodyTag = 1` then the other settings are ignored
+        and won't have any effect.
 
     ..  confval:: disableCanonical
         :name: config-disableCanonical
         :type: :ref:`data-type-boolean`
 
-        When the system extension SEO is installed, canonical tags are generated
-        automatically to prevent duplicate content. A good canonical is added
+        If the SEO system extension is installed, canonical tags are generated
+        to prevent duplicate content. A good canonical is added
         in many cases by default. For edge cases, you might want to disable the
-        rendering of this tag. You can do this by setting this property to `1`.
+        rendering of this tag by setting it to `1`.
 
     ..  confval:: disableHrefLang
         :name: config-disableHrefLang
         :type: :ref:`data-type-boolean`
 
-        When the system extension SEO is installed, hreflang tags are generated
-        automatically in multi-language setups. By settings this option to `1`
-        the rendering of those tags will be skipped.
+        If the SEO system extension is installed, hreflang tags are generated
+        in multi-language setups. By settings this option to `1`
+        the rendering of the tags will be skipped.
 
     ..  confval:: disablePrefixComment
         :name: config-disablePrefixComment
         :type: :ref:`data-type-boolean`
 
-        If set, the stdWrap property :ref:`stdwrap-prefixComment` will be disabled, thus
-        preventing any revealing and space-consuming comments in the HTML
+        If set, stdWrap :ref:`stdwrap-prefixComment` will be disabled, thus
+        preventing any potentially revealing and space-consuming comments in the HTML
         source code.
 
     ..  confval:: disablePreviewNotification
@@ -408,7 +395,7 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: `0`
 
-        Disables the "preview" notification box completely.
+        Disables the "preview" notification box.
 
     ..  confval:: disableLanguageHeader
         :name: config-disableLanguageHeader
@@ -416,7 +403,7 @@ Properties of 'config'
         :Default: `0`
 
         TYPO3 by default sends a `Content-language: XX` HTTP header,
-        where "XX" is the ISO code of the according language. The
+        where "XX" is the ISO code of the relevant language. The
         value is based on the language defined in the
         :ref:`Site Configuration <t3coreapi:sitehandling>`.
 
@@ -443,12 +430,12 @@ Properties of 'config'
         `html5`
             for the HTML5 doctype.
         `none`
-            for *no* doctype at all.
+            for *no* doctype.
 
         See :ref:`config.htmlTag_setParams <setup-config-htmltag-setparams>`
         for more details on the effect on the HTML tag.
 
-        Default is the HTML 5 doctype:
+        It defaults to the HTML 5 doctype:
 
         ..  code-block:: html
 
@@ -459,11 +446,11 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: `1`
 
-        If set, a header "content-length: [bytes of content]" is sent.
+        If set, the header "content-length: [bytes of content]" is sent.
 
-        If a backend user is logged in, this is disabled. The reason is
+        This is disabled if a backend user is logged in. The reason is
         that the content length header cannot include the length of these
-        objects and the content-length will cut off the length of the
+        objects and the content-length will truncate the length of the
         document in some browsers.
 
     ..  confval:: extTarget
@@ -484,18 +471,16 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: `0`
 
-        ..  versionadded:: 12.1
-
-        If this option is set, all links, reference to images or assets
+        If this option is set, all links, image references or assets
         previously built with a relative or absolute path (for example,
         :file:`/fileadmin/my-pdf.pdf`) will be rendered as absolute URLs
         with the site prefix / current domain.
 
-        Examples for such use cases are the generation of a complete static
+        An example of a possible use case is generating a static
         version of a TYPO3 site for sending a page via email.
 
         ..  note::
-            Setting this option will override any setting in :ref:`config.absRefPrefix
+            Setting this option will override :ref:`config.absRefPrefix
             <setup-config-absrefprefix>` and any typolink
             :ref:`typolink-forceAbsoluteUrl` options.
 
@@ -503,20 +488,20 @@ Properties of 'config'
         :name: config-forceTypeValue
         :type: :ref:`data-type-boolean`
 
-        Force the `&type` value of all TYPO3 generated links to a specific value
+        Force the `&type` value of TYPO3 generated links to a specific value
         (except if overruled by local :typoscript:`forceTypeValue` values).
 
-        Useful if you run a template with special content at - say `&type=95` -
-        but still wants to keep your targets neutral. Then you set your
-        targets to blank and this value to the type value you wish.
+        This is useful if you have a template with special content, for example
+        `&type=95`, but still want to keep your targets neutral. Then you can
+        set your targets to blank and this value to your required type value.
 
     ..  confval:: headerComment
         :name: config-headerComment
         :type: :ref:`data-type-string`
 
-        The content is added before the "TYPO3 Content Management Framework"
-        comment in the <head> section of the page. Use this to insert a note
-        like that "Programmed by My-Agency".
+        This content is added above the "TYPO3 Content Management Framework"
+        comment in the <head> page section. Use this to insert text
+        like "Programmed by My-Agency".
 
     ..  confval:: htmlTag.attributes
         :name: config-htmlTag-attributes
@@ -535,15 +520,15 @@ Properties of 'config'
         :type: :ref:`data-type-string`
         :Example: :ref:`setup-config-htmltag-setparams`
 
-        Sets the attributes for the :html:`<html>` tag on the page. If you set
-        :ref:`setup-config-doctype` to a keyword enabling XHTML then some attributes are
-        already set. This property allows you to override any preset
-        attributes with your own content if needed.
+        Sets the :html:`<html>` tag attributes on the page. If you set
+        :ref:`setup-config-doctype` to a keyword that enables XHTML then some
+        attributes will already be set. This property allows you to override preset
+        attributes with your own content.
 
-        **Special:** If you set it to "none" then no attributes will be set at
-        any event.
+        **Special:** If you set it to "none" then setting attributes is no longer
+        possible.
 
-        If you are using `htmlTag.attributes` this property (`htmlTag_setParams`)
+        If you have set `htmlTag.attributes` this property (`htmlTag_setParams`)
         will not have any effect.
 
 
@@ -551,16 +536,16 @@ Properties of 'config'
         :name: config-htmlTag-stdWrap
         :type: :ref:`stdwrap`
 
-        Modify the whole :html:`<html>` tag with stdWrap functionality. This can be
-        used to extend or override this tag.
+        Modify the :html:`<html>` tag with stdWrap functionality. Use
+        this property to extend or override this tag.
 
     ..  confval:: index_descrLgd
         :name: config-index-descrLgd
         :type: :ref:`data-type-integer`
         :Default: `200`
 
-        This indicates how many chars to preserve as description for an
-        indexed page. This may be used in the search result display.
+        This indicates how many chars to preserve in the description of an
+        indexed page. This can be used in search result output.
 
     ..  confval:: index_enable
         :name: config-index-enable
@@ -574,7 +559,7 @@ Properties of 'config'
         :name: config-index-externals
         :type: :ref:`data-type-boolean`
 
-        If set, external media linked to on the pages is indexed as well.
+        If set, external media linked to on pages is indexed.
 
         Automatically enabled when :t3-ext:`indexed_search` is enabled.
 
@@ -583,8 +568,8 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Default: `1`
 
-        This allows to turn on or off the indexing of metatags. It is turned
-        on by default.
+        This allows the indexing of metatags to be switched on or off. It is
+        switched on by default.
 
     ..  confval:: inlineStyle2TempFile
         :name: config-inlineStyle2TempFile
@@ -592,11 +577,11 @@ Properties of 'config'
         :Default: `1`
         :Example: :ref:`setup-config-inlinestyle2tempfile`
 
-        If set, the inline styles TYPO3 controls in the core are written to a
-        file, :file:`typo3temp/assets/css/stylesheet\_[hashstring].css`, and the header
-        will only contain the link to the stylesheet.
+        If set, the inline styles TYPO3 controls in the core are written to
+        the :file:`typo3temp/assets/css/stylesheet\_[hashstring].css` file and
+        the header then contains just a link to the stylesheet.
 
-        The file hash is based solely on the content of the styles.
+        The file hash is based on the content of the styles.
 
     ..  confval:: intTarget
         :name: config-intTarget
@@ -609,33 +594,32 @@ Properties of 'config'
         :type: list
         :Example: :ref:`setup-config-linkvars`
 
-        :php:`HTTP_GET_VARS`, which should be passed on with links in TYPO3. This
+        :php:`HTTP_GET_VARS`, which is passed on in links in TYPO3. It
         is compiled into a string stored in :php:`$GLOBALS['TSFE']->linkVars`
 
         The values are rawurlencoded in PHP.
 
         You can specify a range of valid values by appending a () after each
-        value. If this range does not match, the variable won't be appended to
-        links. This is very important to prevent that the cache system gets
-        flooded with forged values.
+        value. If the range doesn't match, the variable won't be appended to
+        links. This prevents the cache system getting flooded with forged values.
 
-        The range may contain one of these values:
+        The range can contain one of the following values:
 
         `[a]-[b]`
             A range of allowed integer values
         `int`
             Only integer values are allowed
         `[a]\|[b]\|[c]`
-            A list of allowed strings (whitespaces will be removed)
+            A list of allowed strings (whitespace will be removed)
         `/[regex]/`
-            Match against a regular expression (PCRE style)
+            Match a regular expression (PCRE style)
 
         You can use the pipe character (|) to access nested properties.
 
         ..  note::
 
-            Do **not** include the `type` and `L` parameter in the linkVars
-            list, as this will result in unexpected behavior.
+            Do **not** include the `type` and `L` parameters in the linkVars
+            list as this will result in unexpected behavior.
 
     ..  confval:: message_preview
         :name: config-message_preview
@@ -676,7 +660,7 @@ Properties of 'config'
         Imagine you have a TYPO3 site with several mount points, and you need
         certain pages to always include a specific mount point parameter for
         correct content rendering. By configuring :typoscript`MP_defaults`, you
-        ensure consistency and reduce the risk of broken links or incorrect
+        can ensure consistency and reduce the risk of broken links or incorrect
         content being displayed due to missing parameters.
 
 
@@ -695,18 +679,18 @@ Properties of 'config'
         calculated for the branch.
 
         The result is used just like :ref:`MP\_defaults <setup-config-mp-defaults>` are used to
-        find MP-vars if none has been specified prior to the call to
+        find MP-vars if none have been specified prior to the call to
         `\TYPO3\CMS\Frontend\Typolink\PageLinkBuilder`.
 
         You can specify `root` as a special keyword in the list of IDs and
         that will create a map-tree for the whole site (but this may be VERY
         processing intensive if there are many pages!).
 
-        The order of IDs specified may have a significance; Any ID in a branch
-        which is processed already (by a previous ID root point) will not be
+        The order of IDs can be significant - any ID in a branch
+        which has already been processed (by a previous ID root point) will not be
         processed again.
 
-        The configured IDs have to be the uids of Mount Point pages itself, not the targets.
+        Configured IDs have to be the uids of actual mount point pages, not the targets.
 
     ..  confval:: namespaces.[identifier]
         :name: config-namespaces
@@ -725,16 +709,16 @@ Properties of 'config'
         If this is set to `1`, it disables the `pages` cache, meaning that the
         rendered result/response will not be saved to cache.
 
-        If set to `0`, it's ignored. Rendered result (e.g. full html of a page)
+        If set to `0`, it is ignored. The rendered result (e.g. full html of a page)
         is stored in the `pages` cache.
 
         Other parameters may have set it to true for other reasons.
         Note that setting this to `1` doesn't disable other TYPO3 caches.
-        Instead of setting `config.no_cache` you might consider changing dynamic
+        Instead of setting `config.no_cache` you can change dynamic
         (non-cacheable) content from :ref:`USER <cobj-user>` to :ref:`USER_INT <cobj-user>`
         (:ref:`COA <cobj-coa>` to :ref:`COA_INT<cobj-coa>`).
 
-        For more information about cache types see
+        For more information about cache types see the
         :ref:`cache types chapter <t3coreapi:caching-architecture-core>`.
 
     ..  confval:: noPageTitle
@@ -743,13 +727,13 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-pagerenderertemplatefile`
 
-         If you only want to have the site name (from the template record) in
-         your :html:`<title>` tag, set this to 1. If the value is 2 then the :html:`<title>`
-         tag is not printed at all.
+        If you only want to have the site name (from the template record) in
+        your :html:`<title>` tag, set this to 1. If the value is 2 then the :html:`<title>`
+        tag is not output.
 
-         Please take note that this tag is required for (X)HTML compliant
-         output, so you should only disable this tag if you generate it
-         manually already.
+        Please note that this tag is required for (X)HTML compliant
+        output, so you should only disable this tag if you have already
+        generated it manually.
 
     ..  confval:: pageRendererTemplateFile
         :name: config-pageRendererTemplateFile
@@ -772,23 +756,22 @@ Properties of 'config'
         :Default: `0`
         :Example: :ref:`setup-config-pagetitleproviders`
 
-        TYPO3 by default prints a title tag in the format "website: page
+        TYPO3 by default prints title tags in the format "website: page
         title".
 
         If :typoscript:`pageTitleFirst` is set (and if the page title is printed), then the
-        page title will be printed IN FRONT OF the template title. So it will
-        look like "page title: website".
+        page title will be printed before the template title, i.e. "page title: website".
 
     ..  confval:: pageTitleProviders
         :name: config-pageTitleProviders
         :type: array
 
-        In order to keep setting the titles in control, an API to set the page title is available. The API uses
-        :typoscript:`PageTitleProviders` to define the page title based on page record and the content on the page.
+        In order to set page titles, an API is available. The API uses
+        :typoscript:`PageTitleProviders` to set the page title based on the page record and the content on that page.
 
-        Based on the priority of the providers, the :php:`PageTitleProviderManager` will check the providers if a title
-        is given by the provider. It will start with the highest priority :typoscript:`PageTitleProviders` and will end with
-        the lowest in priority.
+        Based on the priority of providers, :php:`PageTitleProviderManager` will
+        check the providers to see if they have titles. It will start with the
+        highest priority :typoscript:`PageTitleProviders`.
 
     ..  confval:: pageTitleSeparator
         :name: config-pageTitleSeparator
@@ -796,11 +779,11 @@ Properties of 'config'
         :Default: `:` *(colon with following space)*
         :Example: :ref:`setup-config-pagetitleseparator`
 
-        The signs which should be printed in the title tag between the website
+        The symbols ouput in the title tag between the website
         name and the page title. If :typoscript:`pageTitleSeparator` is set, but *no*
         sub-properties are defined, then a space will be added to the end of the
-        separator. stdWrap is useful to adjust whitespaces at the beginning and
-        the end of the separator.
+        separator. stdWrap can be used to adjust whitespace at the beginning and
+        end of the separator.
 
     ..  confval:: recordLinks
         :name: config-recordLinks
@@ -810,7 +793,7 @@ Properties of 'config'
             :caption: Frontend TypoScript definition for identifier `my_content`
 
             config.recordLinks.my_content {
-                // Do not force link generation when the record is hidden
+                // If the record is hidden do not force link generation
                 forceLink = 0
 
                 typolink {
@@ -827,22 +810,22 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
         :Example: :ref:`setup-config-removedefaultjs`
 
-        Remove CSS generated by :ref:`\_CSS\_DEFAULT\_STYLE
-        <setup-plugin-css-default-style>` configuration of extensions.
-        (:typoscript:`_CSS_DEFAULT_STYLE` outputs a set of default styles, just because
-        an extension is installed.)
+        Remove CSS generated by the :ref:`\_CSS\_DEFAULT\_STYLE
+        <setup-plugin-css-default-style>` extension property.
+        (:typoscript:`_CSS_DEFAULT_STYLE` outputs a set of default styles for
+        extensions with frontend plugins)
 
     ..  confval:: removeDefaultJS
         :name: config-removeDefaultJS
         :type: :ref:`data-type-boolean` / :ref:`data-type-string`
         :Example: :ref:`setup-config-removedefaultjs`
 
-        If set, the default JavaScript in the header will be removed.
+        If set, default JavaScript in the header will be removed.
 
-        The default JavaScript is the decryption function for email addresses.
+        The default JavaScript decrypts email addresses.
 
-        **Special case:** If the value is the string `external`, then the default
-        JavaScript is written to a temporary file and included from that file.
+        **Special case:** If the value is set to the string `external`, then the default
+        JavaScript is written to a temporary file and included in that file.
         See :ref:`setup-config-inlineStyle2TempFile`.
 
     ..  confval:: sendCacheHeaders
@@ -850,16 +833,16 @@ Properties of 'config'
         :type: :ref:`data-type-boolean`
 
          If set, TYPO3 will output cache-control headers to the client based
-         mainly on whether the page was cached internally. This feature allows
+         on whether the page was internally cached. This feature allows
          client browsers and/or reverse proxies to take load off TYPO3
          websites.
 
          The conditions for allowing client caching are:
 
          *  page was cached
-         *  No `*_INT` or `*_EXT` objects were on the page (e.g. :ref:`cobj-user`)
-         *  No frontend user is logged in
-         *  No backend user is logged in
+         *  No `*_INT` or `*_EXT` objects are on the page (e.g. :ref:`cobj-user`)
+         *  No frontend users are logged in
+         *  No backend users are logged in
 
          If these conditions are met, the headers sent are:
 
@@ -869,56 +852,84 @@ Properties of 'config'
          *  Cache-Control: max-age: [seconds til expiretime]
          *  Pragma: public
 
-         In case caching is not allowed, these headers are sent to avoid client
+         If caching is not allowed, the following headers are sent to avoid client
          caching:
 
          *  Cache-Control: private, no-store
 
-         Notice that enabling the browser caches means you have to consider how
-         log files are written. Because when a page is cached on the client it
+         Notice that enabling browser caches means you will have to consider how
+         log files are written because when a page is cached on the client it
          will not invoke a request to the webserver, thus not writing the
-         request to the log. There should be ways to circumvent these problems
-         but they are outside the domain of TYPO3 in any case.
+         request to a log. There should be ways to circumvent these problems
+         but they are outside the domain of TYPO3.
 
          **Tip:** Enabling cache-control headers might confuse editors seeing
          old content served from the browser cache. "Shift-Reload" will bypass
-         both browser- and reverse-proxy caches and even make TYPO3 regenerate
-         the page. Teach them that trick!
+         both browser- and reverse-proxy caches and make TYPO3 regenerate
+         the page. A good tip worth knowing about!
+
+    ..  confval:: sendCacheHeadersForSharedCaches
+        :name: config-sendCacheHeadersForSharedCaches
+        :type: `auto`, `force`, or empty
+
+        ..  versionadded:: 13.3
+
+        When working with proxies, keeping a cached version for a period of
+        time and answering requests from the client will take load
+        off TYPO3 / the webserver, while at the same time notifying the
+        client not to cache the response in the browser cache.
+
+        This is achieved by setting
+        :typoscript:`config.sendCacheHeadersForSharedCaches = auto`.
+
+        When this option is enabled, TYPO3 evaluates the current TYPO3 frontend
+        request to see if it is being executed behind a reverse proxy. If so, TYPO3
+        sends the following HTTP Response Headers as a cached response:
+
+        ..  code-block:: plaintext
+
+            Expires: Thu, 26 Aug 2024 08:52:00 GMT
+            ETag: "d41d8cd98f00b204ecs00998ecf8427e"
+            Cache-Control: max-age=0, s-maxage=86400
+            Pragma: public
+
+        When :typoscript:`config.sendCacheHeadersForSharedCaches = force` the reverse
+        proxy evaluation can be omitted. Use for local webserver internal
+        caches.
+
+        See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
+        for details and whether your reverse proxy supports this directive.
 
     ..  confval:: showWebsiteTitle
         :name: config-showWebsiteTitle
         :type: :ref:`data-type-boolean`
         :Default: 1
 
-        ..  versionadded:: 12.0
-
-        The option can be used to specify whether the website title defined in
+        This option can be used to specify whether the website title defined in
         the :ref:`site configuration <t3coreapi:sitehandling>` should be added
         to the page title (used for the :html:`<title>` tag, for example).
 
-        By default, the website title is added. To omit the website title, the
-        option has to be set to `0`.
+        By default, the website title is added. To omit the website title, set the
+        option to `0`.
 
     ..  confval:: spamProtectEmailAddresses
         :name: config-spamProtectEmailAddresses
         :type: `-10` to `10`
         :Example: :ref:`setup-config-spamprotectemailaddresses-lastdotsubst`
 
-        If set, then all email addresses in typolinks will be encrypted so
+        If set, all email addresses in typolinks will be encrypted so
         that it is harder for spam bots to detect them.
 
-        If you set this value to a number, then the encryption is an
-        offset of character values. If you set this value to "-2" then all
-        characters will have their ASCII value offset by "-2". To make this
-        possible, a little JavaScript code is added to every generated web
-        page!
+        If you set this value to a number then the encryption method is an
+        offset of character values. If you set this value to "-2" all
+        characters will have their ASCII value offset by "-2". It works by adding
+        a small piece of JavaScript code to every web page.
 
-        (It is recommended to set the value in the range from -5 to 1 since
+        (It is recommended to set the option to a value between -5 to 1 since
         setting it to >= 2 means a "z" is converted to "\|" which is a special
-        character in TYPO3 tables syntax – and that might confuse columns in
-        tables.)
+        character in TYPO3 table syntax – which might lead to confusion.)
 
-        It is required to enable the default JavaScript and not disable it.
+        Default JavaScript needs to be enabled.
         (see :ref:`removeDefaultJS <setup-config-removedefaultjs>`)
 
     ..  confval:: spamProtectEmailAddresses_atSubst
@@ -942,10 +953,10 @@ Properties of 'config'
         :type: array
         :Example: :ref:`setup-config-tx-extension-key-with-no-underscores`
 
-        Configuration space for extensions. This can be used – for example –
-        by plugins that need some TypoScript configuration, but that don't
-        actually display anything in the frontend (i.e. don't receive their
-        configuration as an argument from the frontend rendering process).
+        Configuration space for extensions. This can be used for plugins that
+        have TypoScript configuration, but that don't display anything in the frontend
+        (i.e. don't receive their configuration as an argument from the frontend
+        rendering process).
 
     ..  confval:: typolinkLinkAccessRestrictedPages
         :name: config-typolinkLinkAccessRestrictedPages
@@ -957,9 +968,9 @@ Properties of 'config'
         this setting is an integer it will be interpreted as a page id to
         which the link will be directed.
 
-        If the value is :typoscript:`NONE` the original link to the page will be kept
-        although it will generate a page-not-found situation (which can of
-        course be picked up properly by the page-not-found handler and present
+        If the value is :typoscript:`NONE`, the original link to the page will be kept
+        although it will generate a page-not-found situation (which could, of
+        course, be properly handled by the page-not-found handler and present
         a nice login form).
 
         See :confval:`menu-common-properties-showaccessrestrictedpages`
@@ -970,8 +981,6 @@ Properties of 'config'
         :type: :ref:`data-type-string`
         :Example: :ref:`setup-config-typolinklinkaccessrestrictedpages`
 
-        ..  versionadded:: 12.3
-
         `typolinkLinkAccessRestrictedPages.ATagParams` Add custom attributes to
         the anchor tag.
 
@@ -1029,7 +1038,7 @@ Demonstrates:
 
         config.absRefPrefix = /
 
-#.  Prefixing all links with the path to a subdirectory:
+#.  Prefixing all links with a path to a subdirectory:
 
     ..  code-block:: typoscript
         :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -1113,15 +1122,15 @@ calculation for page 10:
 
     config.cache.10 = fe_users:2
 
-This includes records from multiple sources, namely the :sql:`fe_users`
-records on page 2 and the :sql:`tt_new` records on page 11:
+This includes records from multiple sources; :sql:`fe_users`
+records on page 2 and :sql:`tt_new` records on page 11:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
     config.cache.10 = fe_users:2,tt_news:11
 
-Consider the :sql:`fe_users` records on the storage page 2 for the cache lifetime of all
+Take :sql:`fe_users` records on storage page 2 into account for the cache lifetime of all
 pages:
 
 ..  code-block:: typoscript
@@ -1129,7 +1138,7 @@ pages:
 
     config.cache.all = fe_users:2
 
-Each pages cache lifetime is influenced if fe_users stored on the page itself get
+Each page's cache lifetime is affected if fe_users stored on the same page are
 changed:
 
 ..  code-block:: typoscript
@@ -1343,9 +1352,8 @@ This will add `&print=[print-value]` to all links in TYPO3.
 
     config.linkVars = tracking|green(0-5)
 
-With the above configuration the following example GET parameters will
-be kept: `&tracking[green]=3`. But a get parameter like
-`tracking[blue]` will not be kept.
+In the above configuration, GET parameter `&tracking[green]=3` would
+be kept, but `tracking[blue]` would not be kept.
 
 ..  _setup-config-message-preview-workspace:
 
@@ -1437,15 +1445,16 @@ By default, TYPO3 ships with two providers:
         }
     }
 
-The ordering of the providers is based on the :typoscript:`before` and
+The order of providers is based on the :typoscript:`before` and
 :typoscript:`after` parameters. If you want a provider
 to be handled before a specific other provider, set that provider in
-the :typoscript:`before`, do the same with :typoscript:`after`.
+:typoscript:`before` and :typoscript:`after`.
 
 ..  note::
-    The :typoscript:`seo` PageTitleProvider is only available with installed SEO system extension.
+    The :typoscript:`seo` PageTitleProvider is only available if the SEO system
+    extension is installed.
 
-You can find information about creating own PageTitleProviders in the section
+You can find information about creating your own PageTitleProviders in the section
 :ref:`PageTitle API <t3coreapi:pagetitle>`.
 
 
@@ -1457,14 +1466,14 @@ Use custom separators between page title parts
 Demonstrates:
     * :confval:`config.pageTitleSeparator <config-pageTitleSeparator>`
 
-This produces a title tag with the content "website . page title":
+This produces a title tag with the format "website . page title":
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
 
     config.pageTitleSeparator = .
 
-This produces a title tag with the content "website - page title":
+This produces a title tag with the format "website - page title":
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -1472,7 +1481,7 @@ This produces a title tag with the content "website - page title":
     config.pageTitleSeparator = -
     config.pageTitleSeparator.noTrimWrap = | | |
 
-This produces a title tag with the content "website*page title":
+This produces a title tag with the format "website*page title":
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -1480,7 +1489,7 @@ This produces a title tag with the content "website*page title":
     config.pageTitleSeparator = *
     config.pageTitleSeparator.noTrimWrap = |||
 
-If you want to remove the web page title from the displayed title, choose a separator that is not included in the web page title.
+If you want to remove the web page title from the title, choose a separator that is not included in the web page title.
 Then split the title from that character and return the second part only:
 
 ..  code-block:: typoscript
@@ -1518,7 +1527,6 @@ Spam protect email addresses automatically
 ------------------------------------------
 
 Demonstrates:
-
     * :confval:`config.spamProtectEmailAddresses <config-spamProtectEmailAddresses>`
     * :confval:`config.spamProtectEmailAddresses_atSubst <config-spamProtectEmailAddresses_atSubst>`
     * :confval:`config.spamProtectEmailAddresses_lastDotSubst <config-spamProtectEmailAddresses_lastDotSubst>`
@@ -1566,6 +1574,6 @@ Demonstrates:
         typolinkLinkAccessRestrictedPages_addParams = &return_url=###RETURN_URL###&pageId=###PAGE_ID###
     }
 
-Will create a link to page with id 29 and add GET parameters where the
-return URL and original page id is a part of it. Additionally, a CSS
+Will create a link to the page with id 29 and add GET parameters with
+the return URL and original page id. Additionally, CSS
 class "restricted" is added to the anchor tag.
diff --git a/Documentation/TopLevelObjects/Index.rst b/Documentation/TopLevelObjects/Index.rst
index 71440a0ec..803ecfe38 100644
--- a/Documentation/TopLevelObjects/Index.rst
+++ b/Documentation/TopLevelObjects/Index.rst
@@ -7,7 +7,7 @@
 Top-level objects
 =================
 
-As described in the :ref:`TypoScript syntax introduction <t3coreapi:typoscript-syntax-introduction>`
+As described in the :ref:`TypoScript syntax introduction <typoscript-syntax>`
 TypoScript templates are converted into a multidimensional PHP array.
 You can view this in the TypoScript object browser. Top level
 objects are located on the top level. Top level objects are for
@@ -27,7 +27,6 @@ page | ...                            :ref:`PAGE <page-datatype>`
 config                                :ref:`CONFIG <config-datatype>`
 :ref:`plugin`
 :ref:`tlo-module`
-:ref:`temp <tlo-temp>`
 :ref:`styles <tlo-styles>`
 :ref:`lib <tlo-lib>`
 :ref:`tt_* <tlo-tt>`
@@ -35,12 +34,10 @@ config                                :ref:`CONFIG <config-datatype>`
 :ref:`sitetitle <tlo-sitetitle>`      readonly
 ===================================== =========================
 
-
 ..  toctree::
     :hidden:
 
-    Config
+    PageAndConfig
     Module
-    Page/Index
     Plugin
     Other
diff --git a/Documentation/TopLevelObjects/Module.rst b/Documentation/TopLevelObjects/Module.rst
index 30147f20a..d9a16a6ae 100644
--- a/Documentation/TopLevelObjects/Module.rst
+++ b/Documentation/TopLevelObjects/Module.rst
@@ -18,12 +18,12 @@ settings should be done globally and not changed on a per-page basis.
 Therefore they are usually done in the file
 :ref:`EXT:my_extension/ext_typoscript_setup.typoscript <t3coreapi:ext_typoscript_setup_typoscript>`.
 
-..  versionchanged:: 12.0
+..  note::
     All Core extensions, and in general all extensions
-    that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
+    that switched to the :ref:`simplified backend templating <changelog:feature-96812>`
     no longer use the frontend TypoScript based override approach. This has been
     superseded by a general override strategy based on TSconfig:
-    :ref:`templates <t3tsconfig:pagetemplates>`.
+    :ref:`templates <pagetemplates>`.
 
 ..  _module-options:
 
@@ -33,7 +33,7 @@ Options for simple backend modules
 ..  warning::
     It is strongly recommended not to use TypoScript in custom **backend modules**, for example
     :typoscript:`module.tx_myextension`. Use custom
-    :ref:`Page TSconfig in namespace tx_* <t3tsconfig:page-tsconfig-extension-namespace>`
+    :ref:`Page TSconfig in namespace tx_* <page-tsconfig-extension-namespace>`
     instead.
 
 The configuring backend modules via frontend TypoScript
@@ -77,12 +77,12 @@ view.templateRootPaths
     :name: module-view-templateRootPaths
     :type: file path with :ref:`stdWrap <stdwrap>`
 
-    ..  versionchanged:: 12.0
+    ..  note::
         All Core extensions, and in general all extensions
         that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
         no longer use the frontend TypoScript based override approach. This has been
         superseded by a general override strategy based on TSconfig:
-        :ref:`templates <t3tsconfig:pagetemplates>`.
+        :ref:`templates <pagetemplates>`.
 
     Used to define several paths for templates, which are executed in reverse
     order (the paths are searched from bottom to top). The first folder where
@@ -115,12 +115,12 @@ view.partialRootPaths
     :name: module-view-partialRootPaths
     :type: file path with :ref:`stdWrap <stdwrap>`
 
-    ..  versionchanged:: 12.0
+    ..  note::
         All Core extensions, and in general all extensions
         that switch to the :ref:`simplified backend templating <changelog:feature-96812>`
         no longer use the frontend TypoScript based override approach. This has been
         superseded by a general override strategy based on TSconfig:
-        :ref:`templates <t3tsconfig:pagetemplates>`.
+        :ref:`templates <pagetemplates>`.
 
     Used to define several paths for partials, which will be executed in reverse
     order. The first folder where the desired partial is found, is used. The
diff --git a/Documentation/TopLevelObjects/Other.rst b/Documentation/TopLevelObjects/Other.rst
index c8dafaba8..cdfbd4a26 100644
--- a/Documentation/TopLevelObjects/Other.rst
+++ b/Documentation/TopLevelObjects/Other.rst
@@ -8,45 +8,6 @@ Reserved top-level objects
 ..  contents:: List of the reserved top-level objects
     :depth: 1
 
-..  index:: Top-level objects; temp
-
-..  _top-level-objects-temp:
-..  _tlo-temp:
-
-temp
-====
-
-..  confval:: temp
-    :name: tlo-temp
-
-    This top-level object name is reserved.
-
-    The top-level object :typoscript:`temp` is used to store and copy
-    TypoScript code during parse time.
-
-    :typoscript:`temp` is unset before the template is cached, objects in it
-    can therefore not be referenced. Use :confval:`tlo-lib` for that purpose.
-
-Example: Use the top-level object `temp` to copy code
------------------------------------------------------
-
-..  code-block:: typoscript
-    :caption: EXT:my_sitepackage/Configuration/TypoScript/setup.typoscript
-
-    temp.some_content = TEXT
-    temp.some_content.value = Hello World!
-
-    // Output
-    // <h1>Hello World!</h1><p>Hello World!</p>
-    page = PAGE
-    page {
-        10 < temp.some_content
-        10.wrap = <h1>|</h1>
-
-        20 < temp.some_content
-        20.wrap = <p>|</p>
-    }
-
 ..  index:: Top-level objects; lib
 
 ..  _top-level-objects-lib:
@@ -64,10 +25,8 @@ lib
     TypoScript code.
 
     This top-level object is available after the template is cached,
-    objects in it can therefore be referenced by using the 
-    :ref:`reference operator <t3coreapi:typoscript-syntax-syntax-object-referencing>` :typoscript:`=<`.
-    Just like with a :confval:`tlo-temp` object copying is
-    also possible.
+    objects in it can therefore be referenced and copied by using the
+    :ref:`reference operator <typoscript-syntax-syntax-object-referencing>` :typoscript:`=<`.
 
 ..  code-block:: typoscript
     :caption: EXT:my_sitepackage/Configuration/TypoScript/setup.typoscript
@@ -97,8 +56,7 @@ styles
 ..  confval:: styles
     :name: tlo-styles
 
-    This top-level object name is reserved. It works just like :confval:`tlo-temp`.
-    It is preserved for historic reasons, use :confval:`tlo-temp` instead.
+    This top-level object name is reserved.
 
 ..  index:: Top-level objects; tt_content
 ..  _tlo-tt:
diff --git a/Documentation/TopLevelObjects/Page/Index.rst b/Documentation/TopLevelObjects/Page/Index.rst
index 58750d548..186ef9075 100644
--- a/Documentation/TopLevelObjects/Page/Index.rst
+++ b/Documentation/TopLevelObjects/Page/Index.rst
@@ -1,19 +1,22 @@
+:navigation-title: Page
+
 ..  include:: /Includes.rst.txt
 ..  index::
-   PAGE
-   Top-level objects; page
+    PAGE
+    Top-level objects; page
 ..  _page:
 ..  _page-datatype:
 ..  _object-type-page:
 
-====
-PAGE
-====
+
+================================
+`PAGE` object type in TypoScript
+================================
 
 This defines what is rendered in the frontend.
 
-PAGE is an object type. A good habit is to use :typoscript:`page` as the top-level object name for
-the content-page on a website.
+PAGE is an object type. A good habit is to use :typoscript:`page` as
+the top-level object name for the main `PAGE` object of a website.
 
 TYPO3 does not initialize :typoscript:`page` by default. You must initialize this
 explicitly, for example:
@@ -31,9 +34,20 @@ page is found.
 Most of this code is executed in the PHP script
 :php:`\TYPO3\CMS\Frontend\Http\RequestHandler`.
 
-..  contents:: Table of contens
+..  contents:: Table of contents
     :depth: 1
 
+..  _page-getting-started:
+
+Getting started with the PAGE object
+====================================
+
+See :ref:`PAGE in TypoScript (Getting started), <guide-page>` for an
+introduction into this object.
+
+If no `PAGE` object is found, the error "No page configured for type=0." is
+displayed. See chapter :ref:`Troubleshooting <t3tsref:guide-troubleshooting>`.
+
 ..  _page_output:
 
 Output of the PAGE object
@@ -134,6 +148,8 @@ These are just recommendations. However, especially the name page for the conten
 is very common and most documentation will imply that your main page object is called page.
 
 ..  index:: PAGE; Properties
+..  _setup-page-bodytag:
+..  _setup-page-bodytagadd:
 ..  _setup-page-bodytagcobject:
 ..  _setup-page-config:
 ..  _setup-page-cssinline:
@@ -156,8 +172,6 @@ is very common and most documentation will imply that your main page object is c
 ..  _setup-page-stdwrap:
 ..  _setup-page-typenum:
 ..  _setup-page-wrap:
-..  _setup-page-bodytagadd:
-..  _setup-page-bodytag:
 ..  _setup-page-array:
 ..  _page_properties:
 
@@ -193,7 +207,7 @@ Properties
 
     ..  confval:: bodyTag
         :name: page-bodyTag
-        :type: :ref:`data-type-tag`
+        :type: string
         :Default: `<body>`
         :Example: :ref:`Set a class on the body tag <setup-page-bodytag-example>`
 
@@ -212,11 +226,12 @@ Properties
         :name: page-bodyTagCObject
         :type: cObject
 
-        This is the default body tag. It is overridden by :ref:`setup-page-bodyTag`,
+        This is the default body tag. It is overridden by :ref:`confval-page-bodytag`,
         if that is set.
 
-        ..  note::  Additionally to the body tag properties noted here,
-            there also is the property :ref:`setup-config-disableBodyTag`,
+        ..  note::  
+            Additionally to the body tag properties noted here,
+            there also is the property :confval:`config.disableBodyTag <config-disableBodyTag>`,
             which, if set, disables body tag generation independently
             from what might be set here.
 
@@ -259,12 +274,12 @@ Properties
         Inserts custom content in the head section of the website.
 
         While you can also use this to include stylesheet references or JavaScript,
-        you should better use :ref:`page.includeCSS <setup-page-includecss-array>`
-        and :ref:`page.includeJS <setup-page-includejs-array>` for such files.
+        you should better use :confval:`page.includeCSS <page-includeCSS>`
+        and :confval:`page.includeJS <page-includeJS>` for such files.
         Features like file concatenation and file compression will not work on files,
         which are included using :typoscript:`headerData`.
 
-        For meta tags, use the dedicated configuration :ref:`page.meta <meta>`.
+        For meta tags, use the dedicated configuration :confval:`page.meta <page-meta>`.
 
         By default, gets inserted after all the style definitions.
 
@@ -273,7 +288,7 @@ Properties
 
     ..  confval:: headTag
         :name: page-headTag
-        :type: :ref:`data-type-tag` / :ref:`stdwrap`
+        :type: string / :ref:`stdwrap`
         :Default: `<head>`
 
         Head-tag if alternatives are wanted
@@ -326,8 +341,6 @@ Properties
         `title`
             Setting the title of the :html:`<style>` tag.
 
-        ..  versionadded:: 12.1
-
         Additional data attributes can be configured using a key-value list.
 
     ..  confval:: includeCSSLibs.[array]
@@ -374,8 +387,6 @@ Properties
         `title`
             Setting the title of the :html:`<style>` tag.
 
-        ..  versionadded:: 12.1
-
         Additional data attributes can be configured using a key-value list.
 
     ..  confval:: includeJS.[array]
@@ -444,8 +455,6 @@ Properties
             resources externalized to CDN's. See `SRI <https://www.w3.org/TR/SRI/>`_ for
             more details. Integrity hashes may be generated using `<https://srihash.org/>`_.
 
-        ..  versionadded:: 12.1
-
         `data`
             Array with key/value for additional attributes to be added to
             the script tag.
@@ -454,9 +463,9 @@ Properties
         :name: page-includeJSFooter
         :type: :ref:`data-type-resource`
 
-        Add JavaScript files to footer (after files set in :ref:`includeJSFooterlibs <setup-page-includejsfooterlibs-array>`)
+        Add JavaScript files to footer (after files set in :confval:`includeJSFooterlibs <page-includeJSFooterlibs>`)
 
-        Same as :ref:`includeJS <setup-page-includejs-array>` above, except that this block gets
+        Same as :confval:`includeJS <page-includeJS>` above, except that this block gets
         included at the bottom of the page (just before the closing :html:`</body>`
         tag).
 
@@ -466,15 +475,15 @@ Properties
 
         Add JavaScript library files to footer.
 
-        Same as :ref:`includeJSLibs <setup-page-includejslibs-array>`, except that this block gets
+        Same as :confval:`includeJSLibs <page-includeJSLibs>`, except that this block gets
         included at the bottom of the page (just before the closing :html:`</body>`
         tag).
 
-        The optional properties from :ref:`includeJS <setup-page-includejs-array>`
+        The optional properties from :confval:`includeJS <page-includeJS>`
         can be applied.
 
         Currently one difference between :typoscript:`includeJS` and :typoscript:`includeJSFooterlibs` exists:
-        There is no :typoscript:`data`-array as optional parameter but all keys not explicitly mentioned as parameters are used as additional attributes - behaviour is the same as in :ref:`includeCSS <setup-page-includecss-array>`.
+        There is no :typoscript:`data`-array as optional parameter but all keys not explicitly mentioned as parameters are used as additional attributes - behaviour is the same as in :confval:`includeCSS <page-includeCSS>`.
 
         ..  code-block:: typoscript
             :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -492,15 +501,15 @@ Properties
 
         Adds JavaScript library files to head of page.
 
-        Same as :ref:`includeJSFooterlibs <setup-page-includejsfooterlibs-array>`, except that this block gets
+        Same as :confval:`includeJSFooterlibs <page-includeJSFooterlibs>`, except that this block gets
         included inside :html:`<head>`.
         tag).
 
-        The optional properties from :ref:`includeJS <setup-page-includejs-array>`
+        The optional properties from :confval:`includeJS <page-includeJS>`
         can be applied.
 
         Currently one difference between :typoscript:`includeJS` and :typoscript:`includeJSLibs` exists:
-        There is no :typoscript:`data`-array as optional parameter but all keys not explicitly mentioned as parameters are used as additional attributes - behaviour is the same as in :ref:`includeCSS <setup-page-includecss-array>`.
+        There is no :typoscript:`data`-array as optional parameter but all keys not explicitly mentioned as parameters are used as additional attributes - behaviour is the same as in :confval:`includeCSS <page-includeCSS>`.
 
         ..  code-block:: typoscript
             :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
@@ -591,9 +600,14 @@ Properties
 
         For each key the following sub-properties are available:
 
+        `attribute`
+            Sets the attribute for the meta tag. If it is not defined, the
+            default :html:`name` is used.
+
         `httpEquivalent`
             If set to 1, the :html:`http-equiv` attribute is used in the meta
             tag instead of the :html:`name` attribute. Default: 0.
+
         `replace`
             If set to 1, the tag will replace the one set earlier by a plugin. If set
             to 0 (default), the meta tag generated by the plugin will be used. If
@@ -923,7 +937,7 @@ Example: Make a cObject available in JavaScript
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Demonstrates:
-    * :confval:`page.jsFooterInline <page-jsFooterInline>`
+    * :confval:`page.jsInline <page-jsInline>`
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
diff --git a/Documentation/TopLevelObjects/PageAndConfig.rst b/Documentation/TopLevelObjects/PageAndConfig.rst
new file mode 100644
index 000000000..79362415d
--- /dev/null
+++ b/Documentation/TopLevelObjects/PageAndConfig.rst
@@ -0,0 +1,52 @@
+:navigation-title: page & config
+
+..  include:: /Includes.rst.txt
+..  _page-config:
+
+===============================================
+`page` and `config` on the TypoScript top level
+===============================================
+
+By convention the main rendering of a page (page type 0) is configured in a top
+level object called `page`. It is of type
+`PAGE <https://docs.typo3.org/permalink/t3tsref:object-type-page>`_.
+
+The main TypoScript configuration is always done in a top level object called
+`config`. It is of type
+`CONFIG <https://docs.typo3.org/permalink/t3tsref:top-level-objects-config>`_.
+
+..  contents:: Table of Contents
+
+..  _top-level-objects-page:
+
+The 'page' top-level-object
+=============================
+
+The `page` object should be of type `PAGE <https://docs.typo3.org/permalink/t3tsref:object-type-page>`_
+with property :ref:`typeNum <t3tsref:confval-page-typenum>` (also called page type)
+set to `0`, which is the default.
+
+Some site package authors decide to give the main `PAGE <https://docs.typo3.org/permalink/t3tsref:object-type-page>`_
+object a different top level name like `mypage`, however this can be confusing
+to subsequent integrators and not compatible with extensions that also make
+settings to the `page` top level object.
+
+TYPO3 does not initialize :typoscript:`page` by default. You must initialize this
+explicitly, for example:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/TypoScript/setup.typoscript
+
+    page = PAGE
+
+..  _top-level-objects-config-about:
+
+The 'config' top-level-object
+=============================
+
+Internally TYPO3 always creates an array `config` with various configuration
+values which are evaluated during the rendering process and treated in some
+special, predefined and predictive way. This is what we mean when we say the
+property `config`, actually the array `'config'` is of type CONFIG. It is a
+"top-level-object" because it is not subordinate to any other configuration
+setting.
diff --git a/Documentation/TopLevelObjects/Plugin.rst b/Documentation/TopLevelObjects/Plugin.rst
index a5606a8fd..252a98b34 100644
--- a/Documentation/TopLevelObjects/Plugin.rst
+++ b/Documentation/TopLevelObjects/Plugin.rst
@@ -102,8 +102,6 @@ plugins.
         :type: :ref:`data-type-string`
         :Example: :ref:`Ignore certain FlexForm settings if empty <setup-plugin-configuration-ignoreFlexFormSettingsIfEmpty-example>`
 
-        ..  versionadded:: 12.3
-
         Define :ref:`FlexForm <t3coreapi:flexforms>` settings that will be
         ignored in the extension settings merge process, if their value is
         considered empty (either an empty string or a string containing `0`).
@@ -227,6 +225,45 @@ plugins.
         Same as :ref:`setup-plugin-mvc-callDefaultActionIfActionCantBeResolved`
         but this will raise a "page not found" error.
 
+    ..  confval:: mvc.showPageNotFoundIfTargetNotFoundException
+        :name: plugin-mvc-showPageNotFoundIfTargetNotFoundException
+        :type: :ref:`data-type-boolean`
+        :Default: `false`
+
+        **Only for Extbase plugins**. By default, when calling an extbase controller action
+        that is not registered for an Extbase plugin, a fatal exception
+        :php:`TargetNotFoundException` is thrown
+        (usually an internal error message is shown).
+
+        When this configuration option is set to `1` (true), instead the default
+        "Page not Found" page will be shown instead (with a 404 HTTP header by default).
+
+        The configuration option can be either set on the global `config.tx_extbase`
+        scope, or also plugin-specific via
+        `plugin.tx_yourextension.mvc.showPageNotFoundIfTargetNotFoundException` /
+        `plugin.tx_yourextension_pluginName.mvc.showPageNotFoundIfTargetNotFoundException`.
+
+    ..  confval:: mvc.showPageNotFoundIfRequiredArgumentIsMissingException
+        :name: plugin-mvc-showPageNotFoundIfRequiredArgumentIsMissingException
+        :type: :ref:`data-type-boolean`
+        :Default: `false`
+
+        **Only for Extbase plugins**. By default, when calling an extbase controller action
+        with missing/invalid required arguments a fatal exception :php:`RequiredArgumentMissingException`
+        is thrown (usually an internal error message is shown).
+
+        When this configuration option is set to `1` (true), instead the default
+        "Page not Found" page will be shown instead (with a 404 HTTP header by default).
+
+        The configuration option can be either set on the global `config.tx_extbase`
+        scope, or also plugin-specific via
+        `plugin.tx_yourextension.mvc.showPageNotFoundIfRequiredArgumentIsMissingException` /
+        `plugin.tx_yourextension_pluginName.mvc.showPageNotFoundIfRequiredArgumentIsMissingException`.
+
+        Note that extension authors can also implement the Controller method
+        :php:`ActionController->handleArgumentMappingExceptions()` to individually operate
+        on invalid arguments.
+
     ..  confval:: format
         :name: plugin-format
         :type: :ref:`data-type-string`
diff --git a/Documentation/UserTsconfig/Auth.rst b/Documentation/UserTsconfig/Auth.rst
new file mode 100644
index 000000000..4cb66bf7f
--- /dev/null
+++ b/Documentation/UserTsconfig/Auth.rst
@@ -0,0 +1,92 @@
+..  include:: /Includes.rst.txt
+..  index:: Backend; Redirect after login
+..  _user-auth:
+
+====
+auth
+====
+
+The `auth` key is used for configuration of authentication services.
+
+..  contents::
+    :depth: 2
+
+..  _user-auth-properties:
+
+Properties
+==========
+
+..  confval-menu::
+    :name: auth
+    :display: table
+    :type:
+
+..  _user-auth-be-redirectToURL:
+
+..  confval:: auth.BE.redirectToURL
+    :name: user-auth-be-redirectToURL
+    :type: string
+
+    Specifies a URL to redirect to after login is performed in the backend login form. This
+    has been used in the past to redirect a backend user to the frontend to use frontend editing.
+
+..  _user-auth-mfa-required:
+
+..  confval:: auth.mfa.required
+    :name: user-auth-mfa-required
+    :type: boolean
+
+    Require multi-factor authentication for a user. This overrules the global configuration
+    and can therefore also be used to unset the requirement by using `0` as value.
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/user.tsconfig
+
+        auth.mfa.required = 1
+
+..  _user-auth-mfa-disableProviders:
+
+..  confval:: auth.mfa.disableProviders
+    :name: auth.mfa.disableProviders
+    :type: string, comma separated list of strings
+    :Example: :ref:`user-auth-mfa-disableProviders-example`
+
+    Disable multi-factor authentication providers for the current user or group.
+    It overrules the configuration from the Backend usergroup "Access List". This
+    means, if a provider is allowed in "Access List" but disallowed with TSconfig,
+    it will be disallowed for the user or user group.
+
+..  _user-auth-mfa-recommendedProvider:
+
+..  confval:: auth.mfa.recommendedProvider
+    :name: auth.mfa.recommendedProvider
+    :type: string
+    :Example: :ref:`user-auth-mfa-recommendedProvider-example`
+
+    Set a recommended multi-factor authentication provider on a per user or user group basis, which overrules
+    the global configuration.
+
+..  _user-auth-mfa-example:
+
+Examples
+========
+
+..  _user-auth-mfa-disableProviders-example:
+
+Example: Disable a multi-factor authentication provider
+-------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    auth.mfa.disableProviders := addToList(totp)
+
+..  _user-auth-mfa-recommendedProvider-example:
+
+Example: Set a recommended multi-factor authentication provider
+---------------------------------------------------------------
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    auth.mfa.recommendedProvider = totp
diff --git a/Documentation/UserTsconfig/Index.rst b/Documentation/UserTsconfig/Index.rst
new file mode 100644
index 000000000..bd6c27e30
--- /dev/null
+++ b/Documentation/UserTsconfig/Index.rst
@@ -0,0 +1,25 @@
+..  include:: /Includes.rst.txt
+..  index:: User TSconfig
+..  _usertsconfig:
+..  _usertoplevelobjects:
+
+=======================
+User TSconfig reference
+=======================
+
+The User TSconfig uses several *top level keys*. Their details are listed below.
+
+The most important section is the :ref:`useroptions` part.
+
+..  toctree::
+    :maxdepth: 5
+    :titlesonly:
+
+    admPanel (EXT:adminpanel) <https://docs.typo3.org/c/typo3/cms-adminpanel/main/en-us/Configuration/Index.html#user-tsconfig-settings>
+    Auth
+    Options
+    Page
+    Permissions
+    Setup
+    TcaDefaults
+    Tx
diff --git a/Documentation/UserTsconfig/Options.rst b/Documentation/UserTsconfig/Options.rst
new file mode 100644
index 000000000..d76439ac8
--- /dev/null
+++ b/Documentation/UserTsconfig/Options.rst
@@ -0,0 +1,1065 @@
+..  include:: /Includes.rst.txt
+..  index:: User TSconfig; Options
+..  _useroptions:
+
+=======
+options
+=======
+
+Various options for the user affecting the Core at various points.
+
+As an example, this enables the :guilabel:`Flush frontend caches` button in the
+upper right toolbar cache menu for non-admin users:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    options.clearCache.pages = 1
+
+..  _useroptions-properties:
+
+Properties
+==========
+
+..  confval-menu::
+    :name: useroptions
+    :display: table
+    :type:
+    :Default:
+
+    ..  _useroptions-additionalPreviewLanguages:
+
+    ..  confval:: additionalPreviewLanguages
+        :name: useroptions-additionalPreviewLanguages
+        :type: list of sys_language IDs
+
+        ..  todo:: How does this work with site configurations?
+
+        The user will see these additional languages when localizing stuff in
+        TCEforms. The list are IDs of site languages, as defined in the
+        :yaml:`languageId` property of the
+        :ref:`site configuration <t3coreapi:sitehandling-addingLanguages>`.
+
+
+    ..  _useroptions-alertPopups:
+
+    ..  confval:: alertPopups
+        :name: useroptions-alertPopups
+        :type: bitmask
+        :Default: 255 (show all warnings)
+
+        Configure which Javascript popup alerts have to be displayed and which not:
+
+        *   1 – onTypeChange
+        *   2 – copy / move / paste
+        *   4 – delete
+        *   8 – FE editing
+        *   128 – other (not used yet)
+
+
+    ..  _useroptions-bookmarkGroups:
+
+    ..  confval:: bookmarkGroups
+        :name: useroptions-bookmarkGroups
+        :type: Array of integers / strings
+
+        Set groups of bookmarks that can be accessed by the user. This affects the
+        bookmarks toolbar item in the top right of the backend.
+
+        By default, 5 default groups will be defined globally (shared, can
+        only be set by admins) and also for each user (personal bookmarks):
+
+        1.  Pages
+        2.  Records
+        3.  Files
+        4.  Tools
+        5.  Miscellaneous
+
+        Set 0 to disable one of these group IDs, 1 to enable it (this is the
+        default) or "string" to change the label accordingly.
+
+        Example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            bookmarkGroups {
+              1 = 1
+              2 = My Group
+              3 = 0
+              4 =
+            }
+
+        Bookmark group 1 is loaded with the default label (Pages), group 2 is
+        loaded and labeled as "My Group" and groups 3 and 4 are disabled.
+        Group 5 has not been set, so it will be displayed by default, just
+        like group 1.
+
+        ..  versionadded:: 11.0
+
+        Custom language labels can also be used instead of a fixed label:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            bookmarkGroups {
+              2 = LLL:EXT:sitepackage/Resources/Private/Language/locallang_be.xlf:bookmarkGroups.2
+            }
+
+    ..  _useroptions-clearCache:
+
+    ..  confval:: clearCache
+        :name: useroptions-clearCache
+
+        ..  _useroptions-clearCache-all:
+
+        ..  confval:: all
+            :name: useroptions-clearCache-all
+            :type: boolean
+            :Default: 0
+            :Path: options.clearCache.all
+
+            This will allow a non-admin user to clear frontend and page-related caches,
+            plus some backend-related caches (that is everything including templates);
+            if it is explicitly set to 0 for an admin user, it will remove the clear all
+            option on toolbar for that user.
+
+        ..  _useroptions-clearCache-pages:
+
+        ..  confval:: pages
+            :name: useroptions-clearCache-pages
+            :type: boolean
+            :Default: 0
+            :Path: options.clearCache.pages
+
+            If set to 1, this will allow a non-admin user to clear frontend and
+            page-related caches.
+
+    ..  _useroptions-clipboardNumberPads:
+
+    ..  confval:: clipboardNumberPads
+        :name: useroptions-clipboardNumberPads
+        :type: integer (0-20)
+        :Default: 3
+
+        This allows you to enter how many pads you want on the clipboard.
+
+    ..  _useroptions-contextMenu-key-disableItems:
+
+    ..  confval:: contextMenu.table.[tableName][.context].disableItems
+        :name: useroptions-contextMenu-key-disableItems
+        :type: list of items
+
+        List of :ref:`context menu <t3coreapi:context-menu>` ("clickmenu") items to
+        disable.
+
+        ..  figure:: /Images/ManualScreenshots/List/PagesContextMenu.png
+            :alt: Context menu of the page tree
+            :class: with-shadow
+
+            Context menu of the page tree
+
+        The :typoscript:`[tableName]` refers to the type of the record (database
+        table name) the context menu is shown for, for example, :sql:`pages`,
+        :sql:`sys_file`, :sql:`tt_content`, etc.
+
+        The optional key :typoscript:`[.context]` refers to the place from which the
+        context menu is triggered. The Core uses just one context called `tree` for
+        context menus triggered from page tree and folder tree. This way you can
+        disable certain options for one context, but keep them for another.
+
+        Items to disable for "page" type are:
+
+        *   :typoscript:`view`
+        *   :typoscript:`edit`
+        *   :typoscript:`new`
+        *   :typoscript:`info`
+        *   :typoscript:`copy`
+        *   :typoscript:`copyRelease`
+        *   :typoscript:`cut`
+        *   :typoscript:`cutRelease`
+        *   :typoscript:`pasteAfter`
+        *   :typoscript:`pasteInto`
+        *   :typoscript:`newWizard`
+        *   :typoscript:`pagesSort`
+        *   :typoscript:`pagesNewMultiple`
+        *   :typoscript:`openListModule`
+        *   :typoscript:`mountAsTreeRoot`
+        *   :typoscript:`hideInMenus`
+        *   :typoscript:`showInMenus`
+        *   :typoscript:`permissions`
+        *   :typoscript:`enable`
+        *   :typoscript:`disable`
+        *   :typoscript:`delete`
+        *   :typoscript:`history`
+        *   :typoscript:`clearCache`
+
+        Items to disable for "sys_file" type (that is files/folders) are:
+
+        *   :typoscript:`edit`
+        *   :typoscript:`rename`
+        *   :typoscript:`upload`
+        *   :typoscript:`new`
+        *   :typoscript:`info`
+        *   :typoscript:`copy`
+        *   :typoscript:`copyRelease`
+        *   :typoscript:`cut`
+        *   :typoscript:`cutRelease`
+        *   :typoscript:`pasteInto`
+        *   :typoscript:`delete`
+
+        When the system extension Import/Export (EXT:impexp) is installed then two
+        more options become available:
+
+        *   :typoscript:`exportT3d`
+        *   :typoscript:`importT3d`
+
+        Example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            # Remove "New" and "Create New wizard" for pages context menu (list module)
+            options.contextMenu.table.pages.disableItems = new,newWizard
+
+            # Remove "New" and "Create New wizard" in page tree context menu
+            options.contextMenu.table.pages.tree.disableItems = new,newWizard
+
+            # Remove the "More options" item in the page tree context menu and all its subelements
+            options.contextMenu.table.pages.tree.disableItems = newWizard, pagesSort, pagesNewMultiple, openListModule, mountAsTreeRoot, exportT3d, importT3d, hideInMenus, showInMenus, permissions
+
+    ..  _useroptions-dashboard:
+
+    ..  confval:: dashboard
+        :name: useroptions-dashboard
+
+        ..  _useroptions-dashboard-dashboardPresetsForNewUsers:
+
+        ..  confval:: dashboardPresetsForNewUsers
+            :name: useroptions-dashboard-dashboardPresetsForNewUsers
+            :type: list of dashboard identifiers
+            :Default: default
+            :Path: options.dashboard.dashboardPresetsForNewUsers
+
+            List of dashboard identifiers to be used on initial dashboard module access.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.dashboard.dashboardPresetsForNewUsers := addToList(customDashboard)
+
+    ..  _useroptions-defaultResourcesViewMode:
+
+    ..  confval:: defaultResourcesViewMode
+        :name: useroptions-defaultResourcesViewMode
+        :type: `list` or `tiles`
+        :Default: `tiles`
+
+        The option :typoscript:`options.defaultResourcesViewMode` has
+        been introduced, which allows to define the initial display mode. Valid
+        values are therefore `list` and `tiles`, e.g.:
+
+        The listing of resources in the TYPO3 Backend, e.g. in the
+        :guilabel:`File > Filelist` module or the `FileBrowser` can be changed
+        between `list` and `tiles`. TYPO3 serves by default `tiles`, if the user
+        has not already made a choice.
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            options.defaultResourcesViewMode = list
+
+    ..  _useroptions-defaultUploadFolder:
+
+    ..  confval:: defaultUploadFolder
+        :name: useroptions-defaultUploadFolder
+        :type: string
+
+        When a user uploads files they are stored in the default upload folder
+        of the first file storage that user may access. The folder is used for
+        uploads in the TCEforms fields. In general, this will be
+        :file:`fileadmin/user_upload/`.
+
+        With this property it is possible to set a specific upload folder.
+
+        The syntax is "storage_uid:file_path".
+
+        ..  note::
+            It is also possible to set a default upload folder for a page via
+            :ref:`page TSconfig <pagedefaultuploadfolder>`.
+
+        Example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            options.defaultUploadFolder = 2:user_folders/my_folder/
+
+    ..  _useroptions-disableDelete:
+
+    ..  confval:: disableDelete
+        :name: useroptions-disableDelete
+        :type: boolean
+
+        Disables the :guilabel:`Delete` button in TCEFORMs.
+
+        Note, it is possible to set this for single tables using
+        :typoscript:`options.disableDelete.<tableName>`. Any value set for a single
+        table will override the default value set for :typoscript:`disableDelete`.
+
+        Example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            options.disableDelete.tt_content = 1
+
+    ..  _useroptions-dontMountAdminMounts:
+
+    ..  confval:: dontMountAdminMounts
+        :name: useroptions-dontMountAdminMounts
+        :type: boolean
+
+        This options prevents the root to be mounted for an admin user.
+
+        ..  note::
+            Only for admin users. For other users it has no effect.
+
+    ..  _useroptions-enableBookmarks:
+
+    ..  confval:: enableBookmarks
+        :name: useroptions-enableBookmarks
+        :type: boolean
+        :Default: 1
+
+        Enables the usage of bookmarks in the backend.
+
+    ..  _useroptions-file_list:
+
+    ..  confval:: file_list
+        :name: useroptions-file_list
+
+        ..  _useroptions-file_list-enableClipBoard:
+
+        ..  confval:: enableClipBoard
+            :name: useroptions-enableClipBoard
+            :type: list of keywords
+            :Default: selectable
+            :Path: options.file_list.enableClipBoard
+
+            Determines whether the checkbox :guilabel:`Show clipboard` in the file list
+            module is shown or hidden. If it is hidden, you can predefine it to be
+            always activated or always deactivated.
+
+            The following values are possible:
+
+            :typoscript:`activated`
+                The option is activated and the checkbox is hidden.
+
+            :typoscript:`deactivated`
+                The option is deactivated and the checkbox is hidden.
+
+            :typoscript:`selectable`
+                The checkbox is shown so that the option can be selected by the user.
+
+        ..  _useroptions-file_list-displayColumnSelector:
+
+        ..  confval:: displayColumnSelector
+            :name: useroptions-file_list-displayColumnSelector
+            :type: boolean
+            :Default: true
+            :Path: options.file_list.displayColumnSelector
+
+            The column selector is enabled by default and can be disabled with this
+            option. The column selector is displayed at the top of each file list.
+
+            It can be used to manage the fields displayed for each file / folder,
+            while containing convenience actions such as "filter", "check all / none"
+            and "toggle selection".
+
+            The fields to be selected are a combination of special fields, such as
+            `references` or `read/write` permissions, the corresponding :sql:`sys_file`
+            record fields, as well as all available :sql:`sys_file_metadata` fields.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                # Disable the column selector
+                file_list.displayColumnSelector = 0
+
+        ..  _useroptions-file_list-enableDisplayThumbnails:
+
+        ..  confval:: file_list.enableDisplayThumbnails
+            :name: useroptions-file_list-enableDisplayThumbnails
+            :type: list of keywords
+            :Default: selectable
+
+            Determines whether the checkbox :guilabel:`Display thumbnails` in the
+            file list module is shown or hidden. If it is hidden, you can predefine it
+            to be always activated or always deactivated.
+
+            The following values are possible:
+
+            :typoscript:`activated`
+                The option is activated and the checkbox is hidden.
+
+            :typoscript:`deactivated`
+                The option is deactivated and the checkbox is hidden.
+
+            :typoscript:`selectable`
+                The checkbox is shown so that the option can be selected by the user.
+
+        ..  _useroptions-file_list-filesPerPage:
+
+        ..  confval:: filesPerPage
+            :name: useroptions-file_list-filesPerPage
+            :type: integer
+            :Default: 40
+            :Path: options.file_list.filesPerPage
+
+            The maximum number of files shown per page in the :guilabel:`File > List`
+            module.
+
+        ..  _useroptions-file_list-primaryActions:
+
+
+        ..  confval:: primaryActions
+            :name: useroptions-useroptions-file_list-primaryActions
+            :type: string
+            :Default: :typoscript:`view,metadata,translations,delete`
+            :Path: options.file_list.primaryActions
+
+            Option to add more primary actions to the list view,
+            which are otherwise only accessible through the "..." menu in the file list
+            module.
+
+            The list of actions to be displayed can be given in the TSConfig of
+            the backend user. The actions that can be set are
+
+            *   :typoscript:`copy`
+            *   :typoscript:`cut`
+            *   :typoscript:`delete`
+            *   :typoscript:`download`
+            *   :typoscript:`edit`
+            *   :typoscript:`info`
+            *   :typoscript:`metadata`
+            *   :typoscript:`paste`
+            *   :typoscript:`rename`
+            *   :typoscript:`replace`
+            *   :typoscript:`translations` (always active)
+            *   :typoscript:`updateOnlineMedia`
+            *   :typoscript:`upload`
+            *   :typoscript:`view`
+
+            Example:
+
+            ..  code-block:: tsconfig
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                # This will add "copy", "cut" and "replace" buttons in addition to the three default
+                # buttons. "translations" can be omitted, as it will be added by default,
+                # if a TYPO3 site is set up multilingual.
+                options.file_list.primaryActions = view,metadata,delete,copy,cut,replace
+
+            ..  figure:: /Images/ManualScreenshots/List/FileListPrimaryActions.png
+                :alt: Show primary action with additional copy, cut and replace buttons
+                :class: with-shadow
+
+                See option `primaryActions` with three default buttons and the three
+                additional buttons "copy", "cut" and "replace". As there is no TYPO3
+                site set up multilingual the button "translations" is not rendered in
+                that TYPO3 environment.
+
+        ..  _useroptions-file_list-thumbnail-height:
+
+        ..  confval:: thumbnail.height
+            :name: useroptions-file_list-thumbnail-height
+            :type: integer
+            :Default: 64
+            :Path: options.file_list.thumbnail.height
+
+            All preview images in the file list will be rendered with the configured
+            thumbnail height.
+
+        ..  _useroptions-file_list-thumbnail-width:
+
+        ..  confval:: thumbnail.width
+            :name: useroptions-file_list-thumbnail-width
+            :type: integer
+            :Default: 64
+            :Path: options.file_list.thumbnail.width
+
+            All preview images in the file list will be rendered with the configured
+            thumbnail width.
+
+        ..  _useroptions-file_list-uploader-defaultaction:
+
+        ..  confval:: uploader.defaultAction
+            :name: useroptions-file_list-uploader-defaultaction
+            :type: string
+            :Default: :typoscript:`Cancel`
+            :Path: options.file_list.uploader.defaultAction
+
+            Default action for the modal that appears when during file upload a name
+            collision occurs. Possible values:
+
+            :typoscript:`cancel`
+                Abort the action.
+
+            :typoscript:`rename`
+                Append the file name with a numerical index.
+
+            :typoscript:`replace`
+                Override the file with the uploaded one.
+
+    ..  confval:: folderTree
+        :name: useroptions-folderTree
+
+        ..  _useroptions-folderTree-altElementBrowserMountPoints:
+
+        ..  confval:: altElementBrowserMountPoints
+            :name: useroptions-folderTree-altElementBrowserMountPoints
+            :type: list of "storageUid:folderName" items
+            :Path: options.folderTree.altElementBrowserMountPoints
+
+            Sets alternative filemounts for use in any folder tree, including in the
+            :guilabel:`File > List` module, in the element browser and in file
+            selectors.
+
+            Each item consists of storage UID followed by a colon
+            and the folder name inside that storage. Separate multiple items by
+            a comma.
+
+            For backwards compatibility, defining only a folder name but no
+            storage uid and colon prepended is still supported. Folders
+            without a storage UID prepended are assumed to be located in the default
+            storage, which by default is the :file:`fileadmin/` folder. If a folder
+            you specify does not exist it will not get mounted.
+
+            Settings this option is effective in
+            :ref:`workspaces <t3coreapi:workspaces>` too.
+
+            The alternative file mounts are added to the existing ones defined in
+            the user or group configuration.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.folderTree.altElementBrowserMountPoints = _temp_/, 2:/templates, 1:/files/images
+
+        ..  _useroptions-folderTree-uploadFieldsInLinkBrowser:
+
+        ..  confval:: uploadFieldsInLinkBrowser
+            :name: useroptions-folderTree-uploadFieldsInLinkBrowser
+            :type: integer
+            :Default: 3
+            :Path: options.folderTree.uploadFieldsInLinkBrowser
+
+            This value defines the number of upload fields in the element browser.
+            Default value is 3, if set to 0, no upload form will be shown.
+
+    ..  _useroptions-hideModules:
+
+    ..  confval:: hideModules
+        :name: useroptions-hideModules
+        :type: list of module groups or modules
+
+        Configure which module groups or modules should be hidden from the main menu.
+
+        ..  attention::
+            It is not an access restriction but makes defined modules invisible.
+            This means that in principle these modules can still be accessed if the
+            rights allow this.
+
+        ..  hint::
+            A list of all available module groups and modules can be found in in the
+            backend module :guilabel:`System > Configuration > Backend Modules`. The
+            system extension "lowlevel" has to be available for accessing this list.
+
+        Example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            # Hide only module groups "file" and "help"
+            options.hideModules = file, help
+
+            # Hide additional modules "info" and "ts" from the "web" group
+            options.hideModules := addToList(web_info, web_ts)
+
+            # Hide only module BeLogLog from "system" group
+            options.hideModules = system_BelogLog
+
+    ..  _useroptions-hideRecords:
+
+    ..  confval:: hideRecords
+
+        ..  _useroptions-hideRecords-pages:
+
+        ..  confval:: pages
+            :name: useroptions-hideRecords-pages
+            :type: list of page IDs
+            :Path: options.hideRecords.pages
+
+            This setting hides records in the backend user interface. It is not an
+            access restriction but makes defined records invisible. That means in
+            principle those records can still be edited if the user rights allow.
+            This makes sense if only a specialized module should be used to edit those
+            otherwise hidden records.
+
+            This option is currently implemented for the pages table only and has an
+            effect in the following places:
+
+            *   Page tree navigation frame
+            *   :guilabel:`Web > List` module
+            *   New record wizard
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.hideRecords.pages = 12,45
+
+    ..  _useroptions-impexp:
+
+    ..  confval:: impexp
+        :name: useroptions-impexp
+
+        ..  _useroptions-impexp-enableExportForNonAdminUser:
+
+        ..  confval:: enableExportForNonAdminUser
+            :name: useroptions-impexp-enableExportForNonAdminUser
+            :type: boolean
+            :Default: 0
+            :Path: options.impexp.enableExportForNonAdminUser
+
+            ..  note::
+                This option was introduced to avoid `information disclosure
+                <https://typo3.org/security/advisory/typo3-core-sa-2022-001>`__.
+
+            The import/export module of `EXT:impexp` is disabled by default for
+            non-admin users. Enable this option, if non-admin users need to use the
+            module and export data. This should only be enabled for trustworthy
+            backend users, as it might impose a security risk.
+
+        ..  _useroptions-impexp-enableImportForNonAdminUser:
+
+        ..  confval:: enableImportForNonAdminUser
+            :name: useroptions-impexp-enableImportForNonAdminUser
+            :type: boolean
+            :Default: 0
+            :Path: options.impexp.enableImportForNonAdminUser
+
+            ..  note::
+                This option was introduced to avoid `information disclosure <https://typo3.org/article/typo3-core-sa-2016-015>`__.
+
+            The import/export module of `EXT:impexp` is disabled by default for
+            non-admin users. Enable this option, if non-admin users need to use the
+            module and import data. This should only be enabled for trustworthy
+            backend users, as it might impose a security risk.
+
+    ..  _useroptions-mayNotCreateEditBookmarks:
+
+    ..  confval:: mayNotCreateEditBookmarks
+        :name: useroptions-mayNotCreateEditBookmarks
+        :type: boolean
+
+        If set, the user can not create or edit bookmarks.
+
+
+    ..  _useroptions-noThumbsInEB:
+
+    ..  confval:: noThumbsInEB
+        :name: useroptions-noThumbsInEB
+        :type: boolean
+
+        If set, then image thumbnails are not shown in the element browser.
+
+    ..  _useroptions-overridePageModule:
+
+
+    ..  _useroptions-pageTree:
+
+    ..  confval:: pageTree
+        :name: useroptions-pageTree
+
+        ..  confval:: overridePageModule
+            :name: useroptions-pageTree-overridePageModule
+
+            ..  versionchanged:: 13.0
+                This setting has been removed.
+
+            In order to replace the :guilabel:`Web > Page` module within a third-party
+            extension, such as TemplaVoila, it is possible to create a custom module entry
+            in an extension's :file:`Configuration/Backend/Modules.php` with the following
+            entry:
+
+            ..  code-block:: php
+                :caption: EXT:my_extension/Configuration/Backend/Modules.php
+
+                return [
+                    'my_module' => [
+                        'parent' => 'web',
+                        'position' => ['before' => '*'],
+                        'access' => 'user',
+                        'aliases' => ['web_layout'],
+                        'path' => '/module/my_module',
+                        'iconIdentifier' => 'module-page',
+                        'labels' => 'LLL:EXT:backend/Resources/Private/Language/locallang_mod.xlf',
+                        'routes' => [
+                            '_default' => [
+                                'target' => \MyVendor\MyExtension\Controller\MyController::class . '::mainAction',
+                            ],
+                        ],
+                    ],
+                ];
+
+        ..  _useroptions-pageTree-altElementBrowserMountPoints:
+
+        ..  confval:: altElementBrowserMountPoints
+            :name: useroptions-pageTree-altElementBrowserMountPoints
+            :type: list of integers
+            :Path: options.pageTree.altElementBrowserMountPoints
+
+            Sets alternative webmounts for use in the element browser. You
+            separate page IDs by a comma. Non-existing page IDs are ignored. If
+            you insert a non-integer it will evaluate to "0" (zero) and the root
+            of the page tree is mounted. Effective in
+            :ref:`workspaces <t3coreapi:workspaces>` too.
+
+            These alternative webmounts **replace** configured DB mount points
+            unless you use the
+            :ref:`altElementBrowserMountPoints.append <useroptions-pageTree-altElementBrowserMountPoints-append>`
+            option.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.pageTree.altElementBrowserMountPoints = 34,123
+
+
+        ..  _useroptions-pageTree-altElementBrowserMountPoints-append:
+
+        ..  confval:: altElementBrowserMountPoints.append
+            :name: useroptions-pageTree-altElementBrowserMountPoints-append
+            :type: boolean
+            :Path: options.pageTree.altElementBrowserMountPoints.append
+
+            This option allows administrators to add additional mount points
+            in the RTE and the wizard element browser instead of replacing
+            the configured database mount points of the user when using the
+            existing user TSconfig option.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.pageTree.altElementBrowserMountPoints = 34,123
+                options.pageTree.altElementBrowserMountPoints.append = 1
+
+        ..  _useroptions-pageTree-backgroundColor:
+
+        ..  confval:: backgroundColor
+            :name: useroptions-pageTree-backgroundColor
+            :type: string
+            :Path: options.pageTree.backgroundColor
+
+            ..  deprecated:: 13.1
+                This setting has been deprecated and will be removed in TYPO3 v14 due to its
+                lack of accessibility. It is being replaced with a
+                :ref:`new label system <useroptions-pageTree-label>` for tree nodes.
+
+            In TYPO3 v13 the setting will be migrated to the new label system. Since the
+            use case is unknown, the generated label will be "Color: <value>". This
+            information will be displayed on all affected nodes.
+
+            Set background colors for tree branches.
+
+            The color can be any valid CSS color value. The best results can be achieved
+            by using RGBa values.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                # The syntax is:
+                # options.pageTree.backgroundColor.<pageId> = <color>
+                options.pageTree.backgroundColor.147 = orange
+                options.pageTree.backgroundColor.148 = #AFAFAF
+                options.pageTree.backgroundColor.151 = rgba(0, 255, 0, 0.1)
+
+            ..  figure:: /Images/ManualScreenshots/List/optionsPageTreeBackgroundColor.png
+                :alt: Tree branches with configured background colors
+                :class: with-shadow
+
+                Tree branches with configured background colors
+
+        ..  _useroptions-pageTree-doktypesToShowInNewPageDragArea:
+
+        ..  confval:: doktypesToShowInNewPageDragArea
+            :name: useroptions-pageTree-doktypesToShowInNewPageDragArea
+            :type: string
+            :Default: 1,6,4,7,3,254,255,199
+            :Path: options.pageTree.doktypesToShowInNewPageDragArea
+
+            If set, the node top panel feature can be configured by a comma-separated
+            list. Each number stands for a :ref:`doktype ID <t3coreapi:list-of-page-types>`
+            that should be added to the node top panel.
+
+            ..  figure:: /Images/ManualScreenshots/List/PanelNormal.png
+                :alt: Top panel in normal mode
+                :class: with-shadow
+
+                Top panel in normal mode
+
+            ..  figure:: /Images/ManualScreenshots/List/PanelModified.png
+                :alt: Top panel modified
+                :class: with-shadow
+
+                Top panel modified
+
+        ..  _useroptions-pageTree-excludeDoktypes:
+
+        ..  confval:: excludeDoktypes
+            :name: useroptions-pageTree-excludeDoktypes
+            :type: list of integers
+            :Path: options.pageTree.excludeDoktypes
+
+            Excludes nodes (pages) with one of the defined
+            :ref:`doktypes <t3coreapi:list-of-page-types>` from the page tree.
+            Can be used, for example, for hiding
+            :ref:`custom doktypes <t3coreapi:page-types-example>`.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:site_package/Configuration/user.tsconfig
+
+                options.pageTree.excludeDoktypes = 254,1
+
+        ..  _useroptions-pageTree-label:
+
+        ..  confval:: label.<page-id>
+            :name: useroptions-pageTree-label
+            :type: list of page IDs
+            :Path: options.pageTree.label.<page-id>
+
+            ..  versionadded:: 13.1
+                This setting is the successor of :ref:`useroptions-pageTree-backgroundColor`.
+
+            Labels offer customizable color markings for tree nodes and require an
+            associated label for accessibility.
+
+            Example:
+
+            ..  code-block:: typoscript
+                :caption: EXT:my_extension/Configuration/user.tsconfig
+
+                options.pageTree.label.296 {
+                  label = Campaign A
+                  color = #ff8700
+                }
+
+            Display:
+
+            ..  figure:: /Images/ManualScreenshots/List/optionsPageTreeLabel.png
+                :alt: Page with configured color and label
+                :class: with-shadow
+
+                Page with configured color and label
+
+            ..  note::
+                Only one label per page can be set through this method. Use the
+                PSR-14 event :ref:`t3coreapi:AfterPageTreeItemsPreparedEvent` to assign
+                multiple labels to a page.
+
+        ..  todo:: does this still work with site configuration?
+        ..  _useroptions-pageTree-showDomainNameWithTitle:
+
+        ..  confval:: showDomainNameWithTitle
+            :name: useroptions-pageTree-showDomainNameWithTitle
+            :type: boolean
+            :Path: options.pageTree.showDomainNameWithTitle
+
+            If set, the domain name will be appended to the page title for
+            pages that have :guilabel:`Is root of web site?` checked in the page properties.
+            Useful if there are several domains in one page tree.
+
+
+        ..  _useroptions-pageTree-showNavTitle:
+
+        ..  confval:: showNavTitle
+            :name: useroptions-pageTree-showNavTitle
+            :type: boolean
+            :Path: options.pageTree.showNavTitle
+
+            If set, the navigation title is displayed in the page navigation tree
+            instead of the normal page title. The page title is shown in a
+            tooltip if the mouse hovers the navigation title.
+
+
+        ..  _useroptions-pageTree-showPageIdWithTitle:
+
+        ..  confval:: showPageIdWithTitle
+            :name: useroptions-pageTree-showPageIdWithTitle
+            :type: boolean
+            :Path: options.pageTree.showPageIdWithTitle
+
+            If set, the titles in the page tree will have their ID numbers printed
+            before the title.
+
+
+        ..  _useroptions-pageTree-showPathAboveMounts:
+
+        ..  confval:: showPathAboveMounts
+            :name: useroptions-pageTree-showPathAboveMounts
+            :type: boolean
+            :Path: options.pageTree.showPathAboveMounts
+
+            If set, the user db mount path above the mount itself is shown.
+            This is useful if you work a lot with user db mounts.
+
+            ..  figure:: /Images/ManualScreenshots/List/PanelUserDB.png
+                :alt: Active user db mount
+                :class: with-shadow
+
+                Active user db mount
+
+    ..  _useroptions-passwordReset:
+
+    ..  confval:: passwordReset
+        :name: useroptions-passwordReset
+        :type: boolean
+        :Default: 1
+
+        If set to `0` the initiating of the password reset in the backend
+        will be disabled. This does not affect the password reset by
+        CLI command.
+
+        To completely disable the password reset in the backend for all users, you
+        can set the user TSconfig globally in your :file:`Configuration/user.tsconfig`:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            options.passwordReset = 0
+
+        If required, this setting can be overridden on a per user basis
+        in the corresponding :guilabel:`TSconfig` field of the backend
+        usergroup or user.
+
+        The password reset functionality can also be disabled globally by setting:
+
+        ..  code-block:: php
+            :caption: config/system/settings.php | typo3conf/system/settings.php
+
+            $GLOBALS['TYPO3_CONF_VARS']['BE']['passwordReset'] = false
+
+    ..  _useroptions-saveClipboard:
+
+    ..  confval:: saveClipboard
+        :name: useroptions-saveClipboard
+        :type: boolean
+
+        If set, the clipboard content will be preserved for the next login.
+        Normally the clipboard content lasts only during the session.
+
+
+    ..  _useroptions-saveDocNew:
+
+    ..  confval:: saveDocNew
+        :name: useroptions-saveDocNew
+        :type: boolean / "top"
+        :Default: 1
+
+        If set, a button :guilabel:`Save and create new` will appear in TCEFORMs.
+
+        Note, it is possible to set this for single tables using
+        :typoscript:`options.saveDocNew.[tableName]`.
+        Any value set for a single table will override the default value set for
+        :typoscript:`saveDocNew`.
+
+        Example:
+
+        In this example the button is disabled for all tables, except
+        :sql:`tt_content` where it will appear, and in addition create the records
+        in the top of the page (default is after instead of top).
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            options.saveDocNew = 0
+            options.saveDocNew.tt_content = top
+
+    ..  _useroptions-saveDocView:
+
+    ..  confval:: saveDocView
+        :name: useroptions-saveDocView
+        :type: boolean
+        :Default: 1
+
+        If set, a button :guilabel:`Save and view` will appear in TCEFORMs.
+
+        Note, it is possible to set this for single tables using
+        :typoscript:`options.saveDocView.[tableName]`.
+        Any value set for a single table will override the default value set for
+        :typoscript:`saveDocView`.
+
+    ..  _useroptions-showDuplicate:
+
+    ..  confval:: showDuplicate
+        :name: useroptions-showDuplicate
+        :type: boolean
+        :Default: 0
+
+        If set, a button :guilabel:`Duplicate` will appear in TCEFORMs.
+
+        Note, that it is possible to set this for single tables using
+        :typoscript:`options.showDuplicate.[tableName]`.
+        Any value set for a single table will override the default value set for
+        :typoscript:`showDuplicate`.
+
+
+    ..  _useroptions-showHistory:
+
+    ..  confval:: showHistory
+        :name: useroptions-showHistory
+        :type: boolean
+
+        Shows link to the history for the record in TCEFORMs.
+
+        Note, it is possible to set this for single tables using
+        :typoscript:`options.showHistory.[tableName]`.
+        Any value set for a single table will override the default value set for
+        :typoscript:`showHistory`.
+
+    ..  confval:: hideSets
+        :name: useroptions-hideSets
+        :type: comma separated list
+
+        Hides existing :ref:`Site sets <t3coreapi:site-sets>` from the list of available
+        sets for backend users, in case only a curated list of sets
+        shall be selectable:
+
+        ..  code-block:: typoscript
+            :caption: EXT:my_extension/Configuration/user.tsconfig
+
+            options.sites.hideSets := addToList(typo3/fluid-styled-content)
+
+        The :guilabel:`Site Management > Sites` GUI will not show hidden sets,
+        but makes one exception if a hidden set has already been applied to a site
+
+        In this case a set
+        marked as hidden will be shown in the list of currently activated sets (that means
+        it can be introspected and removed via backend UI).
diff --git a/Documentation/UserTsconfig/Page.rst b/Documentation/UserTsconfig/Page.rst
new file mode 100644
index 000000000..f0ddce1b2
--- /dev/null
+++ b/Documentation/UserTsconfig/Page.rst
@@ -0,0 +1,18 @@
+..  include:: /Includes.rst.txt
+..  index:: user TSconfig; Overrider page TSconfig
+..  _user-page:
+
+====
+page
+====
+
+Override any page TSconfig property on a user or group basis by prefixing
+the according property path with `page.`. Find more information about this
+in the :ref:`Using and setting <user-override-modify-values>` section.
+
+Example:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    page.TCEMAIN.table.pages.disablePrependAtCopy = 1
diff --git a/Documentation/UserTsconfig/Permissions.rst b/Documentation/UserTsconfig/Permissions.rst
new file mode 100644
index 000000000..2032c8b10
--- /dev/null
+++ b/Documentation/UserTsconfig/Permissions.rst
@@ -0,0 +1,25 @@
+..  include:: /Includes.rst.txt
+..  index:: File permissions
+..  _userTsConfigPermissions:
+
+===========
+permissions
+===========
+
+Set permissions on a user or group basis. This is especially useful for access permissions on files and
+folders as part of the :ref:`Digital assets management (FAL) <t3coreapi:fal>` of the core.
+
+Read more about FAL access permissions in the :ref:`permission chapter <t3coreapi:fal-administration-permissions-user>`
+of the core API document, but find some examples below:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    # Allow to create and upload files on all storages
+    permissions.file.default.addFile = 1
+
+    # Allow to add new folders if user has write permissions on parent folder
+    permissions.file.default.addFolder = 1
+
+    # Allow to edit contents of files on FAL storage with uid 1
+    permissions.file.storage.1.writeFile = 1
diff --git a/Documentation/UserTsconfig/Setup.rst b/Documentation/UserTsconfig/Setup.rst
new file mode 100644
index 000000000..8d76a9cbe
--- /dev/null
+++ b/Documentation/UserTsconfig/Setup.rst
@@ -0,0 +1,183 @@
+..  include:: /Includes.rst.txt
+..  index::
+    User settings; override
+    User settings; default
+..  _usersetup:
+..  _user-setup:
+
+=====
+setup
+=====
+
+Default values and override values for the :guilabel:`User Settings` module.
+
+The :guilabel:`User > User settings` module may only represent a subset of the options from the table below.
+
+..  figure:: /Images/ManualScreenshots/UserSettings/UserSettings.png
+    :alt: Default values and overriding values in the "User > User settings" module
+
+    Default values and overriding values in the :guilabel:`User > User settings` module
+
+The following properties are available:
+
+..  _user-setup-properties:
+
+Properties
+==========
+
+..  confval-menu::
+    :name: user-setup
+    :display: table
+    :type:
+    :Default:
+
+    ..  _user-setup-default:
+
+    ..  confval:: setup.default.[someProperty]
+        :name: user-setup-default
+        :type: any
+
+        With this property you can set *default* values. In case a backend user may override these settings
+        using its :guilabel:`User Settings` module the default settings will be overridden
+        for this specific backend user. To change the defaults for users with this
+        property only affects *new* users who did not login yet. It is usually not
+        possible to set new defaults for users who already logged in, at least once.
+        The only way to apply new defaults to existing users is by :guilabel:`Reset Backend User Preferences`
+        in the :guilabel:`Admin tools > Maintenance` section of the install tool.
+
+        ..  literalinclude:: _Setup/_user-setup-default.tsconfig
+            :language: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+    ..  _user-setup-override:
+
+    ..  confval:: setup.override.[someProperty]
+        :name: user-setup-override
+        :type: mixed
+
+        This forces values for the properties of the list below, a user can not override these
+        setting in its :guilabel:`User settings` module. So, overriding values will be impossible for the
+        user to change himself and no matter what the current value is, the overriding
+        value will overrule it.
+
+        ..  attention::
+            There is a tricky aspect to these `setup.override`: If first you have set a
+            value by `setup.override` and then remove it again, you will experience
+            that the value persists to exist. This is because it is saved in the
+            backend user's profile. Therefore, if you have once set a value, do
+            *not* remove it again but rather set it blank if you want to disable
+            the effect again!
+
+    ..  _user-setup-fields-fieldName-disabled:
+
+    ..  confval:: setup.fields.[fieldName].disabled
+        :name: user-setup-fields-fieldName-disabled
+        :type: boolean
+
+        On top of being able to set default values or override them, it is also possible to
+        hide fields in the :guilabel:`User Settings` module, using `setup.fields.[fieldName].disabled = 1`.
+        You can find the names of the fields in the :guilabel:`Configuration` module by browsing the "User Settings" array, example:
+
+        ..  code-block:: typoscript
+            :caption: EXT:site_package/Configuration/user.tsconfig
+
+            # Do not show the 'emailMeAtLogin' field to the user in "User Settings" module
+            setup.fields.emailMeAtLogin.disabled = 1
+
+            # And force the value of this field to be set to 1
+            setup.override.emailMeAtLogin = 1
+
+    ..  index::  User settings; Format of window title in backend
+
+    ..  _user-setup-backendTitleFormat:
+
+    ..  confval:: backendTitleFormat
+        :name: user-setup-backendTitleFormat
+        :type: string
+
+        Format of window title in backend. Possible values:
+
+        `titleFirst`
+            [title] · [sitename]
+        `sitenameFirst`
+            [sitename] · [title]
+
+
+    ..  index:: User settings; Copy levels
+
+    ..  _user-setup-copyLevels:
+
+    ..  confval:: copyLevels
+        :name: user-setup-copyLevels
+        :type: positive integer
+
+        Recursive Copy: Enter the number of page sub-levels to include, when a page is copied
+
+
+    ..  index:: File upload; In doc module
+
+    ..  _user-setup-edit-docModuleUpload:
+
+    ..  confval:: edit_docModuleUpload
+        :name: user-setup-edit-docModuleUpload
+        :type: boolean
+
+        Allow file upload directly from file reference fields within backend forms.
+
+        ..  note::
+            The uploaded file will be stored in the default upload folder,
+            see :ref:`user TSconfig <useroptions-defaultUploadFolder>` and :ref:`page TSconfig <pagedefaultuploadfolder>`
+
+    ..  _user-setup-emailMeAtLogin:
+
+    ..  confval:: emailMeAtLogin
+        :name: user-setup-emailMeAtLogin
+        :type:  boolean
+
+        Notify me by email, when somebody logs into my account
+
+    ..  _user-setup-lang:
+
+    ..  confval:: lang
+        :name: user-setup-lang
+        :type: language-key
+
+        One of the language keys. For current options see
+        :ref:`t3coreapi:i18n_languages`, for example `dk`, `de`, `es` etc.
+
+    ..  _user-setup-neverHideAtCopy:
+
+    ..  confval:: neverHideAtCopy
+        :name: user-setup-neverHideAtCopy
+        :type: boolean
+
+        If set, then the hideAtCopy feature for records in TCE will not be used.
+
+    ..  _user-setup-showHiddenFilesAndFolders:
+
+    ..  confval:: showHiddenFilesAndFolders
+        :name: user-setup-showHiddenFilesAndFolders
+        :type: boolean
+
+        If set, hidden files and folders will be shown in the filelist.
+
+    ..  _user-setup-startModule:
+
+    ..  confval:: startModule
+        :name: user-setup-startModule
+        :type: string
+
+        Name of the module that is called when the user logs into the backend, for
+        example `web_layout`, `web_list`, `web_view`, `web_info`, `web_ts` etc.
+
+    ..  _user-setup-titleLen:
+
+    ..  confval:: titleLen
+        :name: user-setup-titleLen
+        :type: positive integer
+
+        Maximum length of rendered record titles in the backend interface.
+        It is used in several places: page tree, edit masks, workspace module, etc.
+
+        ..  tip::
+            To find out where this setting is applied, set it to a low number.
diff --git a/Documentation/UserTsconfig/TcaDefaults.rst b/Documentation/UserTsconfig/TcaDefaults.rst
new file mode 100644
index 000000000..ba294c053
--- /dev/null
+++ b/Documentation/UserTsconfig/TcaDefaults.rst
@@ -0,0 +1,64 @@
+..  include:: /Includes.rst.txt
+..  index:: TCAdefaults
+..  highlight:: php
+..  _userTsTcaDefaults:
+
+===========
+TCAdefaults
+===========
+
+This allows to set or override the `default` values of `TCA` fields that is available
+for various TCA types, for instance for :ref:`type=input <t3tca:columns-input-properties-default>`.
+
+The full path of a setting include the table and the field name: `TCAdefaults.[table name].[field]`
+
+This key is also available on :ref:`Page TSconfig level <pageTsTcaDefaults>`, the order of default
+values when creating new records in the backend is this:
+
+#.  Value from :php:`$GLOBALS['TCA']`
+#.  Value from User TSconfig (these settings)
+#.  Value from :ref:`Page TSconfig <pageTsTcaDefaults>`
+#.  Value from "defVals" GET variables
+#.  Value from previous record based on 'useColumnsForDefaultValues'
+
+However the order for default values used by :php:`\TYPO3\CMS\Core\DataHandling\DataHandler` if a certain
+field is not granted access to for user will be:
+
+#.  Value from :php:`$GLOBALS['TCA']`
+#.  Value from User TSconfig (these settings)
+
+So these values will be authoritative if the user has no access to the field anyway.
+
+Example:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    # Show newly created pages by default
+    TCAdefaults.pages.hidden = 0
+
+..  attention::
+
+    This example will not work when creating the page from the context menu
+    since this is triggered by the values listed in the `ctrl` section of
+    :file:`typo3/sysext/core/Configuration/TCA/pages.php`:
+
+    ..  code-block:: php
+        :caption: typo3/sysext/core/Configuration/TCA/pages.php
+
+        'ctrl' => [
+          'useColumnsForDefaultValues' => 'doktype,fe_group,hidden',
+          ...
+        ]
+
+If 'hidden' is in the list, it gets overridden with the "neighbor" record value (see
+:php:`\TYPO3\CMS\Backend\Form\FormDataProvider\DatabaseRowInitializeNew::setDefaultsFromNeighborRow`)
+and as the value is set - usually to '0' - it will not be overridden
+again. To make it work as expected, that value must be overridden. This
+can be done for example in the :file:`Configuration/TCA/Overrides` folder
+of an extension:
+
+..  code-block:: php
+   :caption: EXT:site_package/Configuration/TCA/Overrides/pages.php
+
+   $GLOBALS['TCA']['pages']['ctrl']['useColumnsForDefaultValues'] = 'doktype,fe_group';
diff --git a/Documentation/UserTsconfig/Tx.rst b/Documentation/UserTsconfig/Tx.rst
new file mode 100644
index 000000000..6f3d2a265
--- /dev/null
+++ b/Documentation/UserTsconfig/Tx.rst
@@ -0,0 +1,16 @@
+..  include:: /Includes.rst.txt
+
+..  index::
+    user TSconfig; Extensions
+    user TSconfig; tx_*
+
+..  _user_tx:
+
+====
+tx_*
+====
+
+The `tx_` prefix key is not used in the core itself, and is just a
+reserved space for extensions to never collide with core options, a
+use case could be `tx_news` for the news extension. Extension developers
+should create a key like that: `tx_[extension key with no underscore]`
diff --git a/Documentation/UserTsconfig/_Setup/_user-setup-default.tsconfig b/Documentation/UserTsconfig/_Setup/_user-setup-default.tsconfig
new file mode 100644
index 000000000..c3fee4203
--- /dev/null
+++ b/Documentation/UserTsconfig/_Setup/_user-setup-default.tsconfig
@@ -0,0 +1,20 @@
+[backend.user.isAdmin]
+    # Some settings an administrator might find helpful
+    setup.default {
+        recursiveDelete = 1
+        copyLevels = 99
+        moduleData {
+            # Defaulting some options of the Template/TypoScript backend module
+            web_ts {
+                # Pre-select 'Object browser' instead of 'Constant editor'
+                function = TYPO3\CMS\Tstemplate\Controller\TypoScriptTemplateObjectBrowserModuleFunctionController
+                # Pre-select 'Setup' instead of 'Constants'
+                ts_browser_type = setup
+                # The other settings
+                ts_browser_const = subst
+                ts_browser_fixedLgd = 0
+                ts_browser_showComments = 1
+            }
+        }
+    }
+[END]
\ No newline at end of file
diff --git a/Documentation/UsingSetting/AddTypoScriptWithExtensions.rst b/Documentation/UsingSetting/AddTypoScriptWithExtensions.rst
index d5947f7d5..39714b2e3 100644
--- a/Documentation/UsingSetting/AddTypoScriptWithExtensions.rst
+++ b/Documentation/UsingSetting/AddTypoScriptWithExtensions.rst
@@ -1,10 +1,12 @@
+:navigation-title: TypoScript in Extensions
+
 ..  include:: /Includes.rst.txt
 ..  index:: TypoScript in extensions
 ..  _extdev-add-typoscript:
 
-================================
-Add TypoScript in your extension
-================================
+================================================
+Provide frontend TypoScript in a TYPO3 extension
+================================================
 
 ..  versionchanged:: 13.1
     TypoScript on a per-site basis can now be included via
@@ -18,8 +20,8 @@ Add TypoScript in your extension
 ..  index:: TypoScript in extensions; File locations
 ..  _extdev-add-typoscript-extension:
 
-Create TypoScript files in your extension
-=========================================
+Provide TypoScript in your extension or site package
+====================================================
 
 TypoScript files **must** have the ending :file:`.typoscript`.
 
@@ -28,10 +30,11 @@ extension. Read more about how to
 :ref:`provide the TypoScript as set for TYPO3 v13 and above <extdev-add-typoscript-sets>`
 and :ref:`how to provide TypoScript for both TYPO3 v13 and v12 <extdev-add-typoscript-sets-v12>`.
 
-*   :file:`constants.typoscript` contains the constants
-*   :file:`setup.typoscript` contains the TypoScript setup
+*   :file:`constants.typoscript` contains the frontend TypoScript constants
+*   :file:`setup.typoscript` contains the frontend TypoScript
 
 ..  _extdev-add-typoscript-sets:
+..  _extdev-add-typoscript-sets-typoscript:
 
 TypoScript provided as site set (only TYPO3 v13.1 and above)
 ============================================================
@@ -41,10 +44,6 @@ The file structure of the extension could, for example look like this:
 ..  directory-tree::
     :show-file-icons: true
 
-    *   Classes
-
-        *   ...
-
     *   Configuration
 
         *   Sets
@@ -93,84 +92,187 @@ The sub set for an optional feature
     :language: yaml
     :caption: EXT:my_extension/Configuration/Sets/MyExtensionWithACoolFeature/config.yaml
 
-..  _extdev-add-typoscript-sets-typoscript:
 
-TypoScript files provided by the sets
--------------------------------------
+..  _extdev-add-typoscript-sets-override:
+
+Overriding the TypoScript
+-------------------------
 
-The TypoScript placed in the same folder like the set, contains your
-configurations.
+The TypoScript provided in the site set will be loaded exactly once and respect
+the dependencies defined in the site set configuration. Therefore if you
+have to override the frontend TypoScript of another site set your site set
+should depend on the other site set:
 
+..  code-block:: yaml
+    :caption: packages/my_site_package/Configuration/Sets/MySitePackage/config.yaml
+
+    name: my-vendor/my-site-package
+    label: My Set
+    dependencies:
+      - my-vendor/my-other-set
+      - some-vendor/some-extension
+
+Your extension can then safely override frontend TypoScript of the `some_extension`,
+for example:
+
+..  code-block:: typoscript
+    :caption: packages/my_site_package/Configuration/Sets/MySitePackage/setup.typoscript
+
+    plugin.some_extension_pi1.settings.someSetting = Special setting
+
+..  _extdev-add-typoscript-sets-v12-static_includes:
+..  _extdev-static-includes:
 ..  _extdev-add-typoscript-sets-v12:
 
-TypoScript provided by extensions supporting TYPO3 v12.4 and v13
-================================================================
+Supporting both site sets and TypoScript records
+================================================
 
-When an extension provides TypoScript and should be compatible with both
-TYPO3 v12.4 and v13, you can provide site sets but still support including
-the TypoScript in the :sql:`sys_template` record via `static_file_include`'s.
+..  versionchanged:: 13.1
+    With TYPO3 13.1
+    `site sets as TypoScript provider <https://docs.typo3.org/permalink/t3coreapi:site-sets-typoscript>`_
+    where introduced. Existing extensions **should** support site sets as well as
+    TypoScript records for backward compatibility reasons.
+
+..  warning::
+    For historic reasons you might still see filenames like :file:`setup.ts` and
+    :file:`setup.txt`. These files **cannot** be included with the
+    :ref:`@import <t3tsref:typoscript-syntax-import>` syntax. All frontend
+    TypoScript files **must** end on `.typoscript`.
+
+.. _extension-configuration-typoscript-set-record-one:
+
+One TypoScript include set
+--------------------------
 
-The files in the sets are the same as in the
-:ref:`example for TYPO3 v13 only <extdev-add-typoscript-sets>`.
+If your extension supported one static file include you should provide the same
+files in your main site set as well:
 
-The extended file structure of the extension could, for example look like this:
+.. code-block:: php
+   :caption: EXT:my_extension/Configuration/TCA/Overrides/sys_template.php (before and after)
+
+   \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile(
+       'my_extension',
+       'Configuration/TypoScript/',
+       'Examples TypoScript'
+   );
+
+In your main site set provide the same files that where provided as includes
+by :php:`\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile`
+until now:
 
 ..  directory-tree::
+    :level: 3
     :show-file-icons: true
 
-    *   Classes
+    *   packages/my_extension/Configuration/
 
-        *   ...
+        *   Sets
 
-    *   Configuration
+            *   MySet
 
-        *   Sets
+                *   config.yaml
+                *   constants.typoscript
+                *   setup.typoscript
 
-            *   MyExtension
 
-                *   :ref:`config.yaml <extdev-add-typoscript-sets-main>`
-                *   :ref:`constants.typoscript <extdev-add-typoscript-sets-typoscript>`
-                *   :ref:`setup.typoscript <extdev-add-typoscript-sets-typoscript>`
+        *   TypoScript
 
-            *   MyExtensionWithACoolFeature
+            *   constants.typoscript
+            *   setup.typoscript
 
-                *   :ref:`config.yaml <extdev-add-typoscript-sets-feature>`
-                *   :ref:`setup.typoscript <extdev-add-typoscript-sets-typoscript>`
+..  code-block:: typoscript
+    :caption: packages/my_extension/Configuration/Sets/MySet/constants.typoscript
 
-        *   TCA
+    @import 'EXT:my_extension/Configuration/TypoScript/setup.typoscript'
 
-            *   Overrides
+..  code-block:: typoscript
+    :caption: packages/my_extension/Configuration/Sets/MySet/setup.typoscript
 
-                sys_template.php
+    @import 'EXT:my_extension/Configuration/TypoScript/setup.typoscript'
 
+.. _extension-configuration-typoscript-set-record-multiple:
 
-    *   Resources
+Multiple TypoScript include sets
+--------------------------------
 
-        *   ...
+If there should be more then one set of TypoScript templates that may be
+included, they were usually stored in sub folders of
+:path:`Configuration/TypoScript` until now.
 
-    *   composer.json
-    *   ...
+When introducing site sets usually one site set per TypoScript record include
+set is needed:
 
+..  directory-tree::
+    :level: 3
+    :show-file-icons: true
 
-..  _extdev-add-typoscript-sets-v12-static_includes:
-..  _extdev-static-includes:
+    *   packages/my_extension/Configuration
+
+            *   TypoScript
+
+                *   SpecialFeature1
+
+                    *   constants.typoscript
+                    *   setup.typoscript
 
-Only when supporting TYPO3 v12.4: Make TypoScript available for static includes
--------------------------------------------------------------------
+                *   SpecialFeature2
 
-Make TypoScript available for static includes (only needed if your extensions aims to support TYPO3 v12.4):
+                    *   setup.typoscript
 
-..  literalinclude:: _Sets/_TcaOverridesSystemplateV12.php
-    :language: php
-    :caption: EXT:my_extension/Configuration/TCA/Overrides/sys_template.php
+                *   constants.typoscript
+                *   setup.typoscript
 
-If you include the TypoScript this way, it will not be automatically loaded.
-You MUST load it by adding the static include in the :guilabel:`Web > Template`
-module in the backend, see :ref:`static-includes`. This has the advantage of
-better configurability.
+            *   Sets
 
-This will load your constants and your setup once the template is
-included statically.
+                *   MyMainSet
+
+                    *   config.yaml
+                    *   constants.typoscript
+                    *   setup.typoscript
+
+                *   MySpecialFeature1Set
+
+                    *   config.yaml
+                    *   constants.typoscript
+                    *   setup.typoscript
+
+                *   MySpecialFeature2Set
+
+                    *   config.yaml
+                    *   setup.typoscript
+
+For backward compability reasons :php:`ExtensionManagementUtility::addStaticFile`
+still needs to be called for each folder that should be available in the TypoScript
+template record:
+
+.. code-block:: php
+   :caption: EXT:my_extension/Configuration/TCA/Overrides/sys_template.php
+
+   \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile(
+       'my_extension',
+       'Configuration/TypoScript/',
+       'My Extension - Main TypoScript'
+   );
+
+   \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile(
+       'my_extension',
+       'Configuration/TypoScript/Example1/',
+       'My Extension - Additional example 1'
+   );
+
+   \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile(
+       'my_extension',
+       'Configuration/TypoScript/SpecialFeature2/',
+       'My Extension - Some special feature'
+   );
+
+Each site set then provides the TypoScript files the according location by
+importing it, for example:
+
+..  code-block:: typoscript
+    :caption: packages/my_extension/Configuration/Sets/MySet/setup.typoscript
+
+    @import 'EXT:my_extension/Configuration/TypoScript/MySpecialFeature2Set/setup.typoscript'
 
 ..  index:: TypoScript in extensions; Load always
 ..  _extdev-always-load:
@@ -178,18 +280,21 @@ included statically.
 Make TypoScript available (always load)
 =======================================
 
-Only do this, if your TypoScript must really be always loaded in your site.
-If this is not the case, use the method described in the previous section
-:ref:`extdev-add-typoscript-sets`.
+
+Use :php:`ExtensionManagementUtility::addTypoScript` if the frontend
+TypoScript **must** be available in backend modules without page context,
+for example to :ref:`register the YAML of the EXT:form system extension
+for the backend <typo3/cms-form:concepts-configuration-yamlregistration-backend>`.
 
 ..  literalinclude:: _Sets/_ext_localconf.php
-    :language: php
     :caption: EXT:my_extension/ext_localconf.php
 
-It is also possible to put your TypoScript in a file called
-:ref:`ext_typoscript_setup.typoscript <t3coreapi:ext_typoscript_setup_typoscript>`
-or :ref:`ext_typoscript_constants.typoscript <t3coreapi:ext_typoscript_constants_typoscript>`
-(for constants).
+..  warning::
+    While the content from the files
+    `ext_typoscript_setup.typoscript <https://docs.typo3.org/permalink/t3coreapi:ext_typoscript_setup_typoscript>`_
+    and `ext_typoscript_constants.typoscript <https://docs.typo3.org/permalink/t3coreapi:ext_typoscript_constants_typoscript>`_
+    is loaded by default in sites based on **TypoScript records** it is not
+    loaded in sites depending on **site sets as TypoScript providers**.
 
 
 More information
diff --git a/Documentation/UsingSetting/Constants.rst b/Documentation/UsingSetting/Constants.rst
index 5ff334d53..3f07d2028 100644
--- a/Documentation/UsingSetting/Constants.rst
+++ b/Documentation/UsingSetting/Constants.rst
@@ -7,19 +7,14 @@
 Constants
 =========
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
 ..  figure:: /Images/ManualScreenshots/TypoScriptModule/ConstantEditor.png
     :alt: Screenshot of the TYPO3 Backend showing the constant editor
 
     The :ref:`Constant Editor <constant-editor>` in the TYPO3 backend
 
-Constants are values defined in the  :guilabel:`Constants` field of a template.  They
+Constants are values defined in the :guilabel:`Constants` field of a template.  They
 follow the :ref:`syntax of ordinary TypoScript
-<t3coreapi:typoscript-syntax-syntax>` and are case sensitive! They are used to
+<typoscript-syntax>` and are case sensitive! They are used to
 manage *in a single place* values, which are later used in *several places*.
 
 ..  seealso::
@@ -145,14 +140,6 @@ replacement in green:
 ..  figure:: /Images/ManualScreenshots/TypoScriptModule/ConstantsInActiveTypoScript.png
     :alt: Screenshot of the Active TypoScript with constants substituted
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Active TypoScript` was renamed from
-    "TypoScript Object Browser".
-
 ..  note::
 
     The TypoScript constants are evaluated in this order:
diff --git a/Documentation/UsingSetting/Debugging.rst b/Documentation/UsingSetting/Debugging.rst
index df1a829f2..fe8c0c64a 100644
--- a/Documentation/UsingSetting/Debugging.rst
+++ b/Documentation/UsingSetting/Debugging.rst
@@ -19,14 +19,6 @@ to find errors within TypoScript.
 Analyzing defined constants
 ===========================
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Active TypoScript` was renamed from
-    "TypoScript Object Browser".
-
 The backend submodule :guilabel:`Site Management > TypoScript > Active TypoScript`
 provides a tree view to all defined TypoScript Constants on the currently active page.
 
@@ -41,18 +33,6 @@ provides a tree view to all defined TypoScript Constants on the currently active
 Finding errors
 ==============
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Active TypoScript` was renamed from
-    "TypoScript Object Browser". It does not display syntax warnings anymore,
-    those are displayed in the submodule :guilabel:`Included TypoScript` only.
-
-    The submodule :guilabel:`Included TypoScript` was renamed from
-    "TypoScript Analyzer".
-
 There are no tools that will tell whether the given TypoScript code is 100%
 correct. The :guilabel:`Included TypoScript` will warn about syntax errors though:
 
diff --git a/Documentation/UsingSetting/Entering.rst b/Documentation/UsingSetting/Entering.rst
index 60d5e3f42..3d5d991ce 100644
--- a/Documentation/UsingSetting/Entering.rst
+++ b/Documentation/UsingSetting/Entering.rst
@@ -1,4 +1,5 @@
 :navigation-title: Backend Module
+
 ..  include:: /Includes.rst.txt
 ..  index:: TypoScript; TypoScript backend module
 ..  _typoscript_module:
@@ -43,26 +44,48 @@ a TypoScript record or by having a
 
 If TypoScript was added by a record, it is linked.
 
+..  _typoscript-syntax-constant-editor:
+..  _constant-editor:
+
+Submodule "Constant Editor"
+===========================
+
+..  note::
+    The constant editor is only available in sites that are based on a
+    TypoScript record.
+
+..  versionchanged:: 13.3
+    With the introduction of the site
+    `Site settings editor <https://docs.typo3.org/permalink/t3coreapi:site-settings-editor>`_
+    settings can be edited in a comfortable and type safe way on site level.
+
+    The constant editor is kept for backward compatibility.
+
+The backend module :guilabel:`Site Management > TypoScript > Constant Editor`
+used a special format of
+`Comments <https://docs.typo3.org/permalink/t3tsref:typoscript-syntax-syntax-comment-blocks>`_
+to display a form for editing the constants.
+
+..  figure:: /Images/ManualScreenshots/TypoScriptModule/ConstantEditor.png
+    :alt: Screenshot of the TYPO3 Backend showing the constant editor
+
+It is not recommended to newly introduce constants in the constant editor.
+The documentation of the constant editors comment format can still be found
+at `Comment Syntax <https://docs.typo3.org/permalink/t3tsref:typoscript-syntax-constant-editor-comments@12.4>`_
+
+
 ..  _typoscript_module_edit:
 
 Submodule "Edit TypoScript Record"
 ==================================
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Edit TypoScript Record` was previously named
-    "Info / Modify".
+..  note::
+    The constant editor is only available in sites that are based on a
+    TypoScript record.
 
 This can be done in the :guilabel:`Site Management > TypoScript` module in
 the submodule :guilabel:`Edit TypoScript Record`.
 
-..  hint::
-    It is best practice to use a site package extension to bundle
-    various configuration in an extension. See :ref:`t3sitepackage:start`.
-
 ..  figure:: /Images/ManualScreenshots/TypoScriptModule/EditTypoScriptRecord.png
     :alt: The submodule "Edit TypoScript Record" in the TYPO3 Backend.
 
@@ -84,13 +107,13 @@ edited from the list module:
 Include TypoScript files
 ------------------------
 
-..  versionchanged:: 12.0
+..  note::
     Only the import of files ending on '.typoscript' or '.tsconfig' are
     supported. Importing legacy files with the legacy endings '.txt' or '.ts'
     **does not work**, even if their names are explicitly used in the import.
 
 In both the "Constants" and "Setup" fields, the
-:ref:`@import <t3coreapi:typoscript-syntax-includes>` syntax can be
+:ref:`@import <typoscript-syntax-includes>` syntax can be
 used to include TypoScript contained inside files:
 
 ..  code-block:: typoscript
@@ -117,14 +140,6 @@ Include TypoScript from extensions
     already supports site sets, those should be used instead of TypoScript
     includes in the record.
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Edit TypoScript Record` was previously named
-    "Info / Modify".
-
 It is also possible to "Include TypoScript sets" from extensions in the
 TypoScript record.
 
@@ -166,14 +181,6 @@ records (in the field called :guilabel:`Include TypoScript records`).
 Submodule "Included TypoScript"
 ===============================
 
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-    The submodule :guilabel:`Included TypoScript` was renamed from
-    "TypoScript Analyzer".
-
 With all those inclusions, it may happen that you lose the overview of the
 template structure. The submodule :guilabel:`Included TypoScript` provides
 an overview of this structure. It shows all the TypoScript files that apply to
diff --git a/Documentation/UsingSetting/Index.rst b/Documentation/UsingSetting/Index.rst
index d096eca6a..bd102accb 100644
--- a/Documentation/UsingSetting/Index.rst
+++ b/Documentation/UsingSetting/Index.rst
@@ -1,7 +1,9 @@
+:navigation-title: Usage
 ..  include:: /Includes.rst.txt
 ..  index:: TypoScript; Using and setting
 ..  _using-and-setting:
 
+============================
 Using and setting TypoScript
 ============================
 
@@ -12,17 +14,16 @@ Each template can include other (static) templates, which can again
 define values in their own :guilabel:`Constants` and :guilabel:`Setup` fields.
 
 The TypoScript template configuration can be viewed and edited in the
-:guilabel:`WEB > Template` module.
+:guilabel:`Site Management > TypoScript` module.
 
 ..  toctree::
     :maxdepth: 5
     :titlesonly:
 
     SiteTypoScriptProvider
-    Entering
     AddTypoScriptWithExtensions
+    Entering
     AccessTypoScriptWithExtensions
     Constants
-    TheConstantEditor
     Register
     Debugging
diff --git a/Documentation/UsingSetting/SiteTypoScriptProvider.rst b/Documentation/UsingSetting/SiteTypoScriptProvider.rst
index d2f939677..5e16b3dca 100644
--- a/Documentation/UsingSetting/SiteTypoScriptProvider.rst
+++ b/Documentation/UsingSetting/SiteTypoScriptProvider.rst
@@ -1,3 +1,5 @@
+:navigation-title: TypoScript in Sites
+
 ..  include:: /Includes.rst.txt
 ..  _typoscript-site-sets:
 
diff --git a/Documentation/UsingSetting/TheConstantEditor.rst b/Documentation/UsingSetting/TheConstantEditor.rst
deleted file mode 100644
index efe84cee8..000000000
--- a/Documentation/UsingSetting/TheConstantEditor.rst
+++ /dev/null
@@ -1,331 +0,0 @@
-..  include:: /Includes.rst.txt
-..  _typoscript-syntax-constant-editor:
-..  _constant-editor:
-
-===================
-The constant editor
-===================
-
-..  versionchanged:: 12.0
-    The TypoScript management tools are now found in backend module
-    :guilabel:`Site Management > TypoScript`. It was formerly found in
-    "Page > Template".
-
-It's possible to add comments in TypoScript. Comments are always ignored by the
-parser when the TypoScript is processed. But the backend module
-:guilabel:`Site Management > TypoScript`
-has the ability to use comments in the constant editor to make simple
-configuration of a template even easier than constants already make it
-themselves.
-
-..  figure:: /Images/ManualScreenshots/TypoScriptModule/ConstantEditor.png
-    :alt: Screenshot of the TYPO3 Backend showing the constant editor
-
-When the :guilabel:`Constant Editor` parses the TypoScript constants,
-*all* comments before every constant-definition are registered.
-
-A certain syntax is available to define
-what category the constant should be in, which type it has and to provide a
-description for the constant. Comments are bound to the constant in the next line. There must be no
-empty line between the comment defining a constant and the constant definition.
-
-..  code-block:: typoscript
-
-    styles.content {
-      # cat=content/cHeader/h0; type=int[1-5]; label=Default Header type: Enter the number of the header layout to be used by default
-      defaultHeaderType = 2
-
-      # cat=content/cShortcut/t0; type=string; label=List of accepted tables
-      shortcut.tables = tt_content
-
-      # cat=content/cTextmedia/i1; type=color; label= Media element border, color: Bordercolor of media elements in content elements when "Border"-option for an element is set
-      textmedia.borderColor = #000000
-
-      color1 =
-      color2 = blue
-      properties =
-    }
-
-In the above example, three constants have syntactically correct comments
-and will appear in the "Constant Editor". The other three will not. The
-syntax is described in the rest of this chapter.
-
-Making most important constants available for the "Constant Editor" is a real
-usability gain.
-
-..  _typoscript-syntax-constant-editor-default-values:
-
-Default values
-==============
-
-A constant may be given a default value when it is defined, as is the case for
-the :typoscript:`color2` constant in the above example.
-
-More generally, the default value of a constant is determined by the value the
-constant has before the last TypoScript is parsed.
-
-..  _typoscript-syntax-constant-editor-keys:
-..  _typoscript-syntax-constant-editor-comments:
-
-Comment Syntax
-==============
-
-How the comments are perceived by the module:
-
--   The comment line before the constant is considered to contain
-    its definition.
-
--   Each line is split at the :code:`;` (semicolon) character, that separates
-    the various parameters
-
--   Each parameter is split at the :code:`=` (equal) sign to separate the
-    parameter's key and value.
-
-The possible keys are described below.
-
-..  _typoscript-syntax-constant-editor-keys-cat:
-
-cat
-===
-
--   Comma-separated list of the categories (case-insensitive) that the constant is
-    a member of. Only one category should be used, because it usually turns out to
-    be confusing for users, if the same constant appears in multiple categories.
-
--   If the chosen category is *not* found among the default categories listed
-    below, and is not a custom category either, it's regarded a new category.
-
--   If the category is empty (""), the constant is excluded from the editor.
-
-..  _typoscript-syntax-constant-editor-keys-cat-predefined-categories:
-
-Predefined categories
----------------------
-
-..  versionchanged:: 12.0
-    While the predefined categories still exist for backward compatibility
-    reasons they are not used anymore by the TYPO3 Core except for "content".
-    It is suggested to use one or several
-    :ref:`typoscript-syntax-constant-editor-keys-cat-custom-categories` for
-    each extension supplying categories.
-
-=========  ======================================================================
-Category   Description
-=========  ======================================================================
-basic      Constants of superior importance for the TypoScript. This is typically
-           dimensions, image files and enabling of various features. The most
-           basic constants, which would almost always needed to be configured.
-menu       Menu setup. This includes font files, sizes, background images.
-           Depending on the menu type.
-content    All constants related to the display of page content elements.
-page       General configuration like meta tags, link targets.
-advanced   Advanced functions, which are seldom used.
-=========  ======================================================================
-
-..  _typoscript-syntax-constant-editor-keys-cat-custom-categories:
-
-Custom categories
------------------
-
-To define a new category, a comment including the parameter :typoscript:`customcategory`
-has to be added. Example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    # customcategory=mySitePackage=My Site Package
-
-    #cat=mySitePackage/basic/100; type=boolean; label=Something
-    tx_my_site_package.basic.enableSomething = 0
-
-..  versionchanged:: 12.0
-    There has to be a newline after the definition of a custom category or it will
-    not be considered. See also https://forge.typo3.org/issues/100936.
-
-This line defines the new category "mysite" which will be available for any
-constant defined **after** this line. The :typoscript:`LLL:` reference points to the
-localized string used to "name" the custom category in the Constant Editor.
-Usage example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    #cat=mysite//a; type=boolean; label=Global no_cache
-    config.no_cache = 0
-
-If a custom category is not defined, its identifier will be used in lowercase
-letters.
-
-..  _typoscript-syntax-constant-editor-keys-cat-subcategories:
-
-Subcategories
--------------
-
-There are a number of subcategories one can use. Subcategories are entered
-after the category separated by a slash :typoscript:`/`. Example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    "mySitePackage/color/a"
-
-This will make the constant go into the "BASIC" category and be listed
-under the "COLOR" section.
-
-One of the predefined subcategories can be used or any custom subcategory. If a
-non-existing subcategory is used, the constant will go into the subcategory
-"Other".
-
-..  _typoscript-syntax-constant-editor-keys-cat-predefined-subcategories:
-
-Predefined subcategories
-------------------------
-
-Standard subcategories (in the order they get listed in the Constant
-Editor):
-
-===========  ========================================================================
-Subcategory  Description
-===========  ========================================================================
-enable       Used for options that enable or disable primary functions of a
-             TypoScript configuration.
-dims         Dimensions of all kinds; pixels, widths, heights of images, frames,
-             cells and so on.
-file         Files like background images, fonts and so on. Other options related
-             to the file may also enter.
-typo         Typography and related constants.
-color        Color setup. Many colors will be found with related options in other
-             categories though.
-links        Links: Targets typically.
-language     Language specific options.
-===========  ========================================================================
-
-There also exists a list of subcategories based on the default content elements:
-
-cheader, cheader\_g, ctext, cimage, ctextmedia, cbullets, ctable, cuploads,
-cmultimedia, cmedia, cmailform, csearch, clogin, cmenu, cshortcut, clist,
-chtml
-
-These are all categories reserved for options that relate to content
-rendering for each type of :typoscript:`tt_content` element. See the
-:t3src:`TypoScript constants <typo3/sysext/fluid_styled_content/Configuration/TypoScript/constants.typoscript>`
-of extension :composer:`typo3/cms-fluid-styled-content` for examples.
-
-..  _typoscript-syntax-constant-editor-keys-cat-custom-subcategories:
-
-Custom subcategories
---------------------
-
-Defining a custom subcategory is similar to defining a custom category,
-using the :typoscript:`customsubcategory` parameter. Example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    # customsubcategory=something=Some Subcategory
-
-    #cat=mySitePackage/something/a; type=boolean; label=Turn something on
-    tx_my_site_package.basic.enableSomething = 0
-
-..  versionchanged:: 12.0
-    There has to be a newline after the definition of a custom subcategory or it will
-    not be considered. See also https://forge.typo3.org/issues/100936.
-
-Will look in the Constant Editor like this:
-
-..  figure:: /Images/ManualScreenshots/TypoScriptModule/ConstantEditorSubCategory.png
-    :alt: The Constant Editor showing a custom category.
-
-..  _typoscript-syntax-constant-editor-keys-cat-constants-ordering:
-
-Ordering
---------
-
-The third part of the category definition is optional and represents
-the order in which the constants are displayed in the Constant Editor.
-The values are sorted alphabetically, so it is traditional to use letters.
-Example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    #cat=mysite/something/b; type=boolean; label=Special cache
-    config.no_cache = 0
-    #cat=mysite/something/a; type=boolean; label=Global no_cache
-    config.no_cache = 0
-
-The "Special cache" constant will be displayed after the "Global no_cache"
-constant, because it is ranked with letter "b" and the other constant
-has letter "a". Constants without any ordering information will come last.
-
-..  _typoscript-syntax-constant-editor-keys-type:
-
-type
-====
-
-There exists a number of predefined types, which define what kind of field is
-rendered for inputting the constant.
-
-===========================  ============================================================================
-Type                         Description
-===========================  ============================================================================
-int [low-high]               Integer, optional in range "low" to "high".
-
-int+                         Positive integer
-
-offset [L1,L2,...L6]         Comma-separated list of integers. Default is "x,y", but as comma separated
-                             parameters in brackets one can specify up to 6 labels being comma separated.
-                             If wished to omit one of the last 4 fields, leave the label empty
-                             for that element.
-
-color                        HTML color
-
-wrap                         HTML code that is wrapped around some content.
-
-options [item1,item2,...]    Selectbox with values/labels item1, item2 etc. Comma-separated. Split
-                             by "=" also and in that case, first part is label, second is value.
-
-boolean [truevalue]          Boolean, optional can define the value of "true", default is 1.
-
-string (the default)         A string value
-
-user                         Path to the file and method which renders the option HTML,
-                             for example :typoscript:`type=user[Vendor\Extension\Namespace\ClassName->myCustomField]`.
-                             The method should have following signature:
-                             :php:`public function myCustomField(array $params)`.
-===========================  ============================================================================
-
-
-..  _typoscript-syntax-constant-editor-keys-label:
-
-label
-=====
-
-The label is a trimmed text string. It gets split on the first :typoscript:`:` (colon)
-to separate header and body of the comment. The header is displayed on its own
-line in bold.
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    #cat=mySitePackage/basic/100; type=boolean; label=Turn something on: This turns on a cool feature!
-    tx_my_site_package.basic.enableSomething = 0
-
-The string can be localized by using the traditional "LLL" syntax. Example:
-
-..  code-block:: typoscript
-    :caption: EXT:site_package/Configuration/TypoScript/constants.typoscript
-
-    #cat=mySitePackage/basic/100; type=boolean; label=LLL:EXT:my_site_package/Resources/Private/Language/locallang.xlf:config.something
-    tx_my_site_package.basic.enableSomething = 0
-
-Only a single string is referenced, not one for the header and one for the
-description. This means that the localized string must contain the colon
-separator (:code:`:`). Example:
-
-..  code-block:: xml
-    :caption: LLL:EXT:my_site_package/Resources/Private/Language/locallang.xlf
-
-    <trans-unit id="config.something" xml:space="config.something">
-        <source>Turn something on: This turns on a cool feature!</source>
-    </trans-unit>
diff --git a/Documentation/UsingSetting/_Sets/_ext_localconf.php b/Documentation/UsingSetting/_Sets/_ext_localconf.php
index ab26afc39..9c3ba0e6a 100644
--- a/Documentation/UsingSetting/_Sets/_ext_localconf.php
+++ b/Documentation/UsingSetting/_Sets/_ext_localconf.php
@@ -7,5 +7,13 @@
 ExtensionManagementUtility::addTypoScript(
     'my_extension',
     'setup',
-    "@import 'EXT:my_extension/Configuration/TypoScript/setup.typoscript'",
+    '
+        module.tx_form {
+            settings {
+                yamlConfigurations {
+                    100 = EXT:my_site_package/Configuration/Form/CustomFormSetup.yaml
+                }
+            }
+        }
+    ',
 );
diff --git a/Documentation/UsingSettingTSconfig/Conditions.rst b/Documentation/UsingSettingTSconfig/Conditions.rst
new file mode 100644
index 000000000..4f6df05c3
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/Conditions.rst
@@ -0,0 +1,907 @@
+:navigation-title: Conditions
+
+..  include:: /Includes.rst.txt
+..  index::
+    Conditions
+    Conditions; Difference to TypoScript templates
+    Conditions; Access backend user
+..  _tsconfig-conditions:
+..  _tsconfig-condition-references:
+..  _conditions-example:
+..  _tsconfig-condition-differences:
+
+===========================================
+Conditions in Backend TypoScript / TSconfig
+===========================================
+
+TSconfig TypoScript conditions offer a way to conditionally change TypoScript based
+on current context. See the :ref:`TypoScript syntax condition chapter <t3tsref:typoscript-syntax-conditions>`
+for the basic syntax of conditions.
+
+It is possible to use TypoScript conditions in both user TSconfig and page TSconfig,
+just as it is done in frontend TypoScript. The list of available variables and
+functions is different, though.
+
+The Symfony expression language tends to throw warnings when sub arrays are
+checked in a condition that do not exist. Use the :ref:`traverse <tsconfig-condition-function-traverse>`
+function to avoid this.
+
+..  contents::
+    :local:
+
+..  _tsconfig-condition-variables:
+
+Condition variables available in TSconfig
+=========================================
+
+
+..  index:: Conditions; applicationContext
+..  _tsconfig-condition-applicationContext:
+
+applicationContext
+------------------
+
+..  confval:: applicationContext
+    :name: tsconfig-condition-applicationContext
+    :type: string
+
+    Current application context as string. See :ref:`t3coreapi:bootstrapping-context`.
+
+..  _tsconfig-condition-applicationContext-example:
+
+Example: Condition applies in application context "Development"
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [applicationContext == "Development"]
+        // Your settings go here
+    [END]
+
+Example: Condition applies in any application context that does not start with "Production"
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This condition applies in any context that is "Production" or starts with
+"Production" (for example Production/Staging"):
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [applicationContext matches "/^Production/"]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; page
+..  _tsconfig-condition-page:
+
+page
+----
+
+..  confval:: page
+    :name: tsconfig-condition-page
+    :type: array
+
+    All data of the current page record as array. Only available in page TSconfig, not
+    in user TSconfig.
+
+..  _tsconfig-condition-page-example:
+
+Example: Condition applies only on certain pages
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Check single page uid
+    [traverse(page, "uid") == 2]
+        // Your settings go here
+    [END]
+    # Check list of page uids
+    [traverse(page, "uid") in [17,24]]
+        // Your settings go here
+    [END]
+    # Check list of page uids NOT in
+    [traverse(page, "uid") not in [17,24]]
+        // Your settings go here
+    [END]
+    # Check range of pages (example: page uid from 10 to 20)
+    [traverse(page, "uid") in 10..20]
+        // Your settings go here
+    [END]
+
+    # Check the page backend layout
+    [traverse(page, "backend_layout") == 5]
+        // Your settings go here
+    [END]
+    [traverse(page, "backend_layout") == "example_layout"]
+        // Your settings go here
+    [END]
+
+    # Check the page title
+    [traverse(page, "title") == "foo"]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; tree
+..  _tsconfig-condition-tree:
+
+tree
+----
+
+..  confval:: tree
+    :name: tsconfig-condition-tree
+    :type: Object
+
+    Object with tree information. Only available in page TSconfig, not
+    in user TSconfig.
+
+..  index::
+    Conditions; tree.level
+    Conditions; Page level
+
+..  _tsconfig-condition-tree-level:
+
+tree.level
+----------
+
+..  confval:: tree.level
+    :name: tsconfig-condition-tree-level
+    :type: integer
+
+    Current tree level. Only available in page TSconfig, not
+    in user TSconfig. Starts at `1` (root level).
+
+..  _tsconfig-condition-tree-level-example:
+
+Example: Condition applies on a page on root level
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Check if page is on level 1 (root):
+    [tree.level == 1]
+        // Your settings go here
+    [END]
+
+..  hint::
+
+    In older versions before TYPO3 v10, this setting was available as
+    `treeLevel` variable.
+    That variable started the root level at value `0`, and now it starts at `1`.
+    Keep this in mind when migrating old conditions.
+
+    Unlike the frontend TypoScript condition `tree.level`, the backend tree level
+    is not affected by `pages.is_siteroot`. This means, for nested sites it cannot
+    be used to match "site roots" or in general any n-th levels of page tree depths.
+    It's the *absolute depth* of the entire page tree, starting with `1`.
+
+..  index:: Conditions; tree.pagelayout
+..  _tsconfig-condition-tree-pagelayout:
+
+tree.pagelayout
+---------------
+
+..  confval:: tree.pagelayout
+    :name: tsconfig-condition-tree-pagelayout
+    :type: integer / string
+
+    Check for the defined backend layout of a page including the inheritance of
+    the field :guilabel:`Backend Layout (subpages of this page)`. Only available in page TSconfig,
+    not in user TSconfig.
+
+..  _tsconfig-condition-tree-pagelayout-example:
+
+Example: Condition applies on pages with a certain backend layout
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Use backend_layout records uids
+    [tree.pagelayout == 2]
+        // Your settings go here
+    [END]
+
+    # Use TSconfig provider of backend layouts
+    [tree.pagelayout == "pagets__Home"]
+        // Your settings go here
+    [END]
+
+
+..  index::
+    Conditions; tree.rootLine
+..  _tsconfig-condition-tree-rootLine:
+
+tree.rootLine
+-------------
+
+..  confval:: tree.rootLine
+    :name: tsconfig-condition-tree-rootLine
+    :type: array
+
+    An array of arrays with uid and pid. Only available in page TSconfig, not
+    in user TSconfig.
+
+..  _tsconfig-condition-tree-rootLine-example:
+
+Example: Condition applies on all subpages of page
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [tree.rootLine[0]["uid"] == 1]
+        // Your settings go here
+    [END]
+
+
+..  index::
+    Conditions; tree.rootLineIds
+    Conditions; Pid in rootline
+..  _tsconfig-condition-tree-rootLineIds:
+
+tree.rootLineIds
+----------------
+
+..  confval:: tree.rootLineIds
+    :name: tsconfig-condition-tree-rootLineIds
+    :type: array
+
+    An array with UIDs of the root line. Only available in page TSconfig, not
+    in user TSconfig.
+
+..  _tsconfig-condition-tree-rootLineIds-example:
+
+Example: Condition applies if a page is in the root line
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Check if page with uid 2 is inside the root line
+    [2 in tree.rootLineIds]
+        // Your settings go here
+    [END]
+
+
+..  index::
+    Conditions; tree.rootLineParentIds
+    Conditions; Pid up in rootline
+..  _tsconfig-condition-tree-rootLineParentIds:
+
+tree.rootLineParentIds
+----------------------
+
+..  confval:: tree.rootLineParentIds
+    :name: tsconfig-condition-tree-rootLineParentIds
+    :type: array
+
+    An array with parent UIDs of the root line. Only available in page TSconfig, not
+    in user TSconfig.
+
+..  _tsconfig-condition-tree-rootLineParentIds-example:
+
+Example: Condition applies if a page's parent is in the root line
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Check if page with uid 2 is the parent of a page inside the root line
+    [2 in tree.rootLineParentIds]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; backend
+..  _tsconfig-condition-backend:
+
+backend
+-------
+
+..  confval:: backend
+    :name: tsconfig-condition-backend
+    :type: Object
+
+    Object with backend information.
+
+
+..  index:: Conditions; backend.user
+..  _tsconfig-condition-backend-user:
+
+backend.user
+------------
+
+..  confval:: backend.user
+    :name: tsconfig-condition-backend-user
+    :type: Object
+
+    Object with current backend user information.
+
+..  index::
+    Conditions; backend.user.isAdmin
+    Conditions; Admin logged in
+..  _tsconfig-condition-backend-user-isAdmin:
+
+backend.user.isAdmin
+--------------------
+
+..  confval:: backend.user.isAdmin
+    :name: tsconfig-condition-backend-user-isAdmin
+    :type: boolean
+
+    True if current user is admin.
+
+..  _tsconfig-condition-backend-user-isAdmin-example:
+
+Example: Condition applies if the current backend user is an admin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Evaluates to true if current backend user is administrator
+    [backend.user.isAdmin]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; backend.user.isLoggedIn
+..  _tsconfig-condition-backend-user-isLoggedIn:
+
+backend.user.isLoggedIn
+-----------------------
+
+..  confval:: backend.user.isLoggedIn
+    :name: tsconfig-condition-backend-user-isLoggedIn
+    :type: boolean
+
+    True if current user is logged in.
+
+..  todo: When does this make sense? TSconfig is only applied in backend context...
+
+..  _tsconfig-condition-backend-user-isLoggedIn-example:
+
+Example: Condition applies if any backend user is logged in
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [backend.user.isLoggedIn]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; backend.user.userId
+..  _tsconfig-condition-backend-user-userId:
+
+backend.user.userId
+-------------------
+
+..  confval:: backend.user.userId
+    :name: tsconfig-condition-backend-user-userId
+    :type: integer
+
+    UID of current user.
+
+..  _tsconfig-condition-backend-user-userId-example:
+
+Example: Condition applies if a certain backend user is logged in
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Evaluates to true if user uid of current logged in backend user is equal to 5
+    [backend.user.userId == 5]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; backend.user.userGroupIds
+..  _tsconfig-condition-backend-user-userGroupIds:
+
+backend.user.userGroupIds
+-------------------------
+
+..  confval:: backend.user.userGroupList
+    :name: tsconfig-condition-backend-user-userGroupIds
+    :type: array
+
+    array of user group IDs of the current backend user.
+
+..  _tsconfig-condition-backend-user-userGroupIds-example:
+
+Example: Condition applies if a backend user of a certain group is logged in
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [2 in backend.user.userGroupIds]
+        // Your settings go here
+    [END]
+
+..  index:: Conditions; backend.user.userGroupList
+..  _tsconfig-condition-backend-user-userGroupList:
+
+backend.user.userGroupList
+--------------------------
+
+..  confval:: backend.user.userGroupList
+    :name: tsconfig-condition-backend-user-userGroupList
+    :type: string
+
+    Comma list of group UIDs
+
+..  _tsconfig-condition-backend-user-userGroupList-example:
+
+Example: Condition applies if the groups of a user meet a certain pattern
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  todo: Does this example make sense? What does it really do?
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [like(","~backend.user.userGroupList~",", "*,1,*")]
+        // Your settings go here
+    [END]
+
+..  index:: Conditions; workspace
+..  _tsconfig-condition-workspace:
+
+workspace
+---------
+
+..  confval:: workspace
+    :name: tsconfig-condition-workspace
+    :type: Object
+
+    object with workspace information
+
+
+..  index:: Conditions; workspace.workspaceId
+..  _tsconfig-condition-workspace-workspaceId:
+
+workspace.workspaceId
+---------------------
+
+..  confval:: .workspaceId
+    :name: tsconfig-condition-workspace-workspaceId
+    :type: integer
+
+    UID of current workspace.
+
+..  _tsconfig-condition-workspace-workspaceId-example:
+
+Example: Condition applies only in a certain workspace
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [workspace.workspaceId == 0]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; workspace.isLive
+..  _tsconfig-condition-workspace-isLive:
+
+workspace.isLive
+----------------
+
+..  confval:: workspace.isLive
+    :name: tsconfig-condition-workspace-isLive
+    :type: boolean
+
+    True if current workspace is live.
+
+..  _tsconfig-condition-workspace-isLive-example:
+
+Example: Condition applies only in live workspace
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [workspace.isLive]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; workspace.isOffline
+..  _tsconfig-condition-workspace-isOffline:
+
+workspace.isOffline
+-------------------
+
+..  confval:: workspace.isOffline
+    :name: tsconfig-condition-workspace-isOffline
+    :type: boolean
+
+    True if current workspace is offline
+
+..  _tsconfig-condition-workspace-isOffline-example:
+
+Example: Condition applies only in offline workspace
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [workspace.isOffline]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; typo3
+..  _tsconfig-condition-typo3:
+
+typo3
+-----
+
+..  confval:: typo3
+    :name: tsconfig-condition-typo3
+    :type: Object
+
+    Object with TYPO3 related information
+
+..  index:: Conditions; typo3.version
+..  _tsconfig-condition-typo3-version:
+
+typo3.version
+-------------
+
+..  confval:: typo3.version
+    :name: tsconfig-condition-typo3-version
+    :type: string
+
+    TYPO3 version (e.g. 13.4.0-dev)
+
+..  _tsconfig-condition-typo3-version-example:
+
+Example: Condition only applies in an exact TYPO3 version like 13.4.0
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [typo3.version == "13.4.0"]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; typo3.branch
+..  _tsconfig-condition-typo3-branch:
+
+typo3.branch
+------------
+
+..  confval:: typo3.branch
+    :name: tsconfig-condition-typo3-branch
+    :type: string
+
+    TYPO3 branch (e.g. 13.4)
+
+
+..  _tsconfig-condition-typo3-branch-example:
+
+Example: Condition applies in all TYPO3 versions of a branch like 13.4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [typo3.branch == "13.4"]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; typo3.devIpMask
+..  _tsconfig-condition-typo3-devIpMask:
+
+typo3.devIpMask
+---------------
+
+..  confval:: typo3.devIpMask
+    :name: tsconfig-condition-typo3-devIpMask
+    :type: string
+
+    :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['devIPmask']`
+
+..  _tsconfig-condition-typo3-devIpMask-example:
+
+Example: Condition only applies if the devIpMask is set to a certain value
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  todo: Does this example make sense? Shouldn't we compare it to the
+    IP of the currently logged in backend user or some such?
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [typo3.devIpMask == "203.0.113.6"]
+        // Your settings go here
+    [END]
+
+
+..  _tsconfig-condition-functions:
+
+Condition functions available in TSconfig
+=========================================
+
+..  index:: Conditions; date
+..  _tsconfig-condition-function-date:
+
+date()
+------
+
+..  confval:: date([parameter])
+    :name: tsconfig-condition-function-date
+    :type: integer
+    :Parameter: [parameter]: string / integer
+
+    Get current date in given format. See PHP `date <https://www.php.net/manual/en/function.date.php>`_
+    function as reference for possible usage.
+
+..  _tsconfig-condition-function-date-example:
+
+Example: Condition applies at certain dates or times
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # True if day of current month is 7
+    [date("j") == 7]
+        // Your settings go here
+    [END]
+
+    # True if day of current week is 7
+    [date("w") == 7]
+        // Your settings go here
+    [END]
+
+    # True if day of current year is 7
+    [date("z") == 7]
+        // Your settings go here
+    [END]
+
+    # True if current hour is 7
+    [date("G") == 7]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; like
+..  _tsconfig-condition-function-like:
+
+like()
+------
+
+..  confval:: like([search-string], [pattern])
+    :name: tsconfig-condition-function-like
+    :type: boolean
+    :parameter: [search-string] : string; [pattern]: string
+
+    This function has two parameters: The first parameter is the string to search in,
+    the second parameter is the search string.
+
+..  _tsconfig-condition-function-like-example:
+
+Example: Use the "like()" function in conditions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Search a string with * within another string
+    [like("fooBarBaz", "*Bar*")]
+        // Your settings go here
+    [END]
+
+    # Search string with single characters in between, using ?
+    [like("fooBarBaz", "f?oBa?Baz")]
+        // Your settings go here
+    [END]
+
+    # Search string using regular expression
+    [like("fooBarBaz", "/f[o]{2,2}[aBrz]+/")]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; traverse
+..  _tsconfig-condition-function-traverse:
+
+traverse()
+----------
+
+..  confval:: traverse([array], [key])
+    :name: tsconfig-condition-function-traverse
+    :type: any
+    :Parameter: [array]: array; [key]: string or integer
+
+    This function gets a value from an array with arbitrary depth and suppresses
+    PHP warning when sub arrays do not exist. It has two parameters: The first parameter
+    is the array to traverse, the second parameter is the path to traverse.
+
+    In case the path is not found in the array, an empty string is returned.
+
+..  _tsconfig-condition-function-traverse-example:
+
+Example: Condition applies if request parameter matches a certain value
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  todo: This example does not really make sense in the backend context?
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Traverse query parameters of current request along tx_news_pi1[news]
+    [traverse(request.getQueryParams(), 'tx_news_pi1/news') > 0]
+        // Your settings go here
+    [END]
+
+
+..  index:: Conditions; compatVersion
+..  _tsconfig-condition-function-compatVersion:
+
+compatVersion()
+---------------
+
+..  confval:: compatVersion([version-pattern])
+    :name: tsconfig-condition-function-compatVersion
+    :type: boolean
+    :Parameter: [version-pattern]: string
+
+    Compares against the current TYPO3 branch.
+
+..  _tsconfig-condition-function-compatVersion-example:
+
+Example: Condition applies if the current TYPO3 version matches a pattern
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # True if current version is 13.4.x
+    [compatVersion("13.4")]
+        // Your settings go here
+    [END]
+    [compatVersion("13.4.0")]
+        // Your settings go here
+    [END]
+    [compatVersion("13.4.1")]
+        // Your settings go here
+    [END]
+
+..  _tsconfig-condition-function-getenv:
+
+getenv()
+--------
+
+..  confval:: getenv([enviroment_variable])
+    :name: tsconfig-condition-function-getenv
+    :type: string
+    :Parameter: [enviroment_variable]: string
+
+    PHP function `getenv <https://www.php.net/manual/en/function.getenv.php>`_.
+
+..  _tsconfig-condition-function-getenv-example:
+
+Example: Condition applies if the virtual host is set to a certain value
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    [getenv("VIRTUAL_HOST") == "www.example.org"]
+        // Your settings go here
+    [END]
+
+..  index:: Conditions; feature
+..  _tsconfig-condition-function-feature:
+
+feature()
+---------
+
+..  confval:: feature([feature_key])
+    :name: tsconfig-condition-function-feature
+    :type: any
+    :Parameter: [feature_key]: string
+
+    Provides access to feature toggles current state.
+
+..  _tsconfig-condition-function-feature-example:
+
+Example: condition applies if a feature toggle is enabled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  todo: Add another feature as TypoScript.strictSyntax is not available anymore in current versions.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # True if feature toggle for strict TypoScript syntax is enabled:
+    [feature("TypoScript.strictSyntax") === false]
+        // Your settings go here
+    [END]
+
+..  _tsconfig-condition-function-site:
+
+site()
+------
+
+..  confval:: site([keyword])
+    :name: tsconfig-condition-function-site
+    :type: string
+    :Parameter: [keyword]: string
+
+    Get value from site configuration, or null if no site was found or property
+    does not exists. Only available in page TSconfig, not available in user TSconfig.
+    Available Information:
+
+    site("identifier")
+        Returns the identifier of current site as string.
+
+    site("base")
+        Returns the base of current site as string.
+
+    site("rootPageId")
+        Returns the root page uid of current site as integer.
+
+    site("languages")
+        Returns array of available languages for current site.
+        For deeper information, see :ref:`condition-functions-in-frontend-context-function-siteLanguage`.
+
+    site("allLanguages")
+        Returns array of available and unavailable languages for current site.
+        For deeper information, see :ref:`condition-functions-in-frontend-context-function-siteLanguage`.
+
+    site("defaultLanguage")
+        Returns the default language for current site.
+        For deeper information, see :ref:`condition-functions-in-frontend-context-function-siteLanguage`.
+
+    site("configuration")
+        Returns an array with all available configuration for current site.
+
+..  _tsconfig-condition-function-site-example:
+
+Example: Condition applies if a certain value is set in the site configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    # Site identifier
+    [site("identifier") == "my_website"]
+        // Your settings go here
+    [END]
+
+    # Match site base host
+    [site("base").getHost() == "www.example.org"]
+        // Your settings go here
+    [END]
+
+    # Match base path
+    [site("base").getPath() == "/"]
+        // Your settings go here
+    [END]
+
+    # Match root page uid
+    [site("rootPageId") == 1]
+        // Your settings go here
+    [END]
+
+    # Match a configuration property
+    [traverse(site("configuration"), "myCustomProperty") == true]
+        // Your settings go here
+    [END]
diff --git a/Documentation/UsingSettingTSconfig/Index.rst b/Documentation/UsingSettingTSconfig/Index.rst
new file mode 100644
index 000000000..6fe881733
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/Index.rst
@@ -0,0 +1,53 @@
+.. include:: /Includes.rst.txt
+.. index::
+   TSconfig; Setting
+   TSconfig; Using
+.. _typoscript-syntax-using-setting:
+
+==========================
+Using and setting TSconfig
+==========================
+
+This chapter gives an overview where TSconfig is set, how it
+can be edited, and the load order of the different variants.
+
+TSconfig can be used in page, it is then referred to as
+"Page TSconfig", or for backend users and backend user groups,
+in which case it is known as "User TSconfig".
+
+
+..  card-grid::
+    :columns: 1
+    :columns-md: 2
+    :gap: 4
+    :class: pb-4
+    :card-height: 100
+
+    ..  card:: :ref:`Setting Page TSconfig <setting-page-tsconfig>`
+
+        Lists different options of how to include Page TSconfig options.
+
+
+    ..  card:: :ref:`Setting User TSconfig <setting-user-tsconfig>`
+
+        Lists different options of how to include User TSconfig options.
+
+
+    ..  card:: :ref:`Conditions <conditions>`
+
+        Explains how Conditions can be used in TSconfig of both user and
+        page.
+
+    ..  card:: :ref:`PHP API <phpapi>`
+
+        Explains how TSconfig can be retrieved from and used
+        within the PHP code of backend modules.
+
+.. toctree::
+   :titlesonly:
+   :hidden:
+
+   PageTSconfig
+   UserTSconfig
+   Conditions
+   PhpApi
diff --git a/Documentation/UsingSettingTSconfig/PageTSconfig.rst b/Documentation/UsingSettingTSconfig/PageTSconfig.rst
new file mode 100644
index 000000000..18eb767b0
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/PageTSconfig.rst
@@ -0,0 +1,262 @@
+.. include:: /Includes.rst.txt
+.. index::
+   Page TSconfig; Setting
+   Page TSconfig; Using
+   Page TSconfig
+.. _setting-page-tsconfig:
+
+=====================
+Setting page TSconfig
+=====================
+
+It is recommended to always define custom page TSconfig in a project-specific
+:ref:`sitepackage <t3sitepackage:start>` extension. This way the page TSconfig
+settings can be kept under version control.
+
+The options described below are available for setting page TSconfig in
+non-sitepackage extensions.
+
+Page TSconfig can be defined globally as
+:ref:`Default page TSconfig <pagesettingdefaultpagetsconfig>`, on site level via
+:ref:`Page TSconfig via site or set <include-static-page-tsconfig-per-site>` or for a
+:ref:`page tree <include-static-page-tsconfig>`, a page and all its subpages.
+
+It is also possible to set
+:ref:`set page TSconfig directly in the page properties <pagetsconfig-enter-data>` but
+this is not recommended anymore.
+
+.. contents::
+   :local:
+
+.. index:: pair: Page TSconfig; Default values
+.. _pagesettingdefaultpagetsconfig:
+
+Setting the page TSconfig globally
+==================================
+
+Global page TSconfig should be stored within an extension, usually a sitepackage
+extension. The content of the file :file:`Configuration/page.tsconfig` within
+an extension is automatically loaded during build time.
+
+It is possible to load other TSconfig files with the import syntax within this
+file:
+
+.. code-block:: typoscript
+   :caption: EXT:my_sitepackage/Configuration/page.tsconfig
+
+   @import 'EXT:my_sitepackage/Configuration/TsConfig/Page/Basic.tsconfig'
+   @import 'EXT:my_sitepackage/Configuration/TsConfig/Page/Mod/Wizards/NewContentElement.tsconfig'
+
+
+Many page TSconfig settings can be set globally. This is useful for
+installations that contain only one site and use only one sitepackage extension.
+
+Extensions supplying custom default page TSconfig that should always be included,
+can also set the page TSconfig globally.
+
+The PSR-14 event :ref:`t3coreapi:BeforeLoadedPageTsConfigEvent` is available to
+add global static page TSconfig before anything else is loaded.
+
+.. _page-tsconfig-v11-v12:
+
+Global page TSconfig, compatible with TYPO3 v11 and v12
+-------------------------------------------------------
+
+In TYPO3 v11 installations the content of :file:`Configuration/page.tsconfig`
+is not loaded automatically yet. You can achieve compatibility with both
+TYPO3 v11 and v12 by importing the content of this file with the API function
+:php:`ExtensionManagementUtility::addPageTSConfig`:
+
+..  literalinclude:: _PageTSconfig/_ext_localconf_page_tsconfig_v11.php
+    :language: php
+    :caption: EXT:my_sitepackage/ext_localconf.php
+
+.. _include-static-page-tsconfig-per-site:
+
+Page TSconfig on site level
+===========================
+
+..  versionadded:: 13.1
+    Page TSconfig can be included on a per site level.
+
+Page TSconfig can be defined on a site level by placing a file called
+:file:`page.tsconfig` in the storage directory of the site
+(:ref:`config/sites/<identifier>/ <t3coreapi:site-storage>`).
+
+Extensions and site packages can provide page TSconfig in
+:ref:`site sets <t3coreapi:site-sets>` by placing a file called :file:`page.tsconfig`
+into the folder of that set.
+
+This way sites and sets can ship page TSconfig without the need for database
+entries or by polluting global scope. Dependencies can be expressed via site sets,
+allowing for automatic ordering and deduplication.
+
+See also
+:ref:`site sets as page TSconfig provider <t3coreapi:site-sets-page-tsconfig>`.
+
+.. _include-static-page-tsconfig-per-site-example:
+
+Example: load page TSconfig from the site set and the site
+----------------------------------------------------------
+
+Let us assume, you have a site set defined in your extension:
+
+..  code-block:: yaml
+    :caption: EXT:my_extension/Configuration/Sets/MySet/config.yaml
+
+    name: my-vendor/my-set
+    label: My Set
+
+And use it in a site in your project:
+
+..  code-block:: yaml
+    :caption: config/sites/my-site/config.yaml
+
+    base: 'http://example.com/'
+    rootPageId: 1
+    dependencies:
+      - my-vendor/my-set
+
+You can now put a file called :file:`page.tsconfig` in the same folder like your
+site configuration and it will be automatically loaded for all pages in that
+site.
+
+..  code-block:: tsconfig
+    :caption: config/sites/my-site/page.tsconfig
+
+    # This tsconfig will be loaded for pages in site "my-site"
+    # [...]
+
+Or you can put the file :file:`page.tsconfig` in the same directory like the
+site set you defined in your extension. It will then be loaded by all pages
+of all sites that depend on this set:
+
+
+..  code-block:: tsconfig
+    :caption: EXT:my_extension/Configuration/Sets/MySet/page.tsconfig
+
+    # This tsconfig will be loaded for pages in all sites that depend on set 'my-vendor/my-set'
+    # [...]
+
+
+.. index:: pair: Page TSconfig; Static TSconfig files
+.. _pagesettingstaticpagetsconfigfiles:
+
+Static page TSconfig
+====================
+
+.. _include-static-page-tsconfig:
+
+Include static page TSconfig into a page tree
+---------------------------------------------
+
+Static page TSconfig that has been
+:ref:`registered <register-static-page-tsconfig>` by your sitepackage or a
+third party extension can be included in the page properties.
+
+#.  Go to the page properties of the page where you want to include the page TSconfig.
+#.  Go to the tab :guilabel:`Resources`, then to
+    :guilabel:`page TSconfig > Include static page TSconfig (from extensions)` and
+    select the desired configurations from the :guilabel:`Available Items`.
+
+.. _register-static-page-tsconfig:
+
+Register static page TSconfig files
+-----------------------------------
+
+Register PageTS config files in the :file:`Configuration/TCA/Overrides/pages.php`
+of any extension.
+
+These can be :ref:`selected in the page properties <include-static-page-tsconfig>`.
+
+..  literalinclude:: _PageTSconfig/_pages.php
+    :language: php
+    :caption: EXT:my_sitepackage/Configuration/TCA/Overrides/pages.php
+
+It is not possible to use language strings :php:`LLL:...` for the third
+parameter as the extension name will be automatically appended.
+
+If you need to localize these labels, modify the TCA directly instead of using
+the API function:
+
+..  literalinclude:: _PageTSconfig/_pages_localized.php
+    :language: php
+    :caption: EXT:my_sitepackage/Configuration/TCA/Overrides/pages.php
+
+.. index:: pair: Page TSconfig; Enter data
+.. _pagetsconfig-enter-data:
+.. _pagethetsconfigfield:
+
+Set page TSconfig directly in the page properties
+==================================================
+
+Go to the page properties of the page where you want to include the page TSconfig
+and open the tab :guilabel:`Resources`.
+
+You can enter page TSconfig directly into the field :guilabel:`Page TSconfig`:
+
+.. figure:: /Images/ManualScreenshots/List/TSconfigPageInput.png
+    :alt: TSconfig-related fields in the Resources tab of a page
+    :class: with-shadow
+
+Page TSconfig inserted directly into the page properties is applied to the
+page itself and all its subpages.
+
+.. note::
+   The configuration is stored in the database and not in the file
+   system. Therefore it cannot be kept under version control. This
+   strategy is not recommended. Setting page TSconfig in the page properties
+   directly is available for backward-compatibility reasons and for quickly trying
+   out some settings in development only.
+
+.. index:: pair: Page TSconfig; Verify configuration
+.. _pageverifyingthefinalconfiguration:
+
+Verify the final configuration
+==============================
+
+The full page TSconfig for any given page can be viewed using the module
+:guilabel:`Page TSconfig` with in the :guilabel:`Site Management` section.
+
+
+.. index:: pair: Page TSconfig; Override values
+.. _page-overriding-and-modifying-values:
+
+Overriding and modifying values
+================================
+
+Page TSconfig is loaded in the following order, the latter override the former:
+
+#. :ref:`Default page TSconfig <pagesettingdefaultpagetsconfig>` that was
+   set globally
+#. :ref:`Static page TSconfig <pagesettingdefaultpagetsconfig>` that was
+   included for a page tree.
+#. :ref:`Direct page TSconfig <pagetsconfig-enter-data>` entered directly in
+   the page properties.
+#. :ref:`User TSconfig overrides <userrelationshiptovaluessetinpagetsconfig>`
+
+Static and direct page TSconfig are loaded for the page they are set on and
+all their subpages.
+
+The TypoScript syntax to
+:ref:`modify <t3tsref:typoscript-syntax-syntax-value-modification>` values
+can also be used for the page TSconfig.
+
+Example
+=======
+
+Default page TSconfig
+
+.. code-block:: typoscript
+   :caption: EXT:site_package/Configuration/page.tsconfig
+
+   RTE.default.proc.allowTagsOutside = hr
+
+Static page TSconfig included on the parent page
+
+.. code-block:: typoscript
+   :caption: EXT:site_package/Configuration/page.tsconfig
+
+   RTE.default.proc.allowTagsOutside := addToList(blockquote)
+
+Finally you get the value "hr,blockquote".
diff --git a/Documentation/UsingSettingTSconfig/PhpApi.rst b/Documentation/UsingSettingTSconfig/PhpApi.rst
new file mode 100644
index 000000000..1c0a9cd48
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/PhpApi.rst
@@ -0,0 +1,58 @@
+..  include:: /Includes.rst.txt
+..  index::
+    Page TSconfig; PHP API
+    Page TSconfig; Retrieving
+    Page TSconfig; Getting
+
+..  _phpapi:
+
+=======
+PHP API
+=======
+
+Retrieving TSconfig settings
+============================
+
+The PHP API to retrieve page and user TSconfig in a backend module can be used
+as follows:
+
+..  literalinclude:: _PhpApi/_MyBackendController.php
+    :language: php
+    :caption: EXT:my_sitepackage/Classes/Controller/MyBackendController.php
+
+Both methods return the entire TSconfig as a PHP array. The former
+retrieves the user TSconfig while the latter retrieves the page TSconfig.
+
+All imports, overrides, modifications, etc. are already resolved. This includes
+page TSconfig overrides by user TSconfig.
+
+Similar to other TypoScript-related API methods, properties that contain
+sub-properties return their sub-properties using the property name with a
+trailing dot, while a single property is accessible by the property
+name itself. The example below gives more insight on this.
+
+If accessing TSconfig arrays, the PHP null coalescing operator :php:`??` is
+useful: TSconfig options may or not be set, accessing non-existent
+array keys in PHP would thus raise PHP notice level warnings.
+
+Combining the array access with a fallback using :php:`??` helps when accessing
+these optional array structures.
+
+
+..  literalinclude:: _PhpApi/_user.tsconfig
+    :language: typoscript
+    :caption: Incoming (user) TSconfig:
+
+..  literalinclude:: _PhpApi/_getTSConfig.php
+    :language: php
+    :caption: Parsed array returned by getTSConfig(), note the dot if a property has sub keys:
+
+..  literalinclude:: _PhpApi/_MyBackendLoggedInController.php
+    :language: php
+    :caption: Example how to read user TSconfig
+
+Changing or adding page TSconfig
+================================
+
+The PSR-14 event :ref:`ModifyLoadedPageTsConfigEvent <t3coreapi:ModifyLoadedPageTsConfigEvent>`
+is available to modify or add page TSconfig entries.
diff --git a/Documentation/UsingSettingTSconfig/UserTSconfig.rst b/Documentation/UsingSettingTSconfig/UserTSconfig.rst
new file mode 100644
index 000000000..24e66648c
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/UserTSconfig.rst
@@ -0,0 +1,245 @@
+..  include:: /Includes.rst.txt
+..  index:: User TSconfig
+..  _setting-user-tsconfig:
+
+=====================
+Setting user TSconfig
+=====================
+
+It is recommended to always define custom user TSconfig in a project-specific
+:ref:`sitepackage <t3sitepackage:start>` extension. This way the user TSconfig
+settings can be kept under version control.
+
+.. contents::
+   :local:
+
+..  index:: pair: User TSconfig; Enter data
+..  _userthetsconfigfield:
+
+Importing the user TSconfig into a backend user or group
+========================================================
+
+..  rst-class:: bignums
+
+#.  Open the record of the user or group. Go to
+    :guilabel:`Options > TSconfig`.
+
+    ..  figure:: /Images/ManualScreenshots/BackendUsers/TSconfigUserInput.png
+        :alt: The TSconfig field in the Options tab of a backend user
+        :class: with-shadow
+
+        The :guilabel:`TSconfig` field in the :guilabel:`Options` tab of a backend user
+
+#.  Enter the following TSconfig to import a configuration file from your
+    sitepackage:
+
+    ..  code-block:: typoscript
+        :caption: TsConfig added in the backend record of a backend user or group
+
+        @import 'EXT:my_sitepackage/Configuration/TsConfig/User/my_editor.tsconfig'
+
+This will make all settings in the file available to the user. The file
+itself can be kept under version control together with your sitepackage.
+
+TSconfig defined at user level overrides TSconfig defined at group level.
+
+If a user is a member of several groups, the TSconfig from each
+group is loaded. The order in which the groups are added to the user in field
+:guilabel:`General > Group` is used.
+
+The TSconfig from latter groups overrides the TSconfig from earlier groups if
+both define the same property.
+
+..  index:: pair: User TSconfig; Default values
+..  _usersettingdefaultusertsconfig:
+
+Setting default user TSconfig
+=============================
+
+..  versionadded:: 13.0
+    Starting with TYPO3 v13.0 user TSconfig in a file named
+    :file:`Configuration/user.tsconfig` in an extension is automatically loaded
+    during build time.
+
+User TSconfig is designed to be individual for users or groups of
+users. However, good defaults can be defined and overridden by group or
+user-specific TSconfig.
+
+Default user TSconfig should be stored within an extension, usually a
+sitepackage extension. The content of the file
+:file:`Configuration/user.tsconfig` within an extension is automatically loaded
+during build time.
+
+It is possible to load other user TSconfig files with the import syntax within
+this file:
+
+..  code-block:: typoscript
+    :caption: EXT:my_extension/Configuration/user.tsconfig
+
+    @import 'EXT:my_sitepackage/Configuration/TsConfig/User/default.tsconfig'
+
+The PSR-14 event :ref:`t3coreapi:BeforeLoadedUserTsConfigEvent` is available to
+add global static user TSconfig before anything else is loaded.
+
+User TSconfig, compatible with TYPO3 v12 and v13
+------------------------------------------------
+
+In TYPO3 v12 installations the content of :file:`Configuration/user.tsconfig` is
+not loaded automatically. You can achieve compatibility with both TYPO3 v12 and
+v13 by importing the content of this file with the API function
+:php:`ExtensionManagementUtility::addUserTSConfig`:
+
+..  literalinclude:: _UserTSconfig/_ext_localconf_v12.php
+    :language: php
+    :caption: EXT:my_sitepackage/ext_localconf.php
+
+..  deprecated:: 13.0
+    The method :php:`\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addUserTSConfig()`
+    has been marked as deprecated in TYPO3 v13 and will be removed with TYPO3
+    v14.
+
+..  index:: pair: User TSconfig; Verify configuration
+..  _userverifyingthefinalconfiguration:
+
+
+Verify the final configuration
+==============================
+
+The full user TSconfig of the currently logged-in backend user can be viewed
+using the :guilabel:`System > Configuration` backend module and choosing the
+action :guilabel:`$GLOBALS['BE_USER']->getTSConfig() (User TSconfig)`. However
+this module can only be accessed by admins.
+
+..  figure:: /Images/ManualScreenshots/Configuration/UserTSconfigOverview.png
+    :alt: Viewing user TSconfig using the Configuration module
+    :class: with-shadow
+
+    Viewing user TSconfig using the :guilabel:`Configuration` module
+
+The :guilabel:`Configuration` module is available with installed
+:doc:`lowlevel <ext_lowlevel:Index>` system extension.
+
+..  index:: pair: User TSconfig; Override values
+..  _user-override-modify-values:
+
+Override and modify values
+===========================
+
+Properties, which are set in the TSconfig field of a group, are valid
+for all users of that group.
+
+Values set in one group can be overridden and
+:ref:`modified <t3tsref:typoscript-syntax-syntax-value-modification>` in the
+same or another group. If a user is a member of multiple groups, the TSconfig
+settings are evaluated in the order in which the groups are included in the
+user account: When editing the backend user, the selected groups are evaluated
+from top to bottom.
+
+**Example:**
+
+*   Add in user TSconfig
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/user.tsconfig
+
+        page.RTE.default.showButtons = bold
+
+*   You get the value "bold".
+
+*   Add later in user TSconfig
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/user.tsconfig
+
+        page.RTE.default.showButtons := addToList(italic)
+
+*   You get the value "bold,italic".
+
+Finally, you can override or
+:ref:`modify <t3tsref:typoscript-syntax-syntax-value-modification>` the
+settings from groups that your user is a member of in the user TSconfig
+field of that specific user.
+
+**Example:**
+
+Let's say the user is a member of a *usergroup* with this
+configuration:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCAdefaults.tt_content {
+        hidden = 1
+        header = Hello!
+    }
+
+Then we set the following values in the TSconfig field of the specific *user*.
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/user.tsconfig
+
+    page.TCAdefaults.tt_content.header = 234
+    options.clearCache.all = 1
+
+This would override the default value of the header ("234") and add the
+clear cache option. The default value of the hidden field is not
+changed and simply inherited directly from the group.
+
+
+..  index:: User TSconfig; Override page TSconfig
+..  _userrelationshiptovaluessetinpagetsconfig:
+..  _pageoverridingpagetsconfigwithusertsconfig:
+
+Overriding page TSconfig in user TSconfig
+=========================================
+
+All properties from page TSconfig can be **overridden** in user TSconfig by
+prepending the property name with :typoscript:`page.`.
+
+When a page TSconfig property is set in **user** TSconfig that way, regardless
+of whether it is in the TSconfig field of a
+group or a user, it **overrides** the value of the according **page** TSconfig property.
+
+To illustrate this feature let's say new pages and copied pages are not hidden
+by default:
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/page.tsconfig
+
+    TCAdefaults.pages.hidden = 0
+    TCEMAIN.table.pages.disableHideAtCopy = 1
+
+If we activate the following configuration in the user TSconfig of a certain backend
+user group, new and copied pages will be hidden for that group. The user TSconfig to
+be used is the same, but prefixed with :tsconfig:`page.`
+
+..  code-block:: typoscript
+    :caption: EXT:site_package/Configuration/TSconfig/editors.tsconfig
+
+    // Override the settings from the page TSconfig for the editors usergroup
+    page {
+        TCAdefaults.pages.hidden = 1
+        TCEMAIN.table.pages.disableHideAtCopy = 0
+    }
+
+..  attention::
+
+    It is **not** possible to *reference* the value of a property from page
+    TSconfig and to *modify* this value in user TSconfig! If you set a property
+    in user TSconfig, which already had been set in *page* TSconfig, then the
+    value from page TSconfig will be overridden.
+
+    The result of the example below is *not* the value "bold,italic",
+    but the value "italic".
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/page.tsconfig
+
+        # Enable the "bold" button in Page TSconfig (!)
+        RTE.default.showButtons = bold
+
+    ..  code-block:: typoscript
+        :caption: EXT:site_package/Configuration/user.tsconfig
+
+        # Try to additionally add the "italic" button in User TSconfig (!)
+        page.RTE.default.showButtons := addToList(italic)
diff --git a/Documentation/UsingSettingTSconfig/_PageTSconfig/_ext_localconf_page_tsconfig_v11.php b/Documentation/UsingSettingTSconfig/_PageTSconfig/_ext_localconf_page_tsconfig_v11.php
new file mode 100644
index 000000000..6a0b59756
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PageTSconfig/_ext_localconf_page_tsconfig_v11.php
@@ -0,0 +1,17 @@
+<?php
+
+declare(strict_types=1);
+
+use TYPO3\CMS\Core\Information\Typo3Version;
+use TYPO3\CMS\Core\Utility\ExtensionManagementUtility;
+use TYPO3\CMS\Core\Utility\GeneralUtility;
+
+defined('TYPO3') or die();
+
+$versionInformation = GeneralUtility::makeInstance(Typo3Version::class);
+// Only include page.tsconfig if TYPO3 version is below 12 so that it is not imported twice.
+if ($versionInformation->getMajorVersion() < 12) {
+    ExtensionManagementUtility::addPageTSConfig(
+        '@import "EXT:my_sitepackage/Configuration/page.tsconfig"',
+    );
+}
diff --git a/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages.php b/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages.php
new file mode 100644
index 000000000..f0a1368b5
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages.php
@@ -0,0 +1,9 @@
+<?php
+
+use TYPO3\CMS\Core\Utility\ExtensionManagementUtility;
+
+ExtensionManagementUtility::registerPageTSConfigFile(
+    'extension_name',
+    'Configuration/TsConfig/Page/myPageTSconfigFile.tsconfig',
+    'My special config',
+);
diff --git a/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages_localized.php b/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages_localized.php
new file mode 100644
index 000000000..ec963db9d
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PageTSconfig/_pages_localized.php
@@ -0,0 +1,7 @@
+<?php
+
+$GLOBALS['TCA']['pages']['columns']['tsconfig_includes']['config']['items'][] =
+    [
+        'LLL:EXT:my_sitepackage/Resources/Private/Language/locallang_db.xlf:pages.pageTSconfig.my_ext_be_layouts',
+        'EXT:my_sitepackage/Configuration/TsConfig/Page/myPageTSconfigFile.tsconfig',
+    ];
diff --git a/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendController.php b/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendController.php
new file mode 100644
index 000000000..81a55c659
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendController.php
@@ -0,0 +1,25 @@
+<?php
+
+declare(strict_types=1);
+
+namespace UsingSettingTSconfig\_PhpApi;
+
+use TYPO3\CMS\Backend\Utility\BackendUtility;
+use TYPO3\CMS\Core\Authentication\BackendUserAuthentication;
+
+final class MyBackendController
+{
+    public function someMethod(int $currentPageId): void
+    {
+        // Retrieve user TSconfig of currently logged in user
+        $userTsConfig = $this->getBackendUser()->getTSConfig();
+
+        // Retrieve page TSconfig of the given page id
+        $pageTsConfig = BackendUtility::getPagesTSconfig($currentPageId);
+    }
+
+    private function getBackendUser(): BackendUserAuthentication
+    {
+        return $GLOBALS['BE_USER'];
+    }
+}
diff --git a/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendLoggedInController.php b/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendLoggedInController.php
new file mode 100644
index 000000000..e68e9dd4a
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PhpApi/_MyBackendLoggedInController.php
@@ -0,0 +1,25 @@
+<?php
+
+declare(strict_types=1);
+
+namespace UsingSettingTSconfig\_PhpApi;
+
+final class _MyBackendLoggedInController
+{
+    public function isUserToggleEnabled(): bool
+    {
+        // Typical call to retrieve a sanitized value:
+        return $isToggleEnabled = (bool)($this->getUserTsConfig()['options.']['someToggle'] ?? false);
+    }
+
+    public function getSomePartWithSubToggles(): array
+    {
+        // Retrieve a subset, note the dot at the end:
+        return $this->getUserTsConfig()['options.']['somePartWithSubToggles.'] ?? [];
+    }
+
+    private function getUserTsConfig(): array
+    {
+        return $GLOBALS['BE_USER']->getTSConfig();
+    }
+}
diff --git a/Documentation/UsingSettingTSconfig/_PhpApi/_getTSConfig.php b/Documentation/UsingSettingTSconfig/_PhpApi/_getTSConfig.php
new file mode 100644
index 000000000..888c94abd
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PhpApi/_getTSConfig.php
@@ -0,0 +1,11 @@
+<?php
+
+return [
+    'options.' => [
+        'someToggle' => '1',
+        'somePartWithSubToggles' => 'foo',
+        'somePartWithSubToggles.' => [
+            'aValue' => 'bar',
+        ],
+    ],
+];
diff --git a/Documentation/UsingSettingTSconfig/_PhpApi/_user.tsconfig b/Documentation/UsingSettingTSconfig/_PhpApi/_user.tsconfig
new file mode 100644
index 000000000..69b7f31ba
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_PhpApi/_user.tsconfig
@@ -0,0 +1,3 @@
+options.someToggle = 1
+options.somePartWithSubToggles = foo
+options.somePartWithSubToggles.aValue = bar
diff --git a/Documentation/UsingSettingTSconfig/_UserTSconfig/_ext_localconf_v12.php b/Documentation/UsingSettingTSconfig/_UserTSconfig/_ext_localconf_v12.php
new file mode 100644
index 000000000..8711da661
--- /dev/null
+++ b/Documentation/UsingSettingTSconfig/_UserTSconfig/_ext_localconf_v12.php
@@ -0,0 +1,17 @@
+<?php
+
+declare(strict_types=1);
+
+use TYPO3\CMS\Core\Information\Typo3Version;
+use TYPO3\CMS\Core\Utility\ExtensionManagementUtility;
+use TYPO3\CMS\Core\Utility\GeneralUtility;
+
+defined('TYPO3') or die();
+
+$versionInformation = GeneralUtility::makeInstance(Typo3Version::class);
+// Only include user.tsconfig if TYPO3 version is below 13 so that it is not imported twice.
+if ($versionInformation->getMajorVersion() < 13) {
+    ExtensionManagementUtility::addUserTSConfig(
+        '@import "EXT:my_sitepackage/Configuration/user.tsconfig"',
+    );
+}
diff --git a/Documentation/codesnippets.php b/Documentation/codesnippets.php
index cbf328d2e..478db7b2d 100644
--- a/Documentation/codesnippets.php
+++ b/Documentation/codesnippets.php
@@ -6,4 +6,5 @@
 return array_merge(
     include ('CodeSnippets/Config/DataProcessing.php'),
     include ('CodeSnippets/Config/Menus.php'),
+    include ('CodeSnippets/Config/TSconfig.php'),
 );
diff --git a/Documentation/guides.xml b/Documentation/guides.xml
index e151a98fa..d7f08fc67 100644
--- a/Documentation/guides.xml
+++ b/Documentation/guides.xml
@@ -3,19 +3,19 @@
         xsi:schemaLocation="https://www.phpdoc.org/guides ../vendor/phpdocumentor/guides-cli/resources/schema/guides.xsd"
         links-are-relative="true">
     <extension class="\T3Docs\Typo3DocsTheme\DependencyInjection\Typo3DocsThemeExtension"
-               project-home="https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/"
+               project-home="https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/"
                project-contact="https://typo3.slack.com/archives/C028JEPJL"
                project-repository="https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-Typoscript"
                project-issues="https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-Typoscript/issues"
-               edit-on-github-branch="main"
+               edit-on-github-branch="13.4"
                edit-on-github="TYPO3-Documentation/TYPO3CMS-Reference-Typoscript"
-               typo3-core-preferred="main"
+               typo3-core-preferred="13"
                interlink-shortcode="t3tsref"
                confval-default="TypoScript"
     />
-    <project title="TypoScript Reference"
-             release="main (development)"
-             version="main (development)"
+    <project title="TypoScript Explained"
+             release="13.4"
+             version="13.4"
              copyright="since 2012 by the TYPO3 contributors"
     />
 </guides>
diff --git a/Makefile b/Makefile
index 00741b28f..ef3c97114 100644
--- a/Makefile
+++ b/Makefile
@@ -7,13 +7,13 @@ help: ## Displays this list of targets with descriptions
 docs: ## Generate projects docs (from "Documentation" directory)
 	mkdir -p Documentation-GENERATED-temp
 
-	docker run --rm --pull always -v "$(shell pwd)":/project -t ghcr.io/typo3-documentation/render-guides:latest --config=Documentation
+	docker run --user $(shell id -u):$(shell id -g) --rm --pull always -v "$(shell pwd)":/project -t ghcr.io/typo3-documentation/render-guides:latest --config=Documentation
 
 .PHONY: test-docs
 test-docs: ## Test the documentation rendering
 	mkdir -p Documentation-GENERATED-temp
 
-	docker run --rm --pull always -v "$(shell pwd)":/project -t ghcr.io/typo3-documentation/render-guides:latest --config=Documentation --no-progress --minimal-test
+	docker run --user $(shell id -u):$(shell id -g) --rm --pull always -v "$(shell pwd)":/project -t ghcr.io/typo3-documentation/render-guides:latest --config=Documentation --no-progress --minimal-test
 
 .PHONY: generate
 generate: codesnippets command-json ## Regenerate automatic code documentation
diff --git a/composer.json b/composer.json
index 6b86abd0c..60c6997d9 100644
--- a/composer.json
+++ b/composer.json
@@ -4,7 +4,7 @@
     "description": "The TypoScript Reference (TSref) is a true reference describing the core Content Objects and functions available for Template building using the TypoScript template engine.",
     "license": "OPL-1.0",
     "require": {
-        "typo3/cms-core": "dev-main"
+        "typo3/cms-core": "^13.4"
     },
     "minimum-stability": "dev",
     "prefer-stable": true,
@@ -29,41 +29,41 @@
         "friendsofphp/php-cs-fixer": "^3.46",
         "symfony/yaml": "^7.0",
         "t3docs/codesnippet": "dev-main",
-        "typo3/cms-adminpanel": "dev-main",
-        "typo3/cms-backend": "dev-main",
-        "typo3/cms-belog": "dev-main",
-        "typo3/cms-beuser": "dev-main",
-        "typo3/cms-dashboard": "dev-main",
-        "typo3/cms-extbase": "dev-main",
-        "typo3/cms-extensionmanager": "dev-main",
-        "typo3/cms-felogin": "dev-main",
-        "typo3/cms-filelist": "dev-main",
-        "typo3/cms-filemetadata": "dev-main",
-        "typo3/cms-fluid": "dev-main",
-        "typo3/cms-fluid-styled-content": "dev-main",
-        "typo3/cms-form": "dev-main",
-        "typo3/cms-frontend": "dev-main",
-        "typo3/cms-impexp": "dev-main",
-        "typo3/cms-indexed-search": "dev-main",
-        "typo3/cms-info": "dev-main",
-        "typo3/cms-install": "dev-main",
-        "typo3/cms-linkvalidator": "dev-main",
-        "typo3/cms-lowlevel": "dev-main",
-        "typo3/cms-opendocs": "dev-main",
-        "typo3/cms-recycler": "dev-main",
-        "typo3/cms-redirects": "dev-main",
-        "typo3/cms-reports": "dev-main",
-        "typo3/cms-rte-ckeditor": "dev-main",
-        "typo3/cms-scheduler": "dev-main",
-        "typo3/cms-seo": "dev-main",
-        "typo3/cms-setup": "dev-main",
-        "typo3/cms-sys-note": "dev-main",
-        "typo3/cms-t3editor": "dev-main",
-        "typo3/cms-tstemplate": "dev-main",
-        "typo3/cms-viewpage": "dev-main",
-        "typo3/cms-workspaces": "dev-main",
-        "t3docs/examples": "dev-main",
-        "t3docs/site-package": "dev-main"
+        "t3docs/examples": "^13.2",
+        "t3docs/site-package": "dev-main",
+        "typo3/cms-adminpanel": "^13.4",
+        "typo3/cms-backend": "^13.4",
+        "typo3/cms-belog": "^13.4",
+        "typo3/cms-beuser": "^13.4",
+        "typo3/cms-dashboard": "^13.4",
+        "typo3/cms-extbase": "^13.4",
+        "typo3/cms-extensionmanager": "^13.4",
+        "typo3/cms-felogin": "^13.4",
+        "typo3/cms-filelist": "^13.4",
+        "typo3/cms-filemetadata": "^13.4",
+        "typo3/cms-fluid": "^13.4",
+        "typo3/cms-fluid-styled-content": "^13.4",
+        "typo3/cms-form": "^13.4",
+        "typo3/cms-frontend": "^13.4",
+        "typo3/cms-impexp": "^13.4",
+        "typo3/cms-indexed-search": "^13.4",
+        "typo3/cms-info": "^13.4",
+        "typo3/cms-install": "^13.4",
+        "typo3/cms-linkvalidator": "^13.4",
+        "typo3/cms-lowlevel": "^13.4",
+        "typo3/cms-opendocs": "^13.4",
+        "typo3/cms-recycler": "^13.4",
+        "typo3/cms-redirects": "^13.4",
+        "typo3/cms-reports": "^13.4",
+        "typo3/cms-rte-ckeditor": "^13.4",
+        "typo3/cms-scheduler": "^13.4",
+        "typo3/cms-seo": "^13.4",
+        "typo3/cms-setup": "^13.4",
+        "typo3/cms-sys-note": "^13.4",
+        "typo3/cms-t3editor": "^13.4",
+        "typo3/cms-tstemplate": "^13.4",
+        "typo3/cms-viewpage": "^13.4",
+        "typo3/cms-workspaces": "^13.4"
     },
     "scripts": {
         "generate:codesnippets": [