Jeff Bridgforth :: Webcraftsman

Crafting Web sites since 1999

I am a Web designer passionate about creating elegant, inspiring, and usable Web experiences that connect with an audience and fulfull business objectives.

Blue Beanie Day

November 30, 2009

Blue Beanie DayToday is Inter­na­tional Blue Beanie Day. I’m show­ing my sup­port for Web stan­dards by adding a blue beanie to my avatar today. If you would like to add a beanie to your avatar, grab this Pho­to­shop file cre­ated by Kevin Cor­nell.

What are Web Standards

This video is a very good intro­duc­tion to the topic. Jef­frey Zeld­man really led the charge of this move­ment with his book Design­ing with Web Stan­dards.

Why I use Web standards?

Almost every pro­fes­sional indus­try starts with stan­dards. They are agreed upon best prac­tices and prin­ci­ples that all the play­ers in an indus­try fol­low. It makes for a com­mon lan­guage and allows mul­ti­ple peo­ple to collaborate.

Back before Web stan­dards, dif­fer­ent browser ven­dors would imple­ment HTML dif­fer­ently. It was hard for a designer to build a Web site that would func­tion well across many browsers because the rules would always change. Now there is a com­mon envi­ron­ment that we can build upon to make great expe­ri­ences for the Web user.

Here are some rea­sons I advo­cate using Web standards:

  • Quicker and eas­ier devel­op­ment and main­te­nance — Using struc­tured and seman­tic HMTL and CSS makes it a lot eas­ier to under­stand code that was writ­ten by me or by some­one else. I often have to revisit code that I wrote a year ear­lier. I can quickly get in and make my edits because I under­stand what I was doing in the past. I can also fig­ure out what oth­ers were think­ing when they coded their pages so I can learn from them or con­tribute to their work.
  • It is for­ward think­ing — Using stan­dards future proofs your site for changes in the browsers. Stan­dards gives you a solid foun­da­tion which will keep your site from break­ing and allow you to imple­ment new code and fea­tures as they are imple­mented in the browsers.
  • Leaner pages - Sep­a­rat­ing con­tent and pre­sen­ta­tion allows for less cod­ing on your indi­vid­ual pages. I was able to cut the code on one legacy site down to a third or fourth of what it was when it was coded with tables for lay­out. Leaner pages load quicker which is a win for your visitors.
  • Bet­ter acces­si­bil­ity - Using seman­tic HTML makes it eas­ier for assis­tance devices to cor­rectly inter­pret con­tent. It also makes it eas­ier to develop dif­fer­ent ver­sions of your site for dif­fer­ent devices includ­ing mobile. You just serve up a sep­a­rate stylesheet to each device.
  • Highly adapt­able — Sep­a­rat­ing pre­sen­ta­tion from struc­ture makes it much eas­ier to update a design or apply a new design because you only update one or more CSS files to update instead of updat­ing code on every page.
  • It saves time and money — This is the major busi­ness case for using Web stan­dards. Leaner code means less band­width which saves money. Seman­tic code can improve your search engine rank­ings. It takes less time to develop and main­tain Web sites using stan­dards which saves the site owner money.
  • I am join­ing other pro­fes­sion­als in my indus­try in using agreed upon guide­lines - Using stan­dards makes it eas­ier to work with oth­ers in my pro­fes­sion. We speak a com­mon lan­guage and can con­tribute and col­lab­o­rate with one another because we are com­mit­ted to the same stan­dards.

Comments are closed.