Master pages overview
Master page publishing significantly reduces the time it takes to publish changes to your site. With master pages in R8.3, we went back to the drawing board to rethink our publishing model. We wanted to make these changes as seamless as possible, but at the same time allow our clients to upgrade to the new publishing model at their own pace.
In earlier versions of Contensis, our publishing model was based on flat files. When you approved a page, the Contensis parser would merge the template along with the page content to generate a flat file that would then be published to a site via FTP.
The pitfalls of this publishing model meant that changing a template would affect all pages that were using the template. This, in turn, would require them to be republished. While this didn’t cause a major issue for smaller sites, larger sites could see republishes taking many hours – and in some cases days – even from a minor template change.
In master pages, page parsing moves to the front-end. Instead of publishing a single flat file, we now publish a file for each template and sub template, and a file for each page.
These files are dynamically merged together on the front end when the browser requests a page. Making a change to a template or subtemplate only requires it’s file to be republished, not every page that depends on it. This causes a dramatic performance increase when publishing.
Was this article helpful?