Ecodia
Studio
The platform where clients edit the sites we build for them, with no developer in the loop.
The challenge
A custom site is only useful if its owner can change it. The usual options hand the client a content system they did not ask for: WordPress and a stack of plugins, or a headless CMS that needs a developer every time a headline changes. The site should not go stale the week we hand it over.
What we built
Studio is where Ecodia's site clients edit the sites we built them: visual editing on the real page, a blog, a newsletter, and their subscriber list, all in one place. Sign-in is one Ecodia identity shared across Studio and every other Ecodia surface, so there is no separate account to manage. The owner edits a headline and the public site updates.
Impact, counted
No WordPress
Studio removes the usual overhead: no plugin stack to maintain, no second login, no developer between an owner and their front page. The site stays current because the owner can change it.
A custom site is only useful if its owner can change it.
How we worked
Studio was built so the site and the editor are the same object, not a separate page and dashboard. Editing happens against the live page, so what the owner sees is what goes live.
What it adds up to
A consulting client runs their live site day to day through Studio as a standing arrangement, with no developer touch for routine edits.
Client sites we build, a rainforest education centre, a conservation foundation, and a coastal marketplace, connect to Studio so the owner edits their own content.
One Ecodia sign-in spans Studio and the rest of the Ecodia surface, so there is one identity to hold, not one per tool.
An Ecodia product.
Further reading