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

Build your prototype website in 10 easy steps

Getting started with Cloud CMS for a website takes minimal setup:

  1. Fork a copy of https://github.com/gitana/sdk
    1. Note the URL of your repo; you’ll need this later…

  2. Login to your tenant or signup for a trial of Cloud CMS
  3. When prompted upon login
    1. create a Web Content Management starter project

  4. From the resulting Project Dashboard
    1. navigate to “Applications” in the Manage Project section of the left nav toolbar
    2. you’ll need to scroll down a bit to spot it

  5. Select “Sample Web Application” > Deployments
    1. Tick the radio button on the right
    2. Navigate to Selected > Undeploy (upper right)

  6. Select “Source”
    1. Set “URL of Repository” to your forked version (from Step #1)
    2. Keep Base Path set to /sample-website
    3. “Update” to save new settings

  7. Select “Deployments” again
    1. Tick the radio button on the right
    2. Navigate to Selected > Deploy (upper right)

  8. Click on one of the URLs listed to view your site
  9. Choose either the Product Catalog or City Guide sample

  10. Review, reverse engineer, and otherwise hack away at the
    1. Type Definitions and instances; add you own items
      1. Using the left nav toolbar
      2. Select Content > Content Products > Create Content (for example)

    2. Dust templates, under /sample-website/public/templates
      1. Easily implemented with our query helper
      2. Done with standard DustJS syntax

It’s a great end-to-end reference site, showing all key components of Cloud CMS in action.  For other framework examples or questions, just give us a shout!

image

Finding sanity by losing your head

There was a lot of chatter last year regarding a “headless” or “decoupled” CMS design.  Zeitgeist, maybe… countermovement, definitely.

Since their inception, every expansion of content management software along the continuum from managing basic websites to full-on digital experiences drove CMSes further and further into the application’s presentation tier.

In parallel, we witnessed the maturity of frameworks such as Angular, Ember, and Ionic (just to name a few) - all pushing development out to the browser tier itself, and each one clashing with the template-driven approach ordained by any underlying CMS.

As a result, it’s become fashionable to lose one’s head.

Monolithic CMS vendors are now re-engineering their approach.  Varying levels of RESTful calls are surfacing to placate the JavaScript hungry masses.  Naturally, this journey carries risks - enough that companies keen to succeed are exploring alternatives.

And finding that an API-first solution makes for a more natural fit.

By definition, API-first is headless.  Nothing needs to be “decoupled”, but rather a pure CMS service is made available that blends naturally with your selected framework, whether for a:

  • Static site
  • JS Application
  • Single-page app
  • Mobile app

or a combination of the above.  Need proof, easy.  Just review our SDK packages, or better yet - sign up for a Free Trial.

Comparison: Cloud CMS vs Prismic

Not sure which CMS is a better fit? Review these points to help guide your selection.

Criteria

Cloud CMS

Prismic

Ease of Use

Implements a role-based UI to accommodate various functions.

Complex user interface for defining content types and instances.
Item creation must occur here.
See API Access.

Update Strategy

Documents are published individually, or as part of larger change sets.

Documents are published individually, or as part of larger change sets.

Workflow Process

Flexible workflow capability.

Allows teams and roles to be created along with a workflow designer for defining content production process and constraints.

Limited workflow, provides a writer and publisher role but incomplete support for content production process.

API Access

Fully bidirectional, “API first” design

Read-only, “API first” design.
NO WRITE capability.

Deployment Options

SaaS and / or On-Premise

(Docker images)

SaaS only

Security for Assets

Allows assets to be delivered via either CDN or Web API – with full security available.

Allows assets to be delivered via either CDN or Web API.

Pricing Factors

Based solely on your desired SLA

Pre-defined tiers with a fixed number of

  • Users
  • Features (roles, workflow)
  • API uptime