Head First Web Design

Errata for Head First Web Design

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page Ch.8

Typo with use of "ToDo" appears on multiple pages in chapter 8. 291, 296, 300, 313, 314 : Change "ToDo" to "to do" 300, 302, 307, 208, 311, 313, 318: "ToDo" on blue sticky notes should read "To Do"

Anonymous  Mar 19, 2009  Mar 01, 2009
Printed
Page 11

NDQ answer 2: "Donít skip IA, as it can often determine parts of the design when you come to layout the site." Should read "lay out"

brittany2784  Mar 19, 2009  Mar 01, 2009
Printed
Page 13

The heading should be in sentence case. Change "Determine your Top Level Navigation" to "Determine your top level navigation"

Anonymous  Mar 19, 2009  Mar 01, 2009
Printed
Page 28
thought bubble

"Come on, Writing is writing." should read, "Come on, writing is writing."

Anonymous  Mar 19, 2009  Mar 01, 2009
Printed
Page 30
Exercise

"Rework the copy so that follows the scannability checklist." You left out the word "it"

Note from the Author or Editor:
FIx the second sentence at the top of page 30 to read: "Rework the copy so that it follows the scannability checklist."

Kevin Olson  Mar 30, 2009  May 06, 2011
Safari Books Online
47,48
Sharpen Your Pencil instructions

theme's (Write down two possible central theme's for Mark's site.) should read "themes".

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
49

layout (How you layout your site will affect the overall visual Metaphor...) - in this case should be 'lay out'

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
50

breaks (Whitespace helps to breaks up...) should be 'break' users (focuses the users eye towards content.) - missing apostrophe

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
51

it's (Not every site needs a gorilla-themed metaphor or a snazzy newspaper layout to reinforce it's content.) - remove apostrophe

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
58

"I really can't tell where you guys are going for here." Should read "...what you guys are going for here."

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
64

layout (Grids also provide a foundation that allow you to layout your site with solid order and visual logic.) In this case, should be 'lay out'

Anonymous  Mar 19, 2009  Mar 01, 2009
Safari Books Online
65

- "let tell them" (and let tell them to give you as much feedback as possible...) remove 'let' - meet (Make sure that each meet his needs...) should be 'meets'

Anonymous  Mar 19, 2009  Mar 01, 2009
Printed
Page 79
handwritten note beneath 'Home' category

'...under the cateogy headings...' should be '...under the category headings...'

koster  Dec 09, 2009  Mar 01, 2009
Printed
Page 79
card beneath 'Products' category

'Oudoor' should be 'Outdoor'

koster  Dec 09, 2009  Mar 01, 2009
Safari Books Online
87
2nd paragraph

In the 2nd paragraph, the word "that" is used instead of "than".

Note from the Author or Editor:
Change in the 2nd paragraph: "...different (and better) that what you came up with..." TO: "...different (and better) than what you came up with..."

Anonymous  May 04, 2009  May 06, 2011
Printed
Page 128
rpm.css code

background property of #026dc0 outputs a blue background, not the beige as shown on the next page.

Note from the Author or Editor:
On page the 128, the body background rule should read: "background: #fbf9ef;" not "background: #026dc0;". This is the only page where the error appears and the same CSS later in the chapter, as well as the downloadable code have the correct value.

Josh Feck  Jan 11, 2009  Mar 01, 2009
Printed
Page 178
second code highlight @ #header

It seems that the printed visuals are not correlating to the hexadecimals in the code. Where #adbc49 produces a light to mustard beige brown, the printed example and text revere to a dark brown. Like the character says: "The site feels heavy and oppressive." This darker shade is the #945737 or the second to last in the color swatch.

Note from the Author or Editor:
On page 178 HEX code #adbc49 needs to be changed to "#ad6c49" This also needs to be changed in the #header CSS rule on the same page as well in the code at the bottom of 181. I think these issues also have to do with the color difference between print and monitor display colors.

Frank Klaver  Mar 19, 2009  May 06, 2011
Printed
Page 180
text linked with color wheel figure

*Comment linked with left yellow circles it says "Further form the center results in a darker color" should say: "Further from the center results in a lighter color" * Comment linked with blue circles included in color wheel: it says: "Closer to the center results in a lighter color" should say: "Closer to the center results in a darker color"

Note from the Author or Editor:
*Comment linked with left yellow circles it says "Further form the center results in a darker color" should say: "Further from the center results in a lighter color" * Comment linked with blue circles included in color wheel: it says: "Closer to the center results in a lighter color" should say: "Closer to the center results in a darker color"

Santiago Martin Alfageme  Apr 21, 2009  May 06, 2011
Printed
Page 200
handwritten note above ul code

'...may appear om the site.' should be '...may appear on the site.

koster  Dec 09, 2009  Mar 01, 2009
Printed
Page 212
3rd paragraph

"The nice thing about blocks-and why they are great for navigation elements-is that they all automatically line up horizontally." No they do not of course. We are looking here at a unordered list <ul> and it would "automatically" display verticaly. We need to use CSS to place the block inline in order to display it horizontal. I know that the next picture description states that the <li> is displayed inline so how can that have been overlooked by the technical reader editor of the book. I asume he or she knows CSS or XHTML ? Sorry for being a pain but this information is seriously confusing for some one with minor understanding of the subject. (hey not me! of course...)

Note from the Author or Editor:
Please change the paragraph below the code that starts with "But we can adjust..." to: "But we need to make the navigation lists behave like inline elements so that they line up next to each other horizontally. We can accomplish this using CSS by changing the list to display inline or floating the list items left or right:"

Frank Klaver  Mar 26, 2009  May 06, 2011
Printed
Page 218
Bottom right "handwritten" note.

The note reads, "Each link has it's [sic] own class. so we can assign the right icon to the background." As a minor nit, the period should be a comma. As a larger complaint, here, as in several other places in the book, the authors/editor use apostrophized "it's" when they should use possessive "its" (sans apostrophe). It's a basic error in English usage, and I marvel that it slipped through editing. I've now spotted it literally half a dozen times, and each time it's annoying and distracting. I hope such errors do not indicate a decline in the quality of the *Head First* brand.

Joseph Lockett  Feb 28, 2009  Mar 01, 2009
Printed
Page 228
2nd paragraph

The exercise asks to read the text at "www.headfirstlabs.com/books/hfwd/chapter06/text" and to keep track of how long it takes. However, no such site appears to exist. Additionally, this link refers to 'chapter06' when in fact the exercise occurs in Chapter 7.

Note from the Author or Editor:
I have gone through all of chapter 7 and made note of all references to online content. Submitted updated online material to the Head First webmaster that will take care of any missing content. On page 228, the link should read: http://www.headfirstlabs.com/books/hfwd/ch07/text/index.html.

shred22  Jan 21, 2009  Mar 01, 2009
Printed
Page 237
link rel in sample html

The "don't forget to link your css file!" side note points to the red lantern.css from chapter 1.

Note from the Author or Editor:
In the HTML code example on page 237, the file linked in the first <link> tag needs to read "hipster.css" instead of "redlantern.css."

Frank Klaver  Mar 30, 2009  May 06, 2011
Other Digital Version
237
exercise files

The href="redlantern.css" also apears in all exercise files related to this chapter. Correction would be: "hipster.css".

Note from the Author or Editor:
I will fix this in the files and resubmit them posting to the Head First Labs site. This issues was addressed in another errata submission for the text in the book.

Frank Klaver  Apr 01, 2009 
Printed
Page 286
handwritten note beneath googlestory.html listing

'...is still and HTML file...' should be '...is still an HTML file...'

koster  Dec 09, 2009  May 06, 2011
Printed
Page 292
handwritten note on right side of Exercise Solution

"...don't worry, there's still in our...' should be '...don't worry, they're still in our...'

koster  Dec 09, 2009  Mar 01, 2009
Printed
Page 317
first paragraph of email message

'...forward with distribuint our tax...' should be '...forward with distributing our tax...'

koster  Dec 09, 2009 
Printed
Page 332
Revised question 1

'Do you agree of disagree that...' should be 'Do you agree or disagree that...'

koster  Dec 14, 2009  May 06, 2011
Printed
Page 348
First printed paragraph (Frank)

'...to figure it out a design problem...' should be '...to figure out a design problem...'

koster  Dec 14, 2009  May 06, 2011
Printed
Page 351
'Space' paragraph

'...a quite coffee shop...' should be '...a quiet coffee shop...'

Note from the Author or Editor:
'...a quite coffee shop...' should be changed to: '...a quiet coffee shop...'

koster  Dec 14, 2009  May 06, 2011
Printed
Page 370
Bottom annotation

"Audio2Go" should read "Audio-2-Go"

Anonymous  Mar 19, 2009  Mar 01, 2009
Printed
Page 413
Handwritten note underneath image

'...surprised what and email can do.' should be '...surprised what an email can do.'

Note from the Author or Editor:
'...surprised what and email can do.' should be changed to: '...surprised what an email can do.'

koster  Dec 14, 2009  May 06, 2011
Printed
Page 414
The Foo Bar email message

'...we appologize for the misunderstanding...' should be '...we apologize for the misunderstanding...'

Note from the Author or Editor:
'...we appologize for the misunderstanding...' should be changed to: '...we apologize for the misunderstanding...'

koster  Dec 14, 2009 
Printed
Page 417
Bottom gray box

The Job Poll has 8 questions and then you look at the answer key to see where you fit in the design world. The answer key pairs up questions 1&6, 2&8, 3&8, and 4&6. What happened to questions 5 and 7? Why aren't they listed in the answer key?

Note from the Author or Editor:
In the box at the bottom of 417, the final sentence should have 4 and 5 in circles instead of 4 and 6.

JollyvilleChick  Mar 26, 2010  May 06, 2011
Printed
Page 439
First paragraph

"...its note really a chapter, its more..." should be "...it's not really a chapter, it's more..."

Note from the Author or Editor:
"...its note really a chapter, its more..." should be changed to: "...it's not really a chapter, it's more..."

koster  Dec 14, 2009  Mar 01, 2009
Printed
Page 447
TOP

"All ... even in the smaller content hAAders (headers ?)" "That crewate (create ?) a sense ...."

Note from the Author or Editor:
Correct the following typos: "All ... even in the smaller content hAAders" (should read "headers") "That crewate a sense ...." (should read "create")

Patrick  Apr 30, 2009  Mar 01, 2009