PUBLISHER MASTER PAGES CODE

NET Framework 1.0 release in 2002, which supported Web Application projects and Web Site projects. I've picked these two as these technologies are available on the Crownpeak hosting servers and they are simple enough that we can use them without having to introduce more complexity than necessary.ĪSP.Net Web Forms was included in the original. Generically we refer to this as a master page pattern.ĭepending on the technology available in the content delivery environment, there are a number of ways you could implement this pattern. We will publish out the nav wrapper as an independent asset and change the content template output to include the nav wrapper at or near content request time. The way to solve this is to take advantage of server-side technologies on the content delivery side. It also means that any other content changes may be stalled while waiting for the publishing job to complete.

However, there is a timing problem: while the publishing is happening, visitors to your site may have an inconsistent experience: seeing the updates on some pages and not others until the publishing job completes. The CMS can handle publishing jobs like this without any problems at all - we have seen publishing queues with tens of thousands of assets in them. However, it does mean that we need to republish every page on the site so that the changes can be integrated. Similarly, any content changes only need to be made to one content asset.

PUBLISHER MASTER PAGES CODE

This is very convenient but does suffer from one problem: what happens if we need to make a change to the content or the design of the nav wrapper elements? The changes to the template code are convenient because we only have one template to change. The result is that when pages are published from the CMS to the content delivery environment, the files that are delivered look like the ones from the design, with the header and footer inserted at publish-time by the CMS. Rather than have the header and footer configuration entered by the content editor on every page, the content and the design is extracted out and put into a 'nav wrapper' that is then included in the output form each page template using the Out.Wrap Template API call. When you first start an implementation on Crownpeak, one of the first things you'll need to do is identify the shared elements across all the pages on your site - typically this is the header and footer areas.

Publisher master pages