Now that we have converted all our static CSS files into dynamic LESS scripts, we can definitely take the chance to replace the quick'n'dirty styling that we put together for demonstration purposes, only with something better. However, before doing that, we need to choose which of these we want to do:
- Keep the Bootstrap framework that was shipped by our ASP.NET Core MVC with Angular template.
- Replace it with another frontend framework such as Foundation, Pure, Skeleton, UIKit, and Materialize.
- Remove it and also avoid any framework-based alternative, thus adopting a pure do-it-yourself approach.
The first two options share the same approach: leverage our styling on a consolidated environment used by thousands of developers; no matter which variant we'll choose, we'll end up walking on solid ground. The latter, however, is an entirely different pair of shoes. Anyone who is into CSS design is well aware of such a debate, which we can summarize in the following single phrase:
The answer is not that simple because either alternative has its set of advantages. Let's try to perform a quick recap of the most relevant arguments.