“Oh what a tangled web we weave, When first we practice to deceive”

Netscape Navigator and Internet Explorer began creating two versions of the Internet, each filled with super features that only worked with their browser and not the other. Netscape would jab, and Microsoft would counterpunch. It was an exciting free-for-all and the ones hitting the mat at a dizzying speed were the web page designers trying to make their sites look decent in both browsers.

The unauthorized biography of the miracle table

Once upon a time, there was a patchwork of computers between scientists, mathematicians, teachers, and all-around geeks. This patchwork allowed information to flow quickly and dialogues developed. One day, a technique was discovered to make this information pretty. Images could be added to these pages of inter-linked documents and viewed in a new “browser” called Mosaic. This made the esoteric patchwork of scientific notes appealing to the average person and the Internet as we know it today was born.

It didn’t take long for browsers to become more sophisticated. Mosaic evolved and Netscape Navigator was the way most people accessed the world wide web. Microsoft decided they needed to build a better browser and control the Internet and intranets of companies around the world. The Browser Wars had begun.

Netscape Navigator and Internet Explorer began creating two versions of the Internet, each filled with super features that only worked with their browser and not the other. Netscape would jab, and Microsoft would counterpunch. It was an exciting free-for-all and the ones hitting the mat at a dizzying speed were the web page designers trying to make their sites look decent in both browsers.

The Internet soon became filled with pages that were a mishmash of misunderstood code, boring layouts, and really bad writing. In 1996, David Siegel released his book Creating Killer Web Sites and the web was changed forever. Well, maybe it wasn’t THAT dramatic. Siegel introduced the world to the graphic use of tables to layout a site. Tables are officially used to display information in a tabular format. Columns and rows intersect to show how much the red, pullover sweater will cost on the new www.pullover-red-sweater-store.com web site. But Siegel said “wait!” We could take this ugly web site, throw in a table, chop it up again, take some big happy images, cut them into smaller pieces, reconstruct them with yet another nested table, add some text here, a little color there, maybe a shadow or two, throw in some images to keep the cells from collapsing, and voila! A web page that looks decent in Netscape and Internet Explorer and actually looks fairly nice. The miracle table was born.

Life in Internet land seemed to be full of bliss, pages were beginning to look interesting, web sites were fairly easy to build, and the miracle table was flexible enough to contain the growing design challenges. For you see, Netscape and Internet Explorer continued to fight for the biggest share of the browser market. More and more, designers found their sites only looked and behaved properly in one of the two browsers. People began building mirror sites for those with slow internet connections, Netscape users, Internet Explorer users, and more. The population of users also began expanding. Screen readers were developed for those who are blind. WebTV brought the internet to the living room television. People began asking for internet access on their cell phones and PDA devices. The miracle table was beginning to crack under the pressure.

Luckily, there was a group of rogue developers fighting to stop the browser war madness. These underground heroes fought with guerilla tactics unseen in any previous battle. They created the World Wide Web Consortium and started pounding sense (standards) into the Internet Community. They issued doctrines (suggestions) and distributed propaganda (w3c.org). They demanded the browsers begin to work together, adopt a set of standards, and the world would be happy and free again. Surprisingly, this bloodless coup-d’etat actually worked.

The W3C has been guiding the browsers, developers, and designers down a peaceful path toward a new era of web design that is cross-browser compatible (Internet Explorer, Opera, Safari, Firefox, et al), platform independent (web pages, screen readers, PDA devices, cell-phones, . . . ), much faster to download, more accessible, easier to develop, and ready for the future. Welcome to the world of standards-based web design.

post-cms

I’ve got this problem. My creative juices have dried up worse than the mohave. Sure, I can move things around, write some text, etc. But I’ve had a hard time getting into building a new site. I’ve got some that need to be done, so this is a problem.

So, I’ve been busy researching some backend programming. I’m sure my fingers will be happy soon and my design mind will just purr with excitement. By that time, I’ll have some new structures just waiting for fancy-shmancy skins.

I want to understand how to build a standards-based CMS sytem. I started looking for the perfect package. I’m not a php/asp/perl/jsp programmer so I needed something that had already been put together. I wanted it to be free and I wanted the information to sit on my server, not a hosted solution. I also wanted something that could work for a museum and also work for a small business that needed little more than a brochure-site.

So, what did I find?

Mambo is a great CMS system. It has a great administrative backend and powerful features. Mambo can be modified to create css-based layouts, but the menus and subsections are still table based. So, I continued my search.

MOSXML could be a perfect solution. This project takes the Mambo backend and uses it to output pure XML. XSL and XSLT files are used to create the desired web pages. This project is still in beta and I couldn’t get it to work on my server. I need to do some more tweaking before I give up on this project. It could be a bit too bleeding edge to build a museum web site, but would be good for a test site.

PHPWebSite is another good CMS. While it is much closer to the ideal, it still isn’t perfect. Their goal is to be XHTML 1.0 strict valid by the final launch. Currently, it is still using tables for much of the subsections but the layout can be css-based. The admin is pretty good and the features are great. I found myself dreaming about all of the cool projects that could be built with this. Unfortunately, I don’t have the time to hack up the program to get rid of all the tables.

Basecamp is a nice project management product. I haven’t played with it yet. I just set up a Basecamp site to handle an upcoming project. It will be interesting to see how this develops.

So, where am I now? The latest project that I am testing is WordPress. A recent story on converting it to a CMS system seems promissing. The conversion is pretty simple and I do like the flexibility. WordPress is also standards-based and easy to modify.

Now, I need to find a good photo gallery manager to work with WordPress. I’ve looked at Flickr, but I know this is not a solution for a museum. Image rights management would make Flickr a nightmare. So, I’m looking for something that makes it easy to upload mulitiple images, add the appropriate tombstone information, and present the images with flexible galleries.

Ah, the glory of the research. It’s a good thing my creative mind has dried up, I can just concentrate on the coding features.

post-launch

A web designer blog without a design?! Is it a mistake?

The process is what this design is about. I’m starting with a blank page and will begin adding features, design ideas, and theories.

Post-next…

Today’s ideas are built on yesterday’s movements. Post-rock, post-modern, post-expressionist, post-next… This site will build upon yesterday. Designs will evolve. Textures will build. What happens today will effect tommorow.

Let’s see how we grow.