So, big news… I just started a new job. I resigned as a Web Developer from Hal Leonard the day before Thanksgiving and started my new job as a Web Designer for Journal Interactive, the online division of the Milwaukee Journal Sentinel, on Monday December 14th. It’s very odd switching from spending 95% of my time coding to spending 95% of my time designing and I’m not sure which one I truly like better yet. I can definitely say that I’m enjoying my new work environment, salary, commute, and hours though.
A Change
December 16th, 2009W3, I can’t hear you…
November 30th, 2009Although I’ve always been astounded by how differently the various browsers treat code and how one developer’s approach to a problem can differ so greatly from another’s, it’s only recently really, I mean really truly, dawned on me how ridiculous this all is. At the heart of the problem comes the fact that so much of the W3′s work is ignored whether it’s by major corporations releasing browsers or by stubborn developers who are just going to stick with what the know. If a restaurant blatantly disregards an FDA guideline they are closed down but if company providing half the world with an internet browser blows off the W3 nobody thinks twice. If a lawyer tries to make an argument that violates the Constitution his argument is dismissed but if a developer blatantly disregards a W3 recommendation there’s no consequence. Just imagine all of the frustration and pointless bickering we would rid ourselves of if we all just listened to what the experts are telling us.
CSS vs Tables, the Eternal Struggle
October 22nd, 2009Less Markup
A div based layout uses a fraction of the overall markup that tables do. Well styled divs replace the need to put align, height, and width properties in your HTML, they eliminate table rows and cells that do nothing but contain a blank space, and they reduce the amount of nastily nested ending tags that often reside at the bottom of our pages. Essentially, tag soup becomes tag tartar.
- Less markup means smaller file size for faster loading.
- A higher content to markup ratio for improved Search Engine rankings results from div layouts. Additionally, search engines can better navigation and group content found in the divs and lists used in CSS design.
- Less code means fewer opportunities for coding errors.
Quicker Development
Although frustrating and seemingly mired with problems at first, creating websites with divs and CSS actually takes far less time and effort than creating a table based site. As with any technology, you just need to take a little time to learn it.
- Being familiar with div based layouts can drastically decrease the amount of time spent marking up a design. It is, after all, less code to write.
- Using a CSS framework offers even further improvement. Creating the first draft of the latest project I worked on took less than 30 minutes.
- A review of the BluePrint framework can be found here: http://net.tutsplus.com/tutorials/html-css-techniques/a-closer-look-at-the-blueprint-css-framework/
- This article details and compares the work that goes into creating the same site in tables and in CSS in an unbiased and judicial manner: http://articles.sitepoint.com/article/tables-vs-css
- This blog post reaffirms my sentiments about CSS being difficult to learn at first but rewarding in the end. It also makes an excellent comparison to properly coding with CSS and properly coding in Java: http://mcarthurgfx.com/blog/article/tables-vs-css-really-
Visual Consistency
After having created dozens of sites both with and without tables I have found that with div and CSS layouts it is much easier to achieve a visual consistency throughout the site.
- It is difficult to get every page to appear the same when using deeply nested tables due to the fact that one missed td or one missed spacer row causes text and image margins to appear off.
- During the development process any change made to the table structure of one page needs to be replicated on others. This becomes cumbersome even after only a few pages have been created and often a change made on one page fails to make it to the other leaving inconsistent layouts between the pages.
- One needs only to begin typing after a <div> tag near the top of the page rather than finding the proper table row 150 lines and 6 indentations into the code when using divs and CSS.
Code Readability
A basic div consists only of <div> and </div> tag while a basic table consists of <table><tr><td></td> </tr> </table> . All of these tags become further complicated with nested tables which eventually create a behemoth JSP which is difficult to dissect. Once the time is taken to learn div layouts reading through the page markup is extraordinarily easy. Unfamiliarity with the technology is not legitimate grounds for dismissing it as div layouts with CSS only take a few weeks to learn.
- I once taught a back-end developer div layouts for some admin pages on a website. Having no CSS and div experience he picked it up in a few hours and was amazed and how much simpler the JSP became.
- Using a CSS framework and div layouts my team was able to create the basic layout and integrate into it some image generating back-end code in less than an hour.
Improved Maintenance
Most will agree that the true power of CSS is in the way it allows a site to be redesigned or revamped without having to touch every single page in the site. Using a CSS driven div layout makes it possible to update the appearance of a site on a much more frequent basis without great effort.
- Although we go through painstaking detail to separate business and action logic in our Java, PHP, and .NET code we make no efforts whatsoever to separate content from layout in our page design. A well coded HTML page contains almost nothing but content while the CSS file contains all of the layout properties. Just as we create business, action, domain, and DAO classes for separation of work and easier maintenance in back-end code, we should do the same on our front-end.
- This article reviews the merits of CSS and comes to the conclusion that the separation of content from layout is the cornerstone of CSS: http://www.michaelthorn.co.uk/web-design-tables-versus-css.php
- In order to change the layout of a table based site one must edit each and every page since the formatting properties are on the page. When changing the layout of a CSS driven div layout, it is possible to achieve site-wide dramatic changes with a few minor changes to one CSS file.
- The classic example of this is: http://www.csszengarden.com/
Select a design under the “Select a design” section to watch the site change its appearance completely without altering the HTML markup whatsoever. This demonstrates how much change one can make by only altering a single CSS file when using a div layout.
Javascript/DHTML
All modern JavaScript/DHTML/AJAX techniques rely on div layouts, with the obvious exception of tools designed for sorting and manipulating tables. Creating advanced DHTML interactions is time consuming and frustrating when using tables.
- The DOM structure for a div based site is much simpler than a table based site meaning that DOM traversing, a crucial component of many JavaScript functions, is far easier in a CSS layout.
- A great deal of DHTML simply consists of rewriting CSS rules on the fly. If the original HTML relies on tables instead of CSS for its formatting properties, this incredibly integral functionality of DHTML is rendered moot.
- Virtually all jQuery, MooTools, and Scriptaculous plugins and examples are coded to interact with div layouts on the page. Relying on tables makes it difficult to integrate the wealth of wonderful JavaScript tools into our projects.
Browser Quirks
The battle cry of all of those who dismiss div layouts is that it is not well supported by browsers. This is a fair argument but it is also an argument whose legitimacy is diminishing over time.
- IE6, by far the most problematic browser, can be targeted with IE6 specific style sheets.
- Most browser inconsistencies actually arise from minor coding mistakes which some browsers forgive while others do not. Simply correcting these mistakes often fixes these problems.
- CSS resets eliminate all browser default styles meaning that as you start your actual development your site will render consistently.
- CSS Frameworks like BluePrint come already tested and guaranteed to render correctly in all major browsers, usually back to IE6.
- Tables themselves do not render consistently across all browsers and are actually often much more difficult to style since many of the table and table cell properties such as “align” and “bgcolor” are deprecated as of HTML 4.01 (source).
Modern Design
Many modern design techniques are far easier implemented with CSS div layouts than they are with a table structure. Tiled backgrounds, drop shadows, and rounded corners are just a few of the examples of prevalent design trends made much easier with CSS.
- This website, as well as many others like it, feature fantastic designs that can only be realized through CSS: http://cssremix.com/
Thinking Ahead
With CSS3 on the horizon it is clear that all future advances in HTML markup are going to be done in a table-less CSS driven manner. Quite simply, there is a ton of new functionality being developed for CSS based layouts while nothing new is happening for tables. It is crucial to begin understanding CSS now as to not be completely left in the dust in the upcoming years.
- This article demonstrates some of the amazing CSS techniques on the near horizon: http://net.tutsplus.com/tutorials/html-css-techniques/11-classic-css-techniques-made-simple-with-css3/
Deep Thoughts
September 16th, 2009Revelation of the month:
It’s tough to convince people that they need a good website, not a good enough website.
That’s Not Flash
August 13th, 20099 out of every 10 people who contact me about web design/development projects list Flash as one of their website requirements. Despite this, I have yet to talk to a single client who actually needs Flash on the site. For whatever reason, the general public seems to associate ANY interactivity and movement, no matter how basic, with Flash. I’ve heard all of the following reasons for why people think they absolutely need Flash on their site:
- Embedded Videos
- Photo Galleries
- Drop Down Menus
- Menu Hover Effects
- Dynamic Content
It’s funny enough that all of this BASIC website functionality is easily accomplished without Flash, but when you start thinking about the excellent interactivity that can be achieved with DHTML and Javascript libraries like jQuery and Prototype, Flash starts to seem incredibly obsolete. I don’t know who out there is informing everybody that they need Flash on their website, but man, it has to stop. My emails to clients are really turning into broken records, listing the project requirements one by one and explaining how that’s not Flash and why it’s better that way.
Huzzah, it’s Finished!!!
August 7th, 2009My two-month long redesign project is finally done!!! I spent a lot of time deciding what went into and what would come out of this revamped portfolio/blog and I couldn’t be happier. I decided to take out things like detailed “About Me” sections and the “FAQ” page since nobody seemed to ever read them anyway. The “Services” page also went away for the same reason. I went with a hybrid thumbnails/large images approach to displaying my work on the portfolio page and made a simplified contact form. There were a lot of subtle touches and tough editing that went into the final design and I think it turned out rather well. Now that this is done hopefully I can start some more freelance projects and get back to more regular blogging.
My Latest Project
June 24th, 2009Over the weekend I launched a new site, a personal blog that showcases my somewhat dark and self-deprecating sense of humor. The blog, Just One Day Without Failing, uses WordPress and a theme I made myself. It’s mostly pointless but I hope to keep it entertaining so check it out.
Web 2.0
June 12th, 2009Done with School!!!
June 7th, 2009I just completed all of my requirements for the Web Programming Certificate at MATC and I’ll be picking the certificate up on Monday. I’m ecstatic to be done with school after 5 years, over 160 credits of undergrad followed by a year of working full time and taking evening/online classes at MATC. There’s still plenty for me to learn but I think I’ll be learning from books on my own time from now on because I want to know what it’s like to actually have free time. Grad school isn’t completely out of the question, but I’d like to be clear of undergrad debt and have a really, really clear idea of what to study before I would get a Master’s degree. I think a Master’s is in order if I ever want to be a webmaster or web manager for a career, but just being a web developer is good enough for me right now.
Designing in Milwaukee
May 27th, 2009So, even though I’ve really only been designing/developing for about a year I’m already starting to wonder how this career in Milwaukee compares to the same career in other cities. I already know how the weather here compares, sigh.
One big problem I notice is that Chicago is so close and man are there some real powerhouses of design and development there. This really only matters for medium to large projects as most small projects stay local anyway, but I often wonder how Milwaukee web design firms do any business considering that Chicago based companies usually even come before Milwaukee companies in searches with words like web design, Milwaukee, southeast Wisconsin, etc.
One great thing I see in Milwaukee is that it is a relatively artsy city. UWM has an extraordinarily high number of art and graphic design students, and just on the other side of downtown is the Milwaukee Institute of Art and Design. MSOE and MATC both teach tons of courses in programming and design fundamentals, so this city has more than enough resources and talent to train an army of web designers/developers.
Milwaukee seems to have a ton of small business owners which is both a blessing and a curse. On one hand there are tons of people who need websites for their businesses, but on the other hand, most small business owners seem to be incredibly busy and have little income to throw towards a web project.
All in all, I suppose Milwaukee is a fair city in which to be a web designer/developer, though I may just be seeing greener grass other places.
Archives
Categories
- CMS Applications (14)
- CMSMS 1.6 – Beginner's Guide (8)
- Community (2)
- Freelancing (6)
- jQuery (6)
- Musings (4)
- Plugins (4)
- Projects (13)
- Uncategorized (5)
- Web Design (14)
- Web Programming (19)
Meta
-
Donate
If you're using my jQuery plugins, please encourage my work by donating a small amount.
