Fabian Kägy

Fabian Kägy

@fabian-kaegy.com

Principal Engineer – Editorial Engineering @10up | 🐶🐶 | 🇪🇺🌍

1.7K followers368 following250 posts

Fabian Kägy reposted

🗞️ Big news: 10up has officially unified under the Fueled name, with a bold new brand, mission, and vision for the future. 10up is now the brand of Fueled’s enterprise WordPress practice. 10up.com/blog/2025/ne...

Had a lovely time with @bph.social and @nathanwrigley.com chatting about WordPress 6.8 and other related topics :)

10up@10up.com

Director of Editorial Engineering @fabian-kaegy.com joined the WPBuilds podcast to dig into what’s new in WordPress 6.8—from block editor upgrades to the shift toward annual major releases—and how it’s shaping the future of core. 🎧 Listen here: wpbuilds.com/2025/05/08/4...

The FOMO this week is real with all my friends posting about their journey to PressConf this week. You all have a wonderful week and I'm looking forward to hear all about it when you all are back :)

Always love to see how manny of my colleagues help shape the future of WordPress 🥰

10up@10up.com

#WordPress 6.8 is here, with refinements to blocks, performance, & accessibility. We led the way with 24 contributors, including @jeffpaul.com as Release Coordinator, @joemcgill.bsky.social as Tech Lead, and 3 others acknowledged as Noteworthy Contributors. 10up.com/blog/2025/te...

Fabian Kägy reposted

Replying to @fabian-kaegy.com

The topic didn't let me rest. I don't know if I love it or hate it 👀 Spent this morning applying a light coat of admin redesign CSS to the standard WP Admin to make it look and feel much more like the site editor. What do you think?

Today is my five year anniversary working at @10up.bsky.social 🎉🤯 I cannot believe it's already been five years. Still feels like I've only really just begun, and am still loving every second of it. Here's to many more years with great colleagues working on interesting problems :) 🚀

@jamiemarsland.bsky.social @briancoords.com You know I really enjoy the speed build challenges. But this kind of challenge is what I would love to see more of. Actually getting some time to strategize. And build something that comes closer to real world work

Jason Lengstorf@jason.energy

🔥 NEW WEB DEV CHALLENGE 🚀 there’s chaos is Santa’s workshop, and I challenged @aaronfrancis.com, @kentcdodds.com, @devdevcharlie.com, and @domitri.us to fix it in time to save Christmas @sanity.io sponsored this episode on location in San Francisco — don’t miss it! youtube.com/watch?v=_H5p...

The one thing I really dislike about block themes is how difficult it is to review the markup/structure of block templates. In the past reviewing a PHP based template for accessible and semantic HTML was easy and could be done entirely in GitHub.

View full thread

This is the time to provide feedback on which pieces of @nickdiego.coms fabulous Block Visibility plugin would be useful in WordPress core :)

The one thing I really dislike about block themes is how difficult it is to review the markup/structure of block templates. In the past reviewing a PHP based template for accessible and semantic HTML was easy and could be done entirely in GitHub.

View full thread

I wish we had some sort of linting tools for block templates. Stuff like: - Contains a Main element - All images have alt text - Correct usage of the "Inner blocks use content width" setting etc.

Just to be clear here. I do think that the tradeoff is worth it and that block themes are so much more powerful in many ways. This is just a little frustration that I keep running into doing lots of code reviews all the time. (the markup here gets generated by Create Block Theme most of the time)

The one thing I really dislike about block themes is how difficult it is to review the markup/structure of block templates. In the past reviewing a PHP based template for accessible and semantic HTML was easy and could be done entirely in GitHub.

But with all the block grammar in the .html files my brain just cannot comprehend it anymore. Maybe that is an ADHS thing? I struggle with the same thing when markup has hundreds of tailwind classes...

Do I happen to know anyone who may be able to help get this fixed in Gravity Forms? 😬

Fabian Kägy@fabian-kaegy.com

I cannot fathom how sooooo many large plugins in the WordPress ecosystem still have all of their blocks set to apiVersion: 1... It's been 4 years since Version 2 has been released... And a year and a half since Version 3...

I cannot fathom how sooooo many large plugins in the WordPress ecosystem still have all of their blocks set to apiVersion: 1... It's been 4 years since Version 2 has been released... And a year and a half since Version 3...

Fabian Kägy reposted

Recording some interviews with WordPress (and WP-adjacent) developers/builders. I have some scheduled already but looking for more recommendations. Who should I talk to?

One of the features of the Interactivity API in WordPress I don't see nearly enough hype about is the fact that you can extend/override any part of a store by simply calling the store function with the same namespace over and over. This is such a game changer for building extensible frontend code

This thread here actually reminded me of something else that has been staring in my mind for a while. And that is how Extensibility in WordPress Core used to drive a lot of contribution opportunities where it becomes harder and harder to use those same approaches. fabian-kaegy.com/wordpress-ex...

fabian-kaegy.comWordPress Extensibility and how it used to drive development in core - Fabian KägySomething I have observed over the last few years of working in the WordPress space is that it has become increasingly difficult to use work we develop on Client projects and contribute it back to Wor...
Fabian Kägy@fabian-kaegy.com

There are so many big features that have been in core for years such as global styles for example that simply are inaccessible to us outside of core 🤔 I'm not claiming to have an answer here. Just saying both approaches have their ups and downs...

View full thread

We are very protective of the new UI's in core because we have seen in old WordPress how too much extensibility surface area gets misused for spammy ads & notifications. But I worry that this protectiveness is actually hurting our ability to explore new ideas and be creative outside of core itself

I don't have solutions for any of this and realize how incredibly hard those problems are. But I still wanted to share my thoughts & worries about how we are currently approaching extensibility :)

This thread here actually reminded me of something else that has been staring in my mind for a while. And that is how Extensibility in WordPress Core used to drive a lot of contribution opportunities where it becomes harder and harder to use those same approaches. fabian-kaegy.com/wordpress-ex...

fabian-kaegy.comWordPress Extensibility and how it used to drive development in core - Fabian KägySomething I have observed over the last few years of working in the WordPress space is that it has become increasingly difficult to use work we develop on Client projects and contribute it back to Wor...
Fabian Kägy@fabian-kaegy.com

There are so many big features that have been in core for years such as global styles for example that simply are inaccessible to us outside of core 🤔 I'm not claiming to have an answer here. Just saying both approaches have their ups and downs...

I started writing this all as a long thread here and then realized that it would be too much and that it deserves a longer post. So I hope that makes it easier to read & understand :) I'll still share a quick TLDR in a few posts here:

On client projects it is nearly impossible to build a feature in core before you can use it on a client build. So instead we often custom build it first and then contribute it afterwards. This is much harder to do when you cannot easily override / extend core itself.