Framework vs Content Management System

By Abdeali Chandanwala

Some theory first

▪ When we use the terminology “Framework” we are more often talking about Web application framework . A web application framework is simply based on coding. If you are a programmer or a web developer that loves coding you often choose a Web application framework for your projects.
▪ A CMS is a Content management framework and it is based on the modules rather than code. Anyone can handle a CMS as it doesn’t require any coding knowledge. Of course programmers can also choose a CMS as they can do their job faster.

▪ To put it in simple words, a CMS provides you with a back-end (with a host of plugins and components) like Joomla, Drupal, WordPress, etc so that you can manage front-end where as a frameworks doesn't.
▪ A framework such as CodeIgniter, Kohana, CakePHP, Symphony, etc provides you with readymade classes and libraries BUT you have to use them and build your site yourself.

▪ You can build a CMS with a framework, but you cannot build a framework with a CMS.
▪ A CMS is just that - a Content Management System.

▪ A framework is a collection of libraries to build an application.

▪ A framework doesn't "give" you anything, it's just a skeleton.
▪ A CMS will give you a Functional site, and it's just a matter of themeing and adding content ▪ Frameworks create very good presentable web applications,whereas CMS could be fast but can't create as presentable quality as frameworks can.

There are lot of fights…
▪ There are lot of misunderstandings about what a framework and what a CMS can do. Lot of fans that use CMS they are saying that “We can do everything with a CMS” and the fans of the frameworks are “No we can do everything with a framework” and so on…

▪ As a fan of frameworks of course I will have the same opinion but actually this is not true! The truth is that as we use the same base (PHP,java,python,. NET… e.t.c.), we all can do everything (well almost everything, but still). ▪ Even the myth that CMS doesn’t use a good structure isn’t truth. For example Drupal 8 is based on Symfony framework, a very good object oriented web application framework.

So what do I choose?
▪ Nowadays the CMS is more popular than the Web application Framework as it is really easy to use it. Even if you don’t have programming knowledge you can install and create a whole website with just a CMS. So what to choose? ▪ It is always about four basic things that you have to think before you choose a framework or a CMS in my personal experience: 1. How much time you want to spend? 2. What do you want to do and how flexible has to be this project in the future? 3. How much money (if it matters) you will take after the end of the project. 4. What the hosting environment will be ▪ For the customer it doesn’t really matter what tools you will use. The thing that matters is to have their job done

Conclusion
▪ • Evaluate each project’s needs
▪ • Know your tools ▪ • Build your foundation & library of reusable codes

▪ • Plan properly, but change is inevitable

And finally a conclusion…

▪ So as a conclusion I have to say that it always depends of what you want to do and how much time you have to deal with it. I believe that every tool is build for a reason so as many tools you know (frameworks or CMS), so flexible you are as a professional developer. So it doesn’t worth it to be a CMS or a Framework fan. Just choose the best tool for you situation and that’s it.

Sign up to vote on this title
UsefulNot useful