A Web Built on Content Fidelity

Meta has announced the end of support for Instant Articles, its proprietary format for delivering fast, stripped-down news content. It’s the latest in a line of similar platforms—Google’s AMP being the most prominent—that promised publishers speed and reach but required them to adopt a bespoke format, where publishers lose control over their content and end up maintaining multiple versions of their output.

The irony isn’t lost on Chris Coyier in his own post on the subject: the goal of a publisher is to get their content where the readers are, and so it’s tempting to feed yet another format. But as he points out, that mindset quickly leads to managing 4-5 different content formats, some quite specific, and all far from automatic. None of the big platforms seemed to consider simply taking an RSS feed, despite it solving many of the same distribution and performance problems they were each trying to solve.

The core issue is not just one of formats, but of accessand choice. Jim Nielsen has been exploring a different approach, one that doesn’t rely on proprietary ecosystems like Instant Articles or AMP to deliver a "lean" reading experience. Instead of heading to a separate site like text.npr.org for a no-frills version, his idea starts with existing content sites. The goal is to visit npr.org regardless, but with what he calls a set "fidelity preference" for events, which theoretically sends a header to the server requesting a lower-function version of the website.

Fidelity settings with three choices for default, minimal, and text-only.
So, now this is part of his blog’s user settings.

His actual implementation demonstrates an accessible piece of what this could look like for a content-driven site. It generates alternate renditions of the same article during the build, producing different versions of the same document rather than relying on an explicit URL change. He notes the current tooling—which builds out JSDOM versions and strips them—isn't necessarily clean, but it's a logical next step to a model where sites do not dictate the single richest option but accommodate how a user wants to read.

.
├── index.html # default
├── _fidelity/
    ├── low/
    │    └── index.html # text-only
    └── med/
        └── index.html # minimal

These are separate but clearly communicating ideas. They share a common suspicion of platforms that ask publishers to write in their dialect, and a common readiness to exchange that approach for the plain standards—HTML, RSS—that are already on the table. That's a web we can live with.