Suggestions for Cardinal 2.0.0 about cardinalcss HOT 6 CLOSED

Hey Chris,

Nice to hear that Cardinal will evolve.

• Keeping Cardinal small but efficient is a balance game. I vote for you to keep on that direction. We really don't need another bootstrap. Things that are not 'vital', just be left out.
• IMHO I would not switch to EMs. IE8 is not worth to save http://matthewmorek.com/blog/dropping-ie8-support, unless you have a specific reason for that.
• Responsive Typography. I would love to see more on this topic.
• Grid. Cardinal's grid is great and it works fine. However, it can be overkill. How about just give to the user the 'tool' and let them decide what/how they want to build their stuff. For example, instead having a 'complete' grid system with several classes, why not something like https://github.com/arnaudleray/pocketgrid.

These are just a few things that I can think now. More to come. :-)

from cardinalcss.

@danielzilli - thanks so much for your feedback! I agree with a lot of these sentiments. I think we can keep using REM units. Zurb's Foundation is even is using them now.

I like Pocketgrid, and that is definitely an interesting concept. I was actually pondering whether I should beef up the grid system (adding push & pull, offsetting, etc) ... but you make a good point that it could be overkill. I'll have to think about this a bit more.

Also, I am toying with idea of creating "add-ons" for Cardinal, things like responsive tables, common UI elements, etc, that aren't included in the default Cardinal build but can be downloaded separately if they are things that you need for a particular project.

from cardinalcss.

@cbracco - add-on is a great way to expand Cardinal without making it bloated. I think it's a nice approach. 👍

from cardinalcss.

I’ve pushed up a new branch for 2.0.0 if anyone cares to peruse before I launch it officially...

from cardinalcss.

Hey Chris,

Great release! It looks good. Nice job!

from cardinalcss.

Thanks @danielzilli! 🤘

from cardinalcss.