So you want to write a Typst package. You’ve heard about the typst-community-template. It works. It’s fine. It’s the beige wall of package templates, inoffensive, forgettable, but always slightly too much effort to set up.
Enter my copier template. You answer a handful of questions, it spits out a fully structured Typst package, and you get on with the actually interesting part. Here’s why you should consider using that in the future:
- Interactive setup. Answer a few prompts, get a ready-to-go package. No manual find-and-replace like a medieval scribe.
- Opinionated. Sensible defaults and a clean structure out of the box.
- Future-proof. Copier lets you pull updates from the template into your existing project — so when the template improves, you’re not left behind.
Now, the quirk. The template is opinionated and integrates with gotpm, a Typst package manager I wrote, which is used by approximately one person… me.
You can replace it entirely with a package manager of your choice. I am even considering of letting the user of the template decide which package manager to use in future iteration. You want something changed? Just leave a Pull request or open an Issue. If you like it consider leaving a star on GitHub — no pressure. (Some pressure.)