Found 181 results for "docs fields markdown"

The search executed in 0.001841065 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.455013

Gitana / 3.2 / Guide / Guide / Templates

Templates Cloud CMS supports the usage of templates at various points to generate presentation and output for things like emails, PDFs, web page components and more. Cloud CMS supports two template engines - Handlebars and Freemarker. In general, we recommend using Handlebars since the syntax is a bit easier. This document covers Handlebars and describes helper functions available in Handlebars that make processing simpler. Model Variables The following describes the internal structure of model

Score: 12.362404

Gitana / 4.0 / Data Engine / Templates / Overview

Templates Cloud CMS supports the usage of templates at various points to generate presentation and output for things like emails, PDFs, web page components and more. Cloud CMS supports two template engines - Handlebars and Freemarker. In general, we recommend using Handlebars since the syntax is a bit easier. This document covers Handlebars and describes helper functions available in Handlebars that make processing simpler. Model Variables The following describes the internal structure of model

Score: 12.362404

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.35951

Gitana / 4.0 / Forms / Fields / Markdown Editor Field

Markdown Editor Field The markdown field. The Markdown Editor field renders the SimpleMDE Markdown editor control that allows users to visually work with Markdown. Properties Title Markdown Description Provides an instance of a Markdown Editor control for use in editing HTML Field Type markdown Base Field Type textarea 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 autoco

Score: 9.511036

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.625388

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.625388

Gitana / 3.2 / Guide / Guide / Forms / Fields

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

Score: 8.390276

Gitana / 4.0 / Forms / CMS / Fields

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

Score: 8.390276

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.5293703

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.17248

Precompile your Text fields with Markdown or Handlebars

One of the new features in Cloud CMS 3.2.41 is the f:precompile feature. This feature tells Cloud CMS to automatically precompile one or more fields on your content items whenever the content is saved. With precompiling in place, you can now let your editors work in Markdown or use Handlebars tags in their content and then have that content automatically convert into HTML (or another output format) for use in your front-end applications. An Example Suppose, for example, that you defined an artcl

Score: 5.8464656

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.5827837

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.5827837

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.564824

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-field-templates

project-field-templates [ { "evaluator": "context-project", "config": { "project-field-templates": { "templates": [ { "key": "text", "title": "Text", "type": "string/text", "description": "Text value. e.g. title, name, header", "icon": "fa fa-align-left" }, { "key": "number", "title": "Number", "type": "number/number", "description": "N

Score: 5.231701

Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-field-templates

project-field-templates [ { "evaluator": "context-project", "config": { "project-field-templates": { "templates": [ { "key": "text", "title": "Text", "type": "string/text", "description": "Text value. e.g. title, name, header", "icon": "fa fa-align-left" }, { "key": "number", "title": "Number", "type": "number/number", "description": "N

Score: 5.231701

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

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

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.4846106

Gitana / 3.2 / Guide / Guide / Features / Precompile

Precompile QName: f:precompile Marks a node as having zero or more text properties that contain markdown or templated text that should be compiled (or transformed) when the document is saved. This transformation should occur when the source property is modified and the result should be stored on a new property that will store the compiled text. Suppose you have a property on a node called text. It is a Markdown field where your editors make changes to text stored in the markdown format. When the

Score: 4.429906

Gitana / 4.0 / Data Engine / Aspects / Precompile

Precompile QName: f:precompile Marks a node as having zero or more text properties that contain markdown or templated text that should be compiled (or transformed) when the document is saved. This transformation should occur when the source property is modified and the result should be stored on a new property that will store the compiled text. Suppose you have a property on a node called text. It is a Markdown field where your editors make changes to text stored in the markdown format. When the

Score: 4.429906

Gitana / 3.2 / Guide / Guide / Actions / Send a Slack Message

Send a Slack Message ID: slackMessage Sends a Slack Message to a configured channel. For information on how to connect Slack and Cloud CMS, see Slack Integration. Configuration Property Type Required Default Description url text true The webhook URL provided by slack that will send messages to the configured channel. message text false Markdown message template of message that will be sent when action is fired. Required if template node is not provided. message text false Markdown message templa

Score: 3.6090195

Gitana / 4.0 / Data Engine / Behaviors / Actions / Send a Slack Message

Send a Slack Message ID: slackMessage Sends a Slack Message to a configured channel. For information on how to connect Slack and Cloud CMS, see Slack Integration. Configuration Property Type Required Default Description url text true The webhook URL provided by slack that will send messages to the configured channel. message text false Markdown message template of message that will be sent when action is fired. Required if template node is not provided. message text false Markdown message templa

Score: 3.6090195

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.3650582