Adam ArgyleThe making of a #CSS5 HDR enabled gradient tool
a fun peek into the sketching that led to the gradient line UI, the color picker, the overall layout, some math and more!
Adam ArgyleThe making of a #CSS5 HDR enabled gradient tool
a fun peek into the sketching that led to the gradient line UI, the color picker, the overall layout, some math and more!
nerdy.dev/the-making-o...
Inautilo#Development #Proposals
Searching for a new CSS logo · It’s time for a change and some fresh proposals https://ilo.im/160cew
_____
#Logo #CSS #CSS3 #CSS4 #CSS5 #CSS6 #Evolution #Community #WebDev #Frontend
CSS Café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/
kaiserkiwi 
I would love to see proper versioning on CSS. I still remember the release of CSS3 and it's sad, that this moment just happened once in the 18 years I do this job now.
At the same time other language had multiple ground breaking releases.
CSS isn’t developing in a slow way. Not a bit. But you can't put the finger on a feature set. You can't hire for a specific feature set.
"10 years of CSS experience" can mean, that border-radius is the most exciting thing that person ever did and starts to cry if they see the clamp syntax.
"1 year experience with CSS 5" on the other hand would be pretty clear.
https://www.smashingmagazine.com/2024/08/time-to-talk-about-css5/
It’s Time To Talk About “CSS5” — Smashing Magazine
Have you ever wondered what happened after CSS3? It’s common knowledge that we never saw CSS4 come after it, yet we have a plethora of new features that have no similar way of defining when they were introduced. The W3C CSS-Next community group is actively searching for better approaches for how we describe the evolution of CSS over time and identify feature sets as effectively as we did with CSS3 way back in 2009 — and you can help.
CSS by T. Afif 
Adam SmithA 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/
It’s Time To Talk About “CSS5” — Smashing Magazine
Have you ever wondered what happened after CSS3? It’s common knowledge that we never saw CSS4 come after it, yet we have a plethora of new features that have no similar way of defining when they were introduced. The W3C CSS-Next community group is actively searching for better approaches for how we describe the evolution of CSS over time and identify feature sets as effectively as we did with CSS3 way back in 2009 — and you can help.
#Development #Challenges
It’s time to talk about ‘CSS5’ · What’s the optimal way to describe CSS’s evolution? https://ilo.im/15zpet
_____
#ModernCSS #Naming #CSS3 #CSS4 #CSS5 #CSS6 #W3C #WebDev #Frontend #CSS
It’s Time To Talk About “CSS5” — Smashing Magazine
Have you ever wondered what happened after CSS3? It’s common knowledge that we never saw CSS4 come after it, yet we have a plethora of new features that have no similar way of defining when they were introduced. The W3C CSS-Next community group is actively searching for better approaches for how we describe the evolution of CSS over time and identify feature sets as effectively as we did with CSS3 way back in 2009 — and you can help.
jnpnbody {
background-shader: "(u,v) {
u mod 2 and v mod 2 ? white : black; }";
}
bigandy