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

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 / Thumbnailable

Thumbnailable QName: f:thumbnailable Configures a node to automatically generate thumbnails for the node content or attachments. With this feature applied, one or more thumbnail images will be generated based on the node's JSON or attachment content. These thumbnails can be of various sizes and are automatically generated when the node's content is created, updated or deleted or its relevant attachment is updated. Thumbnail generation is always synchronous. Thumbnails are generated when the node

Score: 19.07138

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

API / Features / Translation

Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration Property Type Default Read-Only Description master-node-id text The node ID of the node that holds t

Score: 6.2384233

API / Features / Container

Container QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl

Score: 6.211789