Public Access
Site / build (pull_request) Successful in 9s
Seven posts imported into site/content/devlog/ with their text unchanged, links between them pointing to /devlog/, and shortcodes (sign, cast, steps, asides, folded sections, diagrams, captions) restyled in the site's palette. The 17 inline SVG diagrams carried <style> blocks and style attributes the site's Content-Security-Policy refuses: their rules moved to devlog-diagrams.css, and a diagram's minimum width is a class. An Atom feed at /devlog/atom.xml. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
13 lines
755 B
Markdown
13 lines
755 B
Markdown
+++
|
|
title = "The devlog"
|
|
description = "How roro9stack gets built, written up as it happens: what worked, what broke, and what the firmware taught me on the way."
|
|
sort_by = "date"
|
|
page_template = "devlog-post.html"
|
|
template = "devlog-index.html"
|
|
generate_feeds = true
|
|
+++
|
|
|
|
One post for each stretch of work, newest first. They are written after the fact, from the commits, the decisions and the logs, and they keep the bad parts in: every post has at least one thing that turned out not to be what I thought. For what the firmware does *today*, read the [user guide](/guide/); this is how it got there.
|
|
|
|
My other write-ups (a vinyl remote, a ZFS rescue) are on [twisla's experiments](https://experiments.twis.la/), where these posts were first published.
|