We’ve got another fairly interesting release from WordPress on the way – 3.6. From Mark Jaquith’s post on features:
- Post Formats: Post Formats now have their own UI, and theme authors have access to templating functions to access the structured data.
- Twenty Thirteen: We’re shipping this year’s default theme in our first release of the year. Twenty Thirteen is an opinionated, color-rich, blog-centric theme that makes full use of the new Post Formats support.
- Audio/Video: You can embed audio and video files into your posts without relying on a plugin or a third party media hosting service.
- Autosave: Posts are now autosaved locally. If your browser crashes, your computer dies, or the server goes offline as you’re saving, you won’t lose the your post.
- Post Locking: See when someone is currently editing a post, and kick them out of it if they fall asleep at the keyboard.
- Nav Menus: Nav menus have been simplified with an accordion-based UI, and a separate tab for bulk-assigning menus to locations.
- Revisions: The all-new revisions UI features avatars, a slider that “scrubs” through history, and two-slider range comparisons.
All good features. However I would suggest that it’s time for WordPress to address the one major feature of a CMS that they have woefully ignored: Workflow.
At it’s basic level, Workflow is the movement of information or tasks through a work process. In our case, it’s content as it moves through the WordPress system. This might be as simple as the blogger opening the editor, writing his content, adding a couple pictures, and then clicking publish; essentially three workflow steps. In a larger media organization, that general process becomes much more involved as more people perform separate and distinct tasks. The workflow might look more like:
- Editor assigns story and deadline
- Writer researches story
- Writer writes story
- Writer archives story research items (not for publication but as resources that may be used later)
- Copy editor edits story
- Photographer takes photos,
- Photo editor edits photos
- Editor (or someone) adds photos to story
So our simple task now involves 5 people at least, as well as spanning 8 distinct workflow steps. Now realize there may be several cases of back and forth, for example., the editor sends the story back to the writer for rewrite, or the photo editor realizes they need another photo, etc. Similarly, these same people are each involved in multiple workflows at the same time.
How do we keep it all straight?
Basically, we’d need a way to provide a “To Do” list for each of the members of our team. The items on that list all might have separate deadlines, which would then allow our editor to see the progress of the story, as well as adequately budget time for the various resources. Obviously your photographer isn’t going to be at two ends of the county at once…thus the editor is able to “budget” his resources. Now extrapolate that to including not just your human resources, but perhaps your equipment. Perhaps you’ve got two events your covering and you want to film both with your Red Camera. Problem is that you’ve only got the one, and the events are both at the same time.
For your human resources, they are able to get notifications when something is ready for them. In the newspaper world, a copy editor would see the article appear in his “queue” (his task list) and then he’d proceed to edit it. This article might be assigned specifically to him, or perhaps it might be generically assigned to someone with the role “copy editor”.
Perhaps this system also enables us to get notifications on things. Such as impending (or worse yet, passed) deadlines. Or new work that needs to be done. And maybe that notification is can be made at several levels of urgency. Level one just sends an email, whereas level 4 alerts you via sms, email, tweet, and probably also warns the editor to something such as a missed deadline.
…And then, magic happens.
So let’s think about those steps in our workflow again. We’re assuming that all of these steps are human steps. They probably aren’t. You might have videos uploaded to the system, and perhaps once they have been edited, you have an automated step that sends then through a program (which isn’t part of WordPress) to convert them to various formats. Or maybe you have a program that extracts keywords from a post and creates a summary post that gets automatically tweeted out. Simple stuff…but important.
So that is sort of what I’d like to see. In it’s core, WordPress works well as a CMS, but the management of people and work is sorely missing. Yes, it is possible to cobble much of this together, but in my mind, there is no reason not to provide it in the system itself. Many of us would be working much more efficiently and the system would certainly get much more acceptance as a real CMS for Media and Enterprise.
(If you’re interested in how you can setup a system with this level of functionality let me know – I’ve already got some of this working right now)