TYPO3 Documentation
How to Document TYPO3
Options
Give feedback View source How to edit Edit on GitHub Full documentation (single file)

How to Document TYPO3

BASICS

  • Basic principles
  • ReST Cheat Sheet
  • Markdown Cheat Sheet

REFERENCE

  • reStructuredText
    • Code blocks and code structure
      • Code blocks
      • Configuration values (confval)
      • Inline Code
      • PHP domain
      • Site settings
    • Directives
      • Accordion
      • Admonitions: tip, note, warning, see also, etc
      • Cards
      • Comments
      • Special characters
      • Tables
      • Tabs
      • Versions
      • ViewHelper
      • Embed YouTube videos
    • Figures and diagrams
      • Images
      • Zoom and lightbox
      • Float and alignment
      • PlantUML diagrams
    • Inline Markup
      • Bold, Italic etc.
      • Text Roles
    • Links
      • Anchors
      • API links
      • Composer / Extensions
      • Core source
      • Documentation references
      • example.org
      • External URLs
    • Lists
      • Styled numbered sections (bignums)
      • Bullet lists / unordered lists
      • Definition lists
      • Directory tree
      • List items as buttons
      • Numbered lists
    • Menus and headers
      • Headlines
      • Main menu
      • Content menu
      • Including files
      • Navigation title
      • Orphans
      • Sidebar
  • CGL for ReST files
  • File structure
  • guides.xml
  • Rendering container
  • Screenshot container

HOWTOS

  • Edit Locally
  • Edit on GitHub
  • Contribute
    • Help
  • Migrate
    • Markdown to ReST
  • Render
    • Automatic re-rendering (WYSIWYG)
  • Document extensions
    • Webhook
    • Reregister versions
    • FAQ
    • Contribute to system extensions
    • Contribute to third-party extensions

ADVANCED

  • Advanced
    • Coding guidelines for reST files
    • Spelling
    • Formats (reST, Markdown)
    • Spelling, terms and glossary
    • Guidelines for creating images
    • How to add translations
    • Licenses
    • Redirects
    • Policy for making and reviewing contributions

MAINTAINERS

  • For maintainers
    • Backport changes
    • Apply Changelog entries to the docs
    • Code snippet generation
    • Fluid ViewHelper reference generation
    • New major Core version
    • Tools of the Documentation Team
  • Sitemap

Options

Give feedback View source How to edit Edit on GitHub Full documentation (single file)
  1. How to Document
  2. reStructuredText
  3. Links
  4. Anchors
Give feedback Edit on GitHub

Link anchors 

Link anchors assign a unique name to a headline and its section. These anchors can be used in internal references and references between TYPO3 manuals.

As long as the anchor of a section stays the same the section can be moved to another page or the headline can be renamed and references will still go to the correct target.

You can define a link anchor with a label for a section.

In the following example, the link target inline-columns is assigned to the section with the title "Inline columns".

Place the link anchor definition directly before the section header:

..  _inline-columns:

Inline columns
==============
Copied!

Link anchors should contain alphanumeric signs plus hyphen: ([a-z][0-9][-]). All other signs are automatically transformed by the symfony \Symfony\Component\String\Slugger\AsciiSlugger .

A recommended recipe could be:

  1. Duplicate the headline
  2. Transform to lowercase
  3. Replace all blanks by a hyphens -
  4. Remove all non-alphanumeric characters or replace them by a hyphen -
  5. Add .. _ at the beginning.
  6. Add : at the end.

We are currently trying to let Fractor support <https://github.com/andreaswolf/fractor/issues/206> this and other transformations.

Keeping anchors working 

An anchor is a promise: once a page containing it has reached main, the anchor must keep working, even after the heading it was on is gone. Never just delete an anchor. What to do instead depends on why the content went away:

  • Restructured, but the concept still exists somewhere — a subchapter or example merged into, or moved under, a different heading: move the anchor to the heading that now covers that content, even if it is now less specific (for example the parent chapter).
  • The whole concept was removed — a breaking change, or it is no longer the recommended approach: move the anchor into a Documentation/404.rst page instead (create it if it does not exist yet), and add a short entry explaining what happened. See Redirecting renamed or deleted pages for the full pattern, including a real example.

This applies everywhere, not just to official TYPO3 documentation repositories — anyone linking to your docs, from a bookmark, a search result, or another page, is relying on the anchor still being there.

Also watch for malformed anchor lines (the wrong number of leading dots, a missing trailing colon) — they silently fail to work as a permalink, and can render as broken, stray text on the page instead of an invisible link target.

  • Previous
  • Next
Reference to the headline

Copy and freely share the link

This link target has no permanent anchor assigned. You can make a pull request on GitHub to suggest an anchor. The link below can be used, but is prone to change if the page gets moved.

Copy this link into your TYPO3 manual.

  • Home
  • Contact
  • Issues
  • Repository

Last rendered: Aug 12, 2026 16:28

© since 2017 by the TYPO3 contributors
  • Legal Notice
  • Privacy Policy