Zego is a commercial motor insurance provider that powers opportunities for businesses to self-employed drivers and riders.

They approached us to help them better manage their content by migrating it to Sanity and rebuilding the website to leverage that.
Check out the live version here

The problem

The website content was either embedded directly in the code or stored in the backend.

It made every content change require developers' involvement, slowing down content management, and taking from developers time that could be used to develop features or fix bugs.

It also made it tricky to translate content and split test it.

The blog as a proof of concept

Zego's blog was edited from a custom admin page that used Draft.js for the frontend editor and stored the content in a database.

After importing and converting the content from the existing blog, we made it possible to write articles and live-preview their content.

Articles had text but also images and some custom blocks like Youtube videos or Zego Quick Esitmate forms.

We also made it possible to create tags and assign them to articles to categorize them.

Building landing pages from the CMS

The feedback from the blog editors was quite positive and motivated us to bring the same value to marketers when creating landing pages.

Together with designers, we divided landing pages into blocks, each having a specific content structure, a design, and variations.

Having this architecture working was possible thanks to the combination of Sanity's GROQ query language, TypeScript, and Next.js.

This empowered marketers quite a lot because it made it possible for them to create landing pages from the CMS by simply glueing together a few blocks and specifying their content.

Next challenges

Zego's content migration to Sanity is still a work in progress.

One interesting challenge we'll be solving soon is localization. Our modular architecture will make it possible to have different content and layouts based on language and country.

We also want to leverage Sanity's incredible flexibility to optimize the user experience for content translators. This could be done by implementing an adaptor to send content fields from Sanity to be translated in a service like Localize.js.

Another helpful feature to have is split testing content, which will make it possible to get feedback from real website visitors to determine what workflows or designs work best.
Got an idea?
Let's chat
Tell us more