Rethinking CSS Grids
markboulton.co.uk
markboulton.co.uk
If they're not wrong, why are they so bloody confusing?
Edit: It's been fixed now. The final example had 2md, 1fr, 1md originally, instead of the 3md, 1fr, 2md that it has now.
How is a grid different than a table? I find it odd that that each element in the grid is explicitly positioned (e.g. #score { grid-column: 1; grid-row: 3 } ).
It seems as though we've been round and round on this topic and I feel as though we're going to go round again some more when we could be improving the core elements (at the risk of some breakage).
EDIT: some answers to my questions here: http://www.htmlgoodies.com/beyond/css/css3-preview-tables-an...
EDIT2: looks as though multiple client sizes are a driver.
A fundamental starting point seems to be that CSS grids should match the mental model and terminology of "designers" rather than "developers". It would be good to have a thorough explanation of why that may or may not be an improvement. How would added abstraction effect development? How would the functionality of the existing CSS Grid Layout proposal be mapped to, or improved, with an alternative syntax?
Hopefully the ideas in the article have already been shared with the community of people working on CSS modules. It would be good for the concerns and approaches of various professions to be exchanged in a constructive fashion so that any future CSS modules are as good as can be.
This is a request for the ability to define an arbitrary unit of measure with gutters called a module and be able to use it as part of CSSG. I like this and have experimented with as part of sass/stylus grid systems.
Most of the rest is a complaint about terminology and I get slightly confused from there. IMO the `grid-x-count` property serves no purpose. Simply using `width` with and md unit value or an appropriate grid sizing definition would serve the same purpose. I'm also not sure how columns and fields interact. I think it's the same as `grid-columns` and `grid-rows` from the CSSG proposal and this is an extended part of his complaint that the CSSG terminology doesn't match up with GDG terminology.
DO NOT USE GRAY TEXT ON A WHITE BACKGROUND.
Plus I would never use a framework for generating CSS.
The fuss about grids is that they make sense on the web and there's no actual, proper, standard way to create and use them yet. Sure, if you know your way around CSS you can effectively create a grid-system for a site (and with media-queries you can make it flexible enough to support multiple devices), but the fact that it isn't a standard (despite being, as you said, graphic design lesson 1) means there's lots of work to do.
So it isn't really about making a fuss (although for some people talking about grids is indeed still in-fashion). It's about working towards making/using grids on the web easy for everyone and not just those of us know know the inner workings of the box-model, DOM and CSS.
We'd still be riding horses if Ford didn't make a "fuss about cars".
And now that nobody can see any numbers, they can't tell if you've gotten massively upvoted or not, either. In the past, I'm sure they'd have gone 'meh, no votes, don't worry about it' but now they can't/won't take that attitude simply because they don't know. So they downvote. It doesn't cost them anything and they feel better for having tried to silence an opinion or fact they don't like.
Now, I'll be downvoted for being off-topic, and that's a whole 'nother story.
> We'd still be riding horses if Ford didn't make a "fuss
> about cars".