Product
Internal Docs Direction
Why the platform docs live inside Saas Dash and how they should evolve
Principle
Internal docs should live close to the code and the operating surface.
That gives:
- versioned decisions
- readable source files
- an internal UI for review and onboarding
- a path to interactive docs later
Preferred format
Use MDX for curated internal docs.
That allows:
- readable repository content
- structured navigation
- embedded platform-specific components later
Evolution path
Phase 1:
- curated docs shell
- architecture and operations pages
- product and contract guidance
Phase 2:
- custom MDX components
- status blocks
- endpoint cards
- embedded operational actions
Phase 3:
- migrate platform control workflows into the same shell