Every Page Links Out

A page with no links out isn't finished.

Thread:
Institutions
Level:
operational, in the guides column
File:
wiki/patterns/every-page-links-out.md
Every Page Links Out Sketch in perspective: a wooden fingerpost stands where two paths cross, with a blank, hatched board at its top. Below the board, four arms point in four directions. On them, in turn, are a small grid, a card with a circle on it, a closed book, and a thread circle. A mannequin stands at the foot of the post, pointing up at the arms. The post's blank board is a single page on the site, the focus. The crossing paths are where readers arrive, often straight from a search. The arms are the page's links, the solution: the grid points to the table, the card to a pattern the page introduces or applies, the book to the sources it draws on, and the thread circle to the other pieces in its thread. The figure is a reader who has just arrived and can see where to go next. The metaphor: a page as a signpost, not a dead end.
Fig. 5

A page with no links out isn’t finished.

Context

A site, wiki, or body of documentation that grows piece by piece over time, often written by different people.

Problem

Pages written one at a time tend to become islands. A guide loses the reasons behind it and becomes a recipe. A theory essay loses its practical consequences and becomes a slogan. Readers who arrive from a search engine land on one page and never see the rest.

Forces

Solution

Therefore, link every page to the other pieces in its thread, to the table, to the patterns it introduces or applies, and to the sources it draws on.

Actions

  • Fill in front matter (threads, patterns, patterns_applied, sources) so the website can generate the table, the thread footer, and pattern backlinks.
  • Keep hand-written links in the body to the ones that carry meaning.
  • After renaming a file, search for its old name and fix every reference.

Consequences

  • Positive: readers who arrive anywhere can find the rest, and reasons travel with instructions.
  • Negative: generated links depend on front matter being right, and links break when files move. The site build checks front matter; renames still need a search.

Mark up this page on GitHub