Found 226 results for "application-server tags content"

The search executed in 0.0 seconds

Content Modeling

Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste

Score: 29.241663

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

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

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

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

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

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

Bulk Import

Bulk Import Cloud CMS provides a bulk import tool that makes it easy to load content into Cloud CMS from a variety of external file formats and data sources. The bulk import tool ingests this data and writes it into a Cloud CMS branch within a single transaction so that you don't suffer from partial imports due to a failure along the way. The Cloud CMS bulk import tool is designed to help you migrate existing content into Cloud CMS. This may include desktop files or structured data from legacy c

Score: 12.891153

Content Modeling / Definitions / Content Type Definition

Content Type Definition A content type defines a type of content that your content workers generally create, edit and publish. For example, an article or a press release might be considered to be a content type. The content type defines the schema, properties, behaviors and everything to do with a specific kind of content. You then set about creating instances of that content type. These are sometimes referred to as content instances. Instances are instantiations of a type. All content instances

Score: 12.415418

Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 12.026591

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

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

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

Application Server / Tags / @content

@content Fetches a single content instance by node id or path and makes it available to the template. Parameters parameter required description id the ID of the node path the path of the node as specifies the name of the variable (by default - content) Response The response is a JSON object representing the node. The exact properties contained here will be dependent on the properties of your content. Examples Example #1: Retrieve by Node ID {@content id="922e6b9c9f4b7564bab"}

Score: 9.2587595

Getting Started / Content Modeling

Content Modeling You can put any kind of content into Cloud CMS. Things like desktop files (Word documents, PDF files, images, audio files and video) are no problem. However, the real power of Cloud CMS begins when you begin to model content type definitions and features to wrap around that content. A content type is a type of thing, such as an Article or a Press Release. You define content types in the same way that you might define a word in the dictionary. You give it a name and then you give

Score: 7.4670925

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

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

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

Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": undefined, "pageCacheRetryTimeout": u

Score: 5.9343195

Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 5.6984277

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

Content Modeling / Content Model Builder / Enable Content Model Builder

Enable Content Model Builder In addition to building content model with JSON, CloudCMS also provides a Content Model Builder where you can build it with UI. To enable it, go to Project Settings page by clicking "Manage Project" button on the top right corner: Scroll down to "Content Model Builder" and check to enable it. Then go back to the project, you should be able to see it in the left side navigation.

Score: 5.5250983

Content Modeling / Content Model Builder / Create A New Content Model

Create A New Content Model Once you have Content Model Builder enabled, you can create a new content model from there. Click button "Create Definition" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and you can find the new content model in the list. Click into it to make it more interesting with the Content Model Builder: As you can see in the above image, there are two tabs -- "UI" and "JSON". CloudCMS provides you with two ways to build a content type

Score: 5.5118265

Content Modeling / Content Model Builder / Edit An Existing Content Model

Edit An Existing Content Model Once you have Content Model Builder enabled, click into it and you will be able to see a list of existing Content Models. Click into one to edit it in the Content Model Builder. Select A Form If the content model has more than one forms, select the one you hope to edit: Then the builder will render with the settings in the selected form. Change Field Order Dragging a field and dropping it on top of another non-object field allows you to move it in front of the othe

Score: 5.5055914

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 th

Score: 5.4999127