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
* Showing search results for tag: content management

Views based on Role in Cloud CMS Trial

We appreciate your interest in Cloud CMS and know your time is valueable. Therefore we have been improving the Cloud CMS Trial to help make it easier for you find the features you are trying to demonstrate.

1. Views based on Role

Different users have different requirements of a CMS and how they need to interact with the CMS. For example, a Web Editor needs to be easily search and edit content, whereas, a developer needs to be able administer and configure the CMS for the users and also to interface with the outside world. We have set up some typical users in the Trial to help you visualize how Cloud CMS could work for you and your users.

  1. Wendy: Web Editor. Work with content entry forms to create, edit and release content to your live web sites and mobile applications. Instant Preview lets you see how your changes would look on the live web site. Scheduled Publishing lets you lock in future release dates for your changes.

image

  1. Dave: Document Manager. Work with desktop files, upload, categorized and tag documents for full-text search and retrieval. Wire up business rules to automatically fire off web hooks, send emails and much more as documents move between folders or update in their lifecycle.

image

  1. Bernard: Developer. Write code to connect your web sites and mobile apps to the Cloud CMS API to query, search and traverse the content graph. Design content models and forms to let your editorial team easily work with well-structured data.

image

2. Sample Project

We have combined the Sample projects and automatically installed them in the Trial. This saves some steps and also gives you a sample web project, deployed sample site, and an example books Document management project.

3. Releases

Releases are a powerful feature in Cloud CMS. They give your content team the ability to use Scheduled Publishing. Releases build on top of the underlying Branching capabilities of Cloud CMS. They utilize branches under the hood while providing easy-to-navigate workspaces, activity tracking and scheduled publishing. Releases are often used to produce a final content production for release at a future date, often to a web site, mobile applications, catalog or external data store. An example release is is setup for Wendy the Editor to explore:

image

4. API

We’ve prepared some easy-to-run examples. Bernard the Developer can now easily downlaod them:

image

Good luck with your CMS evaluation

I hope this article encourages you to start a trial. If you have a question, or cannot find a feature you are looking for, or have a suggestion - please Contact Us.

The top 3 features that differentiate Cloud CMS from the competition

You have determined you need a Content Management System (CMS) and have begun the daunting task of reducing the number of CMS products to a manageable number to evaluate in depth.

Having reached this article you are aware of, or interested in, CMSs that can be described as: Headless CMS, API First, Platform as a Service (PaaS), Decoupled CMS, Cloud-First. I am sure there are more beautiful categorizations and terminology provided by the latest analyst buzz. As much as I may not like the catagorizations, they are useful in that without them what would you search for?

But as you will have discovered, there are a number of CMS products catagorized as Headless CMS, or API First, etc. Cloud CMS is just one of many products you will find with a simple search. How to evaluate further: features, cost, trial, openness of information? It is still difficult to compare products.

At Cloud CMS we believe we have the best product as I am sure all our competitors believe in their products. To an extent we are all telling the truth and it really depends what criteria or features are important to you.

Top 3 Features that differentiate Cloud CMS

To help you evaluate further: here are the top 3 features of Cloud CMS that differentiates Cloud CMS from the competition:

1. Cloud CMS is available both On-Premise and SaaS

We are a Cloud based company embracing the SaaS model. We love the SaaS model. What has changed - in a word “Docker”. Docker containers have allowed us to distribute the Cloud CMS product easily for On-Premise/Private Cloud installation. Whilst SaaS may offer many benefits, On-Premise is still a desirable option for some companies for the following reasons:

  • Regional restrictions: ie the content must reside in a particular region. This may be legal or a business restriction.
  • Internal Security. Some organization have security restrictions/policies that either don’t allow applications/content to be hosted externally or the getting through the security procedures make it quicker and easier to go for on-premise options
  • Control: A benefit of SaaS is that updates and bug fixes occur ‘continuously’. Usually the whole process is transparent to the customer. For some organizations and application the constant change is not acceptable. A change could introduce a change of behavior in the application which could adversely affect users. Hence, on-premise can stabilize a release and allow the customer to control the release cycle for their users.
  • White label / customization
  • MicroService: With your own on-premise installation you can scale and fine tune the Cloud CMS components. Not least, reducing network latency by hosting close to your applications and users.

2. Cloud CMS is a headless CMS with powerful ECM features

Some of the basic functions of creating and managing content that you rightfully expect to be in Content management systems are surprisingly not always there – check! Our background is in Enterprise content management systems so we have designed Cloud CMS to include these features for all our offerings:

  1. Workflow
  2. Versioning and audit
  3. Branches / Workspaces
  4. Content model
  5. Roles / groups / teams
  6. And many more (honestly – take a look)

3. Architecture

This is the CMS your architects would build if they had the time and resources (and were in the CMS business). Cloud CMS runs on top of MongoDB, ElasticSearch and Amazon AWS.

Good luck with your CMS evaluation

I hope this article has saved you some time. Either you have found out early that you are looking for a different type of CMS, e.g., a page builder CMS, and Cloud CMS is not for you. Or, this has helped encourage your interest in Cloud CMS and you would like to find out more - please Contact Us to ask a question, request a demo or call, or start a trial.

Return On Investment (ROI) with Cloud CMS

ROI and Content Management Systems (CMS) are rarely used in the same sentence due to the uncomfortable pricing models from all legacy CMS vendors - as well as the spiraling costs of implementing them. Often so much investment has been made in the CMS that changing is not a realistic consideration.

This negativity only increases when you start using the term Enterprise Content Management (ECM), where suddenly vendors start seeing dollar signs, but offer no additional functionality e.g., Alfresco, Documentum, Adobe CQ5, and many more. Rather, creative “Per User” or “Per CPU” pricing makes selling to the Enterprise very attractive to vendors.

At Cloud CMS we strive to provide exceptional value with a CMS which will meet your current and future needs. The benefits of the Cloud CMS approach can be realized in many ways but occasionally you need to have a “SHOW ME THE MONEY!” conversation.

Some potential ways to realize your ROI with Cloud CMS:

Freedom

We adhere to an API First, or “headless” approach to content management. This means all content and CMS functionality is available via our 1,300+ APIs. Every UI, including our packaged console, uses these APIs. Create and manage content thru our console, and call the APIs to access any content on your frontend applications. This provides greater freedom rather than being limited to a CMS vendor’s templating options.

Future Proofing

  1. Reuse: Through the separation of the CMS and the presentation layer you can create amazing websites and application with the frontend technology of your choice. Whenever you need to refresh or redesign the presentation layer, the CMS and content can be reused in-place. Minimizing the changes and maximizing reuse is huge benefit to any project from the technical, marketing, and business perspectives.
  2. Multi-channel/Device: three possibilities for cost savings:
    1. One CMS, creating content which can be deployed anywhere as needed
    2. What are your future device and application requirements? What devices are coming up in the next 6 months+? The frontend costs are maybe unknown but you can limit the risk and costs by using a CMS that provide the Content via APIs. No change to the CMS
    3. Reduce Time To Market: having the content available in a Headless CMS allows for an organisation to respond to changes and the requirements for new devices and channels.

Software as a Service

  1. 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
  2. Scalable: Cloud CMS scales seamlessly to meet your needs. Again, no upfront costs.
  3. Always on latest version: Cloud CMS continues to grow with new and enhanced features, performance, bug resolution. No need to wait and plan large upgrade projects.

Feature rich

Cloud CMS is a lot more than a well architected repository and API. Jeff Potts summarized this nicely in his blog Content-as-a-Service Review: Cloud CMS: “..Cloud CMS is an extensible platform with a long list of features. This is more than just a place to stick content and an API to get it back out–this is a full-featured CMS that happens to be running as SaaS in the cloud. ..”

Flexibility - Fits with your infrastructure

  1. Application development and delivery teams at publishing organizations, media companies, and branded manufacturers already use API First CMS tools alongside multiple other sets of API-first micro-services to build out new digital products.
  2. Flexible Deployment Options (https://www.cloudcms.com/developers.html ): whether SaaS or On-Premise, direct API, custom Application server, or using our NodeJS module.


At Cloud CMS we have a straight forward honest approach. We care about what we do and how we do it. We are essentially engineers that want to create the “right” solutions and see our customers get value from their CMS. Needless to say we are proud of what we deliver.

If you have any questions or comments please email info@cloudcms.com