How rochacbruno/marmite works
Main Components Identification
The system should be represented with these primary components:
a) Input Processing Layer
• Content Reader (markdown files)
• Configuration Parser (marmite.yaml)
• Static Assets Handler (static/, media/)
b) Core Processing Layer
• Markdown Parser (CommonMark + GFM)
• Metadata Extractor (frontmatter)
• Template Engine (Tera templates)
c) Output Generation Layer
• HTML Generator
• Feed Generator (RSS)
• Search Index Builder
• Static File Copier
d) Development Tools
• HTTP Server
• File Watcher
• CLI Interface
Component Relationships
Input → Processing → Output
• Watch Service (optional)
Specific Implementation Details
a) Input Sources:
• content/*.md files
• templates/*.html
• static/* assets
• marmite.yaml config
b) Processing Pipeline:
• Parallel processing of:
• Content (markdown → HTML)
• Templates (template compilation)
• Static assets (direct copying)
c) Output Targets:
• HTML files
• RSS feeds
• Search index
• Copied static assets
Special Features
• Taxonomy System (tags, streams)
• Author Management
• Template Customization
• Search Functionality
• Development Server
Technical Details
• Integration with:
• CommonMark parser
• Tera templating engine
• Built-in HTTP server
• File system watchers
Development tools as optional components
This system design should help developers understand both the simplicity and capability of Marmite as a static site generator.