How pepodev/digital-garden works
Main Components
a. Client-Side Components:
• Static Site Generator (11ty/Eleventy)
• Frontend UI Components (located in src/site/_includes/components)
• Search Functionality
• Graph Visualization
• Theme System
b. Content Management:
• Obsidian Notes Repository (src/site/notes)
• File Tree System
• Asset Management (images, attachments)
c. Build & Deployment:
• Vercel/Netlify Integration
• Build Pipeline
┌─────────────────────────────────────────────┐
• Presentation │
• (Components, Layouts, Styles, User Interface)│
• ┤
• Content Processing │
• (11ty, Templates, Markdown Rendering) │
• ┤
• Data Management │
• (Notes, Files, Assets, Search Index) │
• ┘
Key Relationships to Highlight
a. Static Site Generation Flow:
• How Eleventy processes Markdown files
• Demonstrate template rendering pipeline
• How components are assembled
b. Data Flow:
• Content → Template processing → HTML output
• Search indexing process
• Graph visualization data generation
Detailed Component Breakdown
┌─ Frontend Components ─────┐
• Navigation │
• Search │
• Graph Visualization │
• File Tree │
• Note Display │
• ┘
┌─ Templates & Layouts ────┐
• Base Layout │
• Note Layout │
• Component Templates │
• ┘
┌─ Data & Content ─────────┐
• Markdown Files │
• Media Assets │
• Search Index │
• Metadata │
• ┘
Additional Elements
• User interaction flows
• Content update mechanisms
• Cache and performance optimizations
• Security considerations
• Integration points with Obsidian
Remember to emphasize the static nature of the final output while showing how dynamic features (search, graph) are implemented client-side. This is crucial for understanding the architecture's constraints and benefits.