Content Delivery Platform

The Atlas Content Delivery Platform unifies a flexible Content Management System (CMS) and Digital Asset Manager (DAM) under an authenticated/private API for internal application content or CDN-backed public API for microsite delivery.

The CMS and DAM features are fully integrated with the Atlas Experience Agent to cache content to local Nodes for full offline operation.

This document steps through the high-level features of the Content Delivery Platform.

Applications

Application Delivery is deeply integrated with, and distributed to the Atlas Experience Agent by the Experience Manager.

See the Application section for information on how Applications work in Atlas.

Content Management System

The Atlas Content Management System is no-code and may be fully modeled and configured within the Experience Manager without code changes. Using the web-based data modeling interface, data models can be built and modified on the fly, automatically generating Private/Public (if configured) API's and Content Management UI. It is designed for use with multiple project, each with their own permissions scheme.

Within the CMS, you will find three content types:

• Collections: A Collection is a grouping of like data models, typically containing all of the models for a specific project/output.
• Data Models: A Data Model belongs to a collection and provides the stricture for the CMS content, along with filter, sort, search and display behavior.
• Records: All Records belongs to a single Collection, and are associated with a Data Model that provices the records field structure.

Content Delivery API's

Data managed in the Content Management System is delivered through one of four API's tailored to different delivery use cases. All API's are interchangable, though the Private API does require authentication.

Private

The Private API requires authentication and is designed for uses such as on-premesis applications where the content is not public. Accessing the Private API requires token authentication.

The Private API is the least likely to be used in production as the Local Agent API's are preferred for accessing cached content, but are often used in development for retriving the latest content from the CMS.

Public

The Public API is publically accessible when a Collections is configured as public and does not require authentication. Collections are required to be public when used for websites and web applications.

The Public API's are mostly used for development as content is not cached, and published records are immediately visible. The Public CDN is preferred for live websites.

Public CDN

The Public CDN mirrors the Public API, but is hosted on a separate domain (visible on your Collection settings page). The Public CDN URL is different than your Experience Manger. It obfuscates the upstream Experience Manager Admin URL and heavily caches all API responses to accelerate page load times and reduce the load on your Experience Manager under heavy web traffic.

This is the preferred endpoint for accessing the CMS for production websites.

Local Agent

When delivering an Application on-premesis with the Experience Agent, the assigned Application Template can have a CMS Collection assigned. When a Collection is assigned to a Template, the content will automatically be downloaded to Agents using that Template. This cached content is then served by an API on the local Agent allowing applications to work, even if there are network connectivity issues.

This is the preferred endpoint for applications running on-premesis.

See CMS Proxy API ->