They seem useful for prototyping design decisions, but less so for structural needs. Ie, i'm pretty bad at design, i can iterate to something i like, but it's slow and not something i enjoy. If i need a design for a side project, i'm not going to want to spend much (any, really) time thinking of fonts, colors that work together, etc. Frameworks can make that easy, atleast.

Also, there are elements of design in structure, too - ie how consistent you are with spaces between elements. I don't really want to think about any of these.

Thanks for your feedback.

Actually Bootstrap v4 provides an opinion to use flex box instead of the traditional grid. http://v4-alpha.getbootstrap.com/getting-started/flexbox/

I would say your suggestion is good. I don't have a convincing reason that `container-side` being a part of the framework. I'll consider to remove it.

What kind of content is never visible on mobile? `Scan the QRCode to view on mobile` and `Go to top` is a kind of this content.

Why does it have to be on the side? I think it's a good design to guide people to view on mobile. Or where do you think it can be?

Thanks!

Apologies for the tone in my previous comment. I guess it came off pretty harsh. Good work on creating and releasing something to the public. Upon looking again today, I like the overall approach you've taken and it seems very reasonable.

The `container-side` thing just feels very opinionated to me. I'm not sure it belongs in a framework, but that's totally your call.

I would argue that big frameworks like Bootstrap still have a reason to exist because they provide interactive, component based functionality.

It's actually small frameworks like this one that are increasingly useless. Consider that most of the provided functionality can be accomplished with 2-3 css properties.