Here??™s an example of the old way of doing things:
The Way We Were...
Take a look at this classic example of how Web sites were coded
before Web standards became widely adopted. This is a snippet of
markup from the Microsoft home page, July 1, 2004.
height="19" border="0" ID="Table5">
|
The Top 10 Bene?¬? ts of Standards-Based Coding (continued)
5. Build ?¬‚ uid pages. It??™s easier to code for varying quantities of dynamic content within your pages. For example,
it??™s much easier to create pages that can accommodate varying numbers of items in a given listing or menu of your
e-commerce store.
6. Con?¬? rm your code is correct. Validation services for XHTML and CSS can be used during development to report
instantly on errors in your coding. This provides faster debugging, and the assurance that a page is truly completed
when it both displays correctly on-screen and passes validation.
7. Streamline production. Production is more ef?¬? cient. It??™s too easy for you (the designer) to be sidetracked into
content management, because you are the only person who knows where the content goes in the mass of presentational
markup. You end up being the one to add it??”a tedious job and probably not what you were hired to do. By
adopting standards-based practices, you can provide simple markup rules to the content team and work in parallel
on the presentational aspects, knowing their content and your design will marry seamlessly down the line.
Pages:
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30