Search Results

API / Branches/Releases / Branches/Releases

Branches/Releases Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git or Mercurial and provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changsets. Transactions span multiple

Score: 54.154446

API / Releases / Overview

Overview Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 48.505833

API / Content Services / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 42.75458

Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 15.246088

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 13.82373

API / Data Types / Branch

Branch Type branch Datastore Type repository Supports authorities, permissions, transfer You can have as many branches as you want. Each branch is a completely isolated workspace. Thus, you can create your own branch for your own projects. You can work on those projects and when you're happy with it, you can share it with the rest of the team. Or, you can create a branch and invite a bunch of people to work with you. They're your own workspaces. You can play with them however you want. Changeset

Score: 11.752959

API / Content Services / Search

Search Cloud CMS provides full-text and structured search for all of your content. The platform uses Elastic Search under the hood to automatically create and manage search indexes for your content so that you can find anything at any time. The platform also offers "composite" search operations which let you layer searches on top of structured queries and traversals around node objects. Cloud CMS automatically indexes all of your content, including both it's JSON structure and any binary attachm

Score: 11.677844

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}!/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}!/branch/get_repositories_rep

Score: 11.629194

How can I retrieve content for a tree view?

The Cloud CMS API offers a number of convenience API methods that go beyond basic CRUD and bulk content operations. Among these methods are those that allow you to retrieve content from your repository branch in a tree-friendly format. A tree-organized format means that the data comes back in a such a way as to make it easy to load into front-end tree controls. Typical front-end tree controls requires the ability to load a "snapshot" of the tree as a starting point as well as iteratively grow or

Score: 11.571445

API / Security / Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 11.483149