I'm glad you asked! So yes, so the new css is part of my initiative to move away from all the old nblug stuff on the site. normalize.css looked like a bunch of twiddly bits to cope with the small inconsistencies between browsers. The copy of normalize.css we have is about 10 years old, so it's not clear to me how many of the cracks it was designed to paper over are still there. We could by all means jump to a new copy of normalize.css, but it's not entirely clear to me if it's necessary. A big part of the reason I moved the site over to CSS grid was to get away from the fiddly nature of floats: https://www.sitepoint.com/css-layouts-floats-flexbox-grid/. Grid behaves a lot more consistently so I suspect we won't run into serious problems across browsers. My long term plan is to continue simplifying the css for the site by debriding a lot of the old twiddling. That's the goal at least.
sen-h. On December 4, 2023 2:54:40 PM PST, "Brian E. Lavender" brian@brie.com wrote:
Sen, Some questions on the new saclug site. https://github.com/brieweb/saclug.org/tree/master/theme/static/css I am not the CSS expert. It looks like the template now just uses saclug.css? It previously used nblug.css and normalize.css. What was your strategy here? Brian