CSS Layout News in the ATmosphere  🔗 **Source:** [CSS Layout News in the ATmosphere](https://rachelandrew.co.uk/archives/2026/09/04/css-layout-news-in-the-atmosphere/) > [!note]+ Document Notes > --- > tags: [atproto, css-layout, newsletters, data-portability, indieweb, rachel-andrew] > author: Rachel Andrew > source: rachelandrew.co.uk > reference: https://rachelandrew.co.uk/archives/2026/09/04/css-layout-news-in-the-atmosphere/ > date created: 2026-09-04 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > <!-- deep-read: light-touch --> > > [!note] Why light-touch. This is a 232-word relaunch announcement. Running the full > > 18-section template over it would pad rather than analyze — the source does not contain > > eighteen sections' worth of material. The sections below are the ones that actually apply, > > per the skill's thin-source guidance. The atproto angle is the reason it is worth a note > > at all rather than a bookmark. > # 🏷️ Title: CSS Layout News in the ATmosphere > ## 📝 Summary > Rachel Andrew is relaunching **CSS Layout News**, the newsletter she started in 2015 to write about CSS Grid before it shipped in any stable browser. It ran to 343 issues and stopped in 2023. Two reasons, and the second is the interesting one: she got busy, and her signup form on the previous platform filled with spam registrations that she was **billed to send email to** unless she cleaned them up manually. > The relaunch is hosted on [Offprint](https://offprint.app/), an atproto publishing app. Her stated reason is the one worth noting: because Offprint is built on AT Protocol, each issue lives in her own PDS, and she expects **this to be the last migration she has to do**. > The old list is gone. Prior subscribers must sign up again — partly the spam problem, partly that mailing a two-year-dormant list is a reliable way to get flagged as spam. > ## 📖 Main Content > - **The failure mode is a platform-economics one, not a technical one.** Spam signups were not merely noise; the pricing model made them a *cost*. A newsletter platform that bills per recipient converts an abuse problem into a bill the publisher pays, with the cleanup labour also falling on the publisher. That is a small, concrete example of a platform externalizing its own abuse-handling onto its users. > - **The migration claim is the substantive part.** Storing issues in a personal data server means the content is addressable independently of the publishing app. If Offprint fails or becomes unpleasant, the archive does not need to be exported and re-imported — it is already hers. That is the whole promise of the protocol, stated by someone with a 343-issue archive and real migration scars, which is a more credible endorsement than an architectural argument. > - **The dormant-list problem is worth knowing independently.** Sending to a list that has not been mailed in two years damages deliverability regardless of consent history or content. Her decision to start clean rather than risk the domain reputation is the correct call and is not obvious to most people restarting a project. > - **What the post does not do.** It makes no technical argument for atproto, shows no code, and does not compare Offprint to alternatives. It is an announcement, and it is honest about being one. > ## 🗒️ Notes > - Started 2015, specifically to have a venue for CSS Grid before stable browser support. > - Ran to **343 issues**, ended 2023. > - Two causes: busyness, and spam signups that incurred send charges unless manually cleaned. > - Relaunched on Offprint; she credits them with help migrating the archive. > > [!quote] > > as Offprint is an atproto app, this should be the last time I need to migrate it anywhere. Each issue is safely stored in my PDS. > - New list from zero. Previous subscribers must re-subscribe. > - Reason given: the spam problem plus the deliverability risk of mailing a two-year-dormant list. > ## 📚 References > - [CSS Layout News](https://csslayout.news) — the newsletter, and the signup > - [Issue 1, 2015](https://csslayout.news/a/3mttbgsjzzw23-issue-1) — the archive's starting point > - [Offprint](https://offprint.app/) — the atproto publishing app now hosting it > - [The archive in her PDS](https://pds.ls/at://did:plc:xi53lkcvx4b3bl5tgsb7tnqe/app.offprint.document.article) — the actual repository record, which is the post's proof-of-concept > ## 💡 Implications > - **For the Post Kinds / Standard.site thread.** This is a working example of what the publisher side of a portable-identity protocol looks like in practice: content authored in an app, stored in a PDS the author controls, addressable outside the app. It is a useful reference point for the publisher-pillar gap the 2026-08-21 PKIW audit found. > - **For anyone running a newsletter.** Two operational facts, cheaply learned here: per-recipient pricing makes spam signups your bill, and a dormant list is a deliverability liability rather than an asset. > - **On the portability claim.** "The last time I need to migrate" is a prediction, not a demonstration. It holds only while Offprint writes to a schema other apps can read, and only while the PDS remains hers. Worth revisiting in a year rather than treating as settled. > ## 🎯 Conclusion > A good newsletter is back, and the reason to note it beyond that is the migration argument: an author with a decade-long archive chose an atproto app specifically so the archive stops being hostage to the publishing tool. Whether that promise holds is the thing to watch — but it is now being tested by someone with enough archive to notice if it fails. > **Next step:** sign up at [csslayout.news](https://csslayout.news) if you want it — the old list is gone and prior subscription does not carry over. And look at the PDS record; it is the most concrete artifact in the post. [In 2015 I started my CSS Layout News newsletter](https://csslayout.news/a/3mttbgsjzzw23-issue-1,) mostly to have my own venue to go on about CSS grid, at the time unavailable in any stable browser. I got to 2023 and 343 issues and it fizzled out. Partly because I got busy, but mostly because the newsletter signup form on the platform I was using became inundated with spam signups. If I didn’t clean them up, I got charged for sending email to them. However, given the number of interesting things happening in the CSS layout space, I thought it might be fun to resurrect the project. The existence of atproto publishing apps gave me a final push. Today I’m announcing a relaunched [CSS Layout News](https://csslayout.news), hosted on [Offprint](https://offprint.app/). They were really helpful in helping me migrate my archive and, as Offprint is an atproto app, this should be the last time I need to migrate it anywhere. Each issue is [safely stored in my PDS](https://pds.ls/at://did:plc:xi53lkcvx4b3bl5tgsb7tnqe/app.offprint.document.article). #### Starting with a new list If you received the email previously, you will need to sign up again. In addition to the spam signups issue, the list hadn’t been sent to for over two years. Suddenly sending email to an old list is a good way to get flagged as spam, even though I’m not selling anything. So, if you want to get nerdy CSS layout observations in your email, [sign up here](https://csslayout.news/)!, CSS Layout News in the ATmosphere, Rachel Andrew, 01m1p91g334h9ar8n1xme88t82.