Found 282 results for "content-models definitions features"

The search executed in 0.001490978 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / 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: 20.26184

Gitana / 4.0 / Data Engine / Content Models / Overview

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

Gitana / 3.2 / Guide / Guide / 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: 17.807524

Gitana / 4.0 / Data Engine / Content Models / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 15.938095

Gitana / 4.0 / Data Engine / Content Models / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 12.058735

Gitana / 4.0 / Data Engine / Aspects / Overview

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

Gitana / 4.0 / Developers / Cookbooks / Content Modeling Cookbook

Content Modeling Cookbook Getting Started To get started with Content Modeling, please visit the Content Modeling Page. Code Samples Here are some code samples of common data structures to help you get started. Array of strings An array of strings. Definition: "prop1": { "type": "array", "items": { "type": "string" } } Form: "prop1": { "type": "array", "items": { "type": "text" } } An Object An object with two properties. Definition: "articleAvailability

Score: 10.750577

Gitana / 3.2 / Guide / Guide / Content Modeling / 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. Definitions come in several flavors, the main ones being: Content Type Definitions Association Definitions Feature Definitions Cloud CMS lets you create adhoc cont

Score: 10.438773

Gitana / 4.0 / Data Engine / 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. Definitions come in several flavors, the main ones being: Content Type Definitions Association Definitions Feature Definitions Cloud CMS lets you create adhoc cont

Score: 10.438773

Gitana / 3.2 / Guide / Guide / 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 tha

Score: 6.633106

Gitana / 4.0 / Data Engine / 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 tha

Score: 6.633106

Gitana / 3.2 / Guide / Guide / 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: 6.6221547

Gitana / 4.0 / Data Engine / 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: 6.6221547

Gitana / 3.2 / Guide / Guide / Content Modeling / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 6.155213

Gitana / 3.2 / Guide / Guide / Content Modeling / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 5.870116

Gitana / 3.2 / Guide / Guide / 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: 4.6121373

Gitana / 4.0 / Data Engine / Content Models / 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: 4.6121373

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-features-list-item-actions

content-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i

Score: 4.4094663

Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-features-list-item-actions

content-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i

Score: 4.4094663

Gitana / 3.2 / Guide / Guide / 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: 4.016572

Gitana / 4.0 / Data Engine / Content Models / 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: 4.016572

Gitana / 3.2 / Guide / Guide / Cookbooks / Content Modeling Cookbook

Content Modeling Cookbook Getting Started To get started with Content Modeling, please visit the Content Modeling Page. Code Samples Here are some code samples of common data structures to help you get started. Array of strings An array of strings. Definition: "prop1": { "type": "array", "items": { "type": "string" } } Form: "prop1": { "type": "array", "items": { "type": "text" } } An Object An object with two properties. Definition: "articleAvailability

Score: 3.6125107

Gitana / 3.2 / Guide / Guide / 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: 3.402021

Gitana / 4.0 / Getting Started / Working with Content / Overview

Working with Content 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

Score: 3.402021

Alpaca 1.0.3 Released!

We’re pleased to announce the release of Alpaca Web Forms 1.0.3 for jQuery, jQuery UI and jQuery Mobile. Alpaca is an open-source project that provides an easy way to render web forms using JSON schema. It consists of a jQuery plugin and provides a nice abstraction so that you can change form layouts, validation logic and presentation with simple changes to JSON. Alpaca provides the web forms capabilities for Cloud CMS - The Cloud Content Management Platform for the Enterprise. This release incl

Score: 3.163083