Found 141 results for "api branches overview"

The search executed in 0.0 seconds

API Keys

API Keys For information on API Keys, please visit the Cloud CMS - API Keys Developer Page.

Score: 33.099636


Branches 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 documents

Score: 30.280546


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

Getting Started

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

Score: 29.33223


Releases 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: 20.080276

Application Server / Services / Overview

Overview For more information on configuration of the Cloud CMS application server, please visit Cloud CMS App Server on GitHub. { "name": "Cloud CMS Application Server", "setup": "single", // single, cluster, sticky-cluster "socketFunctions": [], "routeFunctions": [], "configureFunctions": {}, "beforeFunctions": [], "afterFunctions": [], "viewEngine": "handlebars", "storeEngines": { "app": { "type": "fs", "config": {

Score: 18.028454

API / 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: 12.139395

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 11.102308


Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 10.865725

How to Retrieve content by their document library path

You can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call:!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo

Score: 6.5666437

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

Proxy API calls

Whenever a resulting URL looks something like: It works great as an API URL but not necessarily as one that can be resolved by the end user's browser. In a typical Node.js-based architecture, you have the User’s browser Node.js application server Cloud CMS backend API The URL generated above is the URL directly to the resource in the backend API. What you really would pre

Score: 6.0686703

Modules / 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: 5.766777

User Interface / Multilingual

Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i

Score: 5.746992

User Interface / Workflow / Your Task Dashboards

Your Task Dashboards Tasks assigned to you in a Workflow process can be seen in your Platform Dashboard, Project Dashboard, or an email may have been sent to you with the Task link Platform Dashboard Tasks asigned to you for all Projects will be listed Project Dashboard Tasks asigned to you for the Project only will be listed Task Overview If you click on a task, or open the Task link in the email, the Task Overview page is opened From here you can perform the following actions on the task: appr

Score: 5.739949

Tree Hierarchies

In Cloud CMS, there are no hard and fast rules regarding association types between nodes. And so, when dealing with things like tree structures, you usually have to first make some assumptions about the kinds of relationships between nodes that you want to traverse. For arbitrary relationships and traversals around nodes, Cloud CMS provides traversal methods which are a bit more intensive to use. However, if you're using typical a:child relationships between nodes (which is what Cloud CMS uses f

Score: 5.714942

User Interface / Workflow / View/Create a Workflow Model

View/Create a Workflow Model Switch to Platform level Click 'Workflow Models' (left Nav). Note: You will need to have admin or owner permissions to see the Workflow options. If you select a Workflow model you can Deploy, Undeploy, delete a Workflow model View/Edit Workflow Model Click on the Workflow name, eg Adhoc Approval, to view the Workflow Model To view/edit the Workflow click JSON Manage Active Workflow To see active instances of the workflow model click on Workflow option Note: you can s

Score: 5.6094704


Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 5.544065

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 Documents (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 n

Score: 5.475222

Docker / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 5.3731227

Files / Binaries

Binaries Cloud CMS supports the storage of binary files into one of three possible storage locations: MongoDB GridFS Amazon S3 Local file system Binary files are stored using directory structures (key prefixes) that allow for fast object retrieval from any of these systems. These storage paths are optimized for retrieval and write speed and are subject to implementation changes. The actual API retrieval of these files, on the other hand, utilizes a simple filename convention. You simply retrieve

Score: 5.252861

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

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

Application Server / Services

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

Score: 5.2220054

Files / Attachments

Attachments Cloud CMS provides support for the storage and retrieval of binary assets. These assets are stored as attachments on an object. Unlike some CMS systems which start with the binary asset, Cloud CMS considers all of your objects and content to be JSON documents. The JSON document then has N number of binary BLOBs attached to it. Each attachment has a unique name and retains information such as mimetype, filename and content length. The following kinds of objects support attachments: Co

Score: 5.0891743