Simon Willison May 2026 newsletter: atom-everything feed guide

Simon Willison published his May 2026 newsletter on June 1, 2026, assembling links and short essays aimed at web developers and open-source maintainers. The issue introduces an "atom-everything" feed for site-wide syndication, alongside commentary on tooling and a curated link roundup.

Atom: the "everything" feed

A central item in the newsletter is a discussion of an "atom-everything" feed, a single Atom stream intended to surface all of a site’s content in one place. The writeup describes the motivations for a unified feed, practical tradeoffs around pagination and entry identifiers, and basic implementation notes for generating Atom XML from existing site data.

Willison frames the feed as a pragmatic solution for publishers that do not want to maintain multiple specialized feeds for posts, projects, and updates. He sketches how a single feed can be filtered by recipients or reader software, and outlines considerations for preserving stable permalinks, handling content types, and avoiding duplicate entries when content appears in multiple sections of a site.

The newsletter also includes code snippets and links to example implementations. Those examples aim to be small and composable so they can be adapted into static site generators, server frameworks, or small Python utilities. The writeup highlights compatibility choices that favor feed readers and simple pull-based consumption over heavier push-based syndication protocols.

Tooling, maintenance and curated links

Beyond the Atom material, the newsletter collects short notes about maintenance work and tooling decisions common to small projects. Topics cover release hygiene, dependency updates, and lightweight automation patterns for publishing and monitoring site content. The tone is practical: small changes that reduce cognitive load for maintainers and make it easier to keep feeds and archives consistent.

The issue bundles a curated selection of links to essays, code samples, and utilities relevant to running small public websites and publishing content. Many items are framed as prompts for experimentation rather than full-featured projects, with an emphasis on clear, testable code and reproducible steps for adoption. Readers are encouraged to adapt snippets rather than treating them as black-box dependencies.

The newsletter format blends short technical notes with pointers for further reading. That structure keeps individual items compact while still providing routes to deeper documentation and example repositories.

Why it matters

A single site-wide Atom feed reduces friction for readers and for simple archival workflows, making it easier to subscribe to everything a publisher produces without maintaining many specialized feeds. For small teams and solo maintainers, the emphasis on compact, reusable code and maintenance hygiene lowers the operational cost of running a public website and its syndication. The practical guidance should appeal to developers who prefer lightweight, transparent solutions over heavier publishing platforms.