Team stacks
VeeberMedia
A one-person studio in Germany running several sites at once. The stack is picked so that nobody has to be waited on: no CMS to maintain, content typed into the codebase, and an assistant wired into the jobs that would otherwise need a second pair of hands.
VeeberMediaThe studio site, running on the stack below.What does VeeberMedia run on?
6 layers, one row each: the job on the left, what handles it here on the right. One row is empty on purpose, which is as much of an answer as the rest.
Where the pages live
Every page is a file in one codebase. Nothing is arranged in a builder, so an assistant adds a page the same way a developer does.
Where content lives
No CMS, on purpose. Content is typed into the codebase, so the listing pages, the search index and the sitemap all read from one object and cannot drift apart.
Hosting and deploys
Every push builds and gets its own URL, so a change is checked on the real page instead of a screenshot, and a bad deploy goes back in one click.
Code and review
One repository per site, and the history is the record of what changed. It is also the first thing the assistant reads before it touches anything.
Numbers
Page views without a cookie banner. Enough to see which pages earn their place, and nothing that needs a consent flow in front of it.
The assistant
Wired into the repo with a written brief, so the jobs that would otherwise need a second pair of hands - a new page, a migration, a pre-launch check - run against the real files.
Who does this stack work for?
Works while one person owns everything end to end. The moment somebody else needs to change a headline without opening a pull request, this stack needs a CMS bolted onto it, which is the trade the content entries in the stack section cover.