Liam GoldfinchLiam Goldfinch

Liam Goldfinch

.NET developer

Using Page Templates in Kentico MVC

The launch of Kentico 12

Since the launch of Kentico 12, we now use the MVC approach as our preferred and default development route. This is primarily down to the key features that our clients love being migrated from Kentico’s Portal Engine. For example, in Portal Engine, clients enjoyed using Kentico’s admin panel to build new pages using widgets and seeing exactly what the page looks like before publishing it. This was not possible before Kentico 12. As such, the CMS solution launched the much-loved feature as a part of Kentico 12.

Page Builder functionality

Kentico 12 introduced Page Builder functionality, allowing content editors to create pages using different sections for different layouts and configure MVC based widgets to add relevant content.  Although this was a great addition, making websites entirely widget-based does have its side effects.

For example, if every component on a site is built as a widget when a content editor is creating a brand-new page, it is entirely blank from the start. This means editors need to add the same banners, sections, widgets, etc. repeatedly for every page, even if it was similar to another page they’ve already created. To tackle this issue, Kentico made another addition to their page template functionality with the introduction of the Service Pack.

MVC Page Templates

The launch of Kentico 12’s Service Pack brought the much-needed functionality of MVC Page Templates. Content editors were finally able to save a snapshot of preconfigured sections and widgets of a page builder enabled page, and then reuse that for other pages going forward.

This is a significant timesaver for content editors when building a similar layout repeatedly which is often the case on websites, such as campaign landing pages, news articles and blog posts.

This article was originally posted over on the NetConstruct blog.