| 1. Multilingual – Can the CMS cater for any language both on the front and back end? |
|
| 2. Scalable architecture – Can the software be load balanced across multiple web servers? Is it cluster aware? Can it perform under pressure or does it fail whale? Ask for 3rd party test results. |
 |
| 3. Migration tools – Does it come with tools or methods for migrating tens of thousands of pages of content? |
 |
| 4. Web standards – Can it produce clean, semantic HTML and accessible content? |
 |
| 5. Documentation/support – Is it backed up with appropriate technical documentation and user guides? Is the product supported locally by a team of developers? |
 |
| 6. Installers – Does it have a simple 1 click installation, or is an army of engineers required to make it work? |
 |
| 7. Secure – Ask the vendor when the application had its last security review. Does it have formal accreditation? |
 |
| 8. Usability – Where does the user interface sit on the hierarchy of users’ needs? |
 |
| 9. Extensible – Does it have a mature API or SDK allowing it to be easily integrated or extended? |
 |
| 10. Search – Is a comprehensive search engine ‘baked in’ or will you need to buy an expensive 3rd party tool? From an external perspective is the CMS SEO friendly? |
 |
| 11. Metadata – Is the content underpinned by a robust metadata framework or is information management a manual task? |
 |