Structure, templates and content model — not a reskin of the old site.
Editable
The studio publishes new work itself, without a developer in the loop.
Maintained
Hosting, updates and new sections handled by the same team that built it.
01 — The brief
A portfolio that outgrew its own website
ATÖLYE works across strategy, design, architecture and community — projects that don't fit one shape. The old site described the company; the new one had to carry the work, and keep carrying it as the work changes.
01One content model that fits a strategy project and a building alike
02Case studies the team can publish without engineering support
03Fast pages with heavy imagery, on unreliable connections too
04A front door for recruitment as much as for clients
02 — The work
Templates built from the work, not around it
We started from a shelf of real projects and derived the smallest set of templates that could hold all of them.
Every page is assembled from a small library of blocks. A new case study, a new service, a new job post — all published from the CMS by the team, with no deployment and no ticket. Where an editor could break the layout, the block simply doesn't allow it.
Next.jsHeadless CMSEdge hosting
Before
A new case study meant a developer, a branch and a release.
After
It means an afternoon in the CMS, and publish.
04 — The relationship
The same client trusted us with a marketing site and, separately, with an internal AI platform.
See ATÖLYE Intelligence
05 — How it ran
Define to Operate, with the same team throughout
01DefineAudit of the existing site, then a content model derived from real projects.
02DesignA block library reviewed against the hardest projects, not the easiest.
03BuildFront end and CMS integration, with performance budgets set up front.
04LaunchContent migration, editorial training and handover documentation.
05OperateHosting, maintenance and new sections as the studio's work grows.
