How to Start Documentation for Your TYPO3 Extension

This chapter describes how to create documentation for your extension using local editing and rendering with Docker. It requires Docker for running the rendering toolchain locally on your computer to check if the documentation is rendered correctly.

This is the preferred workflow, but if you have problems with Docker or would like to edit directly on GitHub, see the older Tip of the Day How to start Documentation for your TYPO3 Extension.

If necessary, ask for help as explained in Help & Support.

  1. Clone sample extension manual

    In a temporary directory, clone the GitHub project sample extension manual

    git clone

    Move or copy the entire Documentation directory, so that the Documentation directory is a direct subdirectory of your extension, e.g.

    cp -r TYPO3CMS-Example-ExtensionManual/Documentation <extension-directory>/
  2. Add additional files

    Some files are not mandatory, but it is recommended to use them:

    • .gitignore is useful, so you don't accidentally commit the generated documentation in Documentation-GENERATED-temp to your Git repository.
    • .editorconfig is useful, so you will use the recommended Coding Guidelines in your editor or IDE. You may need to set this up first (see EditorConfig Plugin for PhpStorm).
    # cp .gitignore (make sure you don't accidentally overwrite existing one though!)
    cp -n TYPO3CMS-Example-ExtensionManual/.gitignore <extension-directory>/.gitignore
    # cp .editorconfig (make sure you don't accidentally overwrite existing one though!)
    cp -n TYPO3CMS-Example-ExtensionManual/.editorconfig <extension-directory>/.editorconfig

    You may also want to consider adding CONTRIBUTING.rst and README.rst to your extension, if you plan to host the repository on GitHub.

  3. Edit the documentation

    Start editing away. Use the existing text to guide you. Look at other extension manuals (for example sphinx) for inspiration. (Click on "Related Links" to jump to the repository or scroll to bottom of rendered page and click on "View page source" to see reST source.)

    Check out the section on reST to see how to format headlines, code-blocks, images etc. and use the reST & Sphinx Cheat Sheet as a handy reference.

  4. Fill out Settings.cfg

    Be sure to fill out Settings.cfg correctly as described in Settings.cfg.

  5. Render the Documentation Locally

    Before you publish your changes, make sure the documentation is rendered correctly.

    Look at Rendering Documentation With Docker for a quick start.

  6. When You Are Done, Publish Your Changes

    If you are working on your own extension, make it publicly available. The documentation will then automatically be rendered on


Think about hosting your extension repository on GitHub. That way others can report issues and assist you by creating change requests for the documentation and code!