Wrap-up
Practical Quarto: Patterns, templates, and tooling @ posit::conf(2026)
Four problems, four patterns
Productive workflows with Positron — making the most of your IDE
Design once, use anywhere — one brand, every format
Build reusable structures — the meta data around your content
Why Typst matters — a PDF you can restyle
Which piece for which job?
_brand.yml — the same look across formats and projects. One repo, not a theme per project.
Template partials — the same structure, different content. Format specific, and driven by metadata.
What we did not get to
Lua filters — change the document while Pandoc holds it as an AST.
Not format specific, so one filter can serve html, typst, and revealjs. Reach for one when the change you want is to the content, not the boilerplate around it.
Extending Quarto → — a whole workshop on filters, shortcodes, and extensions
Where to go next
quarto.org — the reference, and the changelog for each release
GitHub Discussions — where the maintainers answer, and where the good examples end up
Discord, #workshop-quarto — we’ll keep an eye on it for a while
These materials
This site and exercise folders will stay up!
Licensed CC BY-SA 4.0 — reuse them, teach from them, just say where they came from.
Workshop survey
Before we move on to Q&A,
please take a note of the workshop survey:
![]()
![]()
and grab a Quarto and/or Positron hex sticker!
Questions?
Any questions, but especially of the kind:
How would I solve _my problem_ with a brand, a partial, or Typst?
Which of those do I even need for _my problem_?
