An advanced markdown engine
tegwick
6e60e5f13d
Implemented sophisticated paragraph handling for the markdown editor: Enhanced HTML-to-Markdown Conversion: - Replaced simple tag stripping with proper structural parsing - Preserves formatting for headers, emphasis, code, blockquotes - Maintains paragraph separation with proper spacing - Handles nested elements and mixed content correctly Dynamic Section Splitting: - Detects paragraph breaks (double newlines) when editing - Automatically creates separate editable sections for each paragraph - Enables independent editing of logically separate content - Maintains proper section indexing with sub-identifiers Visual Enhancements: - Added green styling for edited sections to distinguish from originals - Subtle borders and backgrounds indicate modified content - Hover effects provide clear feedback on editable areas Technical Improvements: - Enhanced blur handler to detect multiple paragraphs - Smart wrapper creation for single vs. multi-paragraph content - Proper DOM manipulation for section insertion and replacement - Preserves editing state and section relationships Benefits: - Empty lines between paragraphs are preserved accurately - Text separated by empty lines becomes independently editable - Better content organization and editing granularity - Improved user experience with clear visual feedback This resolves the empty line swallowing issue and provides intuitive paragraph-level editing that matches user expectations. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude/agents.backup.20251020 | ||
| .github/workflows | ||
| .issues | ||
| .venv_old | ||
| agents | ||
| application | ||
| assets | ||
| capabilities | ||
| cli | ||
| config | ||
| cost_notes | ||
| docs | ||
| domain | ||
| examples | ||
| gitea | ||
| guides | ||
| history | ||
| infrastructure | ||
| markitect | ||
| reports | ||
| services | ||
| test_document_extracted | ||
| testdata | ||
| tests | ||
| todo | ||
| tools | ||
| wiki@8818df03d3 | ||
| .clinerules | ||
| .gitignore | ||
| .gitmodules | ||
| aliases.sh | ||
| asset_registry.json | ||
| CHANGELOG.md | ||
| install | ||
| install.py | ||
| install.sh | ||
| Makefile | ||
| pyproject.toml | ||
| pytest-timeout.ini | ||
| pytest.ini | ||
| release.py | ||
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.