How e74000/shizuka works
Main Components
A. CLI Layer
• Entry point through main.go
• Command handlers in cmd/ directory
• Core commands: init, build, dev, serve
B. Core Engine (shizuka/ directory)
• Content processing
• Frontmatter parsing
• Indexing system
• Location management
C. File System Interaction
• Input: content/, templates/, static/ directories
• Output: dist/ directory
• Configuration: shizuka_conf.json
Level 1 (User Interface):
• CLI Commands (init, build, dev, serve)
Level 2 (Core Processing):
• Content Processing → Template Engine → Static Assets
Level 3 (File System):
• Input Directories ↔ Output Directory
Component Relationships
• CLI commands → Core Engine (direct dependency)
• Core Engine → File System (bidirectional for read/write)
• Template Engine ← Content Processing (content injection)
• Static Assets → Output Directory (direct copy)
Specific Implementation Details
Key architectural elements:
• Markdown processing pipeline
• Template rendering system
• Live reload mechanism (dev server)
• File watching system
• Build process flow
Important Notes
a. Modular design:
• Separate cmd package for CLI
• Core shizuka package for processing
• Clear separation of concerns
b. Development workflow:
• Init → Content Creation → Development → Build → Serve
c. File structure:
• Content organization
• Template system
• Static asset management