Sidebar + main + TOC layout
Three-column docs layout from the start — section nav on the left, content in the middle, table of contents on the right. The pattern every great docs site uses.
Code-block ready
Components for inline code, fenced blocks with syntax highlighting hooks, copy-to-clipboard buttons, and tabbed examples (React / Vue / curl).
Versioned URL pattern
Page slugs like /docs/v2/getting-started — easy to maintain multiple versions when your API changes without breaking old links.
Open Graph for every page
Every doc page emits its own OG image with the title — links shared in Slack and Twitter preview well, not as generic site cards.
Try this prompt
“Build a docs site for a payments API. Sidebar with three top-level sections (Getting started, Guides, API reference), a content area with breadcrumb + h1 + intro + code examples + parameter tables, and a right-side table-of-contents. Include a search bar in the top nav (UI only — wire to Algolia or Pagefind in the export).”
Paste this into InBuild to see the result. Try it free →
Frequently asked questions
Should I use Docusaurus or Mintlify instead?
Docusaurus and Mintlify are docs-specific. They're better if your team is committed to docs-as-code with markdown files. InBuild is better if you want a docs site that visually matches the rest of your product and you'll keep the codebase you export.
How do I add search?
The exported code has the UI scaffolding. For real search, Algolia DocSearch is the standard for docs sites (free for open-source). Pagefind is a great self-hosted alternative. Wire either in the exported Next.js project.
Can I write docs in MDX?
Yes — after export. The InBuild editor uses a component tree; once you export, swap to MDX for long-form pages and keep using the InBuild-generated layout components.