Search Results


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 ele

Score: 9.937364


Association Type association Datastore Type repository Supports authorities, permissions, transfer Associations, on the other hand, do not bear permissions. They are considered structural elements that provide several meanings for the content in a branch: The "linked" relationships between nodes. These relationships can be broken by either party

Score: 6.858237

Oauth 2.0 tokens

Each response from Cloud CMS provides two tokens:  an access token and a refresh token.

The access token is the one that you need to attach to every API call. It gets passed through the Authorization header as "bearer <accessToken>" and  Cloud CMS uses this to identify who the authenticated user is (and thus, what resources they have access to and so forth).

By defa

Score: 6.1343427


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" },

Score: 4.943725


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 e

Score: 4.9214897


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 ge

Score: 4.8781667

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 yo

Score: 4.5800157

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 vari

Score: 4.5198283


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 t

Score: 4.4437747


Permissions Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on

Score: 4.254603