The Functional Page Types Beyond Pillars and Spokes

Some information needs have a shape that a narrative spoke structure fits poorly: a definition needs immediate scannability rather than explanatory buildup, and a comparison needs parallel structure across options rather than sequential narrative. Functional page types, glossary, comparison, FAQ, and evidence pages, exist because each prompt category from Chapter 7.2 implies a different structural shape, and forcing every need into a generic spoke template serves none of them optimally.

A glossary page is built for immediate lookup: the term stated clearly and the definition delivered in the first sentence, judged on how quickly and precisely it delivers the exact meaning a reader or system is looking for. This is a stricter, more compressed discipline than a standard spoke, which can use more narrative buildup; a glossary entry should never bury its core definition inside explanation that must be read in full to extract the term's meaning.

Comparative and evaluative prompts ask how options differ or whether something fits a situation, and answering that well requires the same dimensions, price, features, use case, limitations, assessed consistently and predictably across every option. A comparison written as sequential narrative, discussing one option fully before moving to the next, technically covers the same information but fails the comparison's actual purpose, since the comparison itself has to be assembled by the reader rather than delivered directly.

Every spoke and pillar already carries its own FAQ section serving that specific page's content, per this framework's standing production rules. A dedicated FAQ page serves the silo as a whole, gathering cross-cutting questions that don't belong naturally to any single spoke's narrow scope, or surfacing especially high-value questions that deserve more prominent placement than a page-bottom section provides.

An evidence page holds data, citations, and proof points in a dedicated, standalone location supporting claims made elsewhere in a silo. It becomes useful specifically when the same underlying data supports multiple claims across multiple spokes, letting each spoke reference one canonical, citable source rather than repeating or subtly redescribing the same evidence in different places, which also strengthens source evaluation by keeping evidence consistent.

The decision should happen systematically during the content-to-prompt mapping work in Chapter 7.5, checking whether an intent cluster's underlying prompt category calls for a glossary entry, comparison structure, FAQ placement, or evidence page rather than defaulting to a standard spoke. Catching a mismatch, such as a definitional cluster mapped to narrative prose, during planning is more efficient than discovering it after a page fails to retrieve reliably.

No. They are a vocabulary for recognizing which structural shape an information need calls for, not a checklist requiring every silo to contain all five types. A silo might have no need for a dedicated evidence page if none of its claims are reused across multiple spokes, while another silo built around comparative decisions might rely heavily on comparison pages. The goal is matching shape to need, not filling a quota of page types.

Functional page types define which structural shape a piece of content needs; modular templates, covered in Chapter 8.5, turn each of those shapes into reusable scaffolding that makes the shape repeatable across a silo without becoming rigid. A comparison page's parallel-structure requirement, for instance, becomes a comparison template that encodes the requirement while leaving the actual comparative content flexible to the specific options being discussed.