What happened last week - issue #79
This week: CMS, Open Source, WordPress and more
What happened last week
So, I going to Spain on Friday. For the next two weeks, I will be working from this amazing and sunny place.
Again, a lot of things happened:
together with Tim, we started a CMS Squad on the daily.dev (more info in links below)
I will be speaking virtually at the Warsaw IT Days tomorrow
I’m working hard on one more Astro site for Patchstack
Also, the Easter weather was amazing which meant I had to go cycling
Interesting links
I was at Open Source Day 2024 in Florence
A month ago I was at OS Day Florence and it took me a month to write a review of this amazing event. Check it out and start planning your trip next year - it’s totally worth it.
We started a CMS Squad on daily.dev
Together with Tim, we decided to start a CMS community on the daily.dev. Every CMS is welcome - come and share your knowledge.
Why I don't use WordPress Coding Standards? — Przemek Hernik
This is one of the unluckiest links I have bookmarked. First, it got on my radar minutes after publishing an issue, next I missed adding it in the previous issue. But here it is.
Przemek describes why he doesn't use WP Coding Standards. And I agree with him fully. WPCS is a coding standard that has this legacy vibe.
Exploring the Block Hooks API in WordPress 6.5 — Nick Diego
A great tutorial explaining how Block Hooks API works in WP 6.5. It really came a long way to reach how it looks right now. I think it’s one of the mechanisms that should be there from the beginning to make the whole block editor/ block theme adoption faster.
I heard so much great stuff about Laravel Herd that I was eager to try it out on Windows. Now when it's here I'm a bit disappointed with the fact that I need to pay for MySQL support. But the moment I'll get my paycheck I will give it a try.
The unofficial WP CLI docs — Enrique Chavez
I will be honest with you - I’m not a fan of WP-CLI documentation. It has this weird vibe that is hard to describe. But Enrique just solved the problem - using Tailwind UI, he gave the docs another life.
How Photoshop solved working with files larger than can fit into memory — Thomas Steiner
A very interesting problem that Adobe and Chrome developers had to solve. Those are things that in most cases we don't have to care about.
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