An advanced markdown engine
Find a file
tegwick 9f4e296dd3 chore: clean up TODO.md by removing completed theme system refactor tasks
Remove outdated theme system refactor content from TODO.md since the layered
theme architecture work was already completed and released in v0.6.0. The
todofile is now clean and ready for new active development tasks.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-29 22:25:58 +01:00
.claude feat: add Claude Code agent configuration and registration tools 2025-10-27 20:11:33 +01:00
.github/workflows feat: Implement comprehensive Testing Architecture Enhancement 2025-09-26 22:36:35 +02:00
.issues feat: Integrate Requirements Engineering Agent and fix Issue #59 test failures 2025-10-02 00:45:06 +02:00
.venv_old chore: Keep old venv from ubuntu 18.04 for now just in case. 2025-09-23 01:16:12 +02:00
agents feat: implement todofile system and retire NEXT.md 2025-10-25 02:48:45 +02:00
application feat: Implement domain logic separation with clean architecture 2025-09-26 22:15:45 +02:00
assets feat: complete Issue #146 final integration testing 2025-10-15 00:19:52 +02:00
capabilities feat: update kaizen-agentic submodule reference 2025-10-25 02:51:51 +02:00
cli refactor: remove obsolete issue management system in favor of issue-facade 2025-10-24 21:25:04 +02:00
config feat: Implement unified configuration management system 2025-09-26 17:45:56 +02:00
cost_notes feat: complete core asset management system with database integration 2025-10-14 23:42:42 +02:00
docs feat: implement todofile system and retire NEXT.md 2025-10-25 02:48:45 +02:00
domain fix: Eliminate all 111 test warnings by fixing root causes 2025-09-27 20:14:22 +02:00
examples feat: comprehensive asset management system and testing improvements 2025-10-12 19:57:31 +02:00
gitea feat: Consolidate Gitea API access through unified integration layer 2025-09-28 23:44:51 +02:00
guides chore: history cleanup 2025-10-03 03:39:43 +02:00
history feat: organize and archive legacy files to history directory 2025-10-25 02:55:23 +02:00
infrastructure refactor: remove obsolete issue management system in favor of issue-facade 2025-10-24 21:25:04 +02:00
markitect feat: implement insert mode with heading protection and fix content display bugs 2025-10-28 23:55:21 +01:00
node_modules chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
reports feat: complete Issue #146 - Asset Management Implementation Milestone 2025-10-14 18:29:37 +02:00
services refactor: remove obsolete issue management system in favor of issue-facade 2025-10-24 21:25:04 +02:00
src chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
test_document_extracted feat: complete Issue #151 - Phase 4: Integration and Documentation 2025-10-14 11:11:51 +02:00
testdata chore: history cleanup 2025-10-03 03:39:43 +02:00
tests feat: complete clean editor implementation with comprehensive UI framework 2025-10-28 03:50:21 +01:00
todo chore: some cleanup and houskeeping 2025-10-06 22:51:38 +02:00
tools feat: add Claude Code agent configuration and registration tools 2025-10-27 20:11:33 +01:00
wiki@8818df03d3 chore: commit examples and some cleanup 2025-10-08 10:14:51 +02:00
.clinerules feat: implement markitect installer with version/release commands (issue #80) 2025-10-03 05:47:02 +02:00
.gitignore fix: move test artifacts to tmp directory and update gitignore 2025-10-19 21:39:40 +02:00
.gitmodules feat: add kaizen-agentic as submodule capability 2025-10-25 02:26:16 +02:00
aliases.sh feat: implement plugin-based architecture with md- command prefixes - Issue #44 2025-10-06 16:46:26 +02:00
asset_registry.json chore: update asset registry from recent operations 2025-10-20 07:23:40 +02:00
CHANGELOG.md release: bump version to 0.6.0 with clean editor architecture 2025-10-28 03:51:41 +01:00
demo_clean_editor.html chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
install feat: comprehensive asset management system and testing improvements 2025-10-12 19:57:31 +02:00
install.py feat: implement markitect installer with version/release commands (issue #80) 2025-10-03 05:47:02 +02:00
install.sh feat: implement markitect installer with version/release commands (issue #80) 2025-10-03 05:47:02 +02:00
Makefile feat: reorganize Makefile installation targets for better UX 2025-10-25 20:28:29 +02:00
package-lock.json chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
package.json chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
pyproject.toml release: bump version to 0.6.0 with clean editor architecture 2025-10-28 03:51:41 +01:00
pytest-timeout.ini feat: Implement test timeout infrastructure and fix failing tests 2025-10-01 18:07:05 +02:00
pytest.ini fix: eliminate all test suite warnings - Issue #129 2025-10-06 02:11:28 +02:00
release.py feat: implement comprehensive release process and automation (issue #81) 2025-10-03 06:07:10 +02:00
test_dom_integration.html chore: update project state and prepare for image support development 2025-10-26 08:06:22 +01:00
TODO.md chore: clean up TODO.md by removing completed theme system refactor tasks 2025-10-29 22:25:58 +01:00
UserInterfaceFramework.md feat: implement insert mode with heading protection and fix content display bugs 2025-10-28 23:55:21 +01:00

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

For Users

For Developers

Project Management

Key Concepts

Core Architecture Principles

  1. Parse Once, Use Many Times - AST caching for 60-85% performance improvement
  2. Convention Over Configuration - Sensible defaults with minimal setup
  3. Schema-Driven Processing - Structured markdown with validation
  4. 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:

  1. Clear Structure - Logical organization and navigation
  2. Practical Examples - Real-world usage patterns
  3. Performance Context - Why architectural decisions matter
  4. 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.