CMS sites are all about security first, then design flow of the site itself with intuitiveness and ease of use. Let's face it - websites are no longer just pages written in notepad or an HTML wysiwyg. They are far more complex, with users creating accounts, sharing information, posting comments, shopping and providing payment information, sending and receiving email(s) to/from the site, sharing posts on their social network(s) and so on. The possible attack vectors that bad guys have on your customers AND their users, are exponential. So at the end of the day, before go-live, I highly recommend that web framework vulnerability scan assessments be run on any website. If holes are found, they must be plugged. If an SQL injection attack is possible because you have a poorly written Contact Us form - that could allow an attacker to simply paste in some T SQL code into the form and create an admin user account within your database.......is not a good idea to publish! Nessus scans are essential to find weak points in your website(s) and frankly, most sites today are full of issues most web developers have no idea about. Especially Wordpress sites - don't even get me started on Wordpress - the blog that tries and fails to be an enterprise grade CMS - never mind it's famousness for breaking it's developers extensions when they publish WP patches and fixes.
Search for a product comparison in Web Content Management
CTO and Co-Owner at a tech services company with 11-50 employees
Consultant
2017-10-19T23:29:09Z
Oct 19, 2017
For me, User Experience, intuitive interface and pretty and accurate layout is a must. The interface should be modern.
Security is a default option, which must always persist. Yet it shouldn't bother too much
For the content developer - it has to be no think use interface: point click create, edit/delete/publish/promote etc. From developer/management perspective it has to be secure.
As per the opinions of the PeerSpot community, Web Content Management systems must have strong security gateways and security token translation in place if they are to be evaluated. After security, other important features include powerful reports, website structure, number of pages the system can manage, and ease of use when operating the WCM, while integration with other systems was a minor factor also mentioned.
CMS sites are all about security first, then design flow of the site itself with intuitiveness and ease of use. Let's face it - websites are no longer just pages written in notepad or an HTML wysiwyg. They are far more complex, with users creating accounts, sharing information, posting comments, shopping and providing payment information, sending and receiving email(s) to/from the site, sharing posts on their social network(s) and so on. The possible attack vectors that bad guys have on your customers AND their users, are exponential. So at the end of the day, before go-live, I highly recommend that web framework vulnerability scan assessments be run on any website. If holes are found, they must be plugged. If an SQL injection attack is possible because you have a poorly written Contact Us form - that could allow an attacker to simply paste in some T SQL code into the form and create an admin user account within your database.......is not a good idea to publish! Nessus scans are essential to find weak points in your website(s) and frankly, most sites today are full of issues most web developers have no idea about. Especially Wordpress sites - don't even get me started on Wordpress - the blog that tries and fails to be an enterprise grade CMS - never mind it's famousness for breaking it's developers extensions when they publish WP patches and fixes.
User-friendliness is the most important issue and responsiveness Second is the factual contents. and ofcourse bundled security is extremely important.
number of pages & website structure
Easy integration with other applications
For me, User Experience, intuitive interface and pretty and accurate layout is a must. The interface should be modern.
Security is a default option, which must always persist. Yet it shouldn't bother too much
For the content developer - it has to be no think use interface: point click create, edit/delete/publish/promote etc. From developer/management perspective it has to be secure.
cross-channel publishing and mobility
Ability to manage and deploy complex web solutions while remaining secure and SEO friendly
Security and Powerful reports for both users and administrators.
Security and ease of use
Security
security