HTML and CSS Reference
Generally, there are two possibilities: rewrite the whole site from scratch or manually standardize each page (or
page template) one by one. Both seem to need much more work than developers can afford. The first approach often
results in broken links. The second approach requires lots of time and work (unless the site is very small) and can be
performed in only a few cases.
The World Wide Web Consortium suggests a solution: carefully selected sections should be updated
systematically . The most frequently served (most popular) documents can be identified by the Log Validator,
which also tries to find n invalid documents among the most popular ones (as discussed in the previous chapter).
Certainly, the whole project is affected by the deadline and the affordable workload.
In this chapter, you saw a series of step-by-step guides for manually creating fundamental web site components
character by character. By learning the semantic use of structural elements, you are now capable of creating
meaningful markup with a logical flow and a perfect DOM. The carefully created markup provides a high level of
interoperability and can be rendered in virtually any browser running on any kind of device without multiple site
versions. Even if CSS is disabled, the headings, paragraphs, lists, and other site components remain legible, and the
content is accessible to not only the latest browsers but also to very old versions and mobile browsers with limited
capabilities and standard support.
In the next chapter, you will learn widely used standard-compliant best practices that can be applied in your
Thereaux O (2011) Making your web site valid: a step by step guide. World Wide Web
Consortium. http://www.w3.org/QA/2002/09/Step-by-step . Accessed 2 November 2014