Search Results

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

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

API / Behaviors / Overview

Overview Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, be

Score: 61.440388

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

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

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

API / Behaviors / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: Association Policies function beforeAssociate(association)

Score: 13.953048

API / Features / Watermarkable

Watermarkable Cloud CMS lets you configure your content so that watermarks are automatically applied when content is created and updated. This lets you systematize the watermarking of your images to ensure consistency across your project. You can maintain a single watermark or multiple watermarks and divide up how they are applied on both a per-content instance and per-content type basis. To start, you simply upload a watermark image to Cloud CMS. Typically, watermark images are image/jpeg or im

Score: 9.731043

Content Model - Association example

Question. Suppose that I have the following collection types: Customers Orders and I want to store the Customer ID and the Customer Name on each Order… If the customer then updates his Name, how is it possible (if at all) to update the customer’s name on all of his orders - in a single atomic transaction? Answer. For this situation, you would have two content types - Customer and Order. One good way to address this is to utilize an association between the two. You could declare an association ty

Score: 9.365007

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