Home / Articles / Fix the page yourself / Versions / v1.1.0
Fix the page yourself: what changed in v1.1.0
From v1.0.0 (2026-10-17, 037e8368e) to v1.1.0 (2026-10-18, de821285d), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 56 unchanged. About 3 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
1 unchanged paragraph
Summary: Years ago, during a security assessment, I packaged an exploit as a bookmarklet, a bookmark that runs a line of JavaScript on the page you are on, and gave it to the business owner to show that one user could see data they should never see. She was more excited about the interface I had wrapped it in than about the vulnerability, because my quick Bootstrap page was so much better than the application she used every day. That story still describes most of the web. Sites are built to show ads and hold attention, not to let me read; even the newest products have gaps their own users could fix in a line of code. My argument is that the next generation of user experience is the one the user customises, and that sites should encourage it: publish a small JavaScript API for the page, the primitives a fix needs, so that every fix is one line, the same API serves tests and agents, and the fixes people keep become thea bestbetter brief than the site willcould everwrite get.itself. It is also the cheapest route to accessibility, because each reader can build what they need on primitives the site provides. This newsroom now does it: a page API with six fixes, from reading mode to WCAG text spacing, as buttons, bookmarklets and code. The rest is a brief: a community library of fixes, per-site extensions that only touch the tab you click, and the same API on sgit.ai and ruv.sgit.ai.
25 unchanged paragraphs, under In short {#in-short}, The bookmarklet that out-designed the application {#story}, Every site still fights its readers {#problems}…
And here is the part sites should want. A fix a user writes, and keeps, is thea clearestbetter brief than any the site willcould everwrite get:itself: what a real person needed, in a form that runs. It is explorer coding applied to the page in front of you. The fixes many people keep should become settings, and then the script disappears, because the product does it. This newsroom has done exactly that once already: the first outside reaction to its Industry Wire was two words on WhatsApp, "Dark mode!", and five themes shipped soon after. The personal fixes that stay personal are where the vendor becomes the villager and is paid to maintain them.
30 unchanged paragraphs, under It is the cheapest accessibility there is {#accessibility}, How the fixes reach the page {#delivery}, It runs here {#here}…