Documentation architecture
The documentation system is built as a dedicated @nextsaasai/docs package using Markdoc for content authoring. Markdoc was chosen over MDX for documentation because it provides strict schema validation for custom components and keeps content files free of executable code. Documentation pages are hosted on the marketing site but document the boilerplate product — users access them at /docs alongside the marketing pages.
Content coverage
Every major feature of the boilerplate has a corresponding documentation section: authentication setup and configuration, payment integration with Lemon Squeezy, AI provider configuration, security hardening, database schema management, and deployment workflows. API references are auto-generated from the codebase to stay in sync with the implementation.
Custom Markdoc components handle recurring documentation patterns — callouts for warnings and tips, tabbed sections for multi-environment instructions, and code groups for showing related files side by side. These components render as React elements but are authored in plain Markdoc syntax, keeping the content accessible to non-developers.
Contributors
Sascha Rahn