Register for

Follow the Necessary steps in order to have extension documentation rendered on out of the box. When migrating existing documentation, Info about changes might be interesting as well.

Necessary steps

Walk through the following steps in defined order. Proceed with next step only if the previous step was successful.

  1. Add mandatory composer.json, see composer.json

    This file is necessary, in order to determine required information, like vendor, package name and supported TYPO3 version.

  2. Add Documentation/Settings.cfg, see 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 Documentation/Settings.cfg.

    Example for very minimal Settings.cfg, for full example see Settings.cfg:

    project = Extension name
  3. Add new webhook, see Webhook

    The legacy webhook is no longer necessary, as explained in Legacy webhook. Instead the new webhook has to be added as described at Webhook.

    In case the old hook is in play, remove it first, and add the new one instead.

  4. 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.

  5. 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 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:

    • legacy URL:<extkey>/<version>/
    • new URL:<vendor>/<package>/<branch>/<locale>

All future versions will now be rendered, see Workflow of an extension release. Also some branches will be rendered, see Supported branches.

Workflow of an extension release

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

  1. Add Webhook (if not already done).
  2. Tag the Git commit with a valid version: Version numbers.
  3. Push (publish) the Git tag.

Publishing a tag will trigger rendering of documentation for that tag. The result will be published on 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 to find matching documentation. will only show the link to the latest available version. This has to match the released version on No fallback is in place (e.g. master will not be linked by default).

Please note that it might take some time until displays changed URLs to 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.

Version numbers does no longer show three level version numbers in form of Major.Minor.Patch. Only the first two levels are shown Major.Minor.

This reduces the amount of documentation while keeping relevant information, as patch levels should not introduce breaking changes or new features.

Supported branches

The rendering supports two branches within repositories:

master / main

Should contain the current development state, used for upcoming release. Every push to these branches triggers a new rendering, available at<vendor>/<package>/master/en-us/.

Both branch names are supported, but result in the same URL. Please use either master or main, not both.


Should contain a draft of the documentation. Every push to this branch triggers a new rendering, available at<vendor>/<package>/draft/en-us/ (same URL as master, except master 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.

URL structure

The URL structure now consists of the following parts:<type>/<vendor>/<package>/<version>/<locale>



One of:

Provides documentation for composer packages (TYPO3 third party extensions)
Provides documentation for TYPO3 core extensions.
Provides official manuals (guides, tutorials, references).
Provides the homepage of
Provides further documentation, e.g. for Surf or Fluid
Collects all packages of the same vendor, e.g. “typo3” or a company providing extensions. Same as on
Defines the package. Same as on
Defines the version, either in form of “Major.Minor” or master or draft.
Defines the locale, e.g. en-us or fr-fr.

Info about changes

Since May 29th 2019 a new infrastructure is in place at This requires some migration tasks, in order to ensure that extension documentation is rendered on

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.