A page may be temporary, but the content system usually isn’t.
We built b10cks because every project ended the same way: a developer defining structure, a writer looking for the right words, and a client with one last change, all working in tools that were never meant to meet.
So we put the structure, the editing, the languages, and the history in one workspace, kept the source open, and stopped counting seats. Most of what happens in b10cks is gloriously boring: open the page, change the words, check the diff, publish. That is exactly the point.
The interesting part is how much room a quiet tool gives a team.