Meister Bill Documentation¶
Welcome to the Meister Bill documentation. This directory contains comprehensive guides for developers, contributors, and users.
📚 Table of Contents¶
Getting Started¶
- Development Setup - Installing dependencies, environment setup, and running the application
- Project Structure - Understanding the monorepo layout and workspace organization
- Tech Stack - Overview of technologies and frameworks used
Development Guides¶
- Testing & Debugging - Running tests, pre-commit hooks, and debugging techniques
- Schema Validation - Working with Zod V4 schemas and validation
Architecture¶
- Event Bus Architecture - Type-safe event bus pattern implementation
- Event Bus Implementation Summary - Complete implementation details
- Brand Projection - Multi-brand system architecture
- Stripe Workflow - Stripe integration and payment workflows
- Audit Logging Setup - Audit logging configuration
Features & Planning¶
- Features Catalogue - Complete feature list and capabilities
- Launch Strategy - Product launch planning and strategy
Components¶
- Custom Components - Form components and patterns
Infrastructure¶
- Fly.io Deployment - Production deployment guide
- Price Ladder - Pricing structure and tiers
Ideas & Future Development¶
- Desktop App - Desktop application concept
- Escrow Service - Escrow integration ideas
- MCP Server - Natural language invoicing with MCP
Issue Documentation¶
Detailed implementation documentation for completed issues: - Issue #28 - Issue #82 - Issue #124 - Issue #126 - Issue #136 - Git Provider Integration - Issue #184 - PDF Generation - Issue #189 - Issue #198 - Issue #199 - Issue #200 - Issue #209 - Issue #215 - Issue #216 - Issue #217 - Issue #218 - Issue #219 - Issue #220 - Issue #221 - Issue #222 - Issue #223 - Issue #224 - Issue #225 - Issue #236 - Founder Deal Feature
📖 Documentation Conventions¶
- All file paths are relative to the docs directory
- Code examples use TypeScript by default
- Command examples assume you're in the repository root directory
- Environment-specific notes are clearly marked (Development / Production)
📝 Contributing to Docs¶
When updating documentation: - Keep docs up to date with code changes - Use clear, concise language - Include code examples where helpful - Cross-link related documentation - Update this index when adding new docs
Built with MkDocs