TYPO3-Documentation · linawolf · Apr 1, 2026 · Mar 30, 2026
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: 🔒️ Security Issue
-    url: https://typo3.org/community/teams/security
+    url: https://typo3.community/contribute/teams-committees/security
     about: If you encounter a security issue 👿, please reach out **only** to the TYPO3 Security Team by writing to security (at) typo3.org. Please don't share the information with the Documentation Team or anyone else.
   - name: ❓ Ask question
     url: https://typo3.slack.com/app_redirect?channel=C028JEPJL

diff --git a/Documentation/Administration/Upgrade/Tools/Index.rst b/Documentation/Administration/Upgrade/Tools/Index.rst
@@ -28,7 +28,7 @@ Resources
 Support
 -------
 
-Visit the `TYPO3 Slack <https://typo3.org/community/meet/chat-slack>`__ and search for the `#ext-typo3-rector`
+Visit the `TYPO3 Slack <https://typo3.community/meet/slack>`__ and search for the `#ext-typo3-rector`
 channel. You can also open an issue or start a discussion on the projects GitHub page.
 
 EXT: Core Upgrader (v2)
@@ -44,4 +44,4 @@ The extension allows to perform multiple TYPO3 Core version upgrades in one step
 the older upgrade wizards.
 
 Another way to perform (and test/verify) upgrades of multiple TYPO3 versions in one go is outlined
-in a `blog article "Automatic TYPO3 Updates Across Several Major Versions With DDEV <https://typo3.org/article/automatic-typo3-updates-across-several-major-versions-with-ddev>`__.
+in a `blog article "Automatic TYPO3 Updates Across Several Major Versions With DDEV <https://news.typo3.com/archive/automatic-typo3-updates-across-several-major-versions-with-ddev>`__.
diff --git a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Bestpractice.rst b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Bestpractice.rst
@@ -334,5 +334,5 @@ Further readings
 Get inspired by Martin Pribyl's article about how he did a full translation and
 proofreading of TYPO3 CMS into Czech language: `Bringing Czech to TYPO3 - My Translation Journey`_
 
-.. _Bringing Czech to TYPO3 - My translation Journey: https://typo3.org/article/bringing-czech-to-typo3-my-translation-journey
+.. _Bringing Czech to TYPO3 - My translation Journey: https://news.typo3.com/archive/bringing-czech-to-typo3-my-translation-journey
 
diff --git a/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst b/Documentation/ApiOverview/Localization/TranslationServer/Crowdin/Faq.rst
@@ -44,7 +44,7 @@ Crowdin please contact either the maintainer of the extension or the
     The language needs to be supported by TYPO3 itself as well, see
     :ref:`i18n_languages` for a list of all languages.
 
-..  _Localization Team: https://typo3.org/community/teams/localization
+..  _Localization Team: https://typo3.community/contribute/teams-committees/localization
 
 
 ..  _crowdin-faq-pootle:

diff --git a/Documentation/ExtensionArchitecture/BestPractises/ExtensionKey.rst b/Documentation/ExtensionArchitecture/BestPractises/ExtensionKey.rst
@@ -97,7 +97,7 @@ Security
 
 You are responsible for security issues in your
 extensions. People may report security issues either directly to you
-or to the `TYPO3 Security Team <https://typo3.org/community/teams/security/>`__.
+or to the `TYPO3 Security Team <https://typo3.community/contribute/teams-committees/security>`__.
 In any case, you should get in
 touch with the Security Team which will validate the security fixes.
 They will also include information about your (fixed) extension in
@@ -106,7 +106,7 @@ the Security Team, your extension will be removed by force from the
 TYPO3 Extension Repository.
 
 More details on the security team's policy on handling security issues
-can be found at https://typo3.org/teams/security/extension-security-policy/.
+can be found at https://typo3.community/contribute/teams-committees/security/extension-security-policy.
 
 .. _extension-key-registration:
 

diff --git a/Documentation/ExtensionArchitecture/FileStructure/ComposerJson.rst b/Documentation/ExtensionArchitecture/FileStructure/ComposerJson.rst
@@ -178,7 +178,7 @@ license
 (*recommended*)
 
 Has to be `GPL-2.0-only` or `GPL-2.0-or-later`.
-See: https://typo3.org/project/licenses/.
+See: https://typo3.com/typo3-cms/what-is-typo3/open-source/licenses.
 
 
 require

diff --git a/Documentation/ExtensionArchitecture/HowTo/PublishExtension/PublishToTER/Index.rst b/Documentation/ExtensionArchitecture/HowTo/PublishExtension/PublishToTER/Index.rst
@@ -19,10 +19,11 @@ effort in coding:
 *  Are there any extensions in the TER yet which have the same functionalities?
 *  If yes, why do we need your one? Wouldn't it be an option to contribute to
    other extensions?
-*  Did you read and understand the `TYPO3 Extension Security Policy <https://typo3.org/community/teams/security/extension-security-policy>`__?
+*  Did you read and understand the
+   `TYPO3 Extension Security Policy <https://typo3.community/contribute/teams-committees/security/extension-security-policy>`__?
 *  Does your extension include or need external libraries? Watch for the
    license! Learn more about the
-   `right licensing <https://typo3.org/project/licenses/>`__.
+   `right licensing <https://typo3.com/typo3-cms/what-is-typo3/open-source/licenses>`__.
 *  Do you have a public repository on e.g. GitHub, Gitlab or Bitbucket?
 *  Do you have the resources to maintain this extension?
 *  This means that you should

diff --git a/Documentation/Introduction/Index.rst b/Documentation/Introduction/Index.rst
@@ -39,10 +39,10 @@ to generate one for you or follow the :ref:`site package tutorial <t3sitepackage
 Getting help with TYPO3
 =======================
 
-`Meet the TYPO3 Community <Meet the TYPO3 Community>`_. You can chat with us
-`on Slack <https://typo3.org/community/meet/chat-slack>`_, go to meetings in
-your `local user group <https://typo3.org/community/meet/user-groups>`_ or
-meet us at `events <https://typo3.org/community/events>`_.
+`Meet the TYPO3 Community <https://typo3.community/meet>`_. You can chat with us
+`on Slack <https://typo3.community/meet/slack>`_, go to meetings in
+your `local user group <https://typo3.community/meet/user-groups>`_ or
+meet us at `events <https://news.typo3.com/events>`_.
 
 You can discuss TYPO3 related questions in the https://talk.typo3.org/ forum.
 

diff --git a/Documentation/Security/SecurityTeam/Index.rst b/Documentation/Security/SecurityTeam/Index.rst
@@ -9,13 +9,13 @@ Working with the TYPO3 Security Team
 ====================================
 
 You can find details about the TYPO3 Security Team at
-https://typo3.org/community/teams/security/.
+https://typo3.community/contribute/teams-committees/security.
 
 You can contact the TYPO3 Security Team at `security@typo3.org <mailto:security@typo3.org>`_ .
 
 TYPO3 Core security updates, extension security updates, and unmaintained
 insecure extensions are announced in formal
-`TYPO3 Security Bulletins <https://typo3.org/help/security-advisories>`_.
+`TYPO3 Security Bulletins <https://typo3.org/security>`_.
 
 
 ..  index:: Security; Reporting
@@ -125,4 +125,4 @@ version with the TYPO3 Security Team.
 Further details about the handling of security incidents and time
 frames can be found in the official
 `TYPO3 Extension Security Policy
-<https://typo3.org/community/teams/security/extension-security-policy/>`_
+<https://typo3.community/contribute/teams-committees/security/extension-security-policy>`_
diff --git a/Documentation/Security/Versions/Index.rst b/Documentation/Security/Versions/Index.rst
@@ -140,7 +140,7 @@ Security bulletins
 When security updates for TYPO3 or an extension become available, they
 will be announced on the "TYPO3 Announce" mailing list, as described
 above, but also published with much more specific details on the
-official TYPO3 Security Team website at https://typo3.org/help/security-advisories/.
+official TYPO3 Security Team website at https://typo3.org/security.
 
 Security bulletins for the TYPO3 Core  are separated from security
 bulletins for TYPO3 extensions. Every bulletin has a unique advisory

diff --git a/Documentation/Testing/TestRunners.rst b/Documentation/Testing/TestRunners.rst
@@ -364,7 +364,7 @@ Thus, effort is being made to offer generators that can create
 Composer script integration plus helpers, to achieve integrating
 a choice of most common tools.
 
-Please check out the work of the `TYPO3 Best Practices Team <https://typo3.org/community/teams/best-practices>`__
+Please check out the work of the `TYPO3 Best Practices Team <https://typo3.community/contribute/teams-committees/best-practices>`__
 for more information on this. If you are interested in helping
 this effort, please get in touch.