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 119 of The Content Strategy Experts podcast, Elizabeth Patterson and Bob Johnson of Tahzoo discuss accessibility when authoring DITA content.
“By its very nature, DITA being strongly structured facilitates more accessible content.”
– Bob Johnson
If you were an early adopter of structured content, there’s a good chance that you have a custom XML content model. This article describes the process Scriptorium uses to make a shift from custom XML into DITA.
In episode 118 of The Content Strategy Experts podcast, Bill Swallow and Sarah O’Keefe discuss content ops stakeholders in tech support.
“If you are delivering multi-hundred page PDFs to your tech support people, then I can assure you that your tech support people hate you. Opening a 600 page document and then having to search through it while you’re on the phone under all this pressure is not the experience that you want.”
– Sarah O’Keefe
Digital content is great, but sometimes, I really need the experience of a physical book. To celebrate Scriptorium’s 25th anniversary, we have published a collection of our most popular white papers. All of these featured white papers are available (for free!) on our website, but if you’re having one of those days where only a book will do…this one is for you.
In episode 117 of The Content Strategy Experts podcast, Sarah O’Keefe and Patrick Bosek of Heretto continue their discussion about Content as a Service.
“Content as a Service is becoming a necessity to really deliver a strong customer experience from an answers and knowledge perspective.”
– Patrick Bosek
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
In episode 115 of The Content Strategy Experts podcast, Bill Swallow and Sarah O’Keefe discuss content ops stakeholders in localization.
“Using baseball examples isn’t going to work well in a country where baseball is not a thing. So you have to think about that. Does your text, does your content, do your examples work and are they appropriate in your target language and culture?”
– Sarah O’Keefe
Is your content tool making you miserable?
If you are doing a lot of workarounds and manual labor to address your content requirements, you’ve probably outgrown your content tool and need to move on to greener (and more efficient) pastures.
In episode 114 of The Content Strategy Experts podcast, Bill Swallow and Gretyl Kinsey talk about developers and managers of the technical stack as content ops stakeholders.
“Without a gatekeeper, things can go awry very quickly. Other groups can take ownership of a particular piece of the tech stack and then you start to have some issues.”
– Bill Swallow
