gmtales-docs Help

Automatic Linking

As you write natural prose, GMTales recognizes article names and turns them into hyperlinks. You get a wiki-like web of knowledge without ever inserting a link by hand.

On save, GMTales scans the text for:

  1. Article titles

  2. Article aliases

  3. Comma-separated title variations (the inverted form)

Each match becomes a link and records an article relation behind the scenes. Matching is case-insensitive.

# The Council of Elrond The hobbits rested in Rivendell for two months before the Council met.

If an article titled "Rivendell" exists, the mention is linked automatically.

Comma-Separated Titles

A title like Oakenshield, Thorin also matches its inverted form, Thorin Oakenshield:

The company is led by Thorin Oakenshield, heir to the throne of Erebor.

Aliases

Aliases declare explicit alternative names for the same article:

# Aragorn <!-- alias: Strider, Elessar, Thorongil -->

Any of those names in other articles now links here:

Strider led the hobbits out of Bree by night.

Disambiguation and Priority

When multiple articles could match the same phrase, priority is:

  1. Main title (highest)

  2. Aliases

  3. Comma-separated variations (lowest)

If multiple matches share the same priority, GMTales serves a disambiguation page listing the candidates so the reader can choose:

Baggins may refer to: - Bilbo Baggins (character) - Frodo Baggins (character)

Specificity

When matches overlap in the same text, the more specific (longer) match wins: with articles "Helm's Deep" and "Battle of Helm's Deep", the phrase "Battle of Helm's Deep" links to the battle, not the fortress.

Keys for Explicit Linking

A key is a stable reference that survives title changes:

<!-- key: aragorn --> # Aragorn

Link to it with standard Markdown link syntax:

The council placed its hope in [the heir of Isildur](aragorn).

Article Relations

Every auto-link stores a relation between source and target. Relations power backlinks and the graph view.

Visibility of Relations

Relations always follow the most restrictive rule in play:

  • If the target article is restricted, the relation inherits those restrictions.

  • If the mention appears inside a secret block, the relation is restricted to that block's visibility.

  • If both are restricted, the relation uses the intersection.

21 June 2026