If you’re a content strategist, you have likely heard a lot about the importance of being part of designing and customizing content management systems. But if you’re a developer, you may not have the same perspective.
On a recent project, I witnessed this firsthand. While I made a point of creating content templates, identifying content types, and designing governance practices with an eventual CMS customization in mind, the (external) development team was not prepared for the same level of collaboration. They looked at my deliverables as options, and when my ideas didn’t fit, rather than open a discussion they unilaterally made decisions. Unfortunately, the result was a CMS that didn’t fit the content needs or the editorial team’s abilities.
At this year’s CS Forum in Melbourne, Rachel Lovinger gave a brilliant talk about 10 (well, 8) things she has learned in 10 years as a content strategist. It inspired me to consider what we know as content strategists, as compared to what our users (particularly the editorials teams) know.
Rachel stressed the importance of author experience, explaining how necessary structured content is, in order to have easily findable, and thus usable content. She went over the basics of structured content, reminding us that it needs to:
- Be stored separately from any display infrmation
- Have content types identified
- Be stored in discrete, manageable chunks
All of this is very important to us, as content strategists. But I suddenly remembered a client who told me how frustrated she was to work with Oracle, where she needed to build “links” and “assets” that could then be pulled into “sections” that could then be pulled into “pages.”
Our authors don’t care if their content is structured. Continue Reading
Metadata is a Love Note to the Future, by Rachel Lovinger
Metadata is in code, it’s in security, it is context, and it enables connections.
It’s hard to convey that in a concise and powerful way.
Rachel’s fiance (ooooooh!) had a slide “metadata is a love note to the future” which has now made the rounds via retweets, Tumblr, other peoples’ presentations… and now it’s come full circle.
Rachel had to take ~10 years of magazine content (about 50k articles) and put them into a CMS. 3 years later, doing a redesign, they found almost 7000 different keywords (though they found ~12% were typos, or redundant keywords).
But they wanted the metadata to do more. Continue Reading
CMS Selection: the “C” is for “Content” by Anne Casson
Goal: head for lunch with a better understanding of content requirements that go into choosing a CMS.
A basic approach:
- Define the requirements
- Vendor shortlist
- Vendor evaluation (with a scorecard and checklist)
We’ll focus on: defining the CMS requirements Continue Reading
Who Put Their Technology in My Content Strategy?, by Meghan Walsh
Content strategists job can also include tech planning, partner relationship management, business requirements, cross-program alignment… it’s a lot. We’re creating content that is personalized, and then we need to distribute it.
Meghan looks through both the practitioner lens and as the strategy and planning role, focusing on the technology, not the operations.
“The content strategist is the critical voice in content technology planning, selection and design.” Continue Reading
Onramp: Making the Case for Author Experience, by Rick Yagovich
- What is “author experience?”
- Why is it an imperative?
- The value of author experience for the whole organization.
What’s the purpose of a CMS? Continue Reading
Workflow that Works under Pressure, by Jeff Eaton
Content is everything for some organizations
- Content as the product – organizations produce content
- Lots of it, consistently
- It’s dynamic
- It’s often time-sensitive
- Jeff has a lot of feelings about this.
We adapt to the tools we’re giving
- Jeff had a friend with a “potato” button on the microwave
- When the microwave got old, only the “potato” button worked
- They adapted to cook other things in increments of “potato”
- Our clients do this with our CMSs when they don’t have the tools they need
A World with Fewer Walls, by Noz Urbina
Overt selling has given way to problem solving. Sweeping statements have given way to conversation-like messages -Robert Rose
Silos are a general metaphor for “separation”
- A lack of understanding
- A lack of communication
- A lack of usability
It’s been over a year since Karen McGrane began presenting on “Adapting Ourselves to Adaptive Content,” and her message has been heard far and wide. For many content strategists, “create once, publish everywhere” is an abstract idea which is made manageable through the lens of “how can we manipulate our CMS to best allow a inline editing with previews that accurately represent our responsive design and adaptive content?” But even once content strategists begin to think in terms of content for multiple uses, many are forced to leave their clients with a multi-device strategy and a CMS that doesn’t reflect the mentality.
Rasmus Skjoldan is working on the solution. Rasmus and the Neos team at TYPO3 are attempting to create a CMS with multiple, customizable previews, to help users visualize content across multiple devices and browsers. Not only is this a new technical challenge, but the team needs to consider the user experience. Clients using Neos will ideally find the CMS reinforces the multi-device strategy content strategists have been touting. Done wrong, the CMS will do nothing but confuse the already tangled web of adaptive content. Continue Reading