Popular posts

Skeleton is also smaller and doesn't cover everything, which is actually a plus I think. :)

What if you need to build a bigger app. Will you still use Skeleton? So basically you will use 2 different frameworks for different app sizes?

Absolutely, you don't need to overwrite every single element, it saves so much time :) But for prototyping purposes, i still go with bootstrap, this way i do not touch any css ! ( Css is still kind of a pain for me... )

Well, depends on the complexity of the ui of the big app, if i compare to bootstrap's elements and i need to make a lot of changes, i'll avoid using it and go for something like skeleton. But if bootstrap's elements just need a little change to be ok, you'll save time to go with bootstrap ! ( replace bootstrap with any other big CSS framework of your choice )

@Kristen Garnier but why use Skeleton when you can use Bootstrap (or any other big framework) with minimal settings? So there is no need to have to learn 2 frameworks.

Because Skeleton does not overwrite every single element in the page, sometimes it can really be time consuming to overwrite style for every button (not mentioning the work to avoid using !important ), and apply yours instead.

The cost of learning a CSS framework like Skeleton in really low, i mean it is really verbose and there is like 10 Api to know for mastering this framework ^^