The roadmap should protect the magical core while layering platform capabilities over time.
| Phase | Focus | Core deliverables |
|---|---|---|
| V1 | Magical publishing | Universal input, page model, basic renderer, editor, hosted URLs, serialized free links, public pages, version history. |
| V2 | Identity & better pages | Named spaces, subdomains, custom domains, theme engine, premium templates, media embeds, analytics, SEO controls. |
| V3 | Teams | Workspaces, permissions, comments, approval workflows, shared assets, team publishing controls. |
| V4 | Intelligence | AI structuring, auto-beautification, semantic layout, content rewrite tools, brand-aware styling, multilingual pages. |
| V5 | Living systems | Forms, dynamic blocks, data embeds, actions, integrations, lightweight workflow logic. |
| V6 | Platform | APIs, SDKs, marketplace, private deployments, governance, audit history, enterprise integrations. |
Build the smallest complete system that proves transformation, publishing, and sharing before expanding the platform.
Paste content → generate structured page → render beautiful HTML preview.
Save page → create serialized link → serve public page reliably.
Register → dashboard → manage up to 5 pages → edit and republish.
Paid upgrade → named space → remove branding → custom domain path.
Landing page → waitlist → demo gallery → short-form transformation content.
Analytics, AI credits, templates, teams, marketplace, enterprise readiness.
The architecture centers on a structured page model. Raw content is normalized, transformed, rendered, published, identified, and eventually extended into collaboration and marketplace systems.
The platform should not treat HTML as the only source of truth. The durable object is the structured living page.
Execution should be staged by capability owner. The early team must protect the core transformation loop before expanding into marketplace or enterprise features.