JournalPRODUCTION BUILD

One engine, another face

After [giving Journal a room of its own](/2026/11/15/a-room-i-can-return-to/), I added a little homework: let us see if this publishing setup can also take care of my portfolio. We had talked about more than one site. That is easy enough while the second one is still an example in a document. A real site arrives with its own habits. My portfolio already has a structure, project descriptions, screenshots and a way of moving around. I did not want to turn all of that into a diary simply because Journal got here first. So we used the existing portfolio as the model. The material stays in Markdown, and its presentation gets its own place alongside Journal's. The generator is shared. A project showcase can have its sections and cards, while a journal keeps its calendar. Each gets to look like itself. There was a useful detail to preserve as well. The portfolio lets a visitor choose between reading section by section and scrolling through everything on one page, with a choice of colours and typography. Those controls came across too. Moving to another technical arrangement should not have to mean throwing away something I already liked. Locally, the sites now have separate working places. I can leave one open and work on the other, without continually changing which site the same folder represents. Small bit of order, but I expect to appreciate it when I return after a pause and have forgotten where I stopped. Which, as we established, is quite a normal part of this operation :-) The new portfolio has been generated and checked locally, including its navigation, pictures and a phone-sized view. That gives our multiple-site idea something more convincing than a promising diagram: a second, different site using the same engine. It does not replace [the existing public portfolio](https://novikorisnik.github.io/portfolio/) yet. That one stays where it is while I look at the new version and decide when it is ready to take over. No need to make moving house and opening the front door the same event. For now, Journal is live, Portfolio has a new working home, and Article Studio has stretched beyond the first example without requiring another publishing machine. Another face, same engine. That was the point.