Found 75 results for "application-server tags form"

The search executed in 0.0 seconds

Application Server / Tags

Tags @associations @block @content @debug @dependency @expand @form @fragment @include @iter @layout @link @nodeAttachmentValue @params @processTemplate @query @queryOne @relatives @resource @search @value

Score: 28.340546

Application Server

Application 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: 21.39948

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

Application Server / Tags / @form

@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no override the

Score: 17.641705

Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu

Score: 16.997833

User Interface / Tags

Tags Cloud CMS lets you manage your tag hierarchy and assign those tags to your content. Content that is tagged is automatically marked with the tag information (within the tags property) and will also maintain an a:has_tag association in the content graph that points back to the tag instance. Tags are first class citizens within Cloud CMS. They are content like everything else. Once content is tagged, you will see it reflected in the user interface as such. You will be able to navigate your con

Score: 16.967438

Application Server / Services / Server Tags

Server Tags Model Variables The framework keeps track of specific model variables which are accessible within your templates: user - information about the current user page - information about the current page selected - information about the currently selected content item session - information about the current user application session history - information about the navigation history request - information about the request Here is an example template that displays the user's click path histo

Score: 13.480344

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 7.7658763

Forms / Fields / Related Content

Related Content ID: related-content The related-content field type renders a n upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil

Score: 6.09534

Content Modeling / Content Model Builder

Content Model Builder Create A New Content Model Extend Field Templates Edit An Existing Content Model Enable Content Model Builder

Score: 5.9773736

User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 5.916028

Modules / Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. For a list of these actions, see Actions on the lower left-hand menu. account change-password addon install-addon uninstall-addon applications delete_applications new_appl

Score: 5.694498

Features / Taggable

Taggable QName: f:taggable Indicates that a node should support tagging. Nodes that support tagging maintain a:has_tag associations to n:tag nodes that serve as master tag entries. A single tag entry may have multiple associations linking it to nodes that bear its tag. In addition, taggable nodes maintain a tags array which contains a local array of all of the tags that the node has been assigned. In this way, tags can be traversed using graph-based lookup or they can be queried directly based o

Score: 5.439283

Application Server / Services / Duster

Duster The Duster Service provides template rendering using the LinkedIn Dust.js template engine. The Duster Service loads output templates for you, executes Dust across them and outputs markup like HTML and JSON. It allows you to build full web sites or custom APIs using a powerful template engine. Tags The Cloud CMS Application Server provides a library of * Dust Tags available out of the box. These are listed in more detail on the left-hand side menu. Fragment Caching Some Dust tags support c

Score: 5.3931437

Definitions for Date format

Our definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with th

Score: 4.9626665

Application Server / Web Content Management

Web Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma

Score: 4.875306

Application Server / Services

Services Authentication Awareness Broadcast Cache Config Driver Config Duster Flow Insight Local Notifications Overview Performance Server Tags Virtual Driver Virtual Hosts Web Content Management Welcome

Score: 4.50369

Features / Behavior

Behavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration This feature does need configuration. Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }

Score: 4.437206

Forms / References

References Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally

Score: 4.278667

User Interface

User Interface Cloud CMS provides a full user interface that your editorial team and managers use to create, manage and deliver content to the business, mobile applications and web sites. The user interface is secure, role-based and customizable, allowing your development team to cater the editorial experience to the exact needs of end users. Dashboard Create/Edit Content Embed Media In CKEditor Favorites Multilingual Image Editor Locking Menu Projects Releases Search Security Tags UI Templates

Score: 4.164923

Forms / Fields / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latt

Score: 4.084023

Forms / Fields / Node Picker

Node Picker ID: node-picker The node-picker field type renders a modal picker for a node. The modal picker allows you to filter nodes as well as paginate, sort and inspect nodes. The picker supports single node and multi-node selection depending on how the field is configured. Sample configuration: { "type": "node-picker" } The node picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latter is used for selection

Score: 4.084023

Application Server / Tags / @fragment

@fragment Used to identify a section of output that can be cached based on the presently known request-time dependencies or any dependencies resolved by nested elements or nested @dependency tags. Parameters There are no parameters for this tag. Examples Example #1: Restaurant List Here is a template block that lists restaurants: {@fragment} {@query sort="title" skip="2" limit="7" type="custom:restaurant"}

{#rows}

Score: 4.028608
{_doc}

How does Cloud CMS work with a CDN

There are a few places where this either occurs automatically if you're using our hosted service or can occur optionally if you're either running within Docker containers on your own or integrating to custom CDN endpoints. First, the API itself can be fronted by a CDN that supports fallback lookup to an origin server. In this case, we recommend Amazon CloudFront with short-lived TTLs on cache headers. More specifically, you can use Amazon's API Gateway to get caching coverage across multiple geo

Score: 4.028608

WCM and Caching

In Dust, there is the notion of a context which has a stack running underneath it. As you drill down into tags, a new context is pushed that can write new context variables as well as access previous variables from previous stack frames. What we're doing in cloudcms-server is providing a dependency tracker so that each tag gets to declare the output (the HTML that was generated) and the set of dependencies that it depended on in order to generate the output. As an example, a query might run an u

Score: 4.028608