Platform Roadmap
Product-layer capabilities that turn the docs shell into the DevDocs.dev hosted platform.
The docs reader experience is the foundation. The DevDocs.dev product value comes from the hosted platform wrapped around that foundation: provisioning, previews, release proof, domain orchestration, API references, SDK generation, and safe interactive workflows.
Highest-priority roadmap
| Priority | Capability |
|---|---|
| P0 | Tenant provisioning and site records |
| P0 | PR preview deployments with review feedback |
| P0 | Promotion, rollback, and release-state visibility |
| P0 | Domain lifecycle orchestration |
| P0 | OpenAPI reference generation and safe playground execution |
| P0 | SDK-ready snippets and generated client examples |
| P1 | CLI-in-the-web and sandbox-in-the-web walkthroughs |
| P1 | AI assistant and query analytics |
| P1 | Protected docs and signed interactive surfaces |
| P1 | Version and locale management as a hosted feature |
Why the docs polish still matters
The better the DevDocs.dev shell looks and behaves, the easier it is to separate reader experience quality from hosted platform work:
- the docs UI should feel trustworthy on its own
- previews should be reviewable without extra explanation
- generated API references should feel native to the site
- CLI, sandbox, and side-by-side walkthroughs should feel like part of the same product
- platform work should focus on the operational layer around the reader experience
Useful follow-up paths
- Delivery for the workflow layer
- Platform Architecture for the system split
- API References for the OpenAPI playground path