In This Chapter
Understanding the need for content management systems
Previewing typical content management systems
Installing a content management system
Adding content to a content management system
Setting up the navigation structure
Adding new types of content
Changing the appearance with themes
Building a custom theme
If you've ever built a large Web site, you'll probably agree that the process can be improved. Experienced Web developers have discovered the following maxims about larger projects:
Duplication should be eliminated whenever possible. If you find yourself repeatedly copying the same XHTML code, you have a potential problem. When (not if) that code needs to be changed, you have a lot of copying and pasting to do.
Content should be separated from layout. You've already heard this statement, but it's taken to a new level when you're building a large site. Separating all content from the layout would be helpful so that you could create the layout only one time and change it in one location.
Content is really data. At some point, the content of the Web site is really just data. It's important data, to be sure, but the data can — and should — be separated from the layout code, and should be, if possible.
Content belongs to the user. Developing a Web site for somebody can become a long-term commitment. If the client becomes dependent on the site, he frequently pesters you for changes. It would be helpful if the client could change ...