# Future Docusaurus portal work. # # This file is intentionally not the active Fairway queue source. The active # queue is .fairway/docusaurus-track.yaml. Move one task at a time from this # backlog into the active track when the team is ready to execute it; otherwise # readiness reports would include planned work as missing gates. epics: - id: DOCS-PORTAL-EPIC-CONTENT title: Content consolidation outcome: Internal teams can learn GPUaaS from portal-native pages without opening raw GitHub docs for normal onboarding. review_domains: - product - architecture - security - ops - content - id: DOCS-PORTAL-EPIC-VISUALS title: Visual communication layer outcome: Mixed audiences can understand product, architecture, operations, security, and developer workflows through diagrams and maintained images. review_domains: - product - architecture - security - frontend - content - id: DOCS-PORTAL-EPIC-METADATA title: Ownership and freshness governance outcome: Portal pages carry ownership, review cadence, freshness risk, and sync trigger metadata. review_domains: - content - governance - architecture - id: DOCS-PORTAL-EPIC-PUBLICATION title: Publication tracks and filtering outcome: Internal, customer, partner, and public tracks have explicit readiness and redaction rules. review_domains: - product - security - content - architecture - id: DOCS-PORTAL-EPIC-API title: API reference and playground outcome: Developers get rendered REST/event references and a controlled API playground path. review_domains: - architecture - security - frontend - app-developer - id: DOCS-PORTAL-EPIC-DISCOVERY title: Search and discovery outcome: Readers can find portal pages, source docs, diagrams, and references quickly. review_domains: - content - frontend - id: DOCS-PORTAL-EPIC-PACKAGING title: Review packaging and export outcome: Product, Architecture, Security, Ops, and app-developer review packs can be generated from the portal. review_domains: - product - security - ops - content tasks: - id: DOCS-PORTAL-034 epic: DOCS-PORTAL-EPIC-METADATA title: Add owner and freshness metadata model kind: publication-track priority: P0 outcome: Define required/optional frontmatter for owner, review_domain, last_reviewed, review_cadence, freshness_risk, and sync_trigger. - id: DOCS-PORTAL-035 epic: DOCS-PORTAL-EPIC-METADATA title: Enforce owner and freshness metadata kind: source-link-check priority: P0 outcome: Extend the portal checker to validate ownership/freshness metadata once the model is approved. - id: DOCS-PORTAL-036 epic: DOCS-PORTAL-EPIC-PUBLICATION title: Define publication-track filtering model kind: publication-track priority: P0 outcome: Define internal, customer, partner, and public tracks with redaction, diagram, and API/reference rules. - id: DOCS-PORTAL-037 epic: DOCS-PORTAL-EPIC-VISUALS title: Land P0 diagrams in reader pages kind: content-entry priority: P0 outcome: Add internal team map, security/readiness posture, release rings, App SDK path, shared services model, and governance flow to the relevant pages. - id: DOCS-PORTAL-038 epic: DOCS-PORTAL-EPIC-DISCOVERY title: Add portal search and discovery plan kind: docs-ia priority: P1 outcome: Decide local search vs Algolia/DocSearch and define source inventory/search index expectations. - id: DOCS-PORTAL-039 epic: DOCS-PORTAL-EPIC-CONTENT title: Promote API/domain/event deep dives kind: content-entry priority: P1 outcome: Add portal-native pages for API route modularization, API domain authoring, state machines, event taxonomy, and NATS streams. - id: DOCS-PORTAL-040 epic: DOCS-PORTAL-EPIC-CONTENT title: Promote observability and incident deep dives kind: content-entry priority: P1 outcome: Add portal-native pages for observability architecture, runbook mapping, correlation-first incident workflow, and SRE runbook index. - id: DOCS-PORTAL-041 epic: DOCS-PORTAL-EPIC-CONTENT title: Promote billing and ledger deep dives kind: content-entry priority: P1 outcome: Add portal-native pages for billing flow, immutable ledger, payments/webhooks, usage attribution, and operator billing diagnostics. - id: DOCS-PORTAL-042 epic: DOCS-PORTAL-EPIC-CONTENT title: Promote terminal and node lifecycle deep dives kind: content-entry priority: P1 outcome: Add portal-native pages for terminal/session security, node agent lifecycle, node isolation, and release/reimage posture. - id: DOCS-PORTAL-043 epic: DOCS-PORTAL-EPIC-CONTENT title: Promote storage and artifact lifecycle deep dives kind: content-entry priority: P1 outcome: Add portal-native pages for storage/data lifecycle, artifact trust, app artifacts, runtime bundles, and promotion. - id: DOCS-PORTAL-044 epic: DOCS-PORTAL-EPIC-API title: Research Stoplight Elements API playground viability kind: spike priority: P1 outcome: Determine whether Stoplight Elements can support the GPUaaS playground requirements inside Docusaurus. - id: DOCS-PORTAL-045 epic: DOCS-PORTAL-EPIC-API title: Research Scalar Docusaurus reference and playground viability kind: spike priority: P1 outcome: Determine whether Scalar can replace or complement Stoplight for embedded API reference and playground behavior. - id: DOCS-PORTAL-046 epic: DOCS-PORTAL-EPIC-API title: Add rendered OpenAPI pilot route kind: api-reference priority: P1 outcome: Add a non-production pilot route for rendered OpenAPI using the selected renderer and synced contract artifact. - id: DOCS-PORTAL-047 epic: DOCS-PORTAL-EPIC-API title: Define AsyncAPI/event rendering path kind: api-reference priority: P1 outcome: Decide how event contracts, NATS subjects, event taxonomy, and examples render in the portal. - id: DOCS-PORTAL-048 epic: DOCS-PORTAL-EPIC-PACKAGING title: Define review pack export model kind: publication-track priority: P2 outcome: Define how to package product, architecture, security, ops, and developer portal views for teams without repo access. - id: DOCS-PORTAL-049 epic: DOCS-PORTAL-EPIC-DISCOVERY title: Add source-doc and portal page discovery index kind: content-map priority: P2 outcome: Add a reader-facing index that maps portal pages, source docs, diagrams, audiences, and owners. - id: DOCS-PORTAL-050 epic: DOCS-PORTAL-EPIC-PUBLICATION title: Add publication readiness checker kind: source-link-check priority: P2 outcome: Validate publication-track metadata, public/customer/partner/internal rules, and diagram asset review status.