How neobrutalism-templates/blog works
Main System Components
a) Static Site Generator (Astro)
• This is the foundation of the system
• Handles both build-time and client-side operations
b) Content Layer
• Located in /src/content
• Manages blog posts in MD/MDX format
• Content configuration system
c) Component Layer
• Located in /src/components
• Contains reusable UI components
• Mix of Astro (.astro) and React (.tsx) components
d) Routing Layer
• Located in /src/pages
• Handles dynamic and static routes
• Includes tag-based navigation
[Build Time] [Runtime]
• Content Layer |
• (MD/MDX Files) |
• ↓
• Astro Builder | → → | Static Assets | → → | Browser/Client |
• (HTML/CSS/JS) | | - Theme Switching|
• ↓ +-----------------+ | - Navigation |
• Components |
• Astro |
• React |
Key Relationships to Highlight
a) Build-time Flow:
• Content processing (MD/MDX → HTML)
• Component compilation
• Static route generation
• Style processing (Tailwind CSS)
b) Runtime Flow:
• Client-side navigation
• Theme switching functionality
• Tag-based filtering
Configuration Flow
Configuration dependencies:
• astro.config.mjs
• tailwind.config.mjs
• src/config.ts
• Content configuration
• Build-time vs. Runtime processes
• Static vs. Dynamic components
• Content management vs. UI components
Remember to:
• Static site generation aspect
This structure accurately represents the project's architecture while maintaining clarity about its static-first, content-focused nature.