Build a Documentation Website with AI
The full path to docs people can actually navigate — plan the doc set, structure the site, write the guides and the API reference, then ship it as a coherent documentation site.
Overview
Documentation fails in a specific way: each page is fine, but the whole is a maze — no clear path from 'getting started' to 'reference', guides that assume what they should explain, an API section nobody can find. A documentation website is a structure problem before a writing one. This blueprint builds one documentation-first: plan the doc set around what readers actually need to do, organize it into an information architecture that makes the next step obvious, write the conceptual guides and the API reference as distinct, deliberate layers, and ship it. It's specifically a documentation site — not a company marketing site, and not an internal knowledge base — so every decision serves a reader trying to accomplish a task with your product. Each stage is a NewPrompt playbook you can run on its own; together they turn scattered notes into docs a developer can navigate. You know the product; the blueprint makes sure the docs are organized and complete instead of a pile of pages.
The journey
Each stage runs a NewPrompt playbook, with a supporting resource and tool. Work them in order — the output of each stage feeds the next.
-
Plan the documentation set
Decide what the docs must cover and for whom — the getting-started path, the how-to guides, the reference, the FAQs — driven by the tasks readers actually need to complete, not by what's easy to write.
Outcome A planned doc set tied to what readers need to do.
-
Structure the docs site
Organize the doc set into an information architecture — sections, hierarchy, and navigation — so a reader always knows where they are and what comes next, instead of getting lost three clicks in.
Outcome An information architecture with a clear reading path.
-
Write the guides and concepts
Write the conceptual and how-to documentation — the layer that explains how the product works and walks a reader through real tasks — in clear, consistent prose generated from the actual behavior.
Outcome Guides and conceptual docs that explain and walk through tasks.
-
Write the API reference
Document the API surface as a distinct reference layer — endpoints, parameters, responses, examples — complete and consistent, because reference docs are where a developer ends up when the guides run out.
Outcome A complete, consistent API reference.
-
Ship the docs site
Cross from built to live — check readiness, plan the deploy and a rollback, and decide what to watch — so the docs ship deliberately and the publishing pipeline is something you can rerun for every update.
Outcome The documentation site shipped with a repeatable publish path.
Expected outcome
A documentation website a reader can navigate — a planned doc set, an information architecture with an obvious path from getting-started to reference, conceptual guides and an API reference written as distinct layers, and the whole thing shipped — instead of a maze of pages that are each fine and collectively unusable.