When our creative website team takes over a website from a new client, it usually comes with a Content Management System (CMS). The CMS could be a locked-down theme, plug-in, or predetermined layout fields. Sometimes we inherit a custom CMS developed from scratch using platforms like Strapi or Drupal. Usually, utilizing a new CMS is pretty easy, especially if it’s familiar and flexible. However, overly restrictive, custom-built systems can cripple any attempt to make meaningful changes to improve the site’s user experience or its search or AI rankings.
When you’re thinking of developing a CMS, there is a list of pros and cons.
Using a restrictive CMS does:
- Minimize the risk of your site breaking or being hacked thanks to locked-down admin settings.
- Create a lightweight structure that can help the site’s speed and performance.
- Keep pages uniform in structure and brand.
However, there are some problems with a restrictive CMS:
- One developer-built CMS may use shortcuts or user decisions that don’t make sense to a different digital marketing team.
- A locked-down back end makes optimizations to admin settings and layouts difficult.
- Content and SEO improvements are delayed because the CMS has strict modules with few to no workarounds.
- Custom-made or little-known CMS platforms require training to use them effectively.
- A “headless CMS” is usually more developer-heavy and may need costly development to modernize.
It is super important to take a step back and think about how well the backend’s functionality will work with the new design, content, and SEO needs over the long term. Overall, the backend needs to be user-friendly for you and your digital marketing team. An open CMS that provides structure but allows for improvisation lets all of us work seamlessly together to constantly improve your site. A locked-down, custom-built CMS forces us to use workarounds that slow down both creativity and effectiveness.
When A Custom CMS Becomes A Custom Pain
Let’s take a look at a WordPress CMS that uses the ACF Pro plugin. ACF Pro can be difficult to work with because it's partially integrated with the site’s backend PHP. In this instance, the child theme is locked away through admin settings, which is understandable given how easily one can break a page or site with one misplaced character or space. However, any changes outside the prescribed fields are seemingly impossible.
It’s understandable why the initial developer created the site with a locked-down CMS. The client can add their own content while keeping the site's style and integrity intact. After all, they aren’t web designers and have better things to do. ACF Pro can be fairly well organized and works at a basic functional level. And, you cut out much of the bloat that page builders add, so your site loads faster. (We at Flint Analytics are big fans of super-fast loading times.)
However, in this case, we were trying to elevate the design by adding custom charts optimized for mobile viewing. Having to stick with a custom-made ACF Pro build from an independent developer made upgrading to a new layout tough.
Working Around the Oppression of A Custom CMS
We didn’t want to constantly bug the old developer to build out the site’s module, since that would take time and money the clients might not have. We also didn’t want to dig into the PHP code. That can be a huge learning curve, especially if you didn’t initially develop the site. These tools can be heavily integrated with the page’s template, and modules available on one template may not be available on another.
We really had three options:
- A. Keep the cruddy fields we had that made the site a confusing user nightmare
- B. Delve into development and risk breaking the site
- C. Find a workaround
We chose option C.
There are several ways to work around this if you have the time and resources. We chose the easiest route by using plain old HTML module editor boxes that were initially built with the ACF Pro plugin, and then adding some CSS code through the theme’s additional CSS feature. It took a bit of trial and error to get everything aligned and find what fields would work with the custom code, but in the end, we ended up with a more dynamic page and a big jump in performance.
Pro-tip: Use unique classes for your HTML/CSS for custom-made web elements so that they won’t clash with the current child theme’s settings.
Is A Custom CMS Worth the Hassle?
Having to stick with a custom-made ACF Pro build from an independent developer doesn’t seem ideal for future design and content. We have been seeing a strong trend of companies leaning heavily toward using a custom CMS implemented by an independent developer, only to find their creativity stifled later on.
Unless you have a specific reason to keep content consistent, like case studies or employee profiles, a native page builder is much more appreciated. A tool like Gutenberg blocks within WordPress gives you much more flexibility to grow. Or go with a page builder with a dynamic CMS (bonus if it can integrate with an AI assistant). In any case, if a developer proposes a restrictive CMS “to make things easier,” just know that you're in for future frustration.
Need Help With Your Own Restrictive CMS?
If you’re in the same boat with ACF Pro along with a WordPress platform, then you’re in luck. Flint Analytics & Marketing can help you tackle your website one step at a time. We’ll ensure your site is a seamless user experience and scale your business down the line. Just contact us today and we can discuss your next project.
