Chapter 2. Content Management
In the previous chapter we gained an overview by looking at the big picture of the software architecture behind a website. We identified software for content management and software for content delivery as the prime constituents, and we analysed some of their characteristics and variations. It's now time to move to a more detailed level. We'll begin with patterns for content management in this chapter, while content delivery is on our agenda for Chapter 3.
Much of the content management functionality your site requires is likely to be provided by your content management system. Whatever system you choose, the chances are that it will provide you with a content editing tool and a workflow engine, so you will probably not have to develop much custom software for content management. What you have to do, however, is come up with an appropriate content model for your site and make the necessary configurations to your system.
This is where the patterns in this chapter start. They address the following questions:
How can you model the content artefacts for your site? How are artefacts composed from smaller elements? How are content artefacts related?
How can you integrate content into the navigation hierarchy for your site? How do you specify what content should appear on which page?
What about findability? What mechanisms can content editors use to increase the likelihood that users find the content they're looking for?
You can see from these introductory questions ...
Get Where Code and Content Meet: Design Patterns for Web Content Management and Delivery, Personalisation and User Participation now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
