In my previous post, I discussed about the usability, mobile-friendliness, and Support for Multiple Languages and Internationalization In this post, I’ll be shedding light on cloud vs on-premise deployment, scalability, roles & permissions. Here you go.


For front-end performance, it should be able to use minified JavaScript and CSS, compacted images, and other static resources, in addition to being W3C compliant. Also, its structure should support Ajax caching, image caching, content expiry, and if required, a Content Delivery Network (CDN) for a heavily content-driven website.
Roles and permission management is an important feature, particularly, if your portal needs to be configured in a multi-site mode or if there are numerous users able to perform a variety of actions (e.g. in an internal self-serve employee portal.) Many CMS applications support configuration of various permissions into roles or permission groups, or both. You should look at how easy and robust the configuration is, and how the roles and permission framework can be tailored to your specific needs.
So, that’s it for now. I’ll be highlighting Analytics, Intelligence, & Marketing Optimization, Multi-site Support, Installation/ Migration/ Upgrades, and Documentation/User Support in my next post. Do share your thoughts on the factors one should consider while evaluating a CMS.