Site: roro9stack.net, phase 1 (the home page, Install with a browser flasher, Downloads)

A Zola site in site/, from the design: both themes on the device's palette, notched shapes, self-hosted fonts, the wordmark and icons, two generated hero drawings, nine App cards (the mesh messenger marked planned), real screenshots, the updates and build sections. The Install page builds ESP Web Tools' manifest in the browser from the Gitea API (it needs Caddy to allow the origin), refuses any download that isn't on the project's server, and falls back to the esptool steps. Downloads lists the releases. The focus ring shows on notched controls. A page checker fails the build if a page loads from another origin. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
2026-10-06 18:20:18 +02:00
parent b92fc6e2e5
commit 8f4b5e0ddc
48 changed files with 2939 additions and 0 deletions
@@ -0,0 +1,45 @@
+# The roro9stack site
+
+Source of https://roro9stack.net (docs/milestones/W1.md): a [Zola](https://www.getzola.org/) site. The home page, an Install page with a browser flasher, and the list of releases so far; the user guide, how-tos, FAQ and developer docs come next.
+
+```
+config.toml           base_url, the repository and API addresses
+content/              the pages (Markdown, with their template named in the front matter)
+templates/            base, home, install, downloads, 404; illustrations/ is generated
+data/                 the App cards and the screenshots' captions
+static/               css, js, fonts (self-hosted), img, screens (real screenshots), vendor/esp-web-tools
+tools/                make_illustrations.py, check_site.py
+```
+
+## Build and look
+
+```sh
+docker run --rm -u "$(id -u):$(id -g)" -v "$PWD/site:/app" -w /app ghcr.io/getzola/zola:v0.22.0 build   # public/
+docker run --rm -u "$(id -u):$(id -g)" -p 1111:1111 -v "$PWD/site:/app" -w /app ghcr.io/getzola/zola:v0.22.0 serve --interface 0.0.0.0
+python3 site/tools/check_site.py site/public    # what the pages promise, kept
+```
+
+Or `zola build` with a Zola of your own. The build reads the latest release and the list of releases from the Gitea API (`load_data`); if the server can't be reached, the pages say so instead of failing.
+
+## Publishing
+
+The web server pulls `main` and runs `zola build`, as for the blog. CI (`.gitea/workflows/site.yml`) builds the site and runs the checks when `site/`, `docs/`, `README.md` or `CONTEXT.md` change; the firmware workflow skips a change that touches only those.
+
+## Things to know
+
+- **The Install page needs Caddy's help.** Gitea's release downloads carry no CORS header, so the page asks the API from the browser only if Caddy, in front of Gitea, allows this origin:
+
+  ```caddy
+  @releases {
+      method GET HEAD
+      path /twisla/roro9stack/releases/download/* /api/v1/repos/twisla/roro9stack/releases*
+  }
+  header @releases Access-Control-Allow-Origin "https://roro9stack.net"
+  header @releases Vary Origin
+  ```
+
+  Without it the page says it can't reach the release server and points to the esptool steps.
+- **No third-party requests.** Fonts and the flasher library are served from here; `tools/check_site.py` fails the build if a page loads anything from another origin.
+- **Illustrations.** `templates/illustrations/*.html` are generated by `tools/make_illustrations.py`; run it again rather than editing them.
+- **Updating the flasher library:** see `static/vendor/esp-web-tools/README.txt`.
+- **Fonts** are DM Mono and Hanken Grotesk, under the SIL Open Font License (the licences are in `static/fonts/`).