tegwick
de49c76ff9
This commit preserves work from a refactoring session that attempted to: ACHIEVEMENTS: - Implemented Robustness Principle with dual-mode error handling - Created sophisticated error detection for edit mode failures - Added comprehensive safety utilities in control-base.js - Successfully recovered JavaScript components from git history - Fixed template variable substitution and initialization flow - Added detailed documentation (REFACTORING_SESSION_REPORT.md) PROBLEMS: - Violated GUARDRAILS.md by embedding JavaScript in Python strings - Mixed old and new component systems without proper migration - Content rendering issues - no visible content despite initialization - Became overly complex trying to solve multiple problems simultaneously LESSONS LEARNED: - Focus is critical - solve one problem at a time - Respect architectural constraints (keep JS separate from Python) - Component migration requires explicit planning - Incremental testing prevents complexity accumulation RECOMMENDATION: Reset to working commit and take focused, incremental approach that respects GUARDRAILS.md while achieving core edit mode functionality. See REFACTORING_SESSION_REPORT.md for detailed analysis. 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
MarkiTect Documentation
Welcome to the MarkiTect documentation. This directory contains comprehensive documentation for developers, users, and contributors.
Documentation Structure
📐 Architecture Documentation (architecture/)
Deep technical documentation about system design, performance, and implementation details.
- Caching System - Why and how MarkiTect's AST caching delivers 60-85% performance improvements
- Coming soon: Database Schema, CLI Architecture, Plugin System
👥 User Guides (user-guides/)
End-user documentation for working with MarkiTect CLI and features.
- Coming soon: Getting Started, Command Reference, Best Practices
🔧 Development Documentation (development/)
Documentation for contributors and developers extending MarkiTect.
- Coming soon: Contributing Guide, Testing Strategy, Release Process
Quick Links
For Users
- Installation & Setup
- Command Reference (coming soon)
- Performance Guide (coming soon)
For Developers
- Architecture Overview - System design and component relationships
- Development Setup - Local development environment
- API Documentation (coming soon)
Project Management
- Project Status - Current development status
- Roadmap - Strategic development plan
- Current Tasks - Task management using Keep a Todofile format
Key Concepts
Core Architecture Principles
- Parse Once, Use Many Times - AST caching for 60-85% performance improvement
- Convention Over Configuration - Sensible defaults with minimal setup
- Schema-Driven Processing - Structured markdown with validation
- Relational Metadata - Database-powered document relationships
Performance Philosophy
MarkiTect treats markdown documents as structured, queryable data rather than plain text. This approach enables:
- Lightning-fast document processing through intelligent caching
- Complex querying and relationship management
- Schema validation and consistency enforcement
- Scalable performance that grows with your content
Contributing to Documentation
Documentation follows the same quality standards as code:
- Clear Structure - Logical organization and navigation
- Practical Examples - Real-world usage patterns
- Performance Context - Why architectural decisions matter
- User-Focused - Written for the intended audience
Documentation Standards
- Use clear, concise language
- Include practical examples
- Explain the "why" behind design decisions
- Keep technical accuracy as the highest priority
- Update docs when changing functionality
This documentation is maintained alongside the codebase. For the most current information, always refer to the latest version in the repository.