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
Our internal Slack workspace has channels for projects, events, and other work-related items, but of course our most popular channel is #thefoodchannel, where we share recipes, restaurant recommendations, and general foodie discussions.
In episode 102 of The Content Strategy Experts podcast, Sarah O’Keefe and Sharon Burton of Expel talk about the importance of terminology management.
“If we don’t give customers the information to understand what we’re telling them, they won’t be successful and we have failed.”
– Sharon Burton
In episode 101 of The Content Strategy Experts podcast, Elizabeth Patterson and Sarah O’Keefe talk about what life is like with and without a content management system (CMS).
“You have to decide, by looking at your particular organization, whether you need what a CMS will give you. You will get improvements in consistency and automation for formatting and traceability. You can get improvements in translation because you have more consistent content and better workflows.”
– Sarah O’Keefe
Content Operations (content ops or ContentOps) is the engine that drives your content lifecycle.
The Scriptorium Content Ops Manifesto describes the four basic principles of content ops:
In episode 98 of The Content Strategy Experts podcast, Sarah O’Keefe and Dr. Carlos Evia of Virginia Tech continue their discussion about the pros and cons of markdown.
“If you want to make a website and you need to write the text in a fast way that does not involve adding a lot of the brackets that are in HTML syntax, I think that’s the main use for markdown.”
–Dr. Carlos Evia
In episode 97 of The Content Strategy Experts podcast, Sarah O’Keefe and Dr. Carlos Evia of Virginia Tech discuss the pros and cons of markdown.
“I think markdown has a huge user base because most people need to develop content for the web. But there’s a set of people that need to be working in something more structured for a variety of reasons, and those are the ones who use DITA.”
–Dr. Carlos Evia
Enterprise content strategy means including all customer-facing content in your planning. Our enterprise content strategy maturity model provides requirements for that strategy. This article focuses on content integration. How do you unify content across disparate content teams and technology stacks?
In episode 95 of The Content Strategy Experts podcast, Sarah O’Keefe and Kris Eberlein (chair of the OASIS DITA Technical Committee) discuss the upcoming release of 2.0. What can you expect if you are currently in DITA? And what do you need to know if you are considering DITA?
“If you’ve been shoehorning diagnostic information into troubleshooting topics, Â you’re going to have a good semantic place to put that content with DITA 2.0.”
–Kris Eberlein
First published in Intercom (October 2020) by the Society for Technical Communication.
Scalable content requires you to assess your content lifecycle, identify points of friction, and remove them.
Company growth magnifies the challenges of information enablement. When you grow, you add products, product variants, markets, and languages—and each of those factors adds complexity. Process inefficiencies in your content lifecycle are multiplied for every new language or customer segment.
As a result, content scalability—increasing content throughput without increasing resources—becomes critical. Consider a simple localization example: when you translate, you have a few manual workarounds that require 1 hour of work per 100 pages of translated content. So if you translate 100 pages of content into 8 languages, you have 8 hours of workarounds. But as your content load grows, you are shipping 1,000 pages of content per month and translating into 20 languages. Suddenly, you are facing 200 hours of manual workarounds per month—the equivalent of one full-time person per year.
