Focus: Comprehensive website builder with visual editor, CMS, multi-language support, and SEO optimization
Type: Complete platform implementation (Astro + React 19 + Tailwind v4 + Convex)
Integration: Content management, localization, version control, performance monitoring
Process: Cycle 1-55 optimized sequence
Timeline: 16-20 cycles per specialist per day (3-4 days to MVP, 5-7 days complete)
Target: Fully functional website builder with enterprise features
CYCLE BUDGET (55 Total)
Quick Wins (Cycles 1-10): Foundation + Backend + MVP Editor (45% effort → 80% value)
Cycles 1-2: Requirements & ontology mapping
Cycle 3: Backend schema implementation
Cycles 4-8: Core editor components
Cycles 9-10: MVP deployed and working
Core Features (Cycles 11-30): Components + CMS + Theme System (35% effort → 15% value)
Cycles 11-20: Complete component library + media
Cycles 21-25: Theme customization + responsive
Cycles 26-30: Version control + publishing workflow
Advanced Features (Cycles 31-45): Multi-language + SEO + Analytics (15% effort → 4% value)
Cycles 31-35: Multi-language support
Cycles 36-40: SEO tools and optimization
Cycles 41-45: Analytics and performance monitoring
Polish + Deploy (Cycles 46-55): Testing + Optimization + Documentation (5% effort → 1% value)
Cycles 46-50: Cross-browser testing + accessibility
Cycles 51-53: Performance optimization + Lighthouse
Cycles 54-55: Documentation + final deployment
QUICK WINS (Cycles 1-10) - MVP IN 10 CYCLES
Goal: Working website builder where you can create and edit a simple page, then deploy it.
Tangible Progress Milestones:
✅ Cycle 3: Backend schema live, can store pages in Convex
✅ Cycle 5: Can drag a component onto canvas
✅ Cycle 8: Can edit text inline, see changes live
✅ Cycle 10: MVP deployed to Cloudflare - create/edit/publish one page end-to-end
Why this works: Backend + Frontend in parallel. Schema first, then build on it. Ship early.
PHASE 1: FOUNDATION + BACKEND + MVP EDITOR (Cycle 1-10)
Purpose: Define requirements, implement backend schema, build core editor with ONE working page
Cycle 1: Define Website Builder Structure
Cycle 2: Map Website Builder to 6-Dimension Ontology
Groups: Website (organization), site (project)
People: Owner (admin), editor, contributor, viewer
Things:
website (domain, settings, theme)
page (slug, content, layout, meta)
component (type, props, styles)
template (layout, preset components)
media (images, videos, files)
theme (colors, fonts, spacing)
version (snapshot, timestamp, author)
Connections:
Events:
Knowledge: SEO keywords, performance metrics, visitor analytics
Cycle 3: Implement Backend Schema (CRITICAL - BACKEND FIRST)
Cycle 4: Create Basic Editor Layout
Cycle 5: Implement Drag-and-Drop
Cycle 6: Render Components on Canvas
Cycle 7: Add Component Selection + Properties Panel
Cycle 8: Implement Inline Text Editing
Cycle 9: Create Page List + Publishing Workflow
Cycle 10: Deploy MVP + End-to-End Test
Purpose: Expand component library, add media upload, implement CMS features
Cycle 11-15: Add More Components
Cycle 19-22: Add Component Reordering + Deletion
Cycle 23-25: Add Responsive Design Controls
Cycle 26-30: Implement Version Control
PHASE 3: THEME SYSTEM + ADVANCED FEATURES (Cycle 31-45)
Purpose: Theme customization, multi-language, SEO, analytics
Cycle 31-35: Implement Multi-Language Support
PHASE 4: POLISH + TESTING + DEPLOYMENT (Cycle 46-55)
Purpose: Cross-browser testing, accessibility, performance, documentation
Cycle 46-48: Accessibility + Keyboard Navigation
Cycle 49-50: Cross-Browser Testing
Cycle 54-55: Documentation + Final Deployment
SUCCESS CRITERIA
MVP (Cycle 10) - Can ship a basic website:
✅ Backend schema stores pages in Convex
✅ Visual editor loads with three-panel layout
✅ Can drag 3 component types (Heading, Text, Button) from library to canvas
✅ Can edit text inline with double-click
✅ Can edit component props in properties panel
✅ Can publish page (status change to “published”)
✅ Published page renders at public URL with components
✅ MVP deployed to Cloudflare Pages
Complete (Cycle 55) - Production-ready website builder:
✅ 15+ component types (sections, layouts, content, navigation)
✅ Media library with upload + selection
✅ Component reordering via drag-and-drop
✅ Responsive design controls (mobile/tablet/desktop preview)
✅ Version control with auto-save + restore
✅ Multi-language support with translations
✅ SEO metadata (title, description, Open Graph, sitemap)
✅ Analytics integration (Plausible or Google Analytics)
✅ Keyboard shortcuts + accessibility (WCAG 2.1 AA)
✅ Cross-browser tested (Chrome, Firefox, Safari, Edge)
✅ Lighthouse score > 90 on all metrics
✅ Documentation (user + developer)
✅ Deployed to production with custom domain + SSL
OPTIMIZED TIMELINE
Total: 55 cycles (down from 100)
Savings: 45% reduction through aggressive prioritization
Why this is faster:
Backend first (Cycle 3): Build on solid foundation, not mocks
MVP in 10 cycles: Ship early, iterate based on real usage
Parallel work: Backend + Frontend can run simultaneously after Cycle 3
Cut ceremony: No separate “design” cycles, design while building
Quick wins first: 80% value in first 40% of cycles
Specialist assignment:
Backend (agent-backend): Cycles 3, 16-18 (schema, media storage)
Frontend (agent-frontend): Cycles 4-15, 19-55 (editor, components, UI)
Parallel execution: After Cycle 3, both can work simultaneously
Status: Ready to build
Next: Start Cycle 1 - Define website builder requirements