In episode 121 of The Content Strategy Experts podcast, Alan Pringle and Bill Swallow talk about content consumers as content ops stakeholders.
“If you look up a restaurant on your phone and go to view the menu, most of the time, that menu is going to be a PDF. And you are sitting there, zooming in, scrolling around, and pinching, and trying to read this menu that really should have just been a responsive HTML page.”
– Bill Swallow
Content as a Service (CaaS) changes publishing from a “push” model to an on-demand model. If you’re looking to pull content from multiple sources and incorporate more flexibility into your content operations, it may be time to consider CaaS. Here are some resources to help you get started:
In episode 116 of The Content Strategy Experts podcast, Sarah O’Keefe and Patrick Bosek of Heretto talk about Content as a Service.
“Do we still have places where building a static site or a static set of help materials makes a lot of sense? Totally. But there’s a natural aspect of dynamic changing content. If that content is going to be a little bit different based on who or where or when you access it, then you can’t build it statically. That’s one of the things you’ll never get from a PDF.”
– Patrick Bosek
Scriptorium was founded in 1997, which makes 2022 our 25th anniversary year. A lot has changed since 1997, but our overall focus remains the same. From the beginning, we have offered services at the intersection of content, publishing, and technology.
In episode 108 of The Content Strategy Experts podcast, Alan Pringle and Gretyl Kinsey kick off an occasional series about stakeholders and content operations projects. In this episode, they talk about IT groups as an important stakeholder in your content operations.
“The IT department can be such a great ally on a content ops project. IT folks are generally very good at spotting redundancies and inefficiencies. They’re going to be the ones to help whittle that redundancy down.”
– Alan Pringle
Content as a Service (CaaS) means that you make information available on request. The traditional publishing model is to package and format information into print, PDF, or websites, and make those collections available to the consumer. But with CaaS, consumers decide what information they want and in what format they want it.
In this presentation, Divraj Singh of Adobe and Sarah O’Keefe explore the concept of Content as a Service and provide CaaS examples.
“In a Content as a Service model, content creators write the content and make it available. Then the consumer gets to format that content and read or consume it in whatever way they want. ”
– Sarah O’Keefe
Content as a Service (CaaS) moves content out of the traditional publishing world. Instead of creating content and pushing it to consumers at the end of the content lifecycle, you make content available on demand. Content consumers connect to a content repository and extract what they need.
In a CaaS system, the content consumer might be a human or a machine. Instead of publishing the content, you let the requestor decide what they need.
In this webcast, Sarah O’Keefe (Scriptorium) and Divraj Singh (Adobe) explore the concept of Content as a Service and provide CaaS examples. If you have complex content requirements, especially in personalization or system integration, CaaS could help you by providing a way to disconnect content authoring, rendering, and delivery.
