The new website had to be flexible enough so content editors could easily adapt the website as plans change over time – but rigid enough to maintain a consistent look and feel.
On top of that, it also had to be easy to use so anyone (no matter technical know-how) could make updates to the website.
And lastly, it had to use similar technologies under the hood that the in-house dev team could pick up if necessary in the future.
Taking all of the above into consideration we opted for the following:
- A component-driven website
- NextJS (React which the in-house devs work with)
- Prismic (which is easy to use for editors/devs and is well-documented)
- Vercel (hosting which the team already used)
When it came to content load it became clear we hit the goal of ease of use and flexibility.
The content team picked up the CMS with very little guidance (besides a handful of Loom videos) and the flexibility of creating new pages driven by custom components was working – having had content go through several rounds of revisions.
Note: the designs shown in this case study are early concepts, but we opted for a look which is closer to their existing brand image as this was too big of a change.
- 20 custom components editors can use
- 58 component variations editors can use
