Cloud Connected



"I have been searching for a product like Cloud CMS for over 10 years.

After false starts with some typical content management solutions, we were finally able to design the content repository that our business required."
James Baddiley
James Baddiley, CEO
ChilliSauce

Getting Started Videos for Cloud CMS

We are very proud of Cloud CMS and encourage you to see for yourself the potential of Cloud CMS (Free Trial).

To help you get the most out of the trial and knowledge of some of the features, we have recorded a number of ‘Getting Started’ videos showing some basic features, administration, and a ‘taster’ of some of the more interesting advanced features. (More videos to come for the advanced features).

The Getting Started videos:

  1. Create a Project
  2. Add Users to Projects
  3. Upload Content
  4. Add Comments to your Content
  5. Tag your Content
  6. Search for Content
  7. Print Documents

Content model and Forms, Export

  1. Define your own content Types
  2. Create Forms
  3. Export to CSV, PDF, or ZIP
  4. Export with PDF Templates

Administrative Functions

  1. Define your own Roles
  2. Configure an Email Provider
  3. Customize your Theme
  4. Administration Console

There are so many features in Cloud CMS that you may be interested in. We have made a start with these videos and we are planning to do more. Did you find these videos useful? If there is a specific feature or Use Case you would like to see please let us know Contact Us

Introducing Workflow

One of the main themes of Cloud CMS is the ability to help you automate the recurring actions that make up your team’s daily work. Giving you the flexibility to define how your teams collaborate – so that the organization of work is easy and fluid – is what Cloud CMS is all about.

A workflow is a blueprint that defines how your teams work together. It defines a series of steps and spells out who does what and in what order. It also describes a sequence of activities on top of your content, letting you specify the exact editorial flow for creation, approval and publication of your content.

Once you’ve defined your blueprints (or workflow models), you can launch them to control the lifecycle of your documents. Tasks automatically appear within inboxes for your business users, letting them inspect what needs to be worked on and when things are due. From an intuitive dashboard, they can learn about the task and dive down into the documents to get things done.

As tasks are worked on, a full audit-level capture is retained of every change to the workflow’s documents, properties, comments and data. This workflow history is fully searchable, letting your reconstruct the exact flow of a document’s approval, optimizing for bottlenecks and improving your process over time.

The Cloud CMS workflow feature now joins the vast library of powerful features that Cloud CMS offers. It brings the very best capabilities of enterprise class workflow to your business. It implements a powerful and streamlined facility that brings forward our company’s best learning from working with systems like jBPM, Day CQ5 and a variety of BPM engines.

To get started, take a look at the Cloud CMS workflow documentation. This gets down into the details of what workflow is and how it works.

If you’d like to give it a shot, simply sign up for a free Cloud CMS trial subscription or contact us for more information.

Assessing the CMS cost options?

The risks and costs associated with CMSs can be frightening. Many organizations have entered a CMS project, and are still to come out. Frustrated by the on-going costs of getting the CMS to work and then the costs of keeping it working. Partly this is due to unrealistic expectations but the primary reason is not looking at all the costs upfront and assessing the resources available to support a complex IT initiative.

A basic for assessing your immediate and ongoing costs for any application is where the application a lives and how will it be supported. If you have limited IT resources then you need to be careful where you use them. Ideally, the CMS should be a tool to facilitate you doing business and allow your resources to do what they do best.

Traditional On-Premise

Examples:

  1. Initial Purchase cost
  2. Annual maintenance/subscription
  3. Could be user/CPU/both cost model
  4. Support means product support (not the services to configure)
  5. Additional costs
    • Services
      • Installation
      • Configurations/customizations
      • Upgrades
      • Best practices and getting the most from your investment
    • Environments (Hardware, 3rd party software, Operating Systems, Network,..)
    • Resources (IT team)
    • Additional modules: be careful when getting quotes to ensure all the features you are looking for are included in the price. Deployment, clustering, Records Management, WCM, DM,.. are often priced separately like a ‘Chinese laundry’ list

Open Source

Examples:

There are various flavors of Open Source. Check the features in the Open Source release and the level of support available. Open source companies have a commercial model which you should understand.

Community release vs enterprise release: the Community release has had limited testing, no support from the vendor or partners, and can have limited features. Essentially it is good for proof of concept before purchasing the enterprise release, small companies that cannot afford the enterprise release, or for non-business critical applications. The Enterprise release usually has a (not insignificant) annual cost for maintenance/support which is usually the same model as above for the Traditional On-Premise products.

With Open Source it is not for the faint hearted. There are significant additional costs: cost of hosting the server yourself, hiring IT/devops or custom developers, maintaining it between releases, etc. For either enterprise or community, that’s very non-trivial.

SaaS – (Software as a Service)

Examples:

A SaaS type model can be very appealing to a business in that it allows resources to concentrate on their business.

SaaS CMS services can convert expensive capital outlay for servers and network equipment into a monthly operating expense, while also reducing the IT resources required to manage enterprise records. http://en.wikipedia.org/wiki/Enterprise_content_management

  • typically monthly fee (often annual commitment)
  • Pricing model can be stepped on parameters such as: users, memory, files size, bandwidth, projects, tenants

Cloud Content Management Systems

Examples:

This is an emerging category and is a subset of SaaS. From a high level the differences are: - Designed from the ground up to work in the cloud. So what I here you say! - Content API: the focus of this group is the value of content and presenting the content for developers to integrate in any website or app. - Cost: much cheaper than traditional SaaS CMS vendors

Managed Service

Examples:

This may appear like SaaS but there are be variations on where the software is installed (vendor/on-premise/cloud/SaaS) and levels of responsibility defined in the Service Level Agreement. Additional Services may be included to handle customizations which can include broader IT and support needs .

Summary of Options