tegwick
5264a6083c
Integrates SemanticValidator into CLI validate command: New Options: - --semantic/--no-semantic (default: True) - Enable/disable semantic validation - --check-links - Enable link validation (requires semantic validation) - --strict - Treat warnings as errors (fail on WARNING-level issues) Features: - Automatically detects x-markitect extensions in schema - Runs semantic validation alongside structural validation - Combines results with clear separation in output - Maintains full backward compatibility (--no-semantic for classic mode) - Supports .md schema files with embedded JSON - Graceful degradation: semantic validation errors don't crash command Example Usage: # Full validation (structural + semantic) markitect validate doc.md --schema manpage-schema-v1.0.md # Strict mode (warnings = errors) markitect validate doc.md --schema schema.md --strict # Classic mode (structural only) markitect validate doc.md --schema schema.json --no-semantic Output Format: - Shows structural validation results first - Then semantic validation results (sections, content) - Clear summary with error/warning counts - Exit codes: 0=pass, 1=fail (respects --strict flag) Integration: cli.py:1493-1668 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <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.
- Capabilities Architecture - Critical: How capabilities work as independent git submodules and separation of concerns
- Caching System - Why and how MarkiTect's AST caching delivers 60-85% performance improvements
- Coming soon: Database Schema, CLI Architecture
👥 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.