slides¶
Service¶
| Field | Value |
|---|---|
| Kind | static-site |
| Host | makerfloss.eu |
| URL | https://slides.makerfloss.eu |
| Tech | Marp + Mermaid.js |
| Upstream | https://marp.app |
| TLS | letsencrypt |
| Status | in-use |
Notes¶
Slide-deck site. Decks are authored as Marp markdown and compiled to HTML by
build-slides.sh (CI invokes it via the marp toolchain). Built output is rsynced to
the VPS and served alongside docs.
Two source roots, two output conventions:
| Source | Published at |
|---|---|
docs/presentations/<name>.md |
https://slides.makerfloss.eu/<name>.html |
slides/<path>/<name>.md |
https://slides.makerfloss.eu/<path>/<name>.html |
Use slides/ when a deck belongs to a named series and the URL should read like a path — for
example slides/tappaas/how-to/new-module/index.md is served at
https://slides.makerfloss.eu/tappaas/how-to/new-module/. Only the markdown is committed; the
generated HTML under slides/ is git-ignored.
Images belong next to the deck source (slides/<path>/<name>.jpg) and are referenced with a
plain relative path. Marp keeps relative URLs as-is, so build-slides.sh copies image files from
slides/ into the output tree at the same relative path — unlike the HTML, these are committed.
Only path-mirrored slides/ decks can carry images; docs/presentations/ decks are flattened to
<name>.html, so a relative path would not survive.