1. DOCTYPE Declaration

   DOCTYPE (short for “document type declaration”) informs the browser of which HTML or XHTML standards you would like your code to be checked against. You’re essentially declaring to the browser that these are the rules that you have used to create this page and in return you are expecting that it will render accordingly. Failure to specify a DOCTYPE can lead to unexpected rendering — a developers worst nightmare.

   [ further reading ]

2. Navigation

   A website’s navigation plays a key role in the success or failure of a site. It allows humans and search engines alike to easily locate the desired information. Or it doesn’t. Navigations made up of Flash or JavaScript/DHTML may seem attractive at first, but ultimately can cripple a website by not allowing search engines to crawl and index the entire site. In addition, viewers that choose not to partake in these technologies can be left with no means to move within the site.

   Most experienced webmasters have left such navigations back in the 90’s with all those AOL discs.

3. CSS is Not an Option

   In the past webmasters could choose to ignore CSS if they so desired. Those days are gone. CSS is no longer an option, it’s part of the trifecta (see The Separation of Concerns for the trifecta) that makes up a quality website. A good webmaster will use CSS exclusively to define the look and layout of a website.

4. The Separation of Concerns

   In days gone by web developers would meld HTML, CSS, and JavaScript code all into a single page; like a web page jambalaya. Inexperienced web developers may still do this, but the experienced ones took notice that the make up of any given page is defined by three elements: the content of the page, the presentation of that content and the behavior of that content.

   Realizing this, competent developers have made an effort to keep these three layers separate from one another. Kevin Yank does a fine job explaining our three layers in his article: Simply JavaScript: The Three Layers of the Web

   When building a site, we work through these layers from the bottom up:

   1. We start by producing the content in HTML format. This is the base layer, which any visitor using any kind of browser should be able to view.

   2. With that done, we can focus on making the site look better, by adding a layer of presentation information using CSS. The site will now look good to users able to display CSS styles.

   3. Lastly, we can use JavaScript to introduce an added layer of interactivity and dynamic behavior, which will make the site easier to use in browsers equipped with JavaScript.

5. Cross-Browser Support

   Any developer that has been building websites for awhile has the battle scars that you get when you try and make your website work on all browsers. Each browser has it’s own idiosyncrasies (some more than others) and designing and redesigning your site to function under each can be a battle; but it’s a battle that must be fought and won.

   [ for more help with cross-browser CSS read this ]

(more…)

There’s no doubt in my mind that the little blocks from Denmark known simply as LEGO are the greatest toy ever. I put in more hours playing with Legos than all other toys combined. I loved to use my imagination to build with them. It really didn’t matter what: a car, a fortress, star destroyer, space station, whatever. It was about taking an idea and bringing it to life piece by piece.

This love to build something from nothing still resides within me; it’s just been replaced with web technologies instead of plastic bricks. Today I build websites, plugins, widgets and anything else that takes life in my imagination. The thing I enjoy most is seeing if I can pull it off — can I get what’s in my head to take form on the web? Most of the time I can.

But there’s something that really bugs me about all of my creations. They simply don’t last. In fact, over the years I’ve found the life span of any web-based product to be short, very short. Of all the websites I’ve built, more are gone than remain. They’ve been replaced by newer versions or completely phased out. There’s no place for nostalgia on the web.

I have a deep jealousy of designs that last. I look at Michelangelo’s Sistine Chapel which has been around for five hundred years and is in no danger of ever being updated or phased out. Or Beethoven’s 9th symphony which he completed in 1824 and still moves the soul today. I’m betting that even more recent artists like Christian R. Lassen probably never worries about their work becoming dated and needing to be replaced. But in the world of computers, nothing lasts.

Does anyone else find this frustrating or at least a little depressing? Of course it’s not just my work. I already have images of a new 3G iPhone dancing in my head and my current iPod is only two years old. My three thousand dollar computer that I hand built from the greatest specs three years ago doesn’t run today’s DirectX 10 games. How sad…

You have to ask yourself when developing software or web pages if pixel perfection’s really all that important when it’s only going to last a handful of years anyways? Could this be why Microsoft released Vista knowing full well that it was far from done? Microsoft is already talking about their next OS, Windows 7 and Vista is barely out of the wrapper.

I know, it is what it is, the beauty and the curse all rolled into one. The ability to create knowing full well that you will do it all over again in a handful of years. I guess it’s job security, right?

Your thoughts?

As you walk into Starbucks the aroma of coffee brewing permeates your senses. Trendy music plays in the background with earth-tone painted walls, nicely lacquered wood and friendly baristas all help to create an inviting perception of quality and comfort.

Of course this is all by design – Howard Schultz, then CEO of Starbucks made a trip to Italy during which he visited some 500 espresso bars in Milan and Verona. He observed local habits, took notes on decor and menus, snapped photographs, and videotaped baristas in action. He was looking to create the right perception.

Now compare this to McDonald’s – what’s your perception of McDonald’s? Probably fast, convenient comfort food; who do you think would have a better cup of coffee, McDonald’s or Starbucks?

Perception dictates reality – Starbucks coffee tastes better because the consumer thinks it tastes better. But, a recent Consumer Reports found that McDonald’s coffee was actually better than Starbucks. That is the power of perception!

So when you start to build a website it’s imperative that you know the perception you want the website to present.

(more…)

Here are the answers to the Web Developer Crossword Puzzle you hopefully took last week (2/6/2008).

I know some of you said it was a little tough, but hopefully you enjoyed it? Besides, it’s good to stretch your brain with a good crossword or sudoku puzzle from time-to-time.

HERE ARE THE ANSWERS:
Web Crossword Answers PDF

Web Crossword Answers GIF

A crossword puzzle for Web developers!

This crossword puzzle’s questions cover such topics as: search engines, CSS, C#, JavaScript, Browsers, Programming and just about anything else Web-related, just like Search-This does.

So get yourself a cup of coffee and download the PDF file or view the image and print it out. Good luck geeks!

There are 25 questions. The answers will be posted next week.

Download Web Developer Crossword Puzzle

You can also click here to view an image of the crossword puzzle and print it should you want to.

Oh No! Not more round corners!

In a previous article we learned how to apply some nice shadowed corners and sides to a fluid width box and I thought it would be good to show a similar method that allows for transparent corners. This will allow the element to sit on any colored background without having to paint the transparent part of the corner with the background color.

I know you might think “Oh no – not another round corner tutorial” but stick with it and I’m sure you’ll find some of this info useful. Round corners are always a bit of a pain to do in CSS so I present here an easy to follow way to make round corners that can be used everywhere. We aren’t going to do anything clever or overly complicated and we aren’t going to bother with shadowed corners/sides because as I mentioned above we have already been there.

Before we begin here is a finished example for you to look at.

(more…)

Have you looked at other people’s style sheets lately? Were you baffled to find square brackets in the CSS code? If so, this article might be of interest to you.

What Does It Mean?

Curly braces should feel comfortable to any CSS author, since you cannot write any useful CSS without them. Regular parentheses should be fairly familiar, too, at least if you’ve used functional notations like background-image:url("/images/bg.png") or color:rgb(128, 128, 255). But square brackets?

The square brackets denote an attribute selector – a concept that was introduced in 1998 in CSS Level 2. An attribute selector modifies a simple selector by imposing an additional constraint on it. Does that sound like Greek to you? (Or like something other than Greek, for those of you who are, in fact, Greek?) Don’t worry, we’ll look at some examples in a short while.

Why Should You Even Bother?

But first, let’s address another question: If attribute selectors really are useful, why didn’t you already know about them? Or, to turn it around, since you’ve managed to get by without them, what’s the point of using them?

The reason you may not have heard about them is quite simple: Internet Explorer for Windows up to and including version 6 don’t support attribute selectors. Since the market share for those browser versions has been well above 80% until very recently, there hasn’t been much incentive for using attribute selectors in public-facing websites.

Version 7 of IE does support attribute selectors, though, and as more and more users upgrade from IE6, attribute selectors gain more interest.

What can those newfangled attribute selectors do then, that’s so useful that you should take some of your precious time to learn about them? The answer is that they allow you to do a lot of things that you hitherto have had no other way to achieve than to pollute your markup with class attributes.

(more…)