Found 242 results for "docs fields tag"
The search executed in 0.001858582 seconds. That's fast.
|
Gitana / 4.0 / Data Engine / Content Models / ConnectorsConnectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf
Score: 16.418236
|
|
|
Gitana / 4.0 / Developers / Application Server / TagsTags @associations @block @content @debug @dependency @expand @form @fragment @include @iter @layout @link @nodeAttachmentValue @params @processTemplate @query @queryOne @relatives @resource @search @value
Score: 15.6237335
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Relator PropertiesRelator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth
Score: 12.80818
|
|
|
Gitana / 3.2 / Guide / Guide / Application ServerApplication Server The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack.
Score: 11.170207
|
|
|
Gitana / 4.0 / Developers / Application Server / OverviewApplication Server The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack.
Score: 11.170207
|
|
|
Gitana / 3.2 / Guide / Guide / FormsForms 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: 8.595948
|
|
|
Gitana / 4.0 / Forms / CMS / OverviewForms 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: 8.595948
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.35971
|
|
|
Gitana / 4.0 / Forms / CMS / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.35971
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / tag-subcontexttag-subcontext [ { "evaluator": "context-tag", "condition": true, "config": { "tag-subcontext": { "items": [ { "key": "tag", "title": "Tag", "header": true, "order": 1000, "items": [ { "key": "tag/overview", "title": "Overview", "uri": "#/projects/{projectId}/tags/{tag}", "order": 1000 }, {
Score: 7.795558
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / tag-subcontexttag-subcontext [ { "evaluator": "context-tag", "condition": true, "config": { "tag-subcontext": { "items": [ { "key": "tag", "title": "Tag", "header": true, "order": 1000, "items": [ { "key": "tag/overview", "title": "Overview", "uri": "#/projects/{projectId}/tags/{tag}", "order": 1000 }, {
Score: 7.795558
|
|
|
Gitana / 4.0 / Forms / Fields / Tag FieldTag Field The tag field. Properties Title Tag Description Renders object items into a table row Field Type tag Base Field Type lowercase Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attributes that will
Score: 7.5525494
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ConnectorsConnectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf
Score: 7.4938693
|
|
|
Gitana / 4.0 / Forms / API / Custom FieldsCustom Fields Alpaca has a pretty inclusive field library that you can use straight away. Fields are simply referenced by their type within your Alpaca forms configuration. If you don't provide specific field types to use, Alpaca guesses at sensible defaults for you. You can also create your own fields. Alpaca fields are object-oriented (essentially) so that you can extend existing fields, override methods and modify behaviors. The result is less work and a complete extensibility layer so that y
Score: 7.1403875
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / TagsTags @associations @block @content @debug @dependency @expand @form @fragment @include @iter @layout @link @nodeAttachmentValue @params @processTemplate @query @queryOne @relatives @resource @search @value
Score: 6.365355
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-document-is-tagcontext-document-is-tag If a Document is currently being observed and is a tag. { "evaluator": "context-document-is-tag" }
Score: 6.173868
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-document-is-tagcontext-document-is-tag If a Document is currently being observed and is a tag. { "evaluator": "context-document-is-tag" }
Score: 6.173868
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Relator PropertiesRelator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth
Score: 6.007809
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fieldsdocuments-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },
Score: 5.552904
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fieldsdocuments-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },
Score: 5.552904
|
|
How to get a content definition JSON from the Cloud CMS API?There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep
Score: 5.089512
|
|
|
How to limit the fields that come back in a queryQuery API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the
Score: 4.5479317
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / Fields / CK EditorCK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config
Score: 4.294487
|
|
|
Gitana / 4.0 / Forms / CMS / Fields / CK EditorCK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config
Score: 4.294487
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Embed Media In CKEditor / Advanced Usages / Extra AttributesExtra Attributes In addition to common attributes like width, height and id, you might need extra attributes for your embedded media HTML tag. For example, you probably hope to have attributes like title and creator: CloudCMS allows you to add extra attributes that best suit your need with some simple configurations. Add JSON Configurations for Extra Attributes Navigate to Manage Project --> Editors --> Embedded Media Editor. Check Enable Additional Attributes and two JSON editors will pop up. W
Score: 4.1099367
|