MakerFLOSS/docs/services/slides.md
Lars Rossen 91f53f1f62
All checks were successful
Build docs site / build (push) Successful in 49s
Build slides / build (push) Successful in 1m16s
slides: frame a 'How to implement a TAPPaaS module' deck
Adds a second Marp source root. Decks under slides/ build to an output path
mirroring their repo path, so slides/TAPPaaS/HOW-TO/NewModule/index.md is
served at slides.makerfloss.eu/TAPPaaS/HOW-TO/NewModule/. Decks in
docs/presentations/ keep their flat URLs.

The deck itself is a frame: structure and headings from the real
src/apps/00-Template anatomy, content still to be written. Unfinished spots
are written as inline `TODO: ...` and rendered in red so a half-finished
deck cannot be presented by accident.

Also fixes the Docker fallback, which could not write to a mktemp directory
on macOS (not shared with Docker Desktop) and must not be passed --user.
2026-08-22 16:01:50 +02:00

956 B

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.