[TASK] Change references previously going to tsconfig

Releases: main, 13.4, 12.4

Author: linawolf

Documentation/About.rst

@@ -8,8 +8,7 @@ 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>`.
+TypoScript as used in frontend TypoScript and backend TypoScript, also called TSconfig.
 
 .. seealso::
 

Documentation/Functions/Stdwrap.rst

@@ -98,7 +98,7 @@ addPageCacheTags
 
     Pages, which have been cached with a tag, can be deleted from cache
     again with the TSconfig option
-    :ref:`TCEMAIN.clearCacheCmd <t3tsconfig:pagetcemain-clearcachecmd>`.
+    :ref:`TCEMAIN.clearCacheCmd <pagetcemain-clearcachecmd>`.
 
     ..  note::
         If you instead want to store rendered content into the

Documentation/Functions/Typolink.rst

@@ -882,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:
 

Documentation/Guide/Index.rst

@@ -9,10 +9,8 @@ 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 :doc:`TypoScript Reference <Index>`, insights into TYPO3
-backend configuration with TypoScript in the :doc:`TSconfig <t3tsconfig:Index>`
-documentation and explanations of TypoScript syntax in the
-":ref:`TypoScript Syntax <typoscript-syntax>`" chapter.
+TypoScript in the menu  on the left, including the
+:ref:`TypoScript Syntax <typoscript-syntax>` chapter.
 
 ----
 

Documentation/Index.rst

@@ -25,11 +25,10 @@ TypoScript Explained
 ----
 
 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.
 
 You can find a quick guide to TypoScript configuration at
-:ref:`guide`, insights into TYPO3 backend configuration with
-TypoScript in the :ref:`TSconfig <t3tsconfig:start>` documentation and
+:ref:`guide` and
 explanations of TypoScript syntax in the ":ref:`TypoScript Syntax <typoscript-syntax>`"
 chapter.
 

Documentation/Syntax/Conditions/Index.rst

@@ -38,7 +38,7 @@ condition that checks for a logged in frontend user.
 
 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 <t3tsconfig:conditions>`. These references
+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

Documentation/Syntax/FileImports/Index.rst

@@ -119,9 +119,9 @@ Alternatives to using file imports
 
 The following features can make file inclusion unnecessary:
 
-*   :ref:`Automatic global inclusion of user TSconfig of extensions <t3tsconfig:usersettingdefaultusertsconfig>`
-*   :ref:`Automatic global inclusion of page TSconfig of extensions <t3tsconfig:pagesettingdefaultpagetsconfig>`
-*   :ref:`Automatic page TSconfig on site level <t3tsconfig:include-static-page-tsconfig-per-site>`
+*   :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.

Documentation/TopLevelObjects/Module.rst

@@ -23,7 +23,7 @@ Therefore they are usually done in the file
     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
@@ -82,7 +82,7 @@ view.templateRootPaths
         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
@@ -120,7 +120,7 @@ view.partialRootPaths
         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