Skip to main content

Page Type View

Use this view when the question is what kind of page you need.

Page type names the job. Section path names the terrain.

Naming starts after classification. Use Naming Standards as the System of Names authority for route names, filenames, and the SSOT that owns each name class.

Type Catalogue​

Every page has one job. Choose the job before writing the body.

  • hub — orients a section and routes the reader. It does not teach. Use for top-level and section-level front doors such as /playbook/index.mdx, /playbook/wiki-index.mdx, and topic folder indexes.
  • concept — explains one reusable idea. Use for models, standards, principles, and definitions that need a durable home.
  • playbook — guides repeatable action. Use when the reader needs steps, outputs, checks, and failure modes.
  • domain-map — maps a territory. Use for industries, domains, ecosystems, value chains, forces, players, and opportunity surfaces.
  • evidence — preserves source-backed claims. Use when confidence, source trail, and implication matter more than teaching.
  • glossary — clarifies language. Use when aliases, canonical terms, and contrast need to be explicit.
  • decision-record — records a public architectural decision. Use when the decision, context, and consequences should remain visible.

Index Patterns​

An index.md or index.mdx is not a type by itself. It is a front-door pattern applied to one of the page types above.

The page type answers "what job does this page perform?" The index pattern answers "how does this route help the reader choose?" Do not create a new page type just because a page is named index.

  • Hub index — route a section. Applies to broad folders such as /playbook/, /playbook/standards/, /playbook/ai/, and /playbook/playbooks/.
  • Domain-map index — help the reader choose inside a territory. Applies to folders such as /playbook/industries/, /playbook/business/, and domain-specific folders with players, platforms, process, and performance pages.
  • Concept index — teach the central model for a folder, then route to deeper children. Applies when the folder is organized around one reusable idea rather than a navigation hub.
  • Template index — help the editor choose the right template or standard. Applies to /playbook/standards/templates/ and similar operating-reference folders.
  • Projection index — render a generated map from frontmatter or data. Applies to /playbook/wiki-index, /playbook/domain-matrix, and this page. The generated projection is a map, not hand-authored canon.

All index pages follow the Index Page Standard: route before teaching, show the choice logic above the fold, add scent to links, and move deep theory into child pages.

Where Applied​

Use this routing table before rewriting an index.

Route shapePage typeIndex patternFirst-screen job
/playbook/index.mdxhubHub indexChoose the main wiki start path
/playbook/<section>/index.*hubHub indexChoose the right child page in a section
/playbook/industries/index.mdxdomain-mapDomain-map indexChoose an industry shortlist before theory
/playbook/<domain>/<domain>-*/index.*domain-mapDomain-map indexChoose by players, platform, process, or KPI
/playbook/standards/templates/index.*conceptTemplate indexChoose the right reusable writing/build shape
/playbook/wiki-index.mdxhubProjection indexRead the generated public wiki spine
/playbook/domain-matrix.mdxdomain-mapProjection indexRead cross-domain intersections
/playbook/page-types.mdxconceptProjection indexChoose the page job and governing pattern

If the route is an index but the first screen does not help the reader choose, rewrite the page or move the teaching into a child page.

When the route, filename, or folder name is the open question, use Naming Standards. When the page job or index pattern is the open question, use this page.

Projection​

Preflight Choice​

Before a /playbook edit, choose and record:

  • change_class: maintenance, content, new-page, or rewrite
  • route: the public /playbook/... destination
  • page_type: the job the page performs
  • template: the shape that governs the edit
  • language_expected: whether DDL/DML updates are likely

New pages and material rewrites must declare page_type and template before editing. Maintenance edits still need a preflight reason so the close record can distinguish a formatting fix from a content decision.

Index pages are decision surfaces. They route before they teach. Use the Index Page Standard before rewriting any /playbook/**/index.* page.

Hub pages orient and route. They do not teach. Use the Hub Index Template for the full migration process.

Enforcement​

Touched /playbook pages now close through two local gates:

  • wiki-flow-guard.mjs blocks edits that skipped Map-First preflight or close receipts.
  • playbook-content-check.mjs --strict blocks touched playbook pages whose type, template shape, or inner/outer boundary fails.

Legacy untouched pages remain backlog. Once a page is touched, it must carry frontmatter type and match its page job before Stop, commit, pre-push, or npm run playbook:quality can pass. Emergency bypasses use the auditable WIKI_FLOW_OVERRIDE=1 receipt path.

Failure Modes​

  • Type drift: The frontmatter says hub, but the body teaches. Change the type or move teaching into child pages.
  • Template drift: The page records a template in preflight but closes without the sections that template requires.
  • Advisory drift: The post-edit warning fires, but no blocking gate catches the same failure at commit time.

Story Surfaces​

src/pages pages sell the Dream, frame the journey, and point toward reusable charts. They may carry the narrative spine, current offer, or product story. They should not become knowledge buckets.

/playbook pages teach reusable know-how. Community, games, systems, agency, AI, and crypto belong here when the reader can apply the pattern without knowing this repo.

Context​