Giddy About Content Management
If there’s one thing Oliver Russell takes seriously, it’s content. Take a look at our website and you’ll start to get an idea of the time we dedicate to insights, changemakers and case studies. In fact it’s somewhat of a company policy—everyone writes.
Our content mantra is so engrained in Oliver Russell culture that when we decided to redesign our site, the focus was less about a visual redesign and more about redesigning how we publish articles and interact with the site.
Oliver Russell’s previous website used a proprietary CMS that served us well, but lacked the functionality for content creators to efficiently design blog and case study pages. Instead, this task was left to the art directors. This means that once an article was ready to publish, the writer gave it to a designer to enter content and lay the page out.
What’s more, we didn’t have access to the raw site files. If we wanted to add a new CTA or create a new font style, we had to ask the software company to add the HTML, CSS, etc. Over time, this became costly and time consuming.
After discussing our somewhat ineffective publishing process, we identified two vital requirements (as well as a few ancillary ones):
get our newsletter.
Although we thought the first requirement listed above would be challenging, it turned out to be incredibly easy. Rather than view the website from a page and template perspective, we broke it down into components, i.e., full screen video, four-column images, single column text, etc. We then combined these individual components to form pages and templates. This allowed us to reuse components over and over, which helped minimize development and design time. All we had to do was ensure the components played nicely with each other and voilà! A blueprint for page building was born.
With the front-end built, we moved on to the CMS. Most content management systems (WordPress, Expression Engine for example) closely match content fields with sections on the page, i.e., Field A populates Slot B, and so on. Which makes perfect sense—they’re content management systems, not page management systems. But we needed something more. We required a CMS that could manage content and page layouts. And we knew Craft could make it happen.
By using Craft with a components-based approach, we were able to remove the designers from the publishing process and reduce the time it takes to go from draft to published content.
Craft also, by the way, helped us meet all of the secondary requirements on our list. Since Craft comes with so much flexibility and a wide variety of field types right out of the box, we had minimal need for extra plugins. Typically, the only plugin we use is for SEO.
Another bonus is what Craft assumes about front-end structure, which is nothing—nada, zilch, oogatz. You could create your entire website using tables and tables within tables, and Craft wouldn’t judge you. We might, but Craft wouldn’t. This approach also means it’s incredibly easy to add a front-end framework like Bootstrap or Foundation to a site.
Inserting data and entries into the front-end of our site is handled through the very capable Twig engine, which makes tasks like applying text filters, performing math functions and merging arrays incredibly easy.
Coming away from this project, it’s clear that our writers love this publishing platform, designers like the creative control, and we are all very happy with the way the whole project came together.
Get our newsletter.
Do yourself a favor and be a CMS contrarian.
When we set out to redesign our website we wanted to create a beautiful yet simple site that offers insight into our company, showcases our work, and offers helpful, thought-provoking content.
Why we built a new site to double down on our commitment to build brands for purpose-driven companies.