Found 243 results for "forms fields related-content"

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

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

Gitana / 4.0 / Forms / Overview

Forms TODO Getting Started To get started with Cloud CMS Forms, please check out the following:

Score: 19.235466

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

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

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

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

Gitana / 4.0 / Forms / API / Forms

Forms Alpaca lets you wrap a standard HTML form binding around your rendered fields to support both direct HTML submits and Ajax, behind-the-scenes submits. You can pass form configuration into the Alpaca engine to control the POST itself and also to bind buttons to the screen for the user to submit the form. If you're interested in multi-step forms, take a look at the section on wizards which describes how you can split fields across multiple pages in a form. You can then capture the data at th

Score: 10.057458

Gitana / 4.0 / Data Engine / Content Models / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 9.82238

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

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

Gitana / 3.2 / Guide / Guide / Forms / Fields

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

Score: 8.354175

Gitana / 4.0 / Forms / CMS / Fields

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

Score: 8.354175

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

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

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

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

Gitana / 3.2 / Guide / Guide / Content Modeling / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 4.1356444

Easy Forms with Cloud CMS

One of the many uses of Cloud CMS is as a storage and reporting mechanism for forms. If you’re looking to put a form up onto your web or mobile site, Cloud CMS serves as an excellent option for capturing and storing this information. Fundamentally, Cloud CMS provides the Alpaca forms engine. Alpaca is an open-source JavaScript library for jQuery. It makes it easy to design and insert forms into your sites. Cloud CMS built Alpaca and been working with the broader community to improve it and make

Score: 3.9303553

Gitana / 4.0 / Forms / API / Callbacks

Callbacks Alpaca provides several places where you can hook in callbacks. Events - events are raised when the user interacts with fields. You can register callbacks to handle these events, adjust field state or other operations. Observables - each field maintains an observable that you can subscribe to. Subscribing to an observable means that you're listening for changes to its value. You can also use observables to interrogate and find values of fields within namespaces. This lets you find valu

Score: 3.7566018

Content Entry Forms Example

Cloud CMS lets you easily design and deploy forms for your web applications and content contributors. In this blog entry, we’ll walk through how you can do this within the Cloud CMS user interface. In this example, we’ll create a form that allows editors to create City Guide information. Note: in the Cloud CMS Trial there is a City Guide Content definition which can be used as a starting point or as a reference for this example. Add a Definition The Content Definitions can be found in the Cloud

Score: 3.7443993

Gitana / 4.0 / Forms / API / Ordering

Ordering The default rendering engine that Alpaca utilizes will render your fields in the order that they are described within your schema. {% raw %} {% endraw %} Use the order option to specify rendering order The precise order of properties can be configured using the order option. {% raw %} {% endraw %} Use a Template to layout fields See Templates for more information on using custom templates to take full control over the layout of your forms.

Score: 3.7339597

Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Custom Form

Custom Form You may wish to introduce custom properties that flow along with your workflow. These properties are tracked as your workflow transitions from state to state. They may comprise things like due dates, notes, parameters for the workflow or anything else you'd like. You can use the form capability to define a form that lets users editing and modify these properties. Global Form The global form can be defined once and it will be used for all places within the workflow where a form can be

Score: 3.6888452

Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Custom Form

Custom Form You may wish to introduce custom properties that flow along with your workflow. These properties are tracked as your workflow transitions from state to state. They may comprise things like due dates, notes, parameters for the workflow or anything else you'd like. You can use the form capability to define a form that lets users editing and modify these properties. Global Form The global form can be defined once and it will be used for all places within the workflow where a form can be

Score: 3.6888452

Gitana / 4.0 / Forms / API / Overview

API Further Reading Callbacks Conditional Dependencies Connectors Cookbook Custom Fields Data Sources Dependencies Events Forms Functions Internationalization Layouts Lookups Observables Ordering Recursive References References Serialization Templates Usage Validation Views Wizards

Score: 3.6496391

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