Found 63 results for "content-models paths"
The search executed in 0.00103857 seconds. That's fast.
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: 19.325823
|
|
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: 12.042327
|
|
How do I retrieve the folder path for my content?In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C
Score: 2.9735641
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / definition-subcontextdefinition-subcontext [ { "evaluator": "context-definition", "condition": true, "config": { "definition-subcontext": { "items": [ { "key": "definition", "title": "Definition", "header": true, "order": 1000, "items": [ { "key": "definition/overview", "title": "Overview", "uri": "{definitionUri}", "order": 1000
Score: 2.750282
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / definition-subcontextdefinition-subcontext [ { "evaluator": "context-definition", "condition": true, "config": { "definition-subcontext": { "items": [ { "key": "definition", "title": "Definition", "header": true, "order": 1000, "items": [ { "key": "definition/overview", "title": "Overview", "uri": "{definitionUri}", "order": 1000
Score: 2.750282
|
|
Gitana / 3.2 / Guide / Guide / Features / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 2.4621184
|
|
Gitana / 4.0 / Data Engine / Aspects / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 2.4621184
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Services / PerformancePerformance { "perf": { "enabled": true, "paths": [{ "regex": "/proxy/repositories/.*", "cache": { "seconds": 60 (or 0 for no cache and -1 for 1 year) } }] } }
Score: 2.4386282
|
|
Gitana / 4.0 / Developers / Application Server / Services / PerformancePerformance { "perf": { "enabled": true, "paths": [{ "regex": "/proxy/repositories/.*", "cache": { "seconds": 60 (or 0 for no cache and -1 for 1 year) } }] } }
Score: 2.4386282
|
|
Gitana / 3.2 / Guide / Guide / Docker / Security NoticesSecurity Notices Please review the following notices for information on mitigating known vulnerabilities and our recommended upgrade paths: CVE-2021-44228 CVE-2022-22965
Score: 2.4239206
|
|
Gitana / 3.2 / Guide / Guide / Actions / Web HookWeb Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca
Score: 2.2676325
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Web HookWeb Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca
Score: 2.2676325
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 2.2166986
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 2.2166986
|
|
Gitana / 3.2 / Guide / Guide / TreeTree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl
Score: 2.1792793
|
|
Gitana / 4.0 / Data Engine / Discovery / TreeTree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl
Score: 2.1792793
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 2.1456914
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 2.1456914
|
|
Gitana / 3.2 / Guide / Guide / Features / AWS TranscodeAWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf
Score: 2.051306
|
|
Gitana / 4.0 / Data Engine / Aspects / AWS TranscodeAWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf
Score: 2.051306
|
|
Upgrade to version 1.0.6 of our new JavaScript/HTML5 driver!The Cloud CMS team is pleased to announce the immediate availability of the 1.0.6 version of the Gitana JavaScript Driver for Cloud CMS. JavaScript Driver for Cloud CMS The Gitana JavaScript Driver is a JS library that you can drop into your HTML5/JS applications to take advantage of the authoring and delivery APIs of the Cloud CMS server. It makes it easier for developers to utilize the Cloud CMS HTTP/REST APIs by providing native convenience functions via JavaScript. The Gitana JavaScript Driv
Score: 2.051306
|
|
Gitana / 3.2 / Guide / Guide / Publishing / Preview ServersPreview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up
Score: 1.9708332
|
|
Gitana / 4.0 / Data Engine / Publishing / Preview ServersPreview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up
Score: 1.9708332
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Copy Node
Copy Node Type: copyNode This handler copies nodes that are part of a workflow's payload to a target folder. The target folder can be identified either by a node ID or a node path. The config for this handler is as follows: {
"targetNodeId": "
Score: 1.9575709
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Copy Node
Copy Node Type: copyNode This handler copies nodes that are part of a workflow's payload to a target folder. The target folder can be identified either by a node ID or a node path. The config for this handler is as follows: {
"targetNodeId": "
Score: 1.9575709
|