How bcars/bcarsdotorg works
Main Components Identification
A. Content Management Layer
• Content (Markdown files)
• Static Assets (images, PDFs, CSV files)
• Archetypes (templates)
B. Build System Layer
• Hugo Configuration
• Layouts
• Shortcodes
• i18n (Internationalization)
C. Output Layer
• Generated Static Website
• Asset Pipeline
┌─────────────────────────────────────────┐
• Content Layer │
• ┬─────────────┬────────────┤
• Markdown │ Static │ Archetypes │
• Content │ Assets │ │
• ┬───────┴─────┬───────┴──────┬─────┘
• ▼ ▼ ▼
┌─────────────────────────────────────────┐
• Build Layer │
• ┬─────────────┬────────────┤
• Hugo │ Layouts & │ i18n │
• Config │ Shortcodes │ │
• ┴──────┬──────┴────────────┘
• ▼
┌─────────────────────────────────────────┐
• Output Layer │
• ┤
• Static Website Files │
• ┘
Component Details
A. Content Layer (Blue)
• Directories for different content types:
• Regular pages (about, activities, etc.)
• Meeting minutes (chronological structure)
• Resources
• Field day information
• Static file storage for PDFs and images
B. Build Layer (Green)
• Hugo configuration (hugo.toml)
• Custom layouts for minutes and other content types
• Shortcodes for special functionality
• i18n support structure
C. Output Layer (Orange)
• Generated HTML
• Processed assets
• Deployment-ready files
Additional Elements
• Version control integration (Git)
• Custom CSS processing (assets/css/custom.css)
• File types and formats in the static assets section