Lars Rossen
87650dac86
Adds a slide after the hardware diagram showing the two racks side by side — the MakerFLOSS rack at Orange Makerspace and the one at home — to make the point that the module contract is what lets those two rooms run the same system. build-slides.sh now copies image files from slides/ into the output tree at the same relative path. Marp keeps relative image URLs, so without this the images would 404 on the published site. Guarded against the local build, where OUTPUT_DIR is the source directory and the copy would be a no-op onto itself. This is the first deck in the repo with images; the convention is documented in docs/services/slides.md. Photos resampled to 1200px on the long edge (~300 KB each) from the 3072x4080 originals. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.4 KiB
| name | kind | status | host | url | upstream | tech | tls |
|---|---|---|---|---|---|---|---|
| slides | static-site | in-use | makerfloss.eu | https://slides.makerfloss.eu | https://marp.app | Marp + Mermaid.js | letsencrypt |
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.