Evaluate quarto

[Tim-Grube]

We could publish the script via quarto on our website

[fschledorn]

You mean the finished script? I think rn we only publish the versions here as releases on git and on the vorkurswebsite. And I am pretty sure by "WE" you mean you right? xD

[Tim-Grube]

I know where you live

[fschledorn]

As do I, and I might have lot’s of wine that needs to be drunk rather fast

[christian-heusel]

What is quarto? Could you post a link?

[fschledorn]

If I remember correctly: https://quarto.org/docs/guide/
Basically a service to auto publish documents. Although we could probably achieve the same behaviour with a Workflow that updates the Wordpress on a new release of the vorkurs script in case we dont want to maintain another service.

[christian-heusel]

Right now it's not even part of wordpress, it's just a static artifact hosted at https://mathphys.info/vorkurs/programmier/
If you want to go for a simple solution just make a job that generates thes artifacts when a tag is pushed and have a webhook that fetches them onto the server 😄

This would be a bit similar to how I've setup my website: https://christian.heusel.eu/blog/website/

[fschledorn]

Yeah that would've been my suggestion as well. We should probably also integrate it with PEPP in some kind or form. Tbf it’s not the only document we publish. We also have the normal vorkursscript that should be on PEPP and updated automatically, maybe we can set up something similar for that as well in the future.

[Tim-Grube]

IIRC the person suggesting this wanted to enable writing the script in markdown, as to lower the initial hurdle of helping with the script. As many people have the knowledge but don't wanna use LaTeX

[fschledorn]

I don't use markdown much, does it support the complexity we currently have in our script?

While I’m not generally opposed to switch to a different language (markdown, typst, or something else), I don’t think we should do so for the upcoming release (Vorkurs 25). There’s still a bit to do and I don't think we currently have the resources to perform a full refactoring in a new language in addition to the changes already planned until early September.

As a quick fix, I suggest that people who want to help but don't like/know Latex can just submit the rewritten text in the corresponding issue(or create a new issue) and then we transport that to latex, which should be fairly easy, without needing a lot of time. Maybe there are even some markdown to Latex Compilers although I don’t know how well they will integrate in our current setup.

[Tim-Grube]

Which complexity? It can show text, lists, code and images - we don't have much more than that anyways

But I agree on the priority aspect

[fschledorn]

I meant primarily stuff like diagramms, table of contens, footers, footnotes and such. I know that some of these features definitely work under markdown, for example images and code.
Also can you write markdown code "decentralised", i.e. not everything in a single file?

Anyways we should probably evaluate that properly after the next Vorkurs.