To avoid
this, it??™s best to rigorously police content, maintaining a small library of the prototype versions
and exercising stringent version control.
It helps to create a file structure on the local or server hard drive that mimics the structure
of the website. For instance, a website category might be ???About Us???; inside the content
directory, there might be a sister folder called About Us containing text files for each HTML
page. Those text files should have descriptive file names like About ??“ Company History
[ver2.3 ??“ 20061203].txt, which signifies version 2.3 of the company history page, created
December 3, 2006. (Regular text files work best for web content because they reduce
the content to plain ASCII characters, stripping out any formatting left over from Word
and e-mail programs, as shown in Figure 4-3.)
ARCHITECTURE AND NAVIGATION
73
4
Figure 4-3. Managing content for a website requires explicit version control so that the correct
content appears in the final site.
Inside the actual text file, keep the content organized. At the top of each file, write the
page title and its metadata information, including description and keywords.
Pages:
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185