Portal Epics And Backlog in-progress
This page now tracks follow-on portal work, not first-time portal creation. The internal multi-audience portal, publication-track checker, static deployment path, source-doc inventory, and build metadata are already implemented.
The active implementation queue is the platform-foundation Fairway track. This page exists to keep future portal improvements visible without pretending the main portal foundation is still missing.
Epics
| Epic | Outcome |
|---|---|
| Content consolidation | Internal teams can learn GPUaaS from portal-native pages without opening raw GitHub docs for normal onboarding |
| Visual communication layer | Mixed audiences can understand product, architecture, operations, security, and developer workflows through diagrams and maintained images |
| Ownership and freshness governance | Portal pages carry ownership, review cadence, freshness risk, and sync trigger metadata |
| Publication tracks and filtering | Internal, customer, partner, and public tracks have explicit readiness and redaction rules |
| API reference and playground | Developers get rendered REST/event references and a controlled API playground path |
| Search and discovery | Readers can find portal pages, source docs, diagrams, and references quickly |
| Review packaging and export | Product, Architecture, Security, Ops, and app-developer review packs can be generated from the portal |
Priority Follow-On Tasks
| Task | Epic | Outcome |
|---|---|---|
| DOCS-PORTAL-DIAGRAMS-FLOWS-001 | Visual communication layer | deepen sequence/C4/runtime diagrams where current pages are still too text-heavy |
| DOCS-PORTAL-API-SDK-REFERENCE-001 | API reference and playground | improve generated renderer/playground only if it beats the current synced-contract path |
| DOCS-PORTAL-CLOUDFLARE-DEPLOYMENT-001 | Publication tracks and filtering | complete first protected publication and capture post-publish smoke evidence |
| DOCS-PORTAL-CONTINUOUS-GATES-001 | Ownership and freshness governance | add new portal gates only when a real stale-content or publication miss escapes current checks |
Deeper Expansion Tasks
| Task | Epic | Outcome |
|---|---|---|
| Search and discovery | Search and discovery | decide whether local search is enough once audience grows |
| Runtime depth visuals | Content consolidation | expand terminal, proxy, observability, and node/runtime deep dives with more diagrams |
| External publication filtering | Publication tracks and filtering | produce customer/partner/public-safe builds from the same source model |
| Review packaging and exports | Review packaging and export | package product, architecture, security, and ops review bundles directly from portal content |
Rule
Do not reopen “build the docs portal” as a generic epic. The portal foundation is already implemented. New work should be scoped as specific expansion or maintenance slices with a clear user or reviewer benefit.