Create Once, Publish Everywhere

The Problem We Used to Have

Content

Website

Solution: Content Management Systems

The Problem We Have Now

Content

Separate Workflows for Separate Channels?

NPR’s Create Once, Publish Everywhere

What Is Necessary for COPE?

• Automated Publishing through an API

• Central Repository of Structured Content

• Unified Publishing Workflow

The Axilent Platform

• Automated Publishing through an API

• Central Repository of Structured Content

• Unified Publishing Workflow

1. Automated Publishing Through An API

Just publishing every piece of content in the

repository is dumb.

Editorial Policy

• Editorial policy decides what, when and where to publish content.

• In the pre-Internet and WYSIWYG world, done with content selection and layout decisions.

• However, in the multi-channel world, layout doesn’t make a lot of sense any more.

Content Channels

• Automates editorial policy

• Any mix of content selection algorithms

• Accessed through the API

• Change the mix at any time without re-programming.

Content Channels Demo

Different Content for Different Purposes?

Different Content for Different Purposes?

i18n

Content Flavors

Content Flavors

Mobile

Web

Tablet

Title

Body

Summary

Mobile Summary

Content Flavors

Mobile

Web

Tablet

Mobile Channel

Web Channel

Content Flavors Demo

2. A Central Repository of Structured Content

Structuring Content With Content Types

Article

TitleAuth

or

Body Category

• Structure defined by Fields

• Fields have data types

• Publishing channels can rely on structure of content

Structuring Content With Content Types

Article

TitleAuth

or

Body Category

• Fields have Saliency

• How relevant is a content item with a matching field?

• Assists with content selection algorithms

3. Unified Workflow

Workflow

Review

Process

Deploy

Review Steps: Editing Content

• Review Steps allow people to edit content.

• A focus on editing structured content

• A full blown CMS

Review Steps: Editing Content

• Version Control

• Team Editing and Communications

• Tagging and more

Inbox Demo

Process Steps: Automated Content Processing

• Shapes content in preparation for publishing

• Automatically applied to content when it passes through a Process Step.

Process Steps: Automated Content Processing

• Truncate words

• Sanitize text

• Convert to slug

• Auto-tagging

• More to come!

Content Processing Demo

Deploy Steps: Publishing Content

• On deployment, content becomes available to the API

• Content published to “Deployment Targets”: availability zones for content

• A Deployment Step can publish to any number of Deployment Targets

Content Deployment Demo

Integration

• RESTful APIs

• Content as JSON or XML

• API is secure! API keys + HTTPS.

Integration

• Content API retrieves deployed content and Content Channels

• Library API pushes content into the repository

• Integration with legacy CMS possible

• WordPress plugin, more to come!

Documentation

docs.axilent.com

Axilent - a SaaS Platform

• Automated Publishing through an API

• Central Repository of Structured Content

• Unified Publishing Workflow

Axilent - a SaaS Platform

• Free to open an account - no credit card required!

• Free for developer use

• Pricing based on production API usage

www.axilent.com

info@axilent.com