Frontend Web UI Framework Options
Twitter Bootstrap[edit]
Pros[edit]
- Comprehensive and solidly engineered.
Cons[edit]
- Class name changes between versions requiring refactoring
- Difficult to override styles to make a site not look derivative of Bootstrap
Foundation[edit]
Pros[edit]
- Lightweight
Actually, I don't think this is true. It requires some time to install and configure. It also has a need to control the web project, and so doesn't exist easily with other technology (e.g. Django). - Easy to apply a custom look to a site built with Foundation
Cons[edit]
- Reported to not be as well engineered as Bootstrap
- Relies on jQuery for many components (i.e. all you get is the grid if you want to use Angular)
- Non-trivial installation (for the Sass install)
- Doesn't exist easily with things like Django.
- A lot of prerequisites
Materialize[edit]
Pros[edit]
- Designed using Google's Material design principles
- Clear documentation
- Tuned performance in its JavaScript
- Focused set of features, i.e. not bloated
Semantic-UI[edit]
Installation[edit]
$ npm install semantic-ui --save-dev
Then JavaScript and CSS are compiled with gulp.
There are also Git repos for CSS and Less distributions.
Pros[edit]
- Feature complete compared to other frameworks.
- Inherent support for dimmers, flags, feeds, 3-dimensional cards
Cons[edit]
- Non-traditional CSS syntax
- Built with Less.
Skeleton[edit]
Pros[edit]
- Ultra lightweight.
UIKit[edit]
External links[edit]
- Delving Into UIKit (Sitepoint)