Axilent Tool Talk from Breaking Development 2012
-
Upload
loren-davie -
Category
Technology
-
view
198 -
download
0
description
Transcript of Axilent Tool Talk from Breaking Development 2012
![Page 1: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/1.jpg)
Create Once, Publish Everywhere
![Page 2: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/2.jpg)
The Problem We Used to Have
Content
Website
![Page 3: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/3.jpg)
Solution: Content Management Systems
![Page 4: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/4.jpg)
The Problem We Have Now
Content
![Page 5: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/5.jpg)
Separate Workflows for Separate Channels?
![Page 6: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/6.jpg)
NPR’s Create Once, Publish Everywhere
![Page 7: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/7.jpg)
What Is Necessary for COPE?
• Automated Publishing through an API
• Central Repository of Structured Content
• Unified Publishing Workflow
![Page 8: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/8.jpg)
The Axilent Platform
• Automated Publishing through an API
• Central Repository of Structured Content
• Unified Publishing Workflow
![Page 9: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/9.jpg)
1. Automated Publishing Through An API
![Page 10: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/10.jpg)
Just publishing every piece of content in the
repository is dumb.
![Page 11: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/11.jpg)
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.
![Page 12: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/12.jpg)
Content Channels
• Automates editorial policy
• Any mix of content selection algorithms
• Accessed through the API
• Change the mix at any time without re-programming.
![Page 13: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/13.jpg)
Content Channels Demo
![Page 14: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/14.jpg)
Different Content for Different Purposes?
![Page 15: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/15.jpg)
Different Content for Different Purposes?
i18n
![Page 16: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/16.jpg)
Content Flavors
![Page 17: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/17.jpg)
Content Flavors
Mobile
Web
Tablet
Title
Body
Summary
Mobile Summary
![Page 18: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/18.jpg)
Content Flavors
Mobile
Web
Tablet
Mobile Channel
Web Channel
![Page 19: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/19.jpg)
Content Flavors Demo
![Page 20: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/20.jpg)
2. A Central Repository of Structured Content
![Page 21: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/21.jpg)
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
![Page 22: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/22.jpg)
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
![Page 23: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/23.jpg)
3. Unified Workflow
![Page 24: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/24.jpg)
Workflow
Review
Process
Deploy
![Page 25: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/25.jpg)
Review Steps: Editing Content
• Review Steps allow people to edit content.
• A focus on editing structured content
• A full blown CMS
![Page 26: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/26.jpg)
Review Steps: Editing Content
• Version Control
• Team Editing and Communications
• Tagging and more
![Page 27: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/27.jpg)
Inbox Demo
![Page 28: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/28.jpg)
Process Steps: Automated Content Processing
• Shapes content in preparation for publishing
• Automatically applied to content when it passes through a Process Step.
![Page 29: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/29.jpg)
Process Steps: Automated Content Processing
• Truncate words
• Sanitize text
• Convert to slug
• Auto-tagging
• More to come!
![Page 30: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/30.jpg)
Content Processing Demo
![Page 31: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/31.jpg)
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
![Page 32: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/32.jpg)
Content Deployment Demo
![Page 33: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/33.jpg)
Integration
• RESTful APIs
• Content as JSON or XML
• API is secure! API keys + HTTPS.
![Page 34: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/34.jpg)
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!
![Page 35: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/35.jpg)
Documentation
docs.axilent.com
![Page 36: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/36.jpg)
Axilent - a SaaS Platform
• Automated Publishing through an API
• Central Repository of Structured Content
• Unified Publishing Workflow
![Page 37: Axilent Tool Talk from Breaking Development 2012](https://reader035.fdocuments.in/reader035/viewer/2022062513/554bcda4b4c905ac708b474f/html5/thumbnails/37.jpg)
Axilent - a SaaS Platform
• Free to open an account - no credit card required!
• Free for developer use
• Pricing based on production API usage