Acquia Content Hub: Connect Technologies & Extend Systems to Source Content
Download as PPTX, PDF2 likes900 views
The document outlines the capabilities and advantages of Acquia Content Hub, which facilitates content syndication, integration, and management across multiple platforms, addressing challenges faced by enterprises with legacy systems. It highlights features like robust content discovery tools, bi-directional content distribution, and a platform-agnostic integration approach, aiming to enhance customer experiences. Additionally, the document emphasizes the growing need for efficient content management in a rapidly evolving digital landscape.
Acquia Content Hub: Connect Technologies & Extend Systems to Source Content
- 1. Acquia Content Hub: Connect Technologies & Extend Systems to Source Content Chris Pliakas Director, Content Services Engineering Ken DeBlois Product Manager, Content Hub & Search John Dolce Solutions Architect March 31, 2016
- 2. Agenda → Today’s Enterprise Landscape & Acquia Content Hub Overview (15 minutes) → Acquia Content Hub Technical Components (15 minutes) ▪ Drupal Module ▪ Data Flows ▪ Rest API → Demo: Easily Build Custom Apps with API (15 minutes) → Q&A (15 minutes)
- 3. Today’s enterprise landscape is evolving. Company C Company A Company B → Multiple legacy systems Company AC → Acquisitions → Mergers → New technologies
- 4. Content gets locked away in silos... … across different teams and technologies.
- 5. Acquia Content Hub SyndicationDiscovery Robust content discovery tools Full faceted search Automatic subscription updates Saved, customizable filters Bi-directional content distribution Automatic and curated re- publishing to any endpoint Centralized or distributed content models Aggregation Secure, cloud-based content repository Integration into existing technology footprint Connectors and robust APIs Acquia Content Hub enables customers to author, search and share content, to deliver engaging customer experiences across a complex network of sites and channels.
- 6. Integration Approach & Open API No need to rip and replace No need to change business models Decrease implementation risk Separation of Content & Presentation Reuse content across diverse sites Integrate into existing Drupal environment workflow Acquia Content Hub Differentiation Drupal
- 7. Acquia Content Hub Data Flow Drupal → Write operations are asynchronous (eventually consistent) → Expect syndication to happen within 5 seconds, usually under 2 seconds → Publish subscriber model, enabled by webhooks → Common model in most modern distributed services, e.g. AWS → Facilitates better scale and performance, although slightly more complex → Live example, with explanation
- 8. DEMO Background • 2 Media Sites • Legacy & Drupal • Publish Articles from Legacy to Drupal
- 9. High Level Flow Author Publish Content Hub Drupal Activate Put Entity Callback Query/Get json Register
- 10. Questions?
- 11. Chris Pliakas Director, Content Services Engineering Ken DeBlois Product Manager, Content Hub & Search John Dolce Solutions Architect March 31, 2016 Thank You
- 12. Appendix
- 13. Acquia Content Hub vs. Custom Builds Significantly faster time to market Significantly lower cost to build, maintain and upgrade Access to Content Hub API, to easily connect to multiple technologies and content sources Acquia Professional Services best practices
- 14. There is an unprecedented growth of new channels and markets. “Our survey reveals that, on average, enterprises manage 268 customer-facing websites…Delivering great experiences across every device a customer wants fuels complexity.” -Forrester Research, The State of Digital Experience Delivery, 2015, April 2015
- 16. Enterprises struggle to integrate deeply rooted legacy systems with newer technologies. “In 2014, digital experience technology decision-makers cited integration with back-end systems as the biggest hurdle they faced in delivering great digital experiences. In 2015, ease of back-end integration tops the priority list when buying new DX software.” -Forrester Research, Digital Experience Technology Integration: Go Beyond Just A Basket Of Solutions, August 2015
- 17. What if you had the key…
- 18. …to publish everywhere, from anywhere?
- 19. There is a Massive Content Explosion Happening Today
- 20. Everyone is a content creator and content publisher. “Between the time the world was born and 2003, a total of 5 exabytes had been created. In 2013, 5 exabytes of content was created every day! Today, Google alone processes over 20 petabytes of information every day!” -Newstex, Digital Content in Real Time, January 2015
- 21. Big content comes with a big cost, mainly time spent searching for content. “In 2013, content searches cost companies over $14,000 per worker and nearly 500 hours per worker.” -Newstex, The Data Explosion in 2014, July 2014
- 22. Enterprises struggle to integrate deeply rooted legacy systems with newer technologies. “Most organizations overinvest in features and underinvest in integration… Yet customers don’t care about these legacy issues. They want easy, convenient, enjoyable experiences on any device or interaction with your brand. Digital experience demands a new strategy.” -Forrester Research, Digital Experience Technology Integration: Go Beyond Just A Basket Of Solutions, August 2015
- 23. Takeaways from Forrester Research Digital Experience Technology Integration: Go Beyond Just A Basket Of Solutions, August 2015 →Avoid one-off, point-to-point integrations ▪ Do not scale for future integration needs ▪ Result in multiple, incompatible versions ▪ Increases need for ongoing maintenance ▪ Adopt extension philosophy (ie. APIs) and code philosophy instead →Be weary of monolithic applications and “all-in-one” platforms ▪ Inhibit evolution of your technology footprint ▪ Not practical – legacy systems, limited budgets, business changes (ie. mergers, acquisitions)
- 24. Content Syndication Automatic and curated re-publishing to any content endpoint
- 25. Content Discovery Full faceted search Date, source and tag filters Automatic subscription updates Saved, customizable filters
- 26. Customer Use Cases →Share and discover content bi-directionally (Ivy League Medical University) ▪ Share relevant content across diverse departments, sites, teams - ie. physician profiles, medical publications →Keep site experiences up-to-date (Global Financial Services Company) ▪ Information on latest news and product updates →Launch new sites faster and more efficiently (Global Financial Services Company) ▪ Spinning up new client and agent sites frequently ▪ Need rich content to efficiently populate new sites
- 27. Customer Use Cases (cont) →Migrate content away from legacy systems (Higher Education Services Company) ▪ Enable migration to new Drupal sites →Cross promote and share content (Big Three Music Publishing) ▪ Cross-sell products across diverse content sources - ie. merchandise, albums, artist sites “Clearly reducing time and cost by half at a minimum...” “Tremendous amount of time saved, but also money saved...”
- 29. Authoring can be centralized...
- 31. Acquia Content Hub Roadmap →D8 Support →Client-side API →Content Hub authoring experience →“Packaged” connectors & client libraries →Audit trail
- 32. Acquia Content Hub Differentiators → Integration approach (platform agnostic) ▪ No need to rip and replace technologies ▪ No need to change business model ▪ Decrease time to value ▪ Decrease risk of implementation → Separation of content and presentation → Drupal customers can integrate into existing Drupal environment and workflow
- 33. Competition: Custom Build →Costly maintenance burden. ▪ Difficult to maintain ▪ Require dedicated internal support and resources →More content sources, more problems. ▪ Will require custom integration between content source and CMS ▪ Content Hub both Drupal-based and open API, so can easily integrate with any solution OOTB ▪ Content Hub’s open marketing approach and flexibility is necessary in today’s world of increasing devices, opportunities, channels, and sites →Slow pace of change. ▪ No single organization can match pace and scale of feature delivery that technology organizations can ▪ Custom platforms require all custom feature development, restricted by budget and resources.