I would add a scripting language and a database to the mix. But I agree with Paolo:
K-logs and the Google Search Applicance Recently we have been working a lot on k-logs, or knowledge (web) logs, or anyway on the concept of using weblogs as a company internal communication tool. We use k-logs ourselves at evectors and so far everything works perfectly but, of course, I miss google on my intranet. No problem, as you probably know, if you are based in the US you can get it in the form of the Google Search Applicance (there also are ASP based services offered by google). The reason I would like google on my Intranet, is becuse the whole weblogs architecture works perfectly with google (just check your weblog's referer traffic). The real value of google is in their page ranking system, which is based on the fact that users are linking pages from their pages. Now: in a regular intranet site, let alone on file server, there are usually very few or no links. So, on a regular intranet, the Google Search Appliance would be just yet another search engine. But with internal weblogs, everything would start to make sense again. And I have not even told you what we are up to with centralized rss aggregators and dynamic file servers! Anyway, to my enquires google replied saying that they are not distributing it in Europe yet, so I guess I will have to wait some more... ";->" [Paolo Valdemarin: Paolo's Weblog]
Oh, oh, I have a couple of friends that will not like this:
Thanks to Column Two for passing this on (though I've seen it reposted elsewhere, too). I love the story of visiting the booth at the CMS conference with a client and witnessing this interchange:
The head Sales Guy started grilling my client: how many pages did the site have (in the thousands!), how many users updated it (almost ten!). You could hear the Sales Guy's mental cash register ringing up dollars signs as he went straight for the close: "And what are your editors using to update all those pages: Dreamweaver or Frontpage? Or maybe you built your own homegrown CMS?"
My faithful client didn't miss a beat. "Actually, have you heard of weblogs?" he asked the Sales Guy. You shoulda seen this guy's face fall - it was like he'd been hit by a truck. "Yeah," he admitted, "So you use blogging software?"
"Yeah pretty much," came the answer. "It pretty does most of what I need. There are a couple things you described that I could use, but I can't justify that sort of outlay when blogware hits most of my specs."
That was really my eureka moment: my first realization that content management was screwed.
Paul Holbrook's Radio Weblog. Paul's original RSS item was shortened, with no link to his own comments on klogging. He speaks of the discomfort in revealing one's klogging to others on a grand scale.
Shortly after I arrived, I started keeping a klog of my work. So far I've clued in the few people I've worked with so far to my klog, but as best as I can tell, they haven't paid much attention. I've been struggling with the question about when and how to let the larger project team know about my klog, but so far I've been reluctant to do so. Today I was in kick-off meeting for the large project I've been working on. Towards the end of the meeting, I was almost consumed with the desire to tell people about my klog, but I just couldn't bring myself to speak up. I've asked myself why that is, and the answer isn't straight-forward. I've only been at Tech for six weeks; higher-ed politics are notoriously complicated, and I don't know how people might react to the things I've written. A klog is by definition not politically correct; you say what you think, not what you believe others might want to hear. [Paul Holbrook's Radio Weblog via [Ron Lusk's Radio Weblog]
