Absolutely shocked to learn that no responsible development is taking place on Adobe's end, even in a package marketed specifically to K-12 educators and students.

I don't think Masto is perfect by any means, but it at least lets me discern who can and can't follow and/or interact with me, and my current instance is run by lovely people who care.

if anyone’s looking for aknitomy, I’ll be on my own site, which doesn’t quiiiiite have the foot traffic that etsy does. So feel free to share if you know anyone who needs a knitted dissected frog www.aknitomy.com/shop

The irony of wearing this while announcing a battle royale, too. 🙃

Leaving it up to designers in a world where the average "Full Stack Developer" wouldn't even know better. 🫠

The quality of the code that your designs are built on directly impact maintainability and accessibility.

And for me, HTML/CSS is more fun to experiment with than Figma is to use, allows for far more creativity and collaboration with your developers, and makes you a better designer. And it's free!

Today, MDN's Playground is still a completely isolated feature now relegated to the Tools dropdown. It is not as inspired or useful as Codepen or other code playgrounds that have existed long prior. It is an afterthought when it should be a prominent feature to promote learning and feature adoption.

When MDN announced their Playground feature, I said as much on the related GitHub issue.

I wish users could tag technologies/concepts, with an additional flag if they are interested in having it reviewed and ultimately displayed on one or more of the relevant documentation pages.

When you Google "W3C CSS", the first result is W3Schools, which is hilarious considering, but makes sense.

I also find it frustrating that neither W3C/MDN fully utilize code playgrounds to better illustrate concepts and highlight members of the community that create nice, practical examples.