Erich Blume b197bd5f58 Adopt Dagger CI for docs build (Phase 2) (#157 )

## Summary

Migrates the docs build pipeline to Dagger (Phase 2 of the Dagger CI adoption plan).

- **Backfill `date-modified` frontmatter** on all 80 docs — Dagger's `--src=.` excludes `.git`, so Quartz can't use git history for page dates. Frontmatter dates work with or without git.
- **New `docs-check-frontmatter` mise task + pre-commit hook** — validates all docs have `title`, `tags`, and `date-modified`
- **New Dagger functions** — `build_changelog` (towncrier in Python container) and `build_docs` (chains changelog → Quartz build in Node container, returns tarball)
- **Simplified CI workflow** — the ~44-line inline Quartz build (clone, npm ci, build, tar, cleanup) is replaced by `dagger call build-docs`. Changelog step remains local on the runner since towncrier needs to modify the host working tree for the git commit.

### Design decisions

- **Towncrier runs twice in CI**: once inside Dagger (for the docs tarball) and once on the runner (for the git commit). This is intentional — Dagger's directory export is additive and can't delete the consumed changelog fragments from the host.
- **Artifact hosting stays on Forgejo Releases** (not migrated to Forgejo Packages as the plan doc originally suggested). That migration can happen independently.
- **`date-modified` frontmatter** preserved even though `build_changelog` installs git — the git there is only for towncrier's `git add` call, not for history. The local iteration story (`dagger call build-docs --src=. --version=dev` with uncommitted changes) depends on frontmatter dates.

### Local iteration

```bash
dagger call build-docs --src=. --version=dev export --path=./docs-dev.tar.gz
tar tf docs-dev.tar.gz | head -20
```

## Deployment and Testing

- [x] `dagger call build-docs --src=. --version=dev` produces valid 1.1MB tarball (149 HTML pages)
- [x] Pre-commit hooks pass (including new `docs-check-frontmatter`)
- [ ] Full `workflow_dispatch` run after merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/157

2026-02-11 16:33:16 -08:00

1.8 KiB

Raw Blame History

title

date-modified

Tutorials

Learning-oriented guides for understanding and working with BlumeOps.

Audience Guide

Each tutorial indicates which audiences it serves:

Icon	Audience	Description
Owner	Erich	Quick recall and operational refreshers
AI	Claude/AI agents	Context for AI-assisted operations
Reader	External readers	Understanding what BlumeOps is
Contributor	Operators/contributors	Helping with BlumeOps development
Replicator	Replicators	Building your own similar setup

Getting Started

Tutorial	Audiences	Description
exploring-the-docs	All	How to navigate and use this documentation
ai-assistance-guide	AI, Owner	Context for effective AI-assisted operations

Contributing

Tutorial	Audiences	Description
contributing	Contributor	Your first contribution to BlumeOps
adding-a-service	Contributor, Replicator	Deploy a new service via ArgoCD

Replication

For those building their own homelab GitOps setup.

Tutorial	Audiences	Description
replicating-blumeops	Replicator	Overview: building a similar environment
[[tailscale-setup	Tailscale Setup]]	Replicator
[[core-services	Core Services]]	Replicator
[[kubernetes-bootstrap	Kubernetes Bootstrap]]	Replicator
[[argocd-config	ArgoCD Config]]	Replicator
[[observability-stack	Observability Stack]]	Replicator

1.8 KiB Raw Blame History