ADR-001: Use Quarto for site generation

Status

Accepted

Context

We needed a framework to publish ~30 years of DSP material as a web portfolio and teaching resource. Candidates were MkDocs Material (already used in the old GitLab repo), Jupyter Book, and Quarto.

Decision

Use Quarto.

Consequences

• Positive: Multi-format output (HTML, PDF, slides) from the same source, important for teaching. Native LaTeX/Pandoc pipeline makes migrating existing LaTeX chapters easier. RevealJS slides can replace PowerPoint workshops. Active development and modern theming.
• Positive: Official GitHub Actions for build + deploy.
• Negative: Quarto is not pip-installable (separate binary). Mitigated by building on GitHub Actions only.
• Negative: .qmd is a new format to learn (though it’s just markdown with YAML headers).

Alternatives considered

• MkDocs Material: Already known, but weaker on notebooks, no slide output, Sphinx-era tooling.
• Jupyter Book: Pure Python ecosystem, but Sphinx-based theming, no slide output, slower development.