The Model-View-Controller method, or pattern, of building CMS websites divides backend (Model) and frontend (View) development from each other and from their system of communication (Controller). This ‘separation of concerns’ allows developers to work on all parts of development simultaneously instead of consecutively or iteratively.
Teaming up to save time
The immediate benefit of being able to deploy your frontend and backend development teams side by side is that the project is going to be built a lot faster. Before Kentico started introducing MVC development in Version 12, one side was necessarily always waiting for the other before they could begin their part of the work. MVC opens up the work floor. Once design and functionality of a site is agreed, both backend and frontend can get to work.
Keeping the data under control
One of the reasons this is possible is that MVC allows the frontend to make use of mocked data more easily. In other words, they don’t have to wait for the data in the Model to be up and running to start testing how it will work in the user interface, or View. This doesn’t just save time. It’s also potentially more secure. The more sensitive the real data, the fewer unnecessary eyes you want on it. For industries that handle lots of personal details, such as the medical or educational sectors, for example, this type of data mocking could keep access to the real data strictly limited during development and testing. MVC’s way of compartmentalising data also benefits website owners because it is never stored on the web page itself—the View. It is only ever transmitted there via the Controller. As a result, it can be transmitted to any View via the Controller, whether that’s a mobile site, an app, a smartwatch or other platform. It doesn’t require a different backend (Model) in order to do so because a separate View (frontend) can be created that suits each platform but which works with the same Model. That saves time, of course, and money. But it also saves a lot of managerial hassle when it comes to keeping content consistent across platforms.
Creating a space for content creators
Controlling content updates on the frontend is made easier overall with MVC methodology. That’s easiest to see in the Kentico Page Builder, which is a drag-and-drop layout editor. During the project build, developers create widgets for different types of content, which can then be deployed as desired throughout the website. It makes updating pages with new content simple to execute for website managers because it limits the parameters of the content automatically. You can’t accidentally mess up the layout of the page because the possible locations and size options of the widgets will be pre-determined. MVC is where .NET CMS development is headed in the long run. And there is value in keeping up with current technology for the sake of it. Everything does get faster and more secure, which keeps you competitive within your market. And MVC does have genuine business benefits in terms of time and money saved both during build and deployment, but also in day to day website management. Want to talk more about how MVC is going to benefit your business? Call Technical Director Ben Franklin for a chat.
Get more of this by subscribing to our regular newsletter