What happened last week - issue #101 🎆
This week: Statamic, WordPress, CSS and more
What happened last week
I hope you all had a chance to rest during the Christmas break and that you found some amazing gifts under the Christmas tree.
I didn’t do too much creative stuff this time apart from playing with Gravitrax, which is really fascinating. I’m afraid we have a new family hobby. And together with Lego, it can be another costly one.
Apart from this, I’m getting more and more tired of the whole WordPress debacle. Both sides are right at some points and those points should be used to start a discussion to end this war. Instead, it’s getting worse. I hope that at some point both sides will find some common ground.
So, see you next year 🙃 I hope the next year will be better.
Interesting links
A Practical Guide to Finding Speaking Opportunities — Maciek Palmowski
I wrote a guide that should help you find public speaking opportunities. It also covers how to organize all your submissions and how to prepare everything.
Field Actions in Statamic are Amazing — Maciek Palmowski
Field Actions are one of the coolest features that Statamic introduced lately. It allows you to convert or generate content for a given field. This is something that enables you to extend Statmic’s admin panel in so many ways.
Adding actions to specific Statamic fields — Jack Sleight
While talking about Field Actions - you should check this article by Jack. It shows how to enable Field Actions for specific fields. Another big step for improving flexibility.
Breaking the Status Quo — Joost De Valk
Joost published a proposal on how to break the status quo in WordPress. I do agree with most of the points he mentioned (especially that the current situation is unbearable), but I think that first, we need to bridge the gap that happened because of Matt vs WP Engine.
Judge Grants WP Engine Injunction, Orders Mullenweg to Reinstate WordPress.org Access — Rae Morey
Speaking of the Matt vs WP Engine case. We can say the WP Engine won the first round. The horrible checkbox is gone (although it was replaced with another one that really hurt the whole Italian WP community), ACF is back in the repo and the team got their access back.
Announcing Patchstack API for Endless Automations — Oliver Sild
At Patchstack, we finally released an API that allows you to automate a lot of things without having to log in to your Patchstack dashboard.
Making content-aware components using CSS :has(), grid, and quantity queries — Eric Bailey
Eric wrote an amazing article showing the power of :has in CSS. Before this, I would probably use PHP or JS to parse the data and add a class if needed. Now we can just add a bit of CSS 🤯
The results of the State of JS 2024 are in. I’m really happy seeing how Astro is getting more and more popular.
Open-Source: More than just readable code — Andreas Møller
Very often we forget how important is owning your data until the moment we learn that the SaaS we are using is shutting down. Great article reminding about this.
Trailing Slash for Frameworks — Bjorn Lu
This great article by Bjorn shows the difference in how frameworks treat the slash at the end of the URL.
Thoughts on Tailwind 4 — Naman Goel
Naman shares his thoughts about Tailwind 4. In general, he’s very happy about the changes happening in the fourth version, but there are some things that could have been done in a better way.
CSS Wishlist 2025 — Adam Argyle
Adam shares his wishlist for new CSS features in 2025. Personally, I would love to see gesture-driven animations and a CSS carousel would be amazing.
An Introduction To CSS Scroll-Driven Animations: Scroll And View Progress Timelines — Mariana Beldi
Mariana shows a few amazing examples of using CSS Scroll-Driven animations. It’s really amazing what we can achieve using CSS.
And how was your week? Did you learn something interesting? Don’t hesitate to press the reply button or share your thoughts in the comment section.
Cheers,
Maciek