01 / Challenge
Let the client manage content in multiple languages and assemble pages within the supplied design.
Multilingual website with a page builder
A multilingual website editors can build from predefined sections.
Architecture · CMS · Technical leadership
Freedom for editors. A consistent system.
Page document
Hero banner
Projects list
Configurable sections
02 / Decision
Configurable Sanity sections map to React components in Next.js.
03 / Outcome
Editors control page content and composition. The team shares an architecture.
A page builder from predefined sections
Sanity document
Page content and ordered sections
Section type
A matching React component
Next.js page
Consistent design and behaviour
Editors choose sections, change their order, and edit their content. Components keep the interface consistent.
Connected languages. Independent content.
Language version A
Page address · content · sections
Translation links
Select content · build navigation
Language version B
Page address · content · sections
Language versions were stored as separate Sanity documents with links between translations. Each version could have its own content and page address.
Those links were used to select content and build the language switcher. Every language was available through a URL prefix; English also worked without a prefix.
Ready for the client to manage.
The client received a multilingual website with CMS controls for both page content and composition. The team had a shared architecture for developing and adding sections. My main contribution was the application architecture and content model, multilingual support, deployment, and technical leadership.
I was responsible for application architecture, Sanity configuration, multilingual support, and deployment. The other developer and I shared the work on sections and components roughly equally.
Get in touch
Have a project, a technical challenge, or a collaboration in mind? Send me a message.