Skip to main content
Twenty slots. One hero article per authority area, each with a named owner and a scheduled review. An article is not finished until it has a row here.
Areas are chosen using the authority test in the article library overview. Rows are worked through the article maintenance process on a fixed cycle. Default review cadence for a hero article is quarterly.

The register

Fill a row when an area is agreed, before the article is written. Leave the empty slots visible: they are the honest picture of how much of the set is claimed. Rows 1 and 2 show examples using Doughnut Labs, a company that sells Doughnut Technology. Delete them and fill in your own.

Status values

Rules for this register

  • The cap is twenty. Adding a twenty-first hero article means demoting or retiring one first. A hero set that grows quietly becomes an ordinary content library with an aspirational label.
  • One owner per row, named. Not a team, not a role.
  • Every live row has a next review date. A row without one will never appear in a review cycle.
  • A last-updated date means something changed. Bumping a date without a substantive change removes the signal that tells you which articles need attention.
  • IDs are permanent and never reused. A demoted article keeps its history in the supporting register notes.
Last modified on August 6, 2026