Published Surface (Documentation / Knowledge Site)
Make your knowledge navigable at a persistent URL.
Hosts a structured, searchable, browsable surface — docs site, help centre, expertise hub, internal handbook — where readers find what they need on demand. Handles navigation structure, content versioning, and theme so the corpus is always live and current.
Shape
Operational dimensions
Each output waits on a human decision.
Fires when a user asks.
Owns a system-of-record; expensive to migrate.
Reads from and writes to external systems.
Inputs
- content corpus (docs, KB articles, handbook pages)
- information architecture / navigation structure
- brand and theme spec
- access policy (public / scoped)
Outputs
- live hosted site at a persistent URL
- structured navigation (nav tree, search index, ToC)
- versioned content state
- reader-side search and anchor affordances
Mechanism
Hosts a persistent, structured, browsable published surface (documentation site, knowledge site, public KB, expertise site) where a corpus of written content is navigable, current, and discoverable by readers on demand.
Why this is a primitive
Cannot be decomposed — the operation is one act of being-a-hosted-navigable-published-surface: persistent URL, structured navigation (nav tree / search / index), versioned content, public or scoped access for reading. It is not the authoring of the content (authoring composes with this), not the recurring delivery of content out to a list (that is scheduled distribution), and not the access-controlled delivery to specific recipients with tracking (that is access-controlled delivery). The surface itself — live, navigable, current — is what the buyer pays for.
Where it shows up
Related primitives
Tags
See where it fits.
Primitives are configured into named solution shapes for each client’s domain. The fastest next step is a conversation about which shape fits your problem.
Start a conversation