Found 184 results for "docs fields color"

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

Gitana / 4.0 / Data Engine / Content Models / Connectors

Connectors 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 / Data Engine / Content Models / Relator Properties

Relator 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.332876

Gitana / 4.0 / Forms / Fields / Color Field

Color Field The color field implements a color picker that runs on most modern browsers. It allows for the selection of hexadecimal color values using the browser's preferred color picker. Properties Title Color Description A color picker for selecting hexadecimal color values Field Type color Base Field Type text 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 autocomplet

Score: 9.263523

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

Gitana / 4.0 / Forms / CMS / Overview

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

Gitana / 3.2 / Guide / Guide / Forms / Fields

Fields Attachment Picker CK Editor File Picker Node Picker Related Content Slug

Score: 8.35971

Gitana / 4.0 / Forms / CMS / Fields

Fields Attachment Picker CK Editor File Picker Node Picker Related Content Slug

Score: 8.35971

Gitana / 4.0 / Forms / Fields / Color Picker Field

Color Picker Field The colorpicker field implements a color picker that runs on Bootstrap. It relies on the following library: https://mjolnic.com/bootstrap-colorpicker/ The colorpicker option can be used to feed configuration settings to the plugin. Properties Title Color Picker Description A color picker for selecting hexadecimal color values Field Type colorpicker Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when

Score: 8.236641

Gitana / 4.0 / Forms / Fields / Pick A Color Field

Pick A Color Field The pickacolor field implements a simple color picker that lets the end user choose from a selection of colors. It runs on Botostrap and relies on the following library: Uses: https://github.com/billyaraujo/pick-a-color The pickacolor option can be used to feed configuration settings to the plugin. Properties Title Pick-A-Color Description A color picker for selecting hexadecimal color values Field Type pickacolor Base Field Type text Schema Property Type Default Description

Score: 7.5839415

Gitana / 3.2 / Guide / Guide / Content Modeling / Connectors

Connectors 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 Fields

Custom 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 / UI Developers Guide / Contexts / documents-list-sort-fields

documents-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-fields

documents-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 / 3.2 / Guide / Guide / Content Modeling / Relator Properties

Relator 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: 5.5325055

Gitana / 4.0 / Forms / Fields / Overview

Fields Further Reading Address Field Any Field Array Field Checkbox Field Chooser Field CKEditor Field Color Field Color Picker Field Country Field Currency Field Date Field Date Time Field Editor Field Email Field File Field Grid Field Hidden Field Image Field Integer Field IPv4 Field JSON Field Lower Case Field Map Field Markdown Editor Field Number Field Object Field Option Tree Field Password Field Personal Name Field Phone Field Pick A Color Field Radio Field Search Field Select Field State

Score: 5.100239

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

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

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

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

Forms Cloud CMS provides a forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine so t

Score: 4.5969667

Gitana / 3.2 / Guide / Guide / Getting Started / Web Forms

Web Forms Cloud CMS provides an forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine

Score: 4.5608006

How to limit the fields that come back in a query

Query 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

Is there a programmatic way to add more content to workflows?

There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor

Score: 3.479019

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

Score: 3.4673607

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

Score: 3.4673607

Gitana / 4.0 / Forms / Fields / Text Field

Text Field The text field is used to represent text within a form. Properties Title Text Description Renders object items into a table row Field Type text Base Field Type control 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 k

Score: 3.2955089