Chapter 9 Output and Publication Management


This chapter will explain how your CMS actually gets content out into the world where visitors can consume it.

  • What are the two major schools of thought on templating functionality?

  • What are common features of most templating languages?

  • What is “the surround” and "the operative content object" and how do they relate to each other?

  • What are some advantages to using a decoupled CMS?

  • How might a decoupled CMS communicate with and manage the delivery environment?


On the hard-coding of content in the template as the “load bearing walls” of an implementation

While an editor might be able to change page layout, colors, and other superficial aspects of a page, eventually they're going to run into load-bearing walls. These walls are things that editors cannot change. They either have to work around them, or call a developer to perform major modifications.

Many of these load-bearing walls happen at the template level. The developer bakes items into the template that cannot be controlled by content or the CMS interface. These are the load-bearing walls. How many of these exist and where they're figuratively placed will have a huge impact on the value of the CMS implementation over time.