Last Updated: November 28, 2025
Project Status: Phase 3 In Progress
Welcome to the Rise Visual Low-Code Builder documentation! This guide will help you navigate the comprehensive documentation suite.
| Phase | Status | Key Deliverables |
|---|---|---|
| Phase 0 | ✅ Complete | FileChangeTracker, SchemaValidator, APIKeyManager, Testing infra |
| Phase 1 | ✅ Complete | Electron shell, UI layout, Project management, Preview foundation |
| Phase 2 | ✅ Complete | Component tree, Properties panel, Manifest persistence, AI generation |
| Phase 3 | 🔄 In Progress | ReactCodeGenerator ✅, FileManager ✅, Live preview 🔄 |
| Phase 4 | 🔵 Not Started | Testing, error handling, performance, UX polish |
| Phase 5 | 🔵 Not Started | Documentation, packaging, beta release |
- README.md - Project overview, progress, and introduction
- GETTING_STARTED.md - Setup instructions and first steps
- ARCHITECTURE.md - Complete system design and technology stack
- FILE_STRUCTURE_SPEC.md - Project file organization
- COMPONENT_SCHEMA.md - JSON manifest format (has pending updates)
- SCHEMA_LEVELS.md - Feature progression (Level 1→2→3)
- DATA_FLOW.md - Props, state, and reactive variables
- EXPRESSION_SYSTEM.md - Dynamic properties (Level 2 - Post-MVP)
- DEBUGGER_DESIGN.md - Step-through debugging (Level 3 - Future)
- PLUGIN_SYSTEM.md - Framework adapter interface (Post-MVP)
- BIDIRECTIONAL_SYNC.md - Code-to-manifest sync (Post-MVP)
- HOSTED_BACKEND.md - Parse Server backend (Future)
- PERFORMANCE.md - Performance optimization strategy
- SECURITY.md / SECURITY_SPEC.md - Security model
- TESTING_STRATEGY.md - Testing approach and quality assurance
- MVP_ROADMAP.md - Development phases and timeline (Updated Nov 28)
- CLINE_IMPLEMENTATION_PLAN.md - AI-assisted development guide
- EXAMPLES.md - Real-world component examples
- .implementation/ - Detailed task documentation
- Phase 0: Foundation tasks (0.1-0.4) ✅
- Phase 1: Application shell tasks (1.1-1.4) ✅
- Phase 2: Component management tasks (2.1-2.4) ✅
- Phase 3: Code generation tasks (3.1-3.3) 🔄
Recommended order:
- README.md (overview & progress)
- MVP_ROADMAP.md (timeline and status)
- ARCHITECTURE.md (technical approach)
- SCHEMA_LEVELS.md (feature progression)
Focus on: Phases, estimates, success criteria, current progress
Recommended order:
- GETTING_STARTED.md (setup)
- ARCHITECTURE.md (system design)
- COMPONENT_SCHEMA.md (JSON format)
- FILE_STRUCTURE_SPEC.md (project layout)
- CLINE_IMPLEMENTATION_PLAN.md (development approach)
.implementation/folder (task details)
Focus on: Technical implementation, code patterns, task documentation
Essential reading:
.clinerules/folder - Project rules and standards- SCHEMA_LEVELS.md - Level 1 boundaries (CRITICAL)
- SECURITY_SPEC.md - Security requirements
- Relevant
.implementation/task file
Key rule: Check SCHEMA_LEVELS.md before implementing ANY feature
Recommended order:
- README.md (product vision)
- GETTING_STARTED.md (user workflows)
- COMPONENT_SCHEMA.md (component structure)
- DEBUGGER_DESIGN.md (UI examples)
Focus on: User interfaces, workflows, visual examples
| Document | Status | Last Updated | Notes |
|---|---|---|---|
| README.md | ✅ Updated | Nov 28, 2025 | Progress tracking added |
| MVP_ROADMAP.md | ✅ Updated | Nov 28, 2025 | Phase statuses current |
| ARCHITECTURE.md | ✅ Complete | Oct 25, 2025 | No changes needed |
| SCHEMA_LEVELS.md | ✅ Complete | Oct 25, 2025 | Defines L1/L2/L3 boundaries |
| COMPONENT_SCHEMA.md | Oct 25, 2025 | Level indicators proposed | |
| FILE_STRUCTURE_SPEC.md | ✅ Complete | Oct 25, 2025 | No changes needed |
| SECURITY_SPEC.md | ✅ Complete | Oct 25, 2025 | Implemented in Phase 0 |
| TESTING_STRATEGY.md | ✅ Complete | Oct 25, 2025 | No changes needed |
| Document | Status | Relevance |
|---|---|---|
| DATA_FLOW.md | ✅ Complete | Level 2+ reference |
| EXPRESSION_SYSTEM.md | ✅ Complete | Level 2 - Post-MVP |
| DEBUGGER_DESIGN.md | ✅ Complete | Level 3 - Future |
| PLUGIN_SYSTEM.md | ✅ Complete | Post-MVP reference |
| BIDIRECTIONAL_SYNC.md | ✅ Complete | Post-MVP reference |
| HOSTED_BACKEND.md | ✅ Complete | Future - properly marked |
| PERFORMANCE.md | ✅ Complete | Reference as needed |
| EXAMPLES.md | ✅ Complete | Reference for patterns |
| Document | Status | Notes |
|---|---|---|
| CLINE_IMPLEMENTATION_PLAN.md | Phase statuses not marked | |
| DOCUMENTATION_INDEX.md | ✅ Updated | Nov 28, 2025 - this document |
| GLOSSARY.md | ✅ Complete | Terminology reference |
...understand the JSON structure? → COMPONENT_SCHEMA.md - Complete specification
...set up the development environment? → GETTING_STARTED.md - Installation section
...understand what's in MVP vs post-MVP? → SCHEMA_LEVELS.md - Level 1/2/3 boundaries
...see what's been implemented? → MVP_ROADMAP.md - Current progress section → .implementation/ - Detailed task logs
...understand the code generation system? → .implementation/phase-3-code-generation-and-preview/task-3.1-react-code-generator.md
...understand how AI generation works? → .implementation/phase-2-component-management/task-2.4-AI-component-generation.md
...understand the security model? → SECURITY_SPEC.md - Security architecture → .implementation/phase-0-foundation/task-0.2-security-foundation.md
...learn about the future hosted backend? → HOSTED_BACKEND.md - Parse Server plans
-
Apply COMPONENT_SCHEMA.md updates
- Add schema level indicators throughout
- Mark Level 2/3 examples clearly
- Add "MVP Limitations" section
- Estimated time: 2-3 hours
-
Add status markers to CLINE_IMPLEMENTATION_PLAN.md
- Mark Phase 0-2 as complete
- Mark Phase 3 as in progress
- Estimated time: 30 minutes
-
Create implementation summary
- What was built in each phase
- Key decisions and their rationale
- Patterns discovered
- Estimated time: 2 hours
-
Update code examples
- Add examples from actual implementation
- Show generated code output
- Estimated time: 1 hour
- Create user guide draft
- Add troubleshooting section
- Document keyboard shortcuts
- Total Documents: 18+ core docs
- Implementation Tasks Documented: 15+ task files
- Code Examples: 350+
- Diagrams: 40+
Update documentation when:
- ✅ Completing a phase (update MVP_ROADMAP.md, README.md)
- ✅ Making key decisions (document in task file + relevant doc)
- ✅ Changing architecture (update ARCHITECTURE.md)
- ✅ Adding features (update relevant feature doc)
- After each task: Update task file in
.implementation/ - After each phase: Update MVP_ROADMAP.md, README.md
- Weekly: Check accuracy against implementation
- Before release: Full documentation audit
Found an error? Have a suggestion?
- Small fixes: Note in task file or create issue
- Big changes: Discuss with project lead first
- New sections: Propose structure before writing
Style Guide:
- Clear, concise language
- Code examples for concepts
- Diagrams for complex flows
- Cross-reference related docs
- Include "Last Updated" dates
- README.md - What is Rise?
- SCHEMA_LEVELS.md - What can it do?
- GETTING_STARTED.md - How to set up
- ARCHITECTURE.md - How it works
- COMPONENT_SCHEMA.md - Data structures
- MVP_ROADMAP.md - Current status
.implementation/- How tasks are done
- All architecture docs
- CLINE_IMPLEMENTATION_PLAN.md - Development approach
.clinerules/- AI development rules- All
.implementation/task files
These documents will be created as features are implemented:
- USER_GUIDE.md - End-user documentation (Phase 5)
- API_REFERENCE.md - Generated code API (Phase 5)
- TROUBLESHOOTING.md - Common issues and solutions (Phase 4)
- CHANGELOG.md - Version history (Phase 5)
- LOGIC_SYSTEM.md - Node-based logic editor (Level 2)
Ready to build the future of low-code development! 🚀
Last Updated: November 28, 2025
Documentation Status: 🔄 Updated with current progress
Next Review: After Phase 3 completion