Register for docs.typo3.org¶
Table of Contents
Walk through the following steps in defined order. Proceed with next step only if the previous step was successful.
composer.json, see composer.json
This file is necessary, in order to determine required information, like vendor, package name and supported TYPO3 version.
Documentation/Settings.cfg, see Settings: Documentation/Settings.cfg
If this file does not exist, documentation will get rendered, but title will not be displayed in the left sidebar.
This requirement may be dropped in the future.For now it is necessary to at least add a minimal
Example for very minimal Settings.cfg, for full example see Settings: Documentation/Settings.cfg:
[general] project = Extension name
Add new webhook, see Webhook
In case the old hook is in play, remove it first, and add the new one instead.
Trigger webhook for released versions, see Reregister versions (optional)
In case documentation for already released versions should be rendered again, follow Reregister versions.
It will explain how the process of rendering can be triggered once more for already released versions.
Request redirects (optional)
This step adds work load to a small team. Please check whether there is a need to request redirects.
Inform the TYPO3 Documentation Team, within #typo3-documentation Slack channel. Registration for Slack is available at my.typo3.org. Alternatively, a redirect can be requested by commenting in this GitHub issue.
The team will setup the redirects from existing legacy rendering to current rendering:
For full information about publishing extensions check Publish your extension.
The following steps only describe what's necessary for documentation publishing and for the link to the documentation to be displayed on extensions.typo3.org:
Add Webhook (if not already done).
Tag the Git commit with a valid version: Version numbers.
Push (publish) the Git tag.
Publishing a tag will trigger rendering of documentation for that tag. The result will be published on docs.typo3.org. Furthermore a JSON file which provides info about the new available documentation will be automatically generated on the documentation server.
This file is used by extensions.typo3.org to find matching documentation.
extensions.typo3.org will only show the link to the latest available version.
This has to match the released version on docs.typo3.org.
No fallback is in place (for example
main will not be linked by default).
Please note that it might take some time until extensions.typo3.org displays changed URLs to docs.typo3.org. The information needs to be picked up by a command. Caches for detail page need to be invalidated, and SOLR index needs to be updated.
docs.typo3.org does no longer show three level version numbers in form of
Only the first two levels are shown
This reduces the amount of documentation while keeping relevant information, as patch levels should not introduce breaking changes or new features.
The rendering supports two branches within repositories:
Should contain the current development state, used for upcoming release. Every push to these branches triggers a new rendering, available at
Both branch names are supported, but result in the same URL. Please use
masteris only supported for backward compatibility.
Should contain a draft of the documentation. Every push to this branch triggers a new rendering, available at
https://docs.typo3.org/p/<vendor>/<package>/draft/en-us/(same URL as main, except main is replaced by draft).
This is not indexed by search engines. This branch can be used to test rendering before releasing a new version of an extension.
In order to test a different rendering, remove the branch, and create it again.
The URL structure now consists of the following parts:
Collects all packages of the same vendor, for example "typo3" or a company providing extensions. Same as on packagist.org.
Defines the package. Same as on packagist.org.
Defines the version, either in form of "Major.Minor" or
Defines the locale, for example
Since May 29th 2019 a new infrastructure is in place at docs.typo3.org. This requires some migration tasks, in order to ensure that extension documentation is rendered on docs.typo3.org.
Existing legacy documentation is kept until end of 2020. Each documentation contains an information block that it's outdated, together with a link to the necessary steps.
In order to migrate, follow Necessary steps.