Your studio
The design and the build: the theme repo, which modules a site gets, when a new version goes out and when the site launches.
How it works
From kickoff to live,
and every day after.
and every day after.
A new client site is a row in the admin, a theme repo and the modules it needs. Here is the whole path, from the first form to the site running on its own, and who takes care of what once it does.
Step by step
Seven steps, none of them a server.
No hosting to order, no CMS to install, no plugins to pick. The work that is left is the work that is actually yours: the design, the content and the moment you go live.
01
Add the site
One form in the admin: a name, the domain and the languages the site speaks. It starts behind a coming-soon page for everyone not on your list, and hidden from search engines, so nothing half-built gets read or indexed while you work on it.
02
Connect its theme
Point the site at its own theme repo: Twig templates and a Tailwind source file, no bundler. Push a git tag and that version turns up on the site's Theme tab. Deploy it, look at it, activate it. Earlier versions stay on disk, so going back is one click.
03
Switch on what it needs
Blog, shop, FAQ, newsletter, bol.com: each module is one toggle per site. A module that depends on another stays off until that one is on too, and a module that is off ships nothing at all.
04
Fill it in
Pages, menus and media live per site. Text is typed on the page itself, and a side panel lists every editable slot with a filled or empty dot, so nothing is forgotten. The SEO fields sit in a drawer next to the copy, and a second language is a tab on the same page.
05
Hand it over
Add the client's people to their own site and nothing else. An editor works in every module the site has on, from pages to orders; settings, payment providers and users stay with an admin. Everyone signs in with a passkey.
06
Go live
When the client signs off, switch off the coming-soon page and the search-engine block. That is the launch. Every other hostname of the site redirects to the canonical one, so links to the old address keep working.
07
Keep it running
Back the site up and restore it on its own. Form submissions are logged, with held spam waiting in a review queue. Statistics are first-party and visible to editors. A design change is a new tag, deployed when the client is ready.
Who does what
Three parties, no overlap.
Your client
The words, the photos, the products and the orders, edited on the page they see, without a ticket to you.
CEEMS
Hosting, upgrades, security patches, backups and the modules themselves. The platform moves forward centrally, for every site at once.
Walk through it on your own sites.
Send us two of your existing sites. We mirror them into a sandbox tenant and you go through these steps yourself in half an hour.