CMS or Not CMS

Nowadays, we have two options to build web application. The first option is using web application framework such as ASP.NET core, ASP.NET web form, Django, and many mpore. The second option is using web application Content Management System such as Umbraco, Kentico, Dotnetnuke, or Orchard. On this article, we will discuss when to build with CMS vs Framework. CMS CMS is built with the existing framework. For example, Orchad and Umbraco is build from .Net Core. Basically, you dont need to understand the framework if only you just want to use the CMS. But if you want to extends the capability of the CMS you should understand the framework and how the CMS works. You can use CMS if 1. You need dynamic content for your customer 2. Your customer write the content and push into your website 3. User doesnt have a lot interaction with your website Typical scenario for CMS: company profile, personal website, and blogs Framework Framework is build by the platform stack that we choose. Framework provide programming layer for the user interface, middleware, dan data services. You have a lot freedom with Framework. However, you need to create a lot of routine from the beginning. Framework provides minimalist template but really extensible rather than CMS. You choose framework if 1. Your web requirements are custom  2. Your customer focuses to manage and to store the data 3. User has lot interaction with the website  Typical scenario for framework: information system, web applicatiob, and data driven application Typically, i will start my journey with CMS, and when i feel so many to extend i will choose framework. How about you? 

Topics Highlights

About @ridife

This blog will be dedicated to integrate a knowledge between academic and industry need in the Software Engineering, DevOps, Cloud Computing and Microsoft 365 platform. Enjoy this blog and let's get in touch in any social media.


Month List