9 reasons you should never use a CMS
- Security vulnerabilities in your chosen CMS become security vulnerabilities in your sites.
- Unless you have a water-tight contract, any harm caused by security vulnerabilities exposes you to litigation; when you install and use the CMS software, you (not the client) agree to a licensing agreement that specifically states that you accept all risk for using the software, you have no recourse to make any claim against the manufacturer, even if the problem was due to negligence on their part.
- All available online WYSIWYG editors have quirks and problems that result in: “What you see is almost what you get, but not quite!”
- For smaller sites that don’t need access to the full range of technologies provided by a CMS, the use of a CMS is overkill that often involves a steep learning curve for the client.
- CMS products inhibit your ability to create semantically structured source code.
- CMS products often make simple tasks more complex.
- All CMS products introduce bloat to your pages which can increase page load time and impede performance.
- Some CMS products are not SEO-friendly right out of the box, you may need to tweak the settings to make your pages crawl-able, and do you really want to leave SEO to a plugin?
- Self-management allows the client to alter your design, but still expect you to support their site (including their changes).
In conclusion, a CMS offers many advantages to designers, developers and content managers for rapid development and somewhat simple access to advanced features. But it is time that we stopped promoting it as a way for clients to manage their own sites, because in reality, you’re going to be doing the managing for them (for free). And honestly, how often do most clients need to update their website? Featured image, CMS image via Shutterstock.