Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Create Once, Publish Everywhere
The Problem We Used to Have   Conten                              Website     t
Solution: Content Management Systems
The Problem We Have Now Conten   t
Separate Workflows for SeparateChannels?
NPR’s Create Once, Publish Everywhere
What Is Necessary for COPE?• Automated Publishing through an API• Central Repository of Structured Content• Unified Publis...
The Axilent Platform• Automated Publishing through  an API• Central Repository of  Structured Content• Unified Publishing ...
1. Automated Publishing Through An API
Just publishing  every piece of  content in therepository is dumb.
Editorial Policy• Editorial policy decides what, when and where to publish content.• In the pre-Internet and WYSIWYG world...
Content Channels• Automates editorial policy• Any mix of content selection  algorithms• Accessed through the API• Change t...
Content Channels Demo
Different Content for Different Purposes?
Different Content for Different Purposes?               i18n
Content Flavors
Content Flavors      Mobil        Mobile                  Summary       e                  Title      Tablet              ...
Content Flavors      Mobil       e                   Mobile                  Channel      Tablet                   Web    ...
Content Flavors Demo
2. A Central Repository of StructuredContent
Structuring Content With Content Types                            • Structure defined by                   Auth Title     ...
Structuring Content With Content Types                            • Fields have Saliency                   Auth Title     ...
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...
Review Steps: Editing Content• Version Control• Team Editing and  Communications• Tagging and more
Inbox Demo
Process Steps: Automated ContentProcessing                          • Shapes content in                            prepara...
Process Steps: Automated ContentProcessing                          • Truncate words                          • Sanitize t...
Content Processing Demo
Deploy Steps: Publishing Content• On deployment, content  becomes available to the API• Content published to  “Deployment ...
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...
Documentation           docs.axilent.com
Axilent - a SaaS Platform• Automated Publishing through an API• Central Repository of Structured Content• Unified Publishi...
Axilent - a SaaS Platform• Free to open an account - no credit card required!• Free for developer use• Pricing based on pr...
www.axilent.cominfo@axilent.com
Upcoming SlideShare
Loading in …5
×

Axilent Tool Talk from Breaking Development 2012

425 views

Published on

This is the talk I gave at Breaking Development 2012 in Dallas. It discusses the Axilent Platform, and it's use in multi-channel publishing: to mobile devices, tablets and whatever else is on the horizon.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Axilent Tool Talk from Breaking Development 2012

  1. 1. Create Once, Publish Everywhere
  2. 2. The Problem We Used to Have Conten Website t
  3. 3. Solution: Content Management Systems
  4. 4. The Problem We Have Now Conten t
  5. 5. Separate Workflows for SeparateChannels?
  6. 6. NPR’s Create Once, Publish Everywhere
  7. 7. What Is Necessary for COPE?• Automated Publishing through an API• Central Repository of Structured Content• Unified Publishing Workflow
  8. 8. The Axilent Platform• Automated Publishing through an API• Central Repository of Structured Content• Unified Publishing Workflow
  9. 9. 1. Automated Publishing Through An API
  10. 10. Just publishing every piece of content in therepository is dumb.
  11. 11. 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.
  12. 12. Content Channels• Automates editorial policy• Any mix of content selection algorithms• Accessed through the API• Change the mix at any time without re-programming.
  13. 13. Content Channels Demo
  14. 14. Different Content for Different Purposes?
  15. 15. Different Content for Different Purposes? i18n
  16. 16. Content Flavors
  17. 17. Content Flavors Mobil Mobile Summary e Title Tablet Bod y Web Summary
  18. 18. Content Flavors Mobil e Mobile Channel Tablet Web Channel Web
  19. 19. Content Flavors Demo
  20. 20. 2. A Central Repository of StructuredContent
  21. 21. Structuring Content With Content Types • Structure defined by Auth Title Fields or • Fields have data types • Publishing channels can rely on structure of Article content CategoBody ry
  22. 22. Structuring Content With Content Types • Fields have Saliency Auth Title or • How relevant is a content item with a matching field? • Assists with content Article selection algorithms CategoBody ry
  23. 23. 3. Unified Workflow
  24. 24. Workflow Review Process Deploy
  25. 25. Review Steps: Editing Content• Review Steps allow people to edit content.• A focus on editing structured content• A full blown CMS
  26. 26. Review Steps: Editing Content• Version Control• Team Editing and Communications• Tagging and more
  27. 27. Inbox Demo
  28. 28. Process Steps: Automated ContentProcessing • Shapes content in preparation for publishing • Automatically applied to content when it passes through a Process Step.
  29. 29. Process Steps: Automated ContentProcessing • Truncate words • Sanitize text • Convert to slug • Auto-tagging • More to come!
  30. 30. Content Processing Demo
  31. 31. 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
  32. 32. Content Deployment Demo
  33. 33. Integration• RESTful APIs• Content as JSON or XML• API is secure! API keys + HTTPS.
  34. 34. 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!
  35. 35. Documentation docs.axilent.com
  36. 36. Axilent - a SaaS Platform• Automated Publishing through an API• Central Repository of Structured Content• Unified Publishing Workflow
  37. 37. Axilent - a SaaS Platform• Free to open an account - no credit card required!• Free for developer use• Pricing based on production API usage
  38. 38. www.axilent.cominfo@axilent.com

×