Developer Documentation Overview

This area is for practical product and engineering documentation that belongs in the public rendering layer: setup guides, support notes, API references, implementation walkthroughs, and code-adjacent explanations.

What belongs here

• product support docs for software and apps
• setup guides for public tools and client-facing workflows
• developer notes for APIs, integrations, and implementation decisions
• technical references that benefit from MDX examples or interactive components

What does not belong here

• local editorial stories and SEO articles
• business-owner interviews
• publishing workflow documentation from Studio Vanilla
• private internal operating notes

Those editorial publishing concerns belong to the future Studio/Payload workflow and will surface publicly through /blog when that integration is ready.

Current implementation

Documentation is local MDX for now. It uses the existing MDX renderer and component map instead of a new framework, which keeps the first implementation small and reversible.

Fumadocs is a good future option if this grows into a larger documentation system with nested navigation, generated sidebars, search, versioning, or deeper API reference needs.