Any exploration of the subject needs to consider what of our framework CSS Grid is going to replace.
The question of whether to use Grid or a framework is flawed, as CSS Grid is not a drop-in replacement for the things that a CSS framework does. All these things are done in reference to your own specific needs rather than very generic ones. The alternative to using a third party framework is to write your own CSS - that might involve developing your own internal framework, using a bunch of common files as a starting point, or creating every project as a new thing. The important factor is that these are something developed externally to you, without reference to your specific issues. You might argue these are really component libraries, but many people (including their own docs) would describe them as a framework so that is what we will use here. In this article when I talk about a framework, I’m describing a third party CSS framework such as Bootstrap or Foundation. I hope that by unpacking these reasons, I can help you to make your own decision, in terms of what is best for the sites and applications that you are working on, and also for the team you work with.
You will discover that the reasons for using frameworks are varied, and not simply centered around use of the grid system contained in that framework. Have you ever considered whether CSS Grid can actually replace the need for CSS frameworks or third-party component libraries? In doing so, Rachel Andrew discovered a range of reasons people use a third-party framework and the positive and negative things about doing so.Īmong the questions I am most frequently asked is some variety of the question, “Should I use CSS Grid or Bootstrap?” In this article, I will take a look at that question.