Search Results

API - API - Features - Behavior

QName: f:behavior...

API - API - Features - Behavior Binding

QName: f:behavior-binding...

API - API - Behaviors - Scripts

Scripts are content nodes with a default attachment of type application/javascript. ...

API - API - Behaviors - Rules

Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch....

API - API - Behaviors - 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 conte...

API - API - Models - 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 ...

API - API - Features - 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 singl...

API - API - Features - Multilingual

QName: f:multilingual...

API - API - Features - Indexable

QName: f:indexable...

API - API - Content Models - 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 ...

API - API - Features - Container

QName: f:container...

API - API - Features - Extractable

QName: f:extractable...

API - API - Features - Locked

QName: f:locked...

API - API - Features - Filename

QName: f:filename...

API - API - Features - Geolocation

QName: f:geolocation...

API - API - Features - Audit

QName: f:audit...

API - API - Features - Renditionable

QName: f:renditionable...

API - API - Features - Renditioned

QName: f:renditioned...

API - API - Features - Rates

QName: f:rates...

API - API - Features - Related

QName: f:related...

API - API - Features - Taggable

QName: f:taggable...

API - API - Features - Previewable

QName: f:previewable...

API - API - Features - Thumbnailable

QName: f:thumbnailable...

API - API - Features - Titled

QName: f:titled...

API - API - Features - Translation

QName: f:translation...

API - API - Features - Relator

QName: f:relator...

API - API - Features - Rendition

QName: f:rendition...

API - API - Features - Knowledge Sharing

QName: f:knowledge-sharing...

API - API - Features - Knowledge Space

QName: f:knowledge-space...

API - API - Features - Knowledge Recipient

QName: f:knowledge-recipient...

API - API - Features - Dublin Core

QName: f:dublincore...

API - API - Features - Propagates Authorities

QName: f:propagates-authorities...

API - API - Features - Property Mapping

QName: f:property-mapping...

API - API - Features - Stats Sum Counter

QName: f:stats-sum-counter...

API - API - Workflow Handlers - Add Features

Type: addFeatures...

API - API - Workflow Handlers - Remove Features

Type: removeFeatures...

API - API - Actions - Remove Feature

ID: removeFeature...

API - API - Actions - Add Feature

ID: addFeature...

API - API - Features - Non-Cyclic

QName: f:non-cyclic...

User Interface - UI Guide - Content - 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_transla...

Mapping properties across types

Q. Suppose that I have the following collection types:...

API - API - Models - 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, ...

API - API - Content Models - 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, ...

API - API - Content Services - 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 connect...

API - API - Content Models - 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 s...

API - API - Models - 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 s...

General - Introduction - How It Works - 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 fe...

Attachments in your content model

Fundamentally, everything in Cloud CMS is JSON. JSON is simply scalar properties (text, numbers, etc). There isn't a way to represent binary data in pure JSON apart from getting into some very awkward encodings. So we don't go that route....

API - API - Integrations - Amazon SQS


...

Evolving your JSON schema

Cloud CMS is provided in one of two ways - either as a public cloud service or as an on-premise installation (using Docker images). The former absolutely prohibits any database access. The only way you can work with content is through our APIs....