Re: [csswg-drafts] [css-grid-3] Designer/developer feedback on masonry layout (#10233)

I think masonry (or whatever it ends up being called) should be a part of CSS Grid, for a few reasons:
- As a designer, a masonry grid is conceptually still just a grid. It has all the same considerations as a regular grid (column width, gap size, etc), except for the way elements stack. 
- As a front-end developer,I already struggle to wrap my head around the differences between flexbox and grid, and when to use one vs the other (though I appreciate the power both afford). Adding another conceptual model to that mix is just adding to the confusion, with no clear user benefit... the only benefit seems to be for the browser developers. The additional effort required to integrate masonry into grid will be outweighed by time saved with reduced developer confusion. 
- As a business owner, I have substantial commercial evidence that masonry layouts are valued by users. Niice.com’s business has been effectively built on offering an easy way for customers to create microsites with masonry-style layouts (including, importantly, elements that span multiple columns). Customers like PlayStation, Nordstrom, Paramount, Fox and more have chosen us specifically because of the layouts they can build on our platform, and we’ve had hundreds of thousands of brand designers, photographers, fashion designers, interior designers, boat designers, product designers, jewellery designers, illustrators and more use it to create layouts that wouldn't be possible without the upside-down Tetris logic of masonry (as you can tell from that list, it’s particularly valuable when presenting visual content).

-- 
GitHub Notification of comment by chrisarmstrong
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2067438273 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 20 April 2024 00:38:47 UTC