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: 82.50234

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: 63.15312

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: 27.366558

API / Features / Renditionable

Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration Property Type Default Read-Only Description schedule text Determines when renditions will be generated. Either synchronous or asynchronous. renditions object Defines the renditions that you

Score: 18.470858

API / Features / Rendition

Rendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration This feature does need configuration. Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }

Score: 11.940759

API / Features / Renditioned

Renditioned QName: f:renditioned Indicates that a f:renditionable node has been renditioned 1 or more times. Configuration This feature does need configuration. Renditioned Example { "title": "My Article", "_features": { "f:renditioned": { } } }

Score: 10.824823

API / Features / Behavior

Behavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration This feature does need configuration. Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }

Score: 7.87931

API / Workflow Handlers / Add Features

Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "", "config": { ... optional configuration for the feature } }] } The config is an optional parameter. You can use this handler to add one or more features

Score: 7.2375

API / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 6.8877435

API / Features / Behavior Binding

Behavior Binding QName: f:behavior-binding Marks an association as pointing to the implementation of a behavior for a policy on the source node. Valid target nodes include script nodes and rules. By applying this feature, you indicate that the target node script or rule should execute when the policy triggers. The target node (script or rule) must implement the f:behavior feature. For example, you might upload a JavaScript file that provides an implementation of a method to handle the afterNodeU

Score: 6.348682