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 ;)

Comments

  1. Anonymous10/2/06 16:31

    Interesting question..
    I consider CMS to be actually consisting of content creation, content management and content delivery. COntent delivery is where I think portals belong. If there is a tight coupling between content management and delivery, than CMS can be a part of portal (or vice versa). However, if they are loosly coupled, they would be different. Both kinds of architectures are prevalant. Vignette, Fatwire, OpenCMS etc fall in the first category, wheread Interwoven, Documentum, ALfresco would fall in the second category.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well: I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there. It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences. To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer s

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

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 wit

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 --