You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have written a package for my school (available here: https://github.com/SkytAsul/INSA-Typst-Template) and I would like to publish it here. However, this package comes with 3 different flavors: one for reports, one for blank documents and one for letters (and I plan on adding one for thesis).
All of those flavors come within one typ file, people simply have to choose between 3 functions to use in the show rule.
Shall I publish 3 separate templates here so they can be chosen from the template selection screen? I fear if everybody does that it will bloat the repository...
The text was updated successfully, but these errors were encountered:
Minor reconfigurations of the same document should be done via arguments to a show rule, but completely different deliverables (e.g. reports vs. letters) should be separate templates. This way, they can have separate preview images, categories, descriptions, etc. Moreover, a template is fully identified and can be instantiated just from its name, rather than "start from this template and then change this functions here".
If you need to share a lot of code between different deliverables for the same institution, you can factor that out into a shared utility package.
Description
Hello,
I have written a package for my school (available here: https://github.com/SkytAsul/INSA-Typst-Template) and I would like to publish it here. However, this package comes with 3 different flavors: one for reports, one for blank documents and one for letters (and I plan on adding one for thesis).
All of those flavors come within one typ file, people simply have to choose between 3 functions to use in the show rule.
Shall I publish 3 separate templates here so they can be chosen from the template selection screen? I fear if everybody does that it will bloat the repository...
The text was updated successfully, but these errors were encountered: