"Switch your extension’s documentation to the new PHP-based rendering"
summary
Claims a full TYPO3 changelog of several thousand pages now renders in 5 minutes for thousands of pages versus 30–60 minutes with the old Sphinx/Python renderer, and small docs hit about 56 seconds on the GitHub workflow. Uses a PHP-based renderer with Docker/Podman and optional GitHub Actions, a migration tool that converts settings.cfg to guides.xml, and automatic linting of PHP code snippets. New features include a hover popup that generates inter-manual composer links and PHP FQN linking to api.typo3.org with IDE-like info and GitHub line anchors; a live demo migrates an extension and produces seven rendered HTML files successfully.
AI-written summary · about
chapters (16)
- 0:00Introduction to new rendering
- 1:53Faster rendering and live updates
- 3:47Improved linking features
- 5:53Class name linking and IDE integration
- 7:38Migration steps and timeline
- 9:47Automatic testing and search options
- 11:42File handling and code snippets
- 14:12Live demo begins
- 20:40Cleaning up old files
- 25:51Setting composer name
- 31:17GitHub Actions setup
- 33:29Makefile for local rendering
- 37:05Q&A on documentation inclusion
- 39:00Q&A on templates and tools
- 41:19Q&A on generation commands
- 43:04Future projects and closing
related talks
01h 02mRewriting 12-Year-Old Code
01h 04mBye bye drupalisms! Propelling Drupal into a modern PHP ecosystem
18mMy Take on PHP
49mPanel Discussion: The Future of PHP
43mStepping into the future: Migrating & Deploying PHP7
59mTransforming your Documentation Process
49mThe why and the how of moving to 7.x
58mTesting Complex Applications for PHP7