Search Results

API / Content Models / Overview

Overview A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other nested elemen

Score: 111.908745

API / Content Models / Types

Types A content type defines a type of content that your content workers generally create, edit and publish. For example, an article or a press release might be considered to be a content type. The content type defines the schema, properties, behaviors and everything to do with a specific kind of content. You then set about creating instances of that content type. These are sometimes referred to as content instances. Instances are instantiations of a type. All content instances adhere to the spe

Score: 76.861534

API / Content Models / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 32.706768

API / Content Models / Definitions

Definitions A content definition is a JSON schema v4 document that informs Cloud CMS of a new content type. The JSON schema semantics spell out the exact properties that a content type should have, the types of every element (such as whether a property is a string or a number), constraints and other nested aspects of the content type. Cloud CMS lets you create adhoc content on the fly which means that you don't technically need definitions. You can just throw JSON content into Cloud CMS and ever

Score: 12.057385

How to unpublish content

Cloud CMS provides a range of options for making content available to your presentation tier. The most common scenarios are: 1) Use an attribute on your Type Quick and easy to implement. Just add an attribute to mark instances as published by defining within the type's JSON: “published”: {  "type": "boolean",  "title": "Published?”  } You can then filter out items where this value is False. 2) Create a Feature for consistency Of course, if you have several content Types, you'll want to avoid re

Score: 9.948184

API / Forms / References

References Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally

Score: 9.869191

How to get a content definition JSON from the Cloud CMS API?

There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname}!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname}!/branch/get_repositories_rep

Score: 9.856002

API / Content Models / Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu

Score: 9.733154

UI Developer Guide / Actions / Actions

Actions account change-password addon install-addon uninstall-addon applications delete_applications new_application archives delete-archives download-archive publish-archives unpublish-archives associations add-association delete-associations attachments add-attachment delete-attachments authorities grant-authority revoke-authority comments add-comment delete-comments conflict evaluate-conflict keep-conflicting-version keep-local-version view-conflict-in-api conflicts delete-conflicts evaluate-

Score: 9.681725

Introduction / How It Works / Content Modeling

Content Modeling You can put any kind of content into Cloud CMS. Things like desktop files (Word documents, PDF files, images, audio files and video) are no problem. However, the real power of Cloud CMS begins when you begin to model content type definitions and features to wrap around that content. A content type is a type of thing, such as an Article or a Press Release. You define content types in the same way that you might define a word in the dictionary. You give it a name and then you give

Score: 9.563284