WEB STANDARDS CREATIVITY

Worries
Introduction text
Name and role of worrier
Further descriptive text
Worrydone
Introduction text
Name and role of worrier
Further descriptive text
Recently worried about
Worry item
Worry item
Worry item
© Stuff and Nonsense Ltd.
A demonstration site by Andy Clarke
Top
These appropriately identified divisions not only add the structure that will enable you to develop the visual layout with
greater ease, but their identifiers also serve to enhance the meaning of the content that they contain. This minimal use of
divisions should always be your approach in a content-based workflow. This places the content, rather than the visual layout,
at the center of your thinking when writing your markup.
If additional divisions are required to accomplish any specific design, these should be added one at a time until your design
can be achieved. For this design, only one additional container division, wrapped around all of your elements, is required.
This container is a common approach for allowing you further styling options in addition to the html and body elements.
All document content
You may have noticed that, in this markup example, no additional identifier or class attributes have been added, despite
the complexity of the design. Such presentational attributes should rarely be required, as your markup already contains all
the elements and attributes (href, title, alt, and so on) that you should ever need when you take a mature approach to
your standards-based design.
chapter 4 Designing for Outside the Box
87