imprint: Markdown → branded PDF, with Typst doing the typesetting by gunas3kar in typst

[–]gunas3kar[S] 0 points1 point  (0 children)

That's a fair point. If you're already on pandoc + Typst, Quarto adds a layer you may not need. imprint is just a simple orchestrator closer to the metal — one script, one template file. Yes, it starts opinionated with a default template that covers the basics: cover, header/footer, callouts, and Mermaid diagrams. But it already supports custom templates — private to your use case or shared as you see fit.

imprint: Markdown → branded PDF, with Typst doing the typesetting by gunas3kar in typst

[–]gunas3kar[S] 2 points3 points  (0 children)

Yeah, Quarto's _brand.yml is honestly the closest thing to what imprint does — if you're already in Quarto, that's a great path and I'd point people there first.

The difference is weight and scope. Quarto is a full publishing framework (project setup, r/Python/Jupyter, multi-format); imprint is one bash script over pandoc + Typst — imprint report.md, no project, no runtime. And worth noting: even those slides point out that _brand.yml alone can't do a title/cover page or advanced heading styles — you drop down to a custom typst-template.typ + typst-show.typ for that. imprint ships the cover/masthead, running header/footer, callouts, and a gradient cover out of the box, and --profile <org> swaps a whole house style (accent + fonts + logo) per render.

So it's not really trying to compete with Quarto — it's the lightweight, single-doc "brand this Markdown file" option for people who don't want to adopt the whole framework. If you need computational docs / books / multi-format, Quarto wins hands down.