How to Choose a Kentico Development Model?

The Kentico CMS has managed to successfully position itself as one of the most preferred enterprise Content Management Systems for the technology industry. Its popularity can be judged from its widespread usage and deployment in more than 18000 websites developed across 90 countries. The integration of a Content Management System becomes necessary if the websites being created are designed to deal with large sets of information that needs frequent additions, deletions and upgradations.

Kentico is basically an all-in-one integrated marketing solution for developers as well as businesses, which offers solutions in online marketing, content management, intranets and e-commerce, among others. The Kentico development process provides three different types of development models for developers – Portal Engine, ASPX Template and the MVC (Model View Controller). This article highlights the various advantages, disadvantages and implementation details of each of the three development models available in Kentico.

Portal Engine provides a browser-based interface for developing as well as designing page layout for the sites. It is the easiest approach to build websites as it utilizes the built-in webparts offered by Kentico, minimizing the need to have knowledge of programming for basic components. But, while building custom components, the developer has to have knowledge and programming capabilities in Visual Studio. A major benefit is that the development of websites is quite fast, besides being easy as the site can be built using just the browser. A proprietary development architecture model, it can act as a deterrent in using this approach.

This is a standard development model to be followed by ASP.Net developers following the .NET architecture and developers are expected to have some basic knowledge of VB.NET or C# as it follows the standard ASP.NET architecture. These templates enable the placement of custom codes and controls onto the page while web forms (or ASPX pages) designed by the developers are used for displaying content from Kentico. The only disadvantage faced with this development model is that the browser-based admin interface panel doesn’t allow for complete management of the design elements being integrated into a web page.

It is based on the ASP.NET framework and follows the Model-View-Controller architecture, which requires developers to be familiar with programming, as well as knowledge of ASP.NET MVC. The developers implement model as an object, MVC controller as a class and view to render pages. A major disadvantage of using this approach is that Kentico in itself does not follow the MVC architecture; hence the built-in components cannot be used if full MVC architecture is to be maintained.

It is recommended that developers use the Portal Engine for Kentico development, but both ASPX Template and MVC can be used if the preferred development tool is Visual Studio. These two models (APSX Template, MVC) can also be used if existing functionalities, built on ASP.NET architecture, are to be integrated into the application. Additionally, these models can be combined into a single website using Kentico development.

A web development California company can also offer insights into which of the three would best work for the type of application a client has in mind.

Sponsor Ads

• Ad Space Available - Rent it Now!

Report this Page

Created on Dec 31st 1969 18:00. Viewed 0 times.

Share on APSense

Comments