Content Management as a Practice

By Deane Barker 5 min read
Author Description

Content management should be treated as a practice, transcendent of any particular language or platform.

AI Summary

This post explores the practical aspects of content management, emphasizing its dynamic and evolving nature. The author discusses the importance of adaptability, collaboration, and ongoing learning, highlighting how effective content management is shaped by real-world practices rather than just theoretical frameworks.

Four years ago, when announcing that the long sought-after title for his profession – that of “interaction architect” – had finally been found, Bruce Tognazzini started off his post with:

This is the most important column I have ever written.

Now, as much as I love hyperbole, I’m not going to go that far. But two months ago, I wrote this

I cut out of [a conference session] to grab a corner with Seth Gottlieb and have what was one of the most professionally meaningful conversations I’ve ever had in my life.

– so I need to deliver. Here goes…

At Web Content 2008, Seth Gottlieb gave a good session about open-source content management. During his introduction, he mentioned that he used to be the “Content Management Practice Director” for Optaros.

That phrase stuck with me. Content Management Practice Director. It resonated over and over for the next 24 hours, until I finally sat down with Seth the next day to talk about it.

Seth’s lofty title at Optaros wasn’t “Development Director” or “Director of CM Integration” or something. Instead, his title evoked something I’ve always been attracted to: the idea of content management as a practice.

What I’ve learned in my years of content management is that it exists on two levels.

  1. Content management itself

  2. Specific platform integration

A lot of people jump right into the second one: platform integration. They learn Drupal. Or eZ publish. Or their company buys Red Dot and they do an integration with that.

Along the way, they’re exposed to some cool features: versioning, workflow, templating, etc. These features make sense, and they get implemented.

However, this person’s knowledge is very brittle. They don’t know content management, they know Drupal. Or eZ publish. Or Red Dot.

And how much do they really know about, say, workflow? If they’ve worked with Ektron, they know that it’s serial approval chains, nothing more. They’ve never been exposed to parallel workflow. Branching workflow. API or code execution steps in workflow. Workflow aliases. Ad-hoc workflow.

In the end, this person isn’t a content management practitioner, they’re an Ektron integrator.

Now, this isn’t all bad. Doing integrations like this pays the bills, and a lot of people do great work and make a great living at this level (I’m one of them).

But I want to go deeper.

I’m interested in content management as a practice. I’m interested in content management as a transcendent skill. I’m interesting in learning, mastering, and teaching the eternal principles of content management, if I can be so dramatic.

Most everything in programming has patterns – ways of doing things that have proven to be pretty well-suited for a particular application. I wrote an entire post about Functional Design Patterns, in fact.

What are the patterns of content management? What are the features, skills, and theories that transcend all platforms. In the end, versioning isn’t about Drupal or eZ publish. Sure, they both have implementations of it will all their quirks and idiosyncrasies, but versioning goes beyond that. It’s an eternal pattern of content management, and something that deserves to be studied and dissected far above the specific implementation level.

When I install and evaluate (read: play around with) a new CMS, I have a mental checklist in my head of what I’m looking for. The checklist looks a lot like the uber-post I made last year about just what comprises a CMS.

I love installing a new system and finding out how it does all of the things on my list. I love digging, prodding, researching, and breaking stuff until I figure out how they implemented Feature X, and how it works.

Seth summed this up in our conversation by saying (I’m paraphrasing from memory), “There are people who like to feel smart, and people who like to feel stupid. People who like to feel smart, never like to use something new because they don’t understand it. People who like to feel stupid, love using something new because it gives them a chance to learn.”

So, the question I posed to Seth, and I’ll pose to you now, is: how do you teach someone the core principles of content management? Have they been defined (my list non-withstanding)? Is there a curriculum? I once wrote a post about wanting a “Masters in Content Management” – what’s the closest thing?

At Blend, my goal has always been to develop a group of solid content management practitioners. While we have our favorite platforms, my hope is that the specific platform we’re currently integrating becomes interchangeable. I want Blend’s people to understand the core principles that transcend those platforms, and not get fixated on one specific environment.

Referring back to the anecdote I opened with, I think I feel the same…relief, as Bruce Tognazzini did when he found the title “interaction architect.” In doing so, he put an identify on an amorphous set of skills and aspirations floating around in his head.

I was just as surprised when Seth tossed out the phrase “Content Management Practice Director” and it started bouncing around in my head. It draws a circle around where I want to be, and where I want my developers to be.

The question becomes: how do we get there? I hope you stick around as I try to answer it.

Links to this – You don't even know what you don't know May 20, 2009
The other day, I got to talking with an old colleague. We worked together in the IT department of a bank about eight years ago. Since then, we’ve both stayed in IT, and our conversation eventually turned to what we knew back then, compared to what we know now. The result prompted me to come up with...
Links to this – The Paradox of Background Knowledge January 1, 2010
I really loved this post from Rajesh Setty about why smart people don’t share their knowledge. He examined why some of the smartest people are so less likely to share their knowledge than other people. His conclusion: Smart people want to give their best and as they learn more, they learn that they...
Links to this – Thoughts on Drupal January 2, 2009
I’m working with Drupal for the first time on a hobby project I’m doing with Seth Gottlieb (about which you’ll hear much more later…). Adam Kalsey – Drupal ninja that he is – is advising us on the technical implementation, and he’s been a great help. Why Drupal? Because I didn’t know it, and...
Links to this – Content Management as a Practice Re-visited September 17, 2008
Content Management as a Practice : Seth has posted a follow-up to my blog post which expanded on a conversation he and I had in Chicago. Our conversation was about teaching content management as an abstract practice rather than as a specific platform integration. In the course of that, we talked...
Links to this – Five Practices of the Well-Rounded Content Management Developer July 12, 2013
Good content management developers constantly work to increase their empathy and perspective. Here are five ways to do that.
Links from this – Functional Design Patterns July 6, 2005
Applications have patterns – ways of doing things that have stood the test of time. These aren’t object modeling patterns , about which books and books have been written, these are…best practices for how to solve a particular type of functional problem. Around my city, you see a certain style of...
Links from this – What Makes a Content Management System? June 30, 2007
Comprehensive post discussing the most common features found in content management systems today.
Links from this – I Want a Masters in Content Management September 29, 2006
I want a masters in content management. Sadly, none exists. I have a bachelors in Government and International Affairs. I was going to be a lawyer, but I got into I.T. during my senior year in college, and I’ve never really looked back. Content management is where I’ve settled – I live, eat, and...