Journal / publishing system / 2026
A Real Home for Writing
The studio can prepare writing privately and publish deliberately; readers simply get a fast, focused Journal.
- Project
- Studio Publishing
- Made for
- Writers and readers
- Role
- Content architecture + design
Project story
Studio is where theProject. prepares published work. The public site is where that work becomes a reading experience.
The need
We wanted writing to have a real home.
A studio Journal should feel like a publication, not an announcement feed and not the public face of an administration tool. Writers need room to prepare. Readers need a page with pace, hierarchy, and a reason to stay.
Those are related needs, but they do not belong in the same interface. Separating them became the most important design decision.
WRITE IN PRIVATE.
PUBLISH WITH INTENT.
LET PEOPLE READ.
The publishing line
Manuscript, Studio, Journal.
Draft
Prepare the story
Writing, editing, media, and publication details remain on the private working side of the studio.
Publish
Make a deliberate release
Only ready work crosses the boundary into the public Journal. Drafts do not leak into the reading experience.
Read
Give the story room
The public page handles type, media, metadata, sharing, and responsive reading without exposing the machinery behind it.
The useful separation
The website did not need to become the office.
Studio by theProject. can support a capable editorial workflow while the public site remains fast, accessible, and clear. That separation also keeps page titles, descriptions, canonical addresses, images, and publication dates attached to the work where readers and search engines need them.
The same public reading language now extends to the more immediate Field Notes, while each keeps its own character: Journal is composed and polished; Field Notes feel closer to the workbench.
The result
The machinery does its job, then gets out of the paragraph’s way.
The studio has one considered place to prepare and manage published work. Readers get stories that feel native to theProject. rather than a skin placed over a content system.