How a note becomes a published page.
Pipeline
flowchart LR A[Obsidian vault] --> B[git push] B --> C[GitHub Actions] C --> D[npx quartz build] D --> E[GitHub Pages] E --> F[kb.dev.avro.cc]
Components
| Layer | Tech |
|---|---|
| Authoring | Obsidian (Markdown) |
| Build | Quartz 4 + GitHub Actions |
| Hosting | GitHub Pages |
| Edge | Custom domain + CNAME |
Auth (optional)
Real OAuth on a static site needs an edge gate (e.g. Cloudflare Access) in front of the domain — see getting-started for the workflow context.
Notes
- Build trigger count, not page count, is what hits Pages/CF limits.
- Themes are pure CSS variables — no rebuild needed to switch at runtime.
Related: markdown-showcase · Home