How seanrreid/ccs_curriculim_hub works
Main Components Identification
a) Content Layer
• Exercises (hexagons)
• Cohort-specific content (rounded rectangles)
b) Framework Layer
• Docusaurus core (central hexagon)
• React components (connected components)
• Static site generator (processing unit)
c) Build/Deploy Layer
• Build pipeline
• Deployment options (SSH/GitHub Pages)
Component Relationships
a) Content Flow
Content Sources → Docusaurus Engine → Static Output
b) Build Process
Source Files → Babel Processing → Static Assets → Deployment
Specific Implementation Details
/docs
• ↳ /lessons
• ↳ /exercises
• ↳ /cohorts
• ↳ /resources
/src
• ↳ /pages
• ↳ /css
/static
• ↳ /img
Data Flow Indicators
• Content compilation flow
• Build process flow
• Deployment paths
• User access patterns
Architectural Patterns to Highlight
Following patterns:
• Static Site Generation
• Component-Based Architecture
• Content-as-Code Pattern
• Educational Module Organization