Words

I came across a very good article with regards to taxonomy titled, Search in Focus: Implementing a Taxonomy by Penny Crosman.  The article is a month or two old, but I haven't run across it before so maybe others haven't either.

The Newbie Issue

I received an interesting e-mail the other day through the contact form at my site regarding the social bookmarking "features" I have for my posts.  The questions asked to me are quite common among new users of any Web content management system.  While the questions in this particular e-mail I received would be more appropriate to be asked and answered in the forums at Drupal.org, there were some things in the message I felt the need to address though my blog.

The first e-mail went like this:

On Planet Drupal, there have been a number of posts lately about the difficulty project leaders and developers have in  saying "no" while working on a project.  As much as Project leaders want to please both their client and their team members, real leaders understand the responsibilities they have in saying "no".  More specifically, I'm talking about Boris Mann's post, "Susan Mernit on the role of "no" in product development" as well as Laura Scott's own post You've got to know when to 'no' them .

This is all interesting to me because for some time I've wanted to talk about Aaron Mentele's post, Every once in a while you need to fire a client.  Aaron Mentele is a web designer and co-owns a web design company based in Sioux Falls, SD.

There comes a time when most project leaders have mastered the the ability to say "no" to certain requests.  But what happens if you find yourself not really saying "yes" to the client?  Do you have it in yourself to recognize that by having to answer "no" so often in a project you likely shouldn't have taken on the project in the first place?  What are you to do?

This fork of Joomla to improve accessibility interested me

Accessible (a8e) Joomla! is a Joomla! fork that conforms to accessibility guidelines and web standards. A8e Joomla! will follow regular Joomla! releases. The project should implode when regular Joomla! finally conforms to the standards.

Accessibility of Internet sites is very huge within the federal government and addressed by Section 508 of the Rehabilitation Act, 1998.

While most bloggers are using the new year to look ahead, I am not quite ready to make promises to the year of 2007. In fact, I am more inclined to looking at the past thanks to the Internet Archive's Wayback Machine.

I'd like to challenge anyone who has designed a web page to find the oldest site in the archive that they authored and post the Wayback Machine link in the comment section of this post. There are no prizes being awarded in this "contest" but I promise you can have some space for bragging rights. Feel free to include any history on the page that you feel is necessary to tell your story.

The archive contains archived web pages from 1996 to the near present. The oldest web pages I could find that I authored was from 1997 for the National Weather Service's forecast office in Sioux Falls, SD.

The above site actually originated in March 1996, but this 1997 image is the earliest I could find in the archive. Not very impressive is it? However, you have to remember that I was authoring with HTML 1.x and worried that Netscape's introduction of the blink element was pushing the envelope further than I wanted to go.

BusinessWeek published an interesting article titiled, Did MySpace Really Beat Yahoo? The article discusses the difficulty to confirm which site actually has more traffic, MySpace or Yahoo.

On a recent visit to Drupal's forum I found another post with both Joomla and Drupal in the subject line. Making comparisons between Joomla and Drupal are very common these days as they are currently considered the top two open source content management systems (CMS) out there. The forum post written by Steve Burge contains a link that takes you to a comparison table he did between Joomla and Drupal.

Over the weekend, I upgraded the server that hosts CMS Report with the latest stable releases of MySQL and eAccelerator. The upgrade from MySQL 4.1 to 5.0 was easy compared to the upgrade I made a year ago from MySQL 3.23 to 4.1. This time around I also have use of CPanel which meant I could make the database upgrade with at least one eye closed. My journey with upgrading from eAccelerator 0.9.4 to 0.9.5 however took a lot longer.

I've been using eAccelerator 0.9.4 since it was released early in 2006. I've gotten into some trouble in the past by those smarter than me when I tried to explain exactly what eAccelerator does and does not do. To play it safe this time around, I'll give you the summary of what eAccelerator does straight from eAccelerator.net:

Wyatt Barnett in his Sitepoint article, "I've Never Met a Boxed CMS I Like" makes some very valid points about content management systems straight out of the box. Take note that he isn't just talking about commercial products but also open source systems. His first complaint about "boxed" CMS:

The first issue is that the very nature of a CMS is not easily boxable, without creating an application that tries to do everything for everyone and fails at doing most things particularly well. The tasks required for content management are generic, but every organization has a far different focus when it comes to how that content should be managed and how it thinks about that content. I have lost days of meetings trying to help subject matter experts understand that an article, according to this system, is really a page. Trying to make a generic application to handle this for all comers is a very, very tricky prospect.

Sadly, his post doesn't really offer a solution. I assume building your own CMS is the only alternative to the boxed version. But I have to ask, who really has the time? I think there are some obvious reasons you see so many capable software developers are using open source software such as Wordpress, TYPO3, e107, Alfresco, and Drupal for their Web presence.

Website owners rejoice! Forgent Networks has dropped their claim on owning the patent rights for JPEG. While this hasn't been a huge concern for most Web designers it's still one less worrisome thought to worry about! Groklaw was the first site that I came across this story:

Here you go, straight from the Public Patent Foundation's press release: Forgent Networks has stopped asserting its patent against JPEG, has dropped all its pending cases that were asserting the patent, and says that it won't file any other infringement claims based on the patent. Read more...