Found 239 results for "features rendition"
The search executed in 0.00159849 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / FeaturesFeatures 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.420202
|
|||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures 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.407394
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / RenditionRendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }
Score: 11.145675
|
|||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / RenditionRendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }
Score: 11.145675
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / Content ModelingContent 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: 9.1756115
|
|||||||||||||||
Gitana / 4.0 / Data Engine / Content Models / OverviewContent 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: 9.1756115
|
|||||||||||||||
Gitana / 4.0 / Data Engine / Content Models / Default PathsDefault 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: 7.9725256
|
|||||||||||||||
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": "
Score: 6.6370525
|
|||||||||||||||
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": "
Score: 6.6370525
|
|||||||||||||||
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": "
Score: 6.6260347
|
|||||||||||||||
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": "
Score: 6.6260347
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-features-list-item-actionscontent-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.4122853
|
|||||||||||||||
Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-features-list-item-actionscontent-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.4122853
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Renditionable
Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration
| |||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / Renditionable
Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration
| |||||||||||||||
Gitana / 3.2 / Guide / Guide / Actions / Invalidate Page RenditionsInvalidate Page Renditions ID: invalidatePageRenditions This action invalidates page renditions in one or more applications. You can target a single page rendition or a broad set of page renditions using a custom query. { "title": "Invalidate Page Renditions", "properties": { "applicationDeployments": { "title": "Application Deployments", "type": "array", "items": { "type": "object", "properties": {
Score: 3.6711705
|
|||||||||||||||
Gitana / 4.0 / Data Engine / Behaviors / Actions / Invalidate Page RenditionsInvalidate Page Renditions ID: invalidatePageRenditions This action invalidates page renditions in one or more applications. You can target a single page rendition or a broad set of page renditions using a custom query. { "title": "Invalidate Page Renditions", "properties": { "applicationDeployments": { "title": "Application Deployments", "type": "array", "items": { "type": "object", "properties": {
Score: 3.6711705
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / Content Modeling / Default PathsDefault 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: 3.523994
|
|||||||||||||||
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @fragment@fragment Used to identify a section of output that can be cached based on the presently known request-time dependencies or any dependencies resolved by nested elements or nested @dependency tags. Parameters There are no parameters for this tag. Examples Example #1: Restaurant List Here is a template block that lists restaurants: {@fragment} {@query sort="title" skip="2" limit="7" type="custom:restaurant"}
|