Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing W3Schools vs mini.css, the Slant community recommends mini.css for most people. In the question“What is the best CSS framework?” mini.css is ranked 4th while W3Schools is ranked 22nd. The most important reason people chose mini.css is:
The whole framework is built on flexbox and works really well on most platforms.
Question Ranking
Pros
Pro Easy to learn
All the tutorials are written in a straightforward and easy to understand way.
Pro Built in editor
Almost every example has a "try it yourself" button which opens up an editor in a new tab. It allows you to play with the example code and see how it works.
Pro Well organized tutorials
All of the lessons are separated into their own pages, which makes it easy to learn about specific concepts.
Pro Great source from Google search's perspective
Pro Flexbox-based
The whole framework is built on flexbox and works really well on most platforms.
Pro Active developer
The developer is actively maintaining the project and responding to any issues and questions.
Pro Minimal
The framework is really tiny, under 7KB gzipped.
This is what makes mini.css stand out, because it looks like a pretty powerful library and it still is under 10KB.
Pro Responsive
It works great on all devices, mobile websites are really easy to develop and view.
Pro Style-agnostic
Few flavours so far, but there is a lot of space for customization.
Pro Great documentation
From basic syntax, templates, examples, customization to-dos and don'ts. The documentation is pretty great.
Pro Supports CSS custom properties (var)
No other framework supports CSS variables right now (as of November 2017). The latest alpha of mini.css supports this feature, making customization even easier.
Pro Accessible
ARIA rules are a priority and it works very well for all users.
Works really well with screenreaders.
Cons
Con Outdated practices / problem solutions
The practices that are shown to solve the problems at hand are rarely, if at all, updated. Usually, their tutorials and learning material is updated only after they see their profits drop.
Con Doesn't care about teaching right
There are multiple errors in the data they show. Although the solutions they show work, they will lead to unmaintainable code. That happens even when the maintainable code alternatives are as easy or accessible to new programmers as the alternatives.
Con Certifications not recognized
Many professionals in IT agree that w3s certifications are not recognized by them and are deemed useless. Good luck finding any respectable professional that accepts a w3s certification.
Con It is for profit
What defines what goes is and what gets fixed on w3schools is what gives them profit and what doesn't (through their ads system).
Con Written tutorials only
While many learning resources offer a mixture of media in their courses (such as videos, challenges etc.), w3schools offers only written tutorials and code editors. This makes w3schools more beneficial as a quick reference rather than a primary learning resource.
Con Archived
Git repo has been archived so it's pretty unlikely to receive bug fixes or new features.
Con Not widely used
A large community is always an advantage especially for open source projects. It means better documentation, continued development, and lowers the possibility for the project to be abandoned in the future since the probability for someone from the community to keep maintaining it is larger if the community is larger.
Con Single developer
There is no team developing this framework, except one guy.
