Skip to main content

The difference between a portal and a WCMS

What is the difference between a portal and a WCMS? I've been asking myself that question since the beginning of this thesis. Others have asked as well. Indeed, the WCMS I've been working on for Primetime used to be called Primetime Portal.

Now it seems the question is bubbling around in the CMS blogosphere these days. John Quirk suggests "..if they are dealing with content a CMS solution is where they should be focused. If they are planning on allowing access to back end applications or information stored in those applications, a portal solution is a better fit.". Toby Ward claims the gap will shrink (or blur, perhaps making it easier to fall down the gap?) as both product families grow and mature. Bob Boiko suggests Knowledge Portals are the last trick from the KM camp. James Robertson has written a white-paper on business portals, explains the concept of portals rather well.

When I present my thesis to more-or-less technology aware people, they sometimes ask "Oh, you're writing about portals then?". The word portal sometimes seems to have become synonymous with company homepage. The definitions are a bit loose, so the answer could actually be yes. The views below explain why:

Portal people: Content management is part of the portal. We have a CMS portlet in our portal. A CMS alone doesn't have personalization or integration of different content sources, nor pluggable functionality in the form of portlets.

CMS people: A portal is just one way to display the CMS to the end user, just like a blog is another (smaller) way to perform CM. Portal is just a hyped product name. CM is the theory behind it. We have pluggable functionality in the form of templates. Personalization is pointless (who cares if you want a pink webpage?).

A CMS is content oriented. Is a portal knowledge oriented? Portals try to be the silver bullet of corporate information management, but the above bloggers suggest that they have become too complex and do still not possess sufficient CMS functionality. Don't get me wrong, portals are very useful for distributed corporations, serving as a central source of information. I haven't played around with too many enterprise class portals, but I can guess they still lack CMS-functionality like content version control, wysiwyg editing and workflow, as Ward mentioned.

So how to relate to portals in the thesis? Should a portal be part of a CM strategy, or should the portal be an integration tool outside the CMS? I think I'll go for the latter alternative and rather focus on WCMS, might mention portal in a side note.

Disclaimer: Suffering with a terrible cold here, so mind that some of these ramblings might be fever inspired ;)

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…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Automating Computer Setup with Boxen

I just finished setting up a new laptop at work, and in doing so I revamped my personal computer automation quite a bit. I set up Boxen for installing software, and I improved my handling of dot-files using vcsh, which I'll cover in the next blog-post after this one.

Since it's a Mac, it doesn't come with any reasonable package manager built in. A lot of people get along with a combination of homebrew or MacPorts plus manual installs, but this time I took it a step further and decided to install all the "desktop" tools like VLC and Spotify using GitHub's Boxen:

  include vlc
  include cyberduck
  include pgadmin3
  include spotify
  include jumpcut
  include googledrive
  include virtualbox

If the above excerpt looks like Puppet to you, it's because it is. The nice thing about this is that I can apply the same puppet scripts on my Ubuntu machines as well. Boxen is Mac-specific, Puppet is not.

It was a little weird to get started with Boxen, as you're offered…