Found 82 results for "content-models types"

The search executed in 0.001 seconds

API

API The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish

Score: 20.1215

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

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

API / Data Types

Data Types

Score: 12.060161

User Interface / Embed Media In CKEditor / Advanced Usages / Extend Media Types

Extend Media Types The out of the box media types on CloudCMS are Youtube, Vimeo, Brightcove and Soundcloud. However, we grant you the ability to introduce any other media types. Follow this tutorial to learn how. (Code is involved!) Create a xxx-link.js File Note: Take a look at these files to get a sense of it. getSchema() and getOptions() These two methods allow you to create a form with specific fields to configure for templates of this type. /** * @override */ getSchema: fun

Score: 10.454084

Bulk Import / Nodes

Nodes The Cloud CMS Bulk Import tool makes it easy to import content from structured data files stored on disk. The Packager API provides several methods which can read content from directories and bulk import that content all in one fell-swoop. This includes content types, content instances and relational information between content items. This is useful for many scenarios including those where you may wish to store a master copy of your foundation content types and content instances for new pr

Score: 8.469094

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

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

Publishing / Workflow

Workflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.

Score: 5.2896657

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

Content Model - Association example

Question. Suppose that I have the following collection types: Customers Orders and I want to store the Customer ID and the Customer Name on each Order… If the customer then updates his Name, how is it possible (if at all) to update the customer’s name on all of his orders - in a single atomic transaction? Answer. For this situation, you would have two content types - Customer and Order. One good way to address this is to utilize an association between the two. You could declare an association ty

Score: 3.2344553

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

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

Role-based security access

You can configure a Cloud CMS project to provide precise, role-based access to content types and content instances. Let's take a look at example of how this is done! Suppose that you have three users - Jim, Dwight and Michael - and two content types (my:article and my:news). We would like things to work like this: Michael is the boss. He is allowed to view, create, edit and delete content content of all types. Dwight is a worker. He is allowed to view, create, edit and delete content of type "my

Score: 2.9751809

Modules / Create a Module / Plugins

Plugins Cloud CMS plugins let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Plugins provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Score: 2.9479823

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

User Interface / Embed Media In CKEditor / Advanced Usages

Advanced Usages Extend Media Types Extra Attributes

Score: 2.8846612

Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 2.8690927

Publishing

Publishing Content Types Example Publishing Setup Lifecycle States Preview Servers Publications Workflow

Score: 2.860265

Content Modeling / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 2.8518822

Chaining vs. Promises

The Cloud CMS JavaScript driver provides it's own internal chaining library that makes it easier to manage callbacks in asynchronous JS applications. The chaining library is powerful and bears some similarity to modern promise libraries. But it is important to bear in mind that it is distinct apart from having some similar method signatures. One similarity in structure in that both promises and chaining have a then() method to resolve the callback. However, the chaining library's chained methods

Score: 2.711621

User Interface / UI Templates

UI Templates On pages like "Content Types" and "Search", each list item has some detailed information displayed. You can customize the information you hope to appear via UI Templates. Create a UI Template Fill in the title and a unique key to create a new UI template. You can also write down some description for the template. Nodes with qname n:ui_template have two properties: key, which is a unique identifier of the template, and type, which is the type of targets the template is applied to. Cu

Score: 2.6848445

Features / Knowledge Sharing

Knowledge Sharing QName: f:knowledge-sharing Used to tag an association as to indicate that it "shares knowledge" between a source node and a target node. The source node is a node is a "knowledge space" and the target node is a "knowledge recipient". An association marked with f:sharing-knowledge will be considered to be an association that knowledge properties may propagate down when changes are made to a knowledge space node. By default, the a:child association which is used to mark relations

Score: 2.6688254

Modules / Create a Module / Bindings / Type Pages

Type Pages The type-pages key lets you define routes that serve as landing pages for entity types. Specific pages within Cloud CMS serve as landing pages for an entity that is being viewed. Type Page configurations allow you to specify which URI should be dispatched to when viewing. Each type page has a very simple binding like this: { "uri": "{uri}" } Example - Dispatching a Workflow Task to the Overview Page { "evaluator": "entity-is-type", "condition": "Gitana.WorkflowTask", "

Score: 2.581863

Modules / Create a Module / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 2.5623024