Skip to main content

Roadmap

Missing pieces​

  • A site manifest (.manifest.toml or equivalent canonical project manifest)
  • Deployment record(s) answering: what changed, what was built, where deployed, how verified
  • An accessibility checklist and recorded accessibility verification for public deployment
  • Release/publication notes or a changelog tied to deployments
  • Monitoring and uptime notes (expectations, alerting, review cadence)
  • A rollback/restore note describing rollback expectations and procedures

Next steps​

  1. Add a canonical site manifest at the repository root to satisfy the WDS manifest requirement
  2. Create and store a deployment record template, populated for the next publish (build command, commit, environment, deploy time)
  3. Run and record an accessibility review (WCAG checklist or audit), committing the results
  4. Add a release notes file or CHANGELOG documenting recent public deployments
  5. Document monitoring and uptime expectations, adding at least a manual review cadence
  6. Document rollback/restore steps for production and archived environments

Potential improvements​

  • Automated generation of WDS-compliant deployment records as part of the build pipeline
  • Lightweight uptime monitoring (synthetic checks), surfaced in the dashboard
  • Per-page structured metadata (JSON-LD), with verified titles/descriptions for all public pages
  • An accessibility regression test as part of local preview, with recorded results
  • Automated post-deploy key-route checks, recorded alongside deployments

Creative enhancements (ideas on file, not committed)​

  • An automatic WDS deployment recorder — on each build, produce a signed JSON deployment record with commit, build output hash, environment, and automated route checks
  • Signed archival publish: integrate ArchiveHasher to produce multi-hash manifests for site release snapshots, stored alongside the sitemap for provenance
  • An interactive route-verification dashboard running periodic checks against key routes, visualizing last-checked times and accessibility/SEO results
  • Embedding SESM metadata into SVG UI assets to make visual components self-describing across the studio — a natural extension of the SVG Lab feature
  • A preview/archive mode: build and store an "archived" static snapshot environment with immutable URLs and baked-in metadata for long-term preservation
  • A deployable "operator checklist" UI walking the operator through WDS publication blockers, recording confirmations