Search Results

API / Deployment / Deployment Target

Deployment Target Deployment Target points to a place for publishing the content. It can be a Channel, a S3 Bucket or any File System Publishing to a channel : To publish the content to a Channel, select 'Channel' from the options while Creating a Deployment Target. Following are the steps to create a Deployment Target: Click on Manage Platform > Deployment Targets Click on Create Deployment Target Title : "Live Web Site" Type : "Channel" Channel : Select the channel where you want to deploy the

Score: 25.788923

API / Deployment / Channel

Channel Channel is the receiver branch to which you want to publish the live content. Channel can be any branch of a project on the Cloud CMS server. Right now, Channel is a branch of a project on the Cloud CMS server, but can be extended to be a file system or S3 bucket. For the publishing feature, it is nothing but a location to upload or publish the live content. Following are the steps to create a Channel: Click on Manage Platform > Channels Click on Create Channel Title - "Deploy to Live We

Score: 24.968327

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

API / Deployment / Deployment Strategy

Deployment Strategy Deployment Strategy holds all the information of the deployment. For example, what is the Source and Destination, when the deployment will happen etc. As soon as the deployment target is created and the project is enable to publish the content, a Deployment Strategy is automatically created. It holds the strategy of the deployment right from the source branch to the deployment target. Following are the details of the information: Title : This shows the title of the strategy.

Score: 19.616585

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

Introduction / How It Works / Publishing

Publishing Cloud CMS brings together several power components to offer publishing of content to your live web sites and applications: Workspaces allow individuals and teams to work together without stepping on each other's toes Workflow provides managers with the tools to review and approve content Instant Preview allows reviewers to see how content changes would impact their live site Completed and approved content can be published to release snapshots or can be copied to target projects on eit

Score: 7.1608915

API / Getting Started / Welcome

Welcome 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 Pub

Score: 5.2805057

UI Guide / Branches/Releases / Overview

Overview Releases, also referred to as branches, 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 Release

Score: 4.7854195

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

How to unpublish content

Cloud CMS provides a range of options for making content available to your presentation tier. The most common scenarios are: 1) Use an attribute on your Type Quick and easy to implement. Just add an attribute to mark instances as published by defining within the type's JSON: “published”: {  "type": "boolean",  "title": "Published?”  } You can then filter out items where this value is False. 2) Create a Feature for consistency Of course, if you have several content Types, you'll want to avoid re

Score: 3.8434536