Found 240 results for "content features behavior"

The search executed in 0.001 seconds

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

Content Modeling

Content Modeling 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 neste

Score: 51.081444

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

Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 17.881084

Forms

Forms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des

Score: 17.86209

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

Content Modeling / 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: 15.977894

Workflow / 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 that

Score: 14.843782

Workflow / 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: 14.800901

Content Modeling / Definitions / Content Type Definition

Content Type Definition 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

Score: 13.707337

Getting Started / Content Modeling

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 features to wrap around that content. A content type is a type of thing, such as an Article or a Press Release. You define content types in the same way that you might define a word in the dictionary. You give it a name and then you give

Score: 13.638884

Bulk Import

Bulk Import Cloud CMS provides a bulk import tool that makes it easy to load content into Cloud CMS from a variety of external file formats and data sources. The bulk import tool ingests this data and writes it into a Cloud CMS branch within a single transaction so that you don't suffer from partial imports due to a failure along the way. The Cloud CMS bulk import tool is designed to help you migrate existing content into Cloud CMS. This may include desktop files or structured data from legacy c

Score: 13.258911

Forms / Fields / Related Content

Related Content ID: related-content The related-content field type renders a n upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil

Score: 12.904743

Content Modeling / Content Model Builder

Content Model Builder Create A New Content Type Extend Field Templates Edit An Existing Content Type Enable Content Model Builder

Score: 12.44066

Content Modeling / Behaviors

Behaviors 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, b

Score: 12.119963

Application Server / Tags / @content

@content Fetches a single content instance by node id or path and makes it available to the template. Parameters parameter required description id the ID of the node path the path of the node as specifies the name of the variable (by default - content) Response The response is a JSON object representing the node. The exact properties contained here will be dependent on the properties of your content. Examples Example #1: Retrieve by Node ID {@content id="922e6b9c9f4b7564bab"}

Score: 9.525058

Actions / Execute Script

Execute Script ID: executeScriptNode Executes a script attachment of a node. The configuration for this action is described using JSON Schema like this: { "scriptNodeId": "d904227f8628b15d4763" } Property Required Description scriptNodeId yes The node id of the script document scriptAttachmentId no The id of the attachment where the script locates methodName no The method name of the script args no The arguments for the method in the script

Score: 7.6278906

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 6.5697546

Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 6.54436

Application Server / Web Content Management

Web Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma

Score: 6.441784

Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview th

Score: 6.2808776

API / 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 similar t

Score: 6.1635065

Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": (24 * 60 * 60) * 1000, // 24 hours "p

Score: 6.1125116

Content Modeling / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 6.0978284

User Interface / 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 i

Score: 5.899201