website (only local/static stuff, other services will be linked to) https://shiny.space
Find a file
2026-02-07 22:35:08 +01:00
content updates 2026-02-07 22:35:08 +01:00
static check in proper css file 2026-01-29 17:53:28 +01:00
templates added old blog entries 2026-02-01 00:31:42 +01:00
.gitignore remove useless public dir - we dont need to track it at all 2026-01-29 18:04:08 +01:00
README.md initial 2026-01-29 17:42:15 +01:00
updatesite.sh small script to update site 2026-01-29 17:59:45 +01:00
zola.toml initial 2026-01-29 17:42:15 +01:00

the website that should open when you go to shiny.space.

currently built with Zola, a static site generator.

Trying to keep it simple.

The basics: "zola build" should parse the templates (mostly html) and the content (markdown) to create the final html files in the output directory, which our webserver (currently caddy) should serve.

attention: zola build deletes the output dir. ideally test if the build works with that version of zola before running it on the production server. yes zola can have breaking changes (rarely and small ones so far).

For making changes that are more complicated than simply adding a markdown file for content: zola serve can watch the filesystem and autmatically serve the site locally, it even adds an autrefresh javascript to reload the page on changes.