How sigpwny/websites works
Main Components
a. Website Applications
• sigpwny.com (Main club website)
• fallctf.com (Fall CTF event website)
• uiuc.tf (UIUCTF event website)
• As separate but connected containers
b. Shared Components Layer
• _global directory containing shared assets, components, and content
• Reusable nature of these components
c. Content Management System
• Static content structure (MDX and JSON)
• Git-based CMS integration
• Content types (meetings, events, profiles, publications)
d. Build and Deployment Pipeline
• GitHub Actions workflows
• Static site generation process
• Deployment targets
┌─────────────────────────────────────────────────────────┐
• GitHub Actions CI/CD │
• ┘
• ↓
┌─────────────────────────────────────────────────────────┐
• Shared Global Layer │
• ┌─────────────┐ ┌────────────┐ ┌────────────────┐ │
• Assets │ │ Components │ │ Content │ │
• ┘ └────────────┘ └────────────────┘ │
• ┘
• ↓
┌─────────────────────────────────────────────────────────┐
• Website Applications │
• ┌─────────────┐ ┌────────────┐ ┌────────────────┐ │
• sigpwny.com │ │fallctf.com │ │ uiuc.tf │ │
• ┘ └────────────┘ └────────────────┘ │
• ┘
• ↓
┌─────────────────────────────────────────────────────────┐
• Static Site Output │
• ┘
Important Relationships
• Inheritance of shared components across websites
• Content flow from global layer to individual sites
• Build process flow from source to deployment
• Integration points between different systems
Key Architectural Patterns to Highlight
• Monorepo structure
• Component reusability
• Static-first approach
• Content-driven architecture
• Separation of concerns between sites
Technical Details
• Astro as the main framework
• MDX for content management
• GitHub Actions for CI/CD
• Netlify for deployment (implied by configuration)
• NPM for package management