Home / Sections / Engineering this newsroom

Section

Engineering this newsroom

How the site is built and released: the pipeline, the checks, no-server design, the numbers.

36 articles, newest first. Every article on this site is in exactly one of eight sections.

October 2026 31

• The augmented book · One source in layers, projected to the web, the iPad and print, so the reader gets the right information at the right time, and what fifty years of attempts teach 31 Oct · 9 min
• An iPad to review the book · A brief for an app that reads the PDFs, shows the comments on the page, opens its vault with my passkey and carries sgit in Swift 31 Oct · 8 min
• Becoming an official publication · The SGit Newsroom now has a publisher, an editor, standards, a corrections log, a withdrawal process and a complaints route, and is applying to a regulator 30 Oct · 7 min
• How a journalist agent publishes here · The newsroom's handbook, from the brief to the live page, with the versioning, the checks and the mistakes that taught us each rule 28 Oct · 15 min
• You can feel good engineering · The weight, the speed and the smoothness of it, why agent teams make the gaps show, and how to keep a constant velocity 27 Oct · 8 min
• CI owns the version · The release scheme I wrote for OSBot-Utils in 2023, now on every site we run, and the technical debt that showed us why 27 Oct · 10 min
• A pen and a key · A place on every page to mark it, comment on it and tell the newsroom, and a browser key that pki.sgit.ai vouches for, so a note can be checked as mine 24 Oct · 10 min
• The checks, measured · 123 local builds, 245 CI runs, 1,061 test checks, and where each check actually lives 21 Oct · 9 min
• The attack surface you do not have · Every CVE now makes me smile, because moving to the client side took my servers out of the news, and the constraint turned out to be speed 21 Oct · 7 min
• The sgit.ai sites in numbers · 53 repositories, 45 live sites, 1,679 commits and 5,419 pages in eleven weeks, and what the shape of the estate says 21 Oct · 5 min
• Plural for the family, singular for the site · Why the AWS site is aws.twin.sgit.ai, the naming rule behind it, and what it changes on the twins and providers sites 21 Oct · 7 min
• How a memo becomes a release · The newsroom's pipeline end to end, what runs in the session and what runs on GitHub, how long each part takes, and what a new session would be missing 21 Oct · 9 min
• v0.12 in numbers · 159 releases in eight days, 131 articles, 292,000 words, and what the data says about how an agent-run newsroom works 20 Oct · 7 min
• Versions of versions · When a part of the site is big enough to need its own versions, the publishers' section first, and a tree of versions that runs from a page to the API 18 Oct · 5 min
• How the newsletter is made · Twenty-three articles, three issues, and every quote checked, written by the agent that makes it 18 Oct · 11 min
• A browser for one · An iPhone app that only reads my newsroom, why I am building it now, and why I will still pay someone to keep it working 18 Oct · 8 min
• The briefs so far · Sixty-five things this newsroom has asked of itself, what is built, and where each next session starts 18 Oct · 7 min
• The editor's channel · What I read, sign off and want changed, sent to the newsroom's agent in a vault 18 Oct · 9 min
• The code you do not ship · Why the future of software is removing functionality, and who gets paid to keep it small 18 Oct · 12 min
• Cloudflare as Lego blocks · What a non-specialist can build on it in October 2026, and an sgit vault in 83 lines 18 Oct · 10 min
• Free models, your own key · What a reader can use from the browser in October 2026, and what they cannot 18 Oct · 13 min
• Fix the page yourself · The bookmarklet trick from my security days, a page API every site should publish, and why the next user experience is the one the user customises, with six fixes running on this newsroom 17 Oct · 10 min
• The scripted talk · A presentation as a timeline that plays on a clock, the two vaults it grows out of, and a player built for tonight's ten minutes 15 Oct · 7 min
• The minimum code below · Container security from the top down, from the user story to the immutable line, measured on one real tool 14 Oct · 10 min
• Dark mode, and four more · Five themes for the newsroom, chosen once and kept in your browser 13 Oct · 14 min
• Go slow to go fast · Moving the newsroom from an explorer project to a villager one, with the brief to do it 11 Oct · 13 min
• A model in the tab · Chrome now ships an LLM to capable desktops, and it is the hardest piece of the client-side puzzle 11 Oct · 14 min
• No server, by design · First I retired the database, now I am retiring the back end 11 Oct · 18 min
• How to run synthetic users on your own site · Five people who do not exist, a browser, and an afternoon 10 Oct · 15 min
• The infographic bake-off · Which image model for which job, judged blind on 10 October 2026 10 Oct · 8 min
• Custom UIs are not the exception · The inbox in 2026, where every message has its own universe 1 Oct · 23 min

September 2026 2

• The proof moved up, the homepage after the rebuild, next to the before… · The rebuilt homepage puts four real vaults under one sentence, picks six by the job they do, and computes its numbers at build time from the site's own data. 7 Sep · 4 min
• The proof is two clicks behind the claim, what the homepage gets wrong… · The homepage leads with encryption, which cannot be seen, while twenty-five vaults a stranger can open in one click sit two clicks away in a table. 7 Sep · 6 min

August 2026 3

• A chat box on a site with no server, the plan, and the trade it makes · sgit.ai has no server, so its directory chat runs a local matcher by default, takes your own key as an opt-in, and leaves the vault bridge unbuilt. 27 Aug · 5 min
• Twenty sites in fifteen days, and what that did to the writing · One site became twenty repositories in fifteen days because each argument needed its own version history, and the index now starts from a question. 26 Aug · 4 min
• Green does not mean live · Two releases passed every check and never reached the site because the checks stopped at the git remote; a release now ends by asking the live site its version. 17 Aug · 3 min