How chayanon-ninyawee/recruitment_hackathon_2627 works
This branch is the hackathon’s documentation front door, not the racing software. Its main workflow takes README and chapter Markdown from the two track branches, renders a shared static site, and publishes that site for readers. The generator also builds the landing page and applies platform-aware rendering; browser JavaScript handles reader interactions. The README documents the broader build and publishing behavior, while the sampled excerpts show only parts of the generator and client script. Link checking and build infrastructure are omitted.
Main entry points: build.py Static-site generator · docs.css Site styles · site.json Landing-page config · templates Page templates
Components 13
Documentation content
- Track Markdown
- Landing-page config
docs-site/site.json
Site generation
- Static-site generator
docs-site/build.py - Page templates
docs-site/templates - Static assets
docs-site/static - Site styles
docs-site/theme/docs.css - Design tokens
docs-site/theme/tokens.css - Rendered track pages
- Track landing page
Reader experience
- Interactive controls
docs-site/theme/app.js - Published site
Other components
- Hackathon reader
- GitHub Pages
Connections 12
- Track Markdown → Static-site generator: provides Markdown
README.md - Landing-page config → Static-site generator: configures landing
README.md - Static-site generator → Rendered track pages: renders chapters
README.md - Static-site generator → Track landing page: renders landing
README.md - Page templates → Static-site generator: supplies shells
README.md - Static assets → Static-site generator: copies assets
README.md - Static-site generator → Published site: assembles output
README.md - Site styles → Published site: styles pages
README.md - Design tokens → Site styles: defines properties
README.md - Interactive controls → Published site: enhances pages
docs-site/theme/app.js - Published site → GitHub Pages: published on
README.md - Hackathon reader → Published site: reads site
README.md