Search Results

Non-Cyclic

Non-Cyclic QName: f:non-cyclic Marks an association as one that does not allow cyclical chains in the graph. Cloud CMS does not assume that cyclical chains are invalid. In fact, for modeling some content, they may be encouraged. This feature gives you a way to indicate that some associations should not support them. An example of a valid cyclic graph might be one where you have multiple friends - Joe, Diane and Pete. An association might be modeled called "is best friends with". In this g

Score: 15.622387

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,

Score: 14.6299515

Knowledge Sharing

Knowledge Sharing QName: f:knowledge-sharing Used to tag an association as to indicate that it "shares knowledge" between a source node and a target node. The source node is a node is a "knowledge space" and the target node is a "knowledge recipient". An association marked with f:sharing-knowledge will be considered to be an association that knowledge properties may propagate down when changes are made to a knowledge space node. By default, the a:child association which is used to mark relat

Score: 11.435528

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 assum

Score: 6.297695

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 fe

Score: 6.2631083

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 ele

Score: 5.8128886

Plugins

Plugins Cloud CMS plugins let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Plugins provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associat

Score: 5.686266

Multilingual

Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user

Score: 5.3518043

Statistics

Statistics Cloud CMS automatically collects and aggregates node statistics for you as you connect nodes together in the content graph. Nodes are entities and associations are used to connect them together through a series of relationships. As nodes are connected together, both the source and target node will have their statistics computed and updated so that you can quickly find out how many relationships a given node has to its neighbors. The basic mechanics behind node statistics are simila

Score: 5.2802353

Overview

Overview Cloud CMS offers the option to run development and production installations of its software on-premise or within a virtual private cloud. This option is available to subscription customers and can be utilized in both a development and production capacity. The actual installation and management of the various servic

Score: 4.7448235