Skip to main content

Roadmap

Missing pieces​

  • A formal deployment record (what changed, build command/result, where deployed, verification)
  • Environment-labeled deployment records (local/preview/production/archived)
  • An accessibility checklist or recorded accessibility review for public deployment
  • A centralized SEO and structured-metadata record
  • Static asset organization notes (explicit guidance mapping assets to site identity)
  • Monitoring and uptime notes (expectations/cadence)
  • A rollback or restore note (expected rollback behavior and steps)
  • A key-route inventory and post-deploy route checks for production
  • Production deployment verification evidence (route checks, accessibility, metadata checks)

Next steps​

  1. Create a WDS-compliant deployment record template and record the next deployment (environment, build command/output, commit or snapshot, deploy time)
  2. Document production readiness: enumerate key routes and add a post-deploy route-check checklist
  3. Add an accessibility checklist and record results before any production publication
  4. Author a concise SEO/structured-metadata register (titles, descriptions, JSON-LD locations) per page/route
  5. Add monitoring/uptime expectations and a review cadence (even manual), recording where alerts go
  6. Write rollback/restore notes covering manual rollback for the Caddy/Docker deployment and DB snapshot/restore guidance
  7. Consolidate static asset organization notes (where generated assets live, generation commands, provenance for exported NDJSON/JSON)
  8. If production is planned, create a minimal production deployment runbook using the port constraints in CLAUDE.md (Caddy :8787, API :8788, Mongo :27015)

Potential improvements​

  • An explicit sitemap.xml linked from robots.txt (robots already references one, but the file wasn't present in the analyzer's evidence)
  • Automated accessibility and SEO checks in a local preflight script, outputting WDS deployment evidence
  • A post-deploy smoke-test script checking key routes and recording HTTP status/basic content
  • A concise site manifest of WDS-required artifacts, derived from CLAUDE.md and humans.txt
  • Lightweight uptime monitoring (ping or synthetic checks), documented in monitoring notes

Creative enhancements (ideas on file, not committed)​

  • A machine-readable WDS deployment endpoint (e.g. /._wds/deploy.json) returning the latest deployment record and verified routes for archival consumers and agents
  • An "AI provenance" JSON-LD envelope for generated exports, recording model version, generation time, and source documents
  • A lightweight "archive snapshot" generator exporting a static archived environment with an attached deployment record and embedded accessibility/SEO checks
  • An optional local "preview" mode spinning up a temporary Caddy container, running automated route/accessibility checks, and emitting a signed deployment artifact
  • A "site health" dashboard page aggregating export counts, last-import timestamps, last-deploy snapshot, accessibility score, and monitoring status