No grid system? :p

[erutan]

This is a little tongue in cheek, but as someone who always used foundation in a semantic way (only outputting typo, forms, etc and using most of the rest with @extends etc) I've never been a fan of grid markup.

Before CSS Grids became widespread, I'd use https://github.com/at-import/Singularity on top of Foundation - the ability to do so was one of the deciding reasons to adopt Foundation back in... '14?

Would it be a bit too aggressive to say people just be using CSS Grids? There's a definite use case for keeping some kind of class based non-semantic grid system for people that don't spend a lot of time in CSS, but it'd be more best practicey to just leave a legacy grid system out IMO.

[joeworkman]

Foundation 7 will keep the XY grid around. It will be optional. I want to develop some helper classes for common Grid layouts. I am open to feedback on that. Looking for ideas on where to take that.

[erutan]

It's always been optional - I don't necessarilly think it's a good idea to ship without one, but it might be worth mentioning in docs that one can just use css-grids instead (it's a lot more powerful and cleaner, even if it has a bit of a learning curve).

[katie1348]

I have moved to the flex grid, so this is a bit academic for me.

But, one of the things that makes Foundation so powerful is the fact that it has all the bits you need, without having to go hunting for a dozen other packages that will work. Then there is the maintenance hassle and the making it all work again hassle with disparat packages.

So, I am in favour of having a system that is a whole system, even for the bits that I personally do not use. This applies to the plugins too.

[erutan]

CSS Grids are part of the CSS spec and aren't a package you have to maintain.