There is no shortage of commercial, free and open source content management systems. They come with a variety of capabilities, approaches to content and different technology requirements. What always appears to be the case though is that they are quite intrusive and dictate how the rest of the solution needs to behave to work with the CMS. Often they demand their own setup, interface and separate hosting considerations to work.

Most enterprise solutions require different types of content to be managed, including typical editorial web content where many standalone CMS would suffice. However, some content is likely to be unique to the enterprise and might be driven by internal ERP systems (like a product catalogue with SKUs, stock levels, RRPs, replenishable status etc). This is core business information which is directly linked to customer orders or KPIs for management reporting, and shouldn't be imported or managed by a system that doesn't acknowledge the source of the content. Most CMS can be customised to achieve this, but the effort and cost is often prohibitive (and sometimes the additional functionality is overlooked or ignored because the team doesn't know how). Even after this integration exercise the business is left with a separate CMS system to manage the content that doesn't necessarily integrate with the rest of the management console or solution.

SPIKA CMS is a capable CMS solution that integrates with our Management Console – a single login to one system. Our security policy controls whether the logged-in user has access to CMS functionality, reporting or customer care. The benefits are an intuitive, coherent interface with all tools accessible based on granted access rights.

SPIKA CMS drives the content on several high-profile sites across the world. Some of the key facts or features are listed below:

• Content publishing and workflow management
  • Pushes published content to preview or live hosting environments. Performance is not affected by the CMS
  • Content can be forced to be previewed before being published
  • Different roles can be set up for content producers, editors and publishers
• Versioning and traceability
  • All content updates are tracked, with who did what and when
  • Old versions are archived
  • Republish an old version if required
• WYSIWYG editor
• Automatic image resizing
  • Image content can be configured to be automatically resized in to any number of sizes. This is typically useful when some content has a few different representations through different channels or on different pages on the site. E.g. small, medium and large thumbnails