Editorial magazine
Long-form features, generous serif type, big covers per project. Lean into the writer's voice — articles, not cards.
→The operator console is now live as the main page. This is the workshop for what comes next — a quiet space to sketch, revise, and decide what the site wants to become.
// directions on the table
Placeholders — meant to be debated, rejected, or expanded. Tell me which thread to pull on and we'll iterate from there.
Long-form features, generous serif type, big covers per project. Lean into the writer's voice — articles, not cards.
→The page itself is a demo. Working widgets from the apps embedded inline — live charts, draggable explorers, real data.
→Strip it down. One sentence, one link, one project at a time. The opposite of a console — fewer signals, sharper edits.
→// what i'm chewing on
Open questions for the next pass. We'll trade ideas here.
The operator console reads as technical, which is honest — but maybe leaves the human side underweight. The next pass might balance the system with a story.
What if the homepage answers a single question the visitor is already asking, and earns the rest of the page from there?
Should the apps page be a separate surface, with the homepage doing less work? Or should everything live on one long scroll?
— jb