Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Semantic Grid System 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 Semantic Grid System is ranked 36th. 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 Responsive layouts
With Semantic.gs, you can manipulate the grid using media queries.
article { .column(9); }
section { .column(3); }
@media screen and (max-width: 720px) {
article { .column(12); }
section { .column(12); }
}Pro Fixed and fluid layouts
By default Semantic Grid System has a fixed layout. But switching to fluid, percentage-based layouts is easy. To switch from pixels to percentages, simply add one variable:
@total-width: 100%;Pro Runs on SCSS, LESS, or Stylus
Semantic.gs supports all modern CSS pre-processors sucha as Sass, LESS and Stylus.
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 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.
