· 2 min read
One graph per page
Structured data is one @graph a page, not a pile of objects — and every id that graph references has to be defined on the same page a consumer is reading.
Blog
Written while building this site, about decisions that were still fresh enough to explain. Newest first, and every one of them is in the feed.
Archive
Everything else
Each of these is an object in one array, rendered by one file. Adding a post is adding an entry.
Dark mode without a toggle
A toggle needs JavaScript this site does not ship, so dark mode is one file of paired colour tokens plus the one line of CSS no utility class expresses.
A link should look like one
Underlining links only on hover leaves keyboard and touch users with nothing to go on, and this site had been doing exactly that in its body copy.
Auditing what the build renders
The build already has every page as a string, so checking them for missing titles, duplicate ids and contradictory ARIA costs almost nothing.
Inlining the stylesheet
Why this site puts its entire stylesheet inside every page, what that costs on a repeat visit, and the escaping trap that comes with it.
Subjects
What it keeps coming back to
Performance, accessibility and the build itself, which on a site like this turn out to be the same subject three times.
- Posts
- 5
- Subjects covered
- 7
- JavaScript per post
- 0 kB
- Every post, in the feed
- RSS
Subscribe, or read the rest of the site
The feed carries the posts and nothing else — a catalogue is not a stream, so the products and services stay out of it.