Kurt wrote this mid-morning:
So continuing with my articles for the ‘31 Days to a Better Blog‘ series, I thought I’d talk a bit about content management systems, how they helped the Web take off in the hands of content creators, and what the implications are for blogging and the direction of the Web in the future.
Uphill Both Ways - Before CMS
In the early days of the Web, not just everyone had a site; those few of us that did had a ‘home page’, the term du jour of the 1990s that fell out of vogue as quickly as that of ‘blogging’ rose up. Your ISP, or perhaps a dedicated web hosting company, would give you a few megabytes of space on their Web server, and you’d be free to muck around in that space as long as you didn’t want to run any dynamic scripts that they hadn’t approved; there were HTML editors out there that supported dynamic content, but you almost had to run your own server to take advantage of them. The end result was a lot of people coding pages in FrontPage or by hand, updating them for a while, and then getting frustrated when the page grew past a certain point; when you needed to change one link on every page, you either had to do it by hand or write a script to do it, and errors inevitably crept in.
However, we finished walking uphill in the snow both ways long ago. With the rise of more and more web hosts allowing dynamic scripting, and the growth in popularity of server-friendly languages like PHP, more and more people found that a collection of HTML files wasn’t the best approach anymore. People began compiling those scripts from the early days into larger collections, and then someone got the bright idea of having the scripts write the HTML on demand and pull the information from a compact, secure database, saving on disk space, maintenence, and manual coding.
And thus the Web entered the age of the Content Management System, tools for putting together content in a page without troubling yourself with the little details like writing HTML (if you had told me in 1998 that writing HTML was a ‘little detail’, I would have laughed myself into a coma. But I was young then, and not wise in the ways of the CMS.). Of course, the most popular of these, and the one with the most public awareness, is the weblog; blogging has enjoyed the same sort of meteoritic growth as tulip prices in European markets and my ego at college.
But blogs aren’t the only form of CMS, and the other important forms of CMS are (probably unfairly) overlooked too often. The two notable forms of CMS that I’ll talk about here are the wiki and the knowledge base.
Going wiki in the knees
The wiki was invented in 1995 by Ward Cunningham, named after the Hawaiian word for ‘quick’. The essence of the wiki is community editing; instead of trusting the users with comments like most blogs do, the wiki is designed instead to trust the users with the article itself. A full-fledged wiki can be started by the administrator, abandoned, and still maintained and expanded by the community (though obviously, this isn’t a great way to build traffic or maintain a reputation for yourself!).
The major upside of a wiki, at least compared to a blog, is the extensive possibility for community involvement. Your users get more significant buy-in for the site when they help maintain it themselves, and administrators get the advantage of splitting their duties between content creation and editing. This is especially useful in corporate and business environments, which is the major growth area for wiki tools (I’ve implemented two business wikis at previous jobs, and both businesses were thrilled with the results). It’s much harder with hobby or niche sites; you generally don’t have a captive audience to ‘lock-in’ to the wiki, and the single biggest hurdle to wikis taking off that I’ve seen is getting users to try editing in the first place; once they start, they love it, but only once in a great while does one start.
That said, there are several large downsides to wikis, some of which you can find in my previous posts. Aside from the trouble of getting people to contribute, you have to deal with the content and editorial problems that come with an open content system. There’s always the risk of bad content or advertising disguised as content, though on small hobby wikis I haven’t seen that too much as a problem. The much bigger problem is spammers abusing the system to insert their own links invisibly, trying to increase their rankings at the expense of your own site’s bandwidth and page rankings. I have pretty direct experience with this, having just cleaned an invisible spam infestation out of StudentNYC that remained there long enough to give me a PageRank of 0. If you abandon a wiki, assume that it will be compromised before too long.
You Have a (Share)Point
The other major form of CMS floating around on the Web right now is the Knowledge Base or Team Services type of site; the biggest example is Microsoft’s SharePoint. It basically provides a web interface to a document managagement system, almost invariably with add-ons like calenders, contact lists, to-do lists, et cetera. There’s big money in implementing these sites for corporations, although their usage for hobbyists is probably strictly limited to running one on your own private network to share documents between computers. Even then, the bells and whistles never seem to see much use; everyone already has a favorite tool for calenders and e-mail.
Beyond Just Blogging
So what do these tools have to do with the growth of the Web? Well, the major search engines were designed in the days when a human could only manageably do so many pages; directories could list everyone by category, and search engines could just index the directories. Now, of course, the Web is far too large to reasonably expect directories to keep track of all the domains out there, much less all the sites (anyone who has tried to get listed in Yahoo or DMOZ knows what I mean!). Algorithms had to be developed to automatically figure out how trustworthy and linkworthy a site was, and CMS software, properly designed, dovetails perfectly with those algorithms to give its content a very high ranking.
But why should anyone care, besides the few extra hits a day they can get from Google with proper search engine optimization? Simple: while the Internet as a whole and the blogoshape in particular has quickly jumped on the CMS bandwagon, corporate America, by and large, hasn’t. So where does this leave your average blogger? In an outstanding position to capitalize on the situation. We’ve hit a unique point where a product blog can outperform the product’s actual static site with some ease, depending on the product, and this could have startling ramifications on marketing on the Internet as a whole.
We’re going to see a lot of noise in this equation: blogs capitalizing on the situation to cash in on popular product keywords and stay atop the rankings. But we’re also going to see some good signal here from honest bloggers who want to spread information and encourage discussion. To anyone who discounts blogs: this is going to be the impact that’s remembered, not just allowing your cousin Bob to have a website of his own.