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!


Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

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 operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

The Best Log Viewer Ever

This is what it looks like when I want to have a look through the logfile, to see what a user did on one of our machines one day:


Read the whole story about how it works on the Viaboxx Systems blog (and upvote on DZone!).

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…