A line before going live
Yesterday we put ghosts on a cover. Today they got a job.
After [bringing a video into Article Studio](/2026/11/14/a-player-and-a-scrapyard-hero/), we went back to a less colourful question: what happens to an article after I write it? It can wait, get published, move in calendar, perhaps disappear again. A folder with some text starts to have quite a life.
I also finally found a name for the site. Journal. Has that slightly French sound of a diary, while leaving room for reflection, experiments and whatever else arrives between project notes. Calendar gives it something of a diary. Looking back at what happened gives it something of a journal. I do not feel a great need to separate those too precisely.
Article Studio can stay the name of the room where I make it. Journal is what comes out.
We settled a clearer route from writing to publishing. Working branches are places where work can remain unfinished. Staging is for preview, main is production. And preview does not need another public address; we can look at the generated site locally. Quite enough for the way I work.
For articles, the calendar follows publication. If I write something today and approve it two days later, it belongs under that later date. A small correction keeps its place; a major update can deserve another appearance.
And here come the ghosts. Move a previously public article, leave a small marker at the old address. It carries the identity, so the generator can find where the article lives now. Old links keep working, even after several moves. If the article is withdrawn or deleted, the reader goes back to a useful calendar listing. Quite considerate ghosts, actually.
We reviewed the earlier articles too. All but one were approved, leaving us a real example to check: visible in preview, absent from the public build.
Then came the structural switch. I expected that Azure might want another visit, but all of this could be done from here. The same site address carried on with the new flow. No new round of proving that I am human. A pleasant omission.
Finally, we wrote down strict instructions for working with the data repository. How approval becomes publication, how an article can move without losing its history, and how unfinished work stays away from the public site. Enough procedure to help the next conversation remember what we agreed.
For this last article of the day, we decided to walk that route deliberately. First the local version on a working branch. When I say it is ready, staging, and another local look at the generated version. Only after the final confirmation does it go live.
We almost cleared the work queue. Good place to draw a line, leave a few things for another day, and let the product we built do some actual work for us. Even if that work is an article about building the product. Apparently the studios are still visiting each other :-)