Here are all the links that were dropped during today's meetup:
* https://github.com/CSS-Next/css-next/discussions/92
* https://syntax.fm/show/812/css-4-5-and-6-with-google-s-una-and-adam
* https://github.com/CSS-Next/css-next/issues/105
* https://css-levels.netlify.app/
* https://github.com/CSS-Next/css-next/pull/104
* https://www.css.cafe/css-speech/
A really interesting read.
“Naming is always hard, yet it’s just something we have to do in CSS to properly select things. I think it’s time we start naming [CSS releases] like this, too. It’s only a matter of time before “modern” isn’t “modern” anymore.” — Geoff Graham
https://www.smashingmagazine.com/2024/08/time-to-talk-about-css5/
Now that CSS Anchor Positioning allows us to "name a reference" in CSS, do we need being able to consume the value of `:nth-child` or similar when naming things?
Something like:
a {
anchor-name: --link-${indexOf};
}
So we could anchor to ANY `<a>` on a page without needing to explicitly give each one of those an `anchor-name`?
I don't much know the View Transitions API, but maybe it could benefit from similar?
Web development in 2022: What will web development be like in 2022? What do we wish it to be? What are my plans as a web developer? Some thoughts to be continued ...
https://dev.to/ingosteinke/web-development-in-2022-40b6
#webdev #webdesign #sustainablewebdevelopment #sustainabledevelopmentgoals #cssnext
