How chrisladzamach/lqh-program works
Project Type & Purpose
• Type: Static Site built with Astro (a static site generator).
• Purpose: Present Taekwondo content (techniques, forms/poomsaes, ranks) as a browsable website.
High-Level Architectural Components
• Development Environment
– Source Repos: Git (project root with .gitignore)
– Editor/IDE Config: VSCode settings under .vscode
– TypeScript config: tsconfig.json
• Build Tool
– Astro config (astro.config.mjs) driving static generation
– package.json & package-lock.json for Node.js dependencies
• Source Structure (src/)
– src/pages: Individual route files (.astro) generating each HTML page
– src/layouts: Shared page wrappers (Layout.astro)
– src/components: Reusable UI pieces (Header, BackButton, GradeCard, etc.)
– src/data: TypeScript modules exporting structured content (poomsaes, grades, techniques)
– src/styles: Global CSS definitions
• Public Assets
– public/manifest.webmanifest & any static files directly copied to dist
• Build Output (dist/)
– Fully static HTML/CSS/JS tree ready for deployment
– Manifest, CSS bundle under dist/_astro
• Deployment Target
– CDN or static-site host (e.g., Netlify, Vercel, GitHub Pages) serving dist/
Relationships & Data Flow
1. Developer writes/updates .astro pages, components, data in src/
2. npm run build (Astro) reads astro.config.mjs → compiles pages + layouts + components + data → emits static assets to dist/
3. CI/CD (optional) picks up dist/ → deploys to static‐site host/CDN
4. Browser requests URL → CDN serves prebuilt HTML/CSS/JS from dist/
Key Architectural Patterns
• Static Site Generation (SSG): One‐time build → static assets
• Component Composition: Pages import shared components & data modules
• Data-Driven Routing: File-based routing in src/pages, with data from src/data
• Separation of Concerns:
– src/pages for routing
– src/components for UI
– src/data for content
– public/ for truly static files