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.

The Future of Content Delivery

146 views

Published on

They way we publish and consume content is changing as the lines between content and data blur. We unpack the current state of content delivery and how it will be managed in the future via headless CMS and the use of APIs.

Published in: Marketing
  • Be the first to comment

  • Be the first to like this

The Future of Content Delivery

  1. 1. Future of Content Delivery What’s a headless CMS and why it might be useful Ingo Schommer, Lead Solutions Architect, SilverStripe
  2. 2. ● Service Design: Meet user in right context ● Multiple Channels: Tailor presentation and language ● Project Complexity: Do more with less Challenges in content management More channels, more problems?
  3. 3. Headless: Why should I care? <Insert joke about heads here> ● Collaboration and reuse through structured content ● Ready for multi channel publishing ● Business value via decoupled presentation
  4. 4. Service Design Example: SmartStart Proof of Concept for govt.nz API-driven content
  5. 5. Service Design Example: SmartStart Proof of Concept for govt.nz API-driven content
  6. 6. Traditional Web Publishing Management and presentation combined, published as responsive website
  7. 7. Example: Community Matters Non-traditional information architecture
  8. 8. Example: Community Matters Non-traditional information architecture
  9. 9. Example: Community Matters Non-traditional information architecture
  10. 10. Integrated Web Publishing Includes data and content from other sources
  11. 11. Web Publishing + API Exposes subset of managed content as API for specialised use cases
  12. 12. Example: ACC Risk Reckoner Mobile app built on SilverStripe 4 and GraphQL
  13. 13. Web Publishing + API Example: govt.nz API Exposes subset of managed content as API for specialised use cases
  14. 14. Headless Publishing Management separate from presentation, multiple channels (optional)
  15. 15. Service Design: Content Reuse Different presentation of content based on user context, retain authoritative source of content
  16. 16. Traditional Content Design Page types with predetermined fields
  17. 17. Content Blocks More flexibility: Assemble page from elements
  18. 18. Shared Content Blocks Reuse in different contexts
  19. 19. ● Workflow: Cross-functional comms ● Information Architecture: Annotate content and data ● Authoring: See changes in context ● Budget: Cost effectiveness for “first channel” ● Analytics: Measuring effectiveness Challenges of Headless When is it useful? Of course, it depends...
  20. 20. Benefits of Headless Many long-term effects with short-term tradeoffs ● Users: Interactive experiences, content in context ● Business: Value, speed of innovation ● Authors: Ownership and consistency ● Designers: Flexibility in tailoring views ● Developers: Freedom in tooling choice
  21. 21. ➔ Join our User Research Panel ➔ Suggest and vote in the CWP Co-Fund Pool ➔ Subscribe to our new CWP Newsletter ➔ silverstripe.org blog post about headless We’d love your feedback Building Open Source software and communities around it
  22. 22. Thank you! Twitter: @chillu Icons by http://ionicons.com (MIT Licensed) ingo@silverstripe.com

×