How phil-opp/blog_os works
Project type and purpose
• This is a static documentation/blog site („Blog OS“) that hosts the “Writing an OS in Rust” tutorial series. It’s not a traditional full-stack app but a static site generator pipeline combining Markdown content, templates, asset preprocessing, CI/CD, and Docker.
File‐structure breakdown
• Top level
• .github/ – GitHub Actions workflows (build blog, link checks, scheduled rebuilds)
• docker/ – Dockerfile + entrypoint for a reproducible build environment
• scripts/ – convenience scripts (merge.fish, push.fish)
• README.md, licensing, CI config
• blog/ folder (site source)
• config.toml – static site generator configuration
• content/ – Markdown posts in multiple editions and translations
• templates/ – HTML templates (base layouts, sections, macros)
• sass/ – SCSS styles, per‐edition
• requirements.txt – Python dependencies for that hook
• CI/CD
• .github/workflows/ – workflows for building the blog, checking links, scheduled nightly builds
Key README insights
• Each OS tutorial post lives in its own Git branch (post-XX) and is built on demand via git worktree.
• The site is generated from the blog/ folder, then deployed (likely to GitHub Pages).