Skip to content

ROADMAP.md

Latest commit

 

History

History
64 lines (44 loc) · 2.64 KB

ROADMAP.md

File metadata and controls

64 lines (44 loc) · 2.64 KB

MOAT Homepage Roadmap

Date: 2026-04-11 Status: Active

Current State

The first-pass homepage narrative is now in place across the main landing page files:

  • index.md
  • _sections/01-introduction.md
  • _sections/02-participants.md
  • _sections/03-get-involved.md
  • _sections/04-ai-enabled-ecosystem.md

This pass replaced the original placeholder copy with public-facing language grounded in Vision/Starting_point/The MOAT Collaboration.md.

Completed In Phase 1

  • Replaced scaffolded hero text with MOAT-specific mission language
  • Rewrote the introduction to describe MOAT origin, purpose, and vision
  • Added the seven founding laboratories in the participants section
  • Replaced placeholder participation text with a restrained public invitation
  • Reframed the ecosystem section around emerging shared tools and infrastructure
  • Added section imagery metadata and summaries to improve homepage coherence

Next Priorities

Phase 2: Editorial Review

  • Confirm naming, acronyms, and institutional references against MOAT source materials
  • Review the homepage for repeated phrases and shorten any paragraph that feels too dense
  • Decide whether "AI work" or "AI-assisted tools" should be the primary recurring phrasing
  • Align capitalization and usage for Genesis Mission, ModCon, and laboratory names

Phase 3: Public Readiness

  • Add a verified contact path or external link once one is approved for publication
  • Replace working image captions with publication-ready captions if needed
  • Confirm that each image asset is appropriate for public use and accurately described
  • Add any approved links to proposals, presentations, or collaboration materials

Phase 4: Information Architecture

  • Decide whether MOAT needs dedicated subpages for vision, roadmap, ecosystem, or resources
  • Add supporting pages only after the homepage language is approved
  • Keep future pages clearly separated between current facts, active collaboration, and planned work

Phase 5: Technical Polish

  • Run a local Jekyll build when requested
  • Review responsive behavior on narrow and wide layouts
  • Make style adjustments only if the new copy exposes readability or spacing issues

Open Questions

  • Should the site remain a concise landing page, or grow into a small documentation hub?
  • Which proposal-related details are public enough to mention directly on the site?
  • What participation pathway should be published first: contact email, form, or external page?
  • Are there approved visuals or diagrams that should replace the current working images?

Notes

ROADMAP.md was added because no roadmap file was present in the repository when this continuation pass began.
⚡