Before you decide on which framework you want to build your website on, let us understand first the difference between two best resulting frameworks which are: CMS and Framework.
A CMS is a Content management framework based on the modules rather than code. CMS is easy to access as it doesn’t require any coding or programming. No doubt programmers can also work on CMS as it fastens their job.
Frameworks; widely known as Web application framework is simply based on coding. If you are a programmer and a die-heart fan of coding then web application framework is your kind of thing.
There is a lot of debate going on which framework’s work is more effective. Web developers using Framework states that “Any kind of websites can be built with Framework” but the fans of CMS has to say the same for their websites. It is not the matter of which one acts superior as every framework shares the same basic platform such as, PHP, RoR, Python, .NET and so on.
No offense, CMS makes the work a lot easier compared to framework due to lack of coding and programming. Even if you don’t have programming knowledge you can install and create a whole website with just a CMS. So how do we choose between both?
While looking out for a website design, keep in mind 4 things:
- How much time do you want to spend building your website?
- How flexible do you want to make this site in near future?
- How much money you will take after the end of the project.
- What will be the hosting environment?
How to build a CSS framework?
There are several possible ways to build a framework, but the most common and the most useful is to abstract your common CSS into individual style sheets. For example, you may have a stylesheet that sets up the typography and another that handles the mass reset. You may end up with six or seven different style sheets in your framework, but if a particular project doesn’t need one or two of them, they don’t have to be included. Some of the examples of style sheets are listed here:
reset.css—handles the mass reset.
type.css—handles the typography.
grid.css—handles the layout grid.
widgets.css—handles widgets like tabs, drop-down menus, and “read more” buttons.
base.css—includes all the other stylesheets, so that we only need to call base.css from our (X) HTML documents to use the entire framework.
We then store the framework in a single location and have every site pull it in from there. Then at the end, there are site-specific style sheets for each site which overwrite and add to the framework’s default when necessary.
As we have seen above the 4 simple things that we need to keep in mind but this works effectively when we are working on small projects and don’t want to spend a lot of time and efforts on it but of course the big sites need a Web Application framework as a solution to your less time consumption.
As a conclusion, it always depends on the size of which project you are working and how much time you are willing to give it. Every framework is built for a reason so as many tools you want to include in your project and want to be a professional developer. So it no more matters you choose a CMS or a Framework. Just choose the best framework as per your situation and availability of time.