A newsroom needs a desk: one screen where the calendar, the drafts, the sources, the people and the health of every publication are visible at once. We could not buy one that understood sixteen publications and one database, so we built it. It is called Atlas Command, it lives at an address only the newsroom can log into, and the core of its second version was built in one day.
What it is
Think of it as the back office of the platform. Everything a reader sees on the sites is produced or checked here.
The editorial calendar, as a month grid and a list, across every publication. A content browser for every article and page with its status. Editors for both, with a preview. The sources library: every transcript and every document we have filed, with which articles cite them. The entities: every person, place and body we track, with their coverage. Authors and tags. A feed monitor watching the outlets we compete with and the sources we follow. An insights view: publishing volume, output by beat and by author, the editorial pipeline as a funnel. Health scores per publication. A bug button on every page, so a problem gets logged instead of fixed in a panic. A command palette so any of it is two keystrokes away.
It is the same database the public sites read, seen from the other side.
The day it was rebuilt
The core of version two, the model of work underneath it and the home view on top, was built on April 21 in seven stages, start to finish. The core of it was a decision about what a piece of work is. We had two separate tracking systems, a planning calendar with 287 rows and a task list with 60, and they did not know about each other. The rebuild folded both into one model of work, moved every existing row into it, with every link to a published piece checked afterward and intact, and put a single home view on top: what is due, what is blocked, what shipped.
I mention the day not to boast about the speed but because of what the speed made possible. A newsroom tool that takes a quarter to change is a tool you stop changing. Ours changes when the work changes. When we added meeting transcripts as a first-class source, the desk got a transcripts view. When we started tracking people and bodies, it got an entities view. When bugs needed a home, it got one in a morning.
What a desk should be
Here is what I think. A rented content system gives you the vendor's idea of a newsroom: posts, pages, a media library, maybe a calendar. Ours gives us our idea of one, and our idea has transcripts and source documents and people at the centre, because that is where local reporting starts. The desk is shaped like the work.
There is a second, quieter benefit. Because the desk and the public sites read the same database, there is no export step, no sync, no "it is in the CMS but not on the site yet." When the desk marks an article published, it is published. When it links a person to a story, the person's public profile shows the story. The tool is not a layer on top of the platform. It is a window into it.
This is No. 05 in We Built Our Own. Previous: Email we own. Next: Analytics without a black box.