🚀 Help Improve TYPO3 Deployment Docs!

We’re looking for testers to try out our overhauled "Deploying TYPO3" documentation.

You’ll get a test account, a checklist, and support — all we need is ~30–60 mins of your time.

🧪 No need to use your own server

🙌 All skill levels welcome

🛠️ Hosts include jweiland.net, Mittwald.de, and Nexaa.io

Interested? Sign up here 👉 https://forms.gle/Cc3F7X14nbQbU2t2A

The #CSP (Content Security Policy) is a topic where many people are afraid of its complexity. 🧠

We have just updated the #TYPO3 📙chapters on this issue: https://docs.typo3.org/permalink/t3coreapi:content-security-policy

The changes include an overview of terminology, more links, and more examples.

We hope this helps to better implement CSP into your projects.

@brotkrueml Thanks, this has now been backported!

@brotkrueml Valid question. The "Releases:" line covered 13.4&12.4, but the merge did not kick off a bot, so it probably was not labelled. We'll check.

Ever worked with the default Extbase Validators and wondered what exactly they do and how they can be configured?

Finally, thanks to sponsorship of Björn Huber / Web Commerce, we now have an exhaustive list in the docs:

https://docs.typo3.org/permalink/t3coreapi:extbase-validator

The TYPO3 Documentation Team has enhanced the resources available to new integrators and developers, delivering a completely revamped #GettingStarted Tutorial. With updated content and new sections, this guide is designed to help #newcomers confidently navigate TYPO3 from day one.

https://typo3.org/article/community-budget-idea-improving-documentation-for-new-integrators-and-developers

👉 New to TYPO3 or need a quick refresh? Get up to speed with the basics in our quick guide—no installation tutorials, just the essentials! Watch now! 🔍

https://buff.ly/40RCYAY

#TYPO3 #CMS #TYPO3Basics

The TYPO3 Documentation Team made significant strides in 2024, achieving groundbreaking advancements and key improvements. 👏 🧡

Let’s explore the accomplishments and contributions that defined this transformative year: https://buff.ly/42vDK87

#TYPO3 #Documentation #TYPO3Community

I'm working on the #PHP dictionary, which collect definitions for every day words in the PHP culture.

handler, haystack, lexical variable, relaxed syntax, truthy or shallow clones often need some explanations.

Missing some words? Ping me !

https://php-dictionary.readthedocs.io/en/latest/

One of our most vital in-depth chapters about #DependencyInjection and #PHP architecture has been updated with a lot of effort from 👏 @lolli - we are happy for getting feedback on these changes.

Please see:

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/PhpArchitecture/Index.html

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/DependencyInjection/Index.html

The docker container that our PHP-based Documentation-rendering provides has a new helpful command:

✨"init" will guide you to quickly setup a fresh Documentation stub folder through a wizard process.

📚Read more: https://docs.typo3.org/permalink/h2document:how-to-start-docs-extension

We consolidated a few manuals, resulting in some moved links.

Please see https://docs.typo3.org/Home/RecentlyMovedChapters.html for detailed information about these moves:

TSconfig
➡️ TypoScript Explained

Typoscript syntax
➡️ TypoScript Explained

Upgrade Guide
➡️ TYPO3 Explained > Administration

several sections of Getting Started
➡️ TYPO3 Explained > Administration

CommonMark Markdown syntax can now be utilized in our documentation rendering pipeline, in addition to reST syntax.

Details are available here: https://typo3.org/article/first-steps-towards-implementing-commonmark-markdown-for-typo3-documentation

‼️PHP-based rendering now enforced for all documentation projects

As of today, all generated documentation on docs.typo3.org will make use of the PHP-based rendering (instead of Sphinx).

Enjoy all the new features and improved layout! Please see https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/Migration/Index.html for details on improving your workflow.

The documentation team is on the finishing stretch on improving the #TYPO3 "Beginner's Guide". Please check out https://typo3.org/article/community-budget-idea-interim-report-improving-documentation-for-new-integrators-and-developers and reach out to us if you are interested in giving feedback and shaping further improvements!

Another small but probably helpful improvement to the #TYPO3 Changelogs:

Each breaking change in the list of previous deprecations is now cross-referenced with the deprecation, see:

📚 https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/14.0/Breaking-105377-DeprecatedFunctionalityRemoved.html#breaking-105377-deprecated-functionality-removed

(Note: v14.0 is not released, this is the current development state)

Really great to see, that TER already has 210 extensions, which are compatible with TYPO3 v13 👍

The great #TYPO3 changelogs get a small, but helpful addition:

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog-13-combined.html

This now lists all features, breaking changes, deprecations and notices on a single page, spanning all minor&patch-releases.

We are excited to announce that the #TYPO3 Documentation Team is preparing to fully transition all extension manuals to the new #PHP-based reStructuredText (reST) rendering system, and we will be shutting down the old Sphinx-based rendering in the near future.

Learn more 👉 https://typo3.org/article/transition-to-full-php-based-rendering-for-all-typo3-extension-manuals