Good documentation is a moat — it cuts support tickets, closes sales, and makes your product feel finished. Bad documentation is worse than none. The reason most products ship thin docs is simple: writing 50 articles, formatting each one, and keeping reference pages accurate is a slog. This guide shows the alternative. With a docs CPT, NIBWP’s content tools and the reusable doc patterns, an agent turns your product knowledge into a full, navigable documentation set — the way this very site’s docs were built.
Set up a docs CPT, connect NIBWP, and have the agent draft guides, references and FAQs from your material, formatted with reusable patterns — callouts, code blocks, tabbed snippets, tables. Reference pages generate straight from your data.
Who this is for
Product teams shipping software, plugin and theme authors, and SaaS founders who know docs sell. You bring the product knowledge; the agent turns it into structured, readable articles — fast enough to document a whole product, not just the happy path.
What you will build
- Categorized documentation articles in a workflow order
- Reusable patterns: callouts, code blocks, tabbed snippets, FAQs, tables
- Reference pages generated automatically from your data
- A consistent, on-brand reading experience with a collapsible sidebar
Before you start
You need a docs CPT (or a docs plugin) with categories, NIBWP with a write-scoped token, and a connected MCP client. The reusable doc patterns — the same ones this site uses — make the articles readable without manual formatting.
The stack
| Layer | What handles it |
|---|---|
| Docs type | A docs CPT with categories |
| Content | nibwp/wp-create-post and nibwp/wp-update-post |
| Reference data | your abilities, settings, integrations — read by the agent |
| Patterns | reusable callouts, code blocks, tables, FAQs |
Step 1 — Set up the docs type
A docs CPT with a category taxonomy and an order field. The categories become your workflow groups — getting started, how-to, reference — ordered basic to advanced.
Step 2 — Generate the articles
Hand the agent your source material — a feature list, a changelog, support transcripts — and it drafts guides, references and FAQs, each formatted with the reusable patterns so they are readable, not walls of text.
You: Draft a getting-started guide and 5 how-to articles from\n this feature list, using callouts and code blocks.\nnibwp/wp-create-post { type: doc, category: How-to } x6\n6 doc drafts created - formatted and categorized
Step 3 — Generate reference pages from data
This is the magic of docs-from-data. Point the agent at your structured information — your abilities, your settings, your integrations — and it generates accurate reference pages straight from the source. When the data changes, regenerate the page; it never drifts out of date.
Step 4 — Organize and publish
Categorize, order, and publish. A collapsible sidebar groups the articles into a workflow; a grid home page makes them browsable. Your product suddenly has docs that feel complete.