Description
Weird title, but I'm currently trying out a new workflow which works pretty great in a local environment, but not here in the Webapp.
I would like to have an additional option for rendering/compilation, that instead of downloading the file after completion, actually uploads it to the location where the .typ document sits (i.e. ./plots/plot.typ -> ./plots/plot.pdf)
Use Case
In my projects I have a file called drawings.typ in my images folder. In there I insert all kinds of drawings/graphics created using typst packages such as lilaq, fletcher, cetz, etc. I export this file to a pdf and then insert the images via #image("./images/drawings.pdf", page: #) where # is the respective image.
It's more to relieve the main document from various package function calls and speed up compilation time (actually, is this true?).
Description
Weird title, but I'm currently trying out a new workflow which works pretty great in a local environment, but not here in the Webapp.
I would like to have an additional option for rendering/compilation, that instead of downloading the file after completion, actually uploads it to the location where the
.typdocument sits (i.e../plots/plot.typ->./plots/plot.pdf)Use Case
In my projects I have a file called
drawings.typin myimagesfolder. In there I insert all kinds of drawings/graphics created using typst packages such as lilaq, fletcher, cetz, etc. I export this file to a pdf and then insert the images via#image("./images/drawings.pdf", page: #)where#is the respective image.It's more to relieve the main document from various package function calls and speed up compilation time (actually, is this true?).