The Headless CMS I want

One of the first projects in our newly founded Becomes studio back in 2019. was to create a simple & fun password-strength web application — a playful and catchy UI with many subtle animations.

As users enter their password, the web app would respond with a funny message, something along the lines of: "Meh, everybody can guess that," or "Okay, this is getting serious, "... all based on the client-side password strength calculation. Basically, an array of message [string] + corresponding password strength [number, from 0 to 100] objects. The client wanted an interface where they could add as many messages as needed.

Of course, this turned into a long discussion about problems with WordPress and how robust and unnecessary it was for such a small and simple project. There's no doubt that WordPress is a powerful tool that has served countless web developers and managers over the years. Decades. Still, we get an anxiety attacks whenever we need to use it.

The following points boiled down to my objections:

Complexity: We find WP overwhelming and challenging to learn. Users, especially new ones, could benefit from a better UX.

Security: We don't want WP, or any WP plugin developer, to track my end users or cause website downtime or bad UX.

Customization: Basically, you can't do anything from scratch without being proficient in PHP. And even then, developers usually install a bunch of plugins and then heavily rely on them and their functionality.

Speed: WordPress + a WP theme + usual plugins weigh a lot, making websites load slow by default. Sure, you can install plugins (more plugins) for caching, but they make websites smaller nor solve issues with websites that change often.

These problems seem pretty fixable, don't they? We were totally ready to use another tool for our client's project. Headless CMS sounded like a way to go.

The article has been originally posted here: https://thebcms.com/blog/headless-cms-we-want