tegwick
5337b26d5e
Addressed multiple critical editing experience issues: Enhanced Markdown Preservation: - Fixed htmlToMarkdown() to properly preserve heading hash signs (# ## ###) - Maintained markdown structure for lists, code blocks, and blockquotes - Preserved inline formatting (bold, italic, code) within paragraphs - Improved spacing and indentation handling for complex structures Font Size & Style Preservation: - Extract and apply original element's font-size to textarea - Preserve line-height from source content for consistent appearance - Use inherit values in CSS, overridden by JavaScript for accuracy - Ensures editing experience matches visual appearance of content Improved Textarea Sizing: - More reasonable height constraints (max 360px vs 400px) - Line-count based minimum height calculation (~24px per line) - Reduced excessive height for short content - Added both horizontal and vertical resize capability - Set minimum width constraint (200px) for better usability CSS Enhancements: - Changed resize from vertical-only to both directions - Added min-width constraint for better proportions - Improved overflow handling (auto vs overflow-y only) - Font properties use inherit with JavaScript override Technical Improvements: - Better content height calculation using actual line count - Proper handling of edge cases in markdown conversion - Maintained smooth transitions while fixing sizing logic - Preserved all existing functionality while fixing issues These fixes ensure that: - Headings preserve their # markers when edited - Font sizes match the original content being edited - Textarea dimensions are proportional and user-controllable - Markdown structure roundtrips accurately 🤖 Generated with [Claude Code](https://claude.ai/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.