Does anyone here use a job runner or a full build system around Typst documents? I was looking at using Just as a means of including post-compile options such as third-party open source PDF overlay and imposing tools, or maybe for data prep ahead of import. Just curious to see what people are doing along these lines.
Hello! If I understand well, you’re looking for usage examples of Typst integrating other softwares to enhance its features. I definitely know of some good use cases:
EDIT: I realise I misunderstood! I personally just use make or just. In the example below, Tesla Zhang uses a script, that also works.
- Large-scale Typst PDF generation: 1.5+ million PDFs in 25 minutes - Zerodha Tech Blog
- Shiroa is the Typst mdbook: GitHub - Myriad-Dreamin/shiroa: shiroa is a simple tool for creating modern online books in pure typst.
- Quarto Typst driver: Typst Basics – Quarto
- CV generation by Tesla Zhang: GitHub - ice1000/resume: 👾 My resume / 我的简历
P.S.: Don’t hesitate to look at How to post in the Questions category! Your title should probably be a question along the lines of “Does anyone use a job runner or build system with Typst documents?”
1 Like
Yes.
I just use make, some people make with just.
3 Likes
I use just too, since Typst handles incremental compilation and dependencies on it’s own I don’t even need anything else.
2 Likes
I’ll endorse Doit as a great job-runner for document production. I’ve been using it for about 8 years now. First with latex, now with typst. Simple to start but very flexible. Where doit really begins to shine is when you have job tasks that don’t depend on files. Maybe you want to query a database or a remote service? Perhaps you have some administrative commands you want to implement that aren’t related to document creation.
You may also find that the definition of when a task is up-to-date and does not need to be run isn’t as simple as file modification. Doit can handle this easily.
1 Like
Ah, hadn’t tried Doit yet. Sounds ideal.