I made mention in the last post of a couple of tutorials I have been going through. One I stumbled upon in Barnes and Nobles shortly after I started using Dreamweaver. It is Dreamweaver CS3 with CSS, Ajax, and PHP, by David Powers. This is a great tutorial and is user friendly and complete. It introduces Dreamweaver’s CSS, PHP, Spry (Adobe’s version of Ajax) and MySQL features for building dynamic websites.
The Ajax, PHP, and MySQL instruction is adequate to bring you up to speed on these tools. The CSS part of the tutorial, however, is more how to use Dreamweaver in using and maintaining style sheets in the software. Powers recommended, and I purchased and read, Beginning CSS Web Development: From Novice to Professional, by Simon Collison. Collison’s book is a fine intro to CSS styling.

When I started playing with webpages in 1994-95 on Compuserve, there were not a lot of WYSIWYG web editors. Many folks just used Notepad. There were not a lot of formatting choices. Folks ingeniously found the tables element worked pretty well for formatting in HTML. But it was web design by the seat of your pants. I suspect WYSIWYG editors came about to test one’s use of tables in formatting to see if it worked. Java script menus came along later. Ah, the cool Java Script that people could, knowingly or otherwise, turn off. As www.w3.org has successfully established itself as the web clearing house for standards, it is clear most people see the need for an organized, standardized approach which keeps styling and formatting separate from content.
Well, I am happy to say, having gone through these manuals, I am forever weaned off of using tables to layout webpages. Tables worked for layout, but I never was convinced they were the best way to format. It seemed like overkill, and you had to use a lot of tags and math to move your rows and columns left or right, up or down. That is still the problem with computers and CSS styling—it takes too much math and understanding absolute versus relative positioning to layout a page that a little magic marker and a photo copy machine would produce nicely in the not so distant past.
In some ways, I think databases have taken over and are being overused in webpage design, much the way tables were. Take for example the tables in the recent Bible Brief posts. I constructed them using, of all things, a database plugin for WordPress since there is now no way to conveniently use the table element natively in the WordPress editor. The editor chokes on HTML tables and spits them out. But, at least for the present, the use of databases does make a handy way of searching for and creating dynamic content.
We are still on the fore edge of web design and use. It will be interesting to see how things continue to merge together in the future. The key concept now seems to be databases, and the key word is “searchable.”
© 2007, Scott Branyan