Link documentation pages

Use a $docs reference for a link to another documentation page. Ginko resolves the reference to the correct public route for the reader's locale.

[Configure the sidebar]($docs/authoring/navigation)

The reference uses the canonical English route segments, not the localized public URL. Ginko maps those segments to the document's numeric identity. The same reference belongs in the German translation:

[Navigation gestalten]($docs/authoring/navigation)

On the English page it resolves to /docs/authoring/navigation. On the German page it resolves to /de/dokumentation/inhalte/navigation.

Link to a heading

Append the heading fragment to the canonical English route reference:

[Choose a section control]($docs/authoring/navigation#choose-the-section-control)

Use a local fragment when the heading is on the current page:

[Jump to installation](#installation)

Keep heading text stable after publishing. Changing a heading also changes its generated fragment.

Link application routes and assets

Use a root-relative URL for a Nuxt route that is not backed by the docs collection:

[Open the status page](/status)

Reference public assets from the site root:

![Acme wordmark](/images/acme-wordmark.svg)

Store that image at public/images/acme-wordmark.svg.

Link external sites

Use a complete HTTPS URL and name the destination:

[Read the Nuxt documentation](https://nuxt.com/docs)

Do not write localized public paths such as /de/dokumentation/... for links between docs pages. $docs references survive German slug changes, and the content build fails when a destination or #anchor no longer exists. Rename an English route segment or a heading only when you are ready to update references that use it.