Skip to main content

Definition review: Gilbane's CM definition

I had a quick read through Gilbane's CM definition to see if it would spawn any ideas or reactions.

Web publishing meets e-Business. Seems like they want to shrink the definition into meaning web content management, excluding stuff like digital document management. I don't mind this, but personally I prefer to use CM as an umbrella for most of the other management types, including web. And I see that towards the end of the document different analysts views on this are presented. And indeed some of them share my view, Gartner even claims (uh, mind that this was in year 2000) that no full CMS does not yet exist (still a valid claim?). Coincedentially, CAP even uses the term "umbrella".
Oh, and there's a very nice comment on knowledge management (this one's for you, Thommy ;)):

Fortunately, the assault on logic and language that was knowledge management has run out of steam. We'll still see the term used by consultants and some technology vendors (including Microsoft and Lotus), but we won't have listen to specious marketing pitches claiming that managing knowledge will replace managing data, documents, content, etc.

Just to clarify, me and Thommy (good friend and KM-specialist) both agree that KM can envelope CM, and CM can envelope KM-tools. We shouldn't try to deny the usefulness of KM, I think KM's golden age has yet to arrive (knowledge is important, and corporate knowledge is not the same as corporate content). As technology improves, KM-tools will become more feasible. In my experience, a KM-evangelist doesn't try to replace CM with his or her own tools, but include CM in the suite of KM-tools. KM and CM do not compete. I guess this is where the commersialism of Gilbane shines through.

But back to the subject, mixing code and content, no surprises there. There's an interesting view of perhaps seperating transactional information out of the content term, but the theory fails. Any CMS but "brochureware" systems (nice word!) produces/supports transaction, like this very blog has transactional information in shape of the RSS-feed (further down on your right).

All in all, it is an old, but still very valid definition. A bit business oriented, but otherwise it didn't contribute much to my understanding of the term.

Note to all content- and knowledge managers, rest assured: You don't have to know what it is to figure out a good way to do it!


Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp