Even in 2021, I am still having multiple conversations with existing Kentico Xperience clients from a business, executive, and/or marketing standpoint about moving from Portal Engine to MVC. Most of my conversations revolve around people who are having difficulties to fully understand why a rebuild of a site in MVC is necessary. These conversations around the migration from Portal Engine to MVC are often times thought of as only purely technical conversation. This is actually a common response, as many of the benefits are stated in a technical way. However, I’m here to tell you that this technical only consideration should be broadened into multiple other considerations.

That motivation is why I have created this blog post series. I’d like to fully answer the question of “Why MVC?” once and for all. I figure that if I am having this conversation multiple times, there must be other people having it to with their clients. Why not answer it fully in writing and in a holistic way, that way all of us in the Kentico Xperience community are able to use it as a resource for all clients out there who have Portal Engine based Kentico Xperience sites and are considering what to do next.

When maintaining your Web Forms based Portal Engine applications, sooner or later, there will come a time when you will need to decide whether to upgrade to the latest version that supports Portal Engine or to take the leap and migrate over to MVC.

From what I understand, widgets are the minimal unit in Kentico MVC to set up variants of content for context marketing and A/B testing. A landing page is an example of a content type to apply thes...

Working in the new Kentika 13 in the latest beta version on .net Core.Created a new page type of news page. I want to get a given NewsPage but only allows the TreeNode to be returned.Throws an err...