An advanced markdown engine
tegwick
3e16793615
Naming Convention: SCOPE-COMPONENT-ELEMENT-SUBELEMENT - ui = User Interface (editor controls, panels, buttons) - dc = Document Content (typography, layout) - md = Mode (light/dark color schemes) - br = Branding (accent colors, corporate styling) New CSS Classes: - ui-edit-floater-panel (main floating control panel) - ui-edit-floater-header (panel header area) - ui-edit-floater-actions (button container) - ui-edit-floater-status (status display) - ui-edit-button (all action buttons) - ui-edit-button-accept (save/accept buttons) - ui-edit-button-cancel (cancel buttons) - ui-edit-button-reset (reset buttons) - ui-edit-section-frame (editable section borders) - ui-edit-textarea-main (text editing areas) Updated Theme CSS: - All UI themes now target systematic class names - Granular control over specific button types - Consistent theming across all editor components - Better separation of concerns (panel vs buttons vs textareas) Benefits: - Easy theme targeting with predictable class names - Scalable for future UI components - Clear hierarchy and naming consistency - Maintainable and extensible architecture 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github/workflows | ||
| .issues | ||
| .venv_old | ||
| agents | ||
| application | ||
| assets | ||
| capabilities | ||
| cli | ||
| config | ||
| cost_notes | ||
| docs | ||
| domain | ||
| examples | ||
| gitea | ||
| guides | ||
| history | ||
| infrastructure | ||
| markitect | ||
| node_modules | ||
| reports | ||
| services | ||
| src | ||
| test_document_extracted | ||
| testdata | ||
| tests | ||
| todo | ||
| tools | ||
| wiki@8818df03d3 | ||
| .clinerules | ||
| .gitignore | ||
| .gitmodules | ||
| aliases.sh | ||
| asset_registry.json | ||
| CHANGELOG.md | ||
| demo_clean_editor.html | ||
| install | ||
| install.py | ||
| install.sh | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| pytest-timeout.ini | ||
| pytest.ini | ||
| release.py | ||
| test_dom_integration.html | ||
| TODO.md | ||
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.