Every paper is a channel

A paper used to be a website. Now it is a channel, and every door is on the paper's own address.

The channel page

Every public paper has /subscribe: what the paper is, the price if it charges, and every way to follow it: the email briefing, the podcast, the video edition, the feeds and the API. Older addresses like /channel and /about lead there.

An API for everyone

Open /api on any paper and you get its developer front door: the base address, the first call in three languages, every door with a live try-it that runs against the paper's own index, four recipes, and the house rules. It is in the reader's language.

The keyless index at /api/v1 answers with the sections, the days, any day's stories, search, the front and the video edition, and describes itself at /api/v1/openapi.json. A reader can subscribe through it too. /api/v1/posts hands back every piece as ready-to-post short form, sized for X. /front.json and /podcast.xml are on every public paper.

Alerts a reader sets

Alerts are the reader's, not the paper's. Each subscriber picks instant, daily or weekly, chooses sections, and decides whether the video edition rides along, on their own clock. A bell on the paper opens the settings, and the reader's account on the paper is where they live.

An alert can also be a watch that fires to a webhook. The delivery is signed with the reader's own key, so their system can check that it came from their subscription, and every story link in it points at the paper's own address.