Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume

Modules One of the features that make CloudCMS super configurable is the ability to implement Modules. Within a Module, you can Create custom fields Create custom templates Create custom actions Create custom pages Customize CloudCMS configurations More... Take a look at some sample modules in our SDK Create a Module Register a Module

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

UI Views Customized changes to the user interface configuration can be introduced through the use of UI Config documents. UI Config documents are JSON documents that contain one or more configuration blocks. The UI Config configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI Configs are scoped either to the platform or to the project. As such, you can use UI Config objects to customize

UI Templates On pages like "Content Types" and "Search", each list item has some detailed information displayed. You can customize the information you hope to appear via UI Templates. Create a UI Template Fill in the title and a unique key to create a new UI template. You can also write down some description for the template. Nodes with qname n:ui_template have two properties: key, which is a unique identifier of the template, and type, which is the type of targets the template is applied to. Cu

UI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store

Role-Based Editorial UI The Cloud CMS Editorial application is a responsive web site that runs on web browsers, iPad, iPhone and a myriad of other devices and form factors. It provides a place where users can work together and collaborate in meaningful ways based on the roles they have been given. As an example, when a Manager signs on to the Editorial environment, he or she will have access to many managerial functions, such as the ability to add or remove team members. Those options will appea

Create a Module Common files that each module should have: module.json (where you give the module a name) install.js uninstall.js As soon as you have these files, the rest is up to you depending on what you would like to customize in the module. Take a look at some sample modules in our SDK Actions Bindings Config Service Evaluators Plugins Templates

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

OEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm
docker-compose up And then open a browser to: http://localhost To acces

Create A New Content Model Once you have Content Model Builder enabled, you can create a new content model from there. Click button "Create Definition" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and you can find the new content model in the list. Click into it to make it more interesting with the Content Model Builder: As you can see in the above image, there are two tabs -- "UI" and "JSON". CloudCMS provides you with two ways to build a content type

What is the recommended Xmx value for running the API service? The 2GB setting on the On-Premise "quickstart" distribution is a default for development usage. In production, we recommend putting as much memory as you can. Essentially, the API should use as much memory as is allocated to the API docker container. We usually ask customers to consider an M class large instance type (something on the order of 7.5GB of RAM per API). The UI can use considerably less. For the UI, a 2GB allocation is fi

Health Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers

There are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and

Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None
- Draft
- Live
- Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview th

How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca

Command Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get

Enable Content Model Builder In addition to building content model with JSON, CloudCMS also provides a Content Model Builder where you can build it with UI. To enable it, go to Project Settings page by clicking "Manage Project" button on the top right corner: Scroll down to "Content Model Builder" and check to enable it. Then go back to the project, you should be able to see it in the left side navigation.

Kits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the

Extend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field