The book doesn't have a lot of weaknesses, considering the niche it fills. Beyond a few nit-picky techie things I might have included had I'd written it, this book is a great beginner's resource for writing HTML and designing Web pages. It's also a nice resource for those less-techno savvy teachers interested in incorporating Web design and HTML into a writing course. Some nit-picky points:
While Batschelet says that her book's chapters can be used in any order, if you know nothing about HTML (her own assumptions stated in the Preface), you must start with the first two chapters. Still, the organization of the book's chapters really builds nicely. Understanding how tags, attributes, and values work, for instance, is crucial to creating tables and fiddling with page colors and cascading style sheets. These strategies are well sequenced.
Chapters 2 and 6 discuss safe color selection, but neither offer any hexadecimal color charts for students to refer to quickly the only real way to control color on a wide variety of monitors. Granted the book is in black and white, so a color chart with hex numbers would be nearly impossible to refer to, but even the most basic colors could have been offered using a spectrum in each of the three color categories (red, green, and blue) without showing each
color gradient. More importantly, a more adequate discussion of the hexadecimal color system would make it easier to see why these numbers should be used over the sixteen predefined color names. There are several useful Web sites offered at the end of Chapter 2, showing hexadecimal color charts, but if a student doesn't have a computer with an Internet connection handy while reading the book, these will most likely be lost in all the material and other sites offered. And since there's an easier option for the beginner to define colors, namely the predefined color names, like "silver," "gray," and "green," hexadecimal color values won't seem readily usable (and they should be). These color names do not give much control or choice to the designer, nor do they give a burgeoning Web writer a chance to use the hexadecimal colors (a must in my book).
 In Chapter 7 when discussing Links, she uses the ALINK attribute in her illustration but doesn't mention it otherwise. It's also not in her reference table at the end of the chapter. While not a crucial part of the chapter, it may cause confusion to someone unfamiliar with this attribute, particularly since it is separate from the other two items she does discuss in this part of the chapter, LINK and VLINK. A few pages later, Batschelet discusses relative links and their protocol a bit unclearly. She doesn't explain how this kind of link is used with a directory structure. She mentions "large directories" and moving "up one level to the next level of directories in a site," but if a student doesn't understand the directory structure system or what "moving up" means, then this section of the chapter can be mystifying. These issues could be solved with a simple diagram illustrating a sample directory structure and how relative link protocol works in it.
Finally, there is no discussion in the book on how to design the actual directory structure of a Web site. She provides plenty of good advice on Web site structuring (how individual pages connect with and work in the "web" of a site), but none on the directory structure all these pages must be filed in. While this aspect of a Web site is unseen by a user, it is crucial if a site is to be updated quickly and efficiently by a Webmaster. A well thought out directory structure can mimic the Web site's structure, but more importantly, it can help a Webmaster know what files are present on the server, which can be updated or deleted, and where all the pictures are, the help files, etc. Particularly for those who must worry about overall file capacity (most ISPs have Web site space limitations) on their servers, this aspect of a Web site is very important and always a consideration.
|