Fabian Kägy

Two vinyl records framed hanging on my office wall. The records are gifts sent to any release team members of WordPress release squads.

And for me personally this release also is a cool milestone. It marks the fifth consecutive release where I was named as a noteworthy contributor.

A milestone I got to celebrate with these wonderful gifts of recognition showing up at my door :)

peterwilson.cc/wordpress-co...

WordPress 6.9 Release: Fueled Leads on Collaboration Features and AI Experiments · Fueled WordPress 6.9 is here, and with it come features that set the stage for the future of content collaboration and AI-assisted workflows inside the world’s most popular CMS.  We’re proud to share that 15...

I won’t lie, these past months, merging two companies haven’t always been easy.

But I’m still so incredibly proud to work for a company that is putting in the work, showing up for the community, and improving the web at large.

fueled.com/blog/wordpre...

Are there any guides on what vh/dvh etc. will mean with the new floating url bar in safari? 🤔

Wondering about how things like mobile menus are going to work when they are set to 100dvh height. Will the regular page content show underneath the floating URL bar? 🤔

Or are there new safe area insets?

Yeah definitely… would have loved to catch up :)

@permanenttourist.ch I take it I’ll see you there though? :)

You aren’t staying over here for WCEU are you? :)

🗞️ 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 :)

Wondering what issues you ran into with that approach that led you down this approach job?

(I can still see many really useful use cases for this. Just wondering about this particular one :))

Congrats on the launch! This does look really cool :)

Question on your example of ramping an existing site onto using a block based theme though 🤔 Given how the template hierarchy works in block themes I always felt that gradual adoption actually was one of the strong suits of it out of the box.

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 🥰

I agree with all you are saying.

Still they just look soo much better the way they are 🫣😅

Oh boy do I want to see that 👀

Just had another new project opt to install gravity forms and it just makes me sad 😅

There were some long discussions about it back when this whole system was first introduced… if I remember correctly the main reason was that php files lead you to think they are dynamic. When they don’t actually are.

As soon as you edit them in the site editor they just become static…

This is still one of the more annoying bits about block themes. For both templates and template parts you cannot translate directly but rather move all of it into a pattern that your then reference.

You can hide that pattern from the inserter…

See github.com/WordPress/tw...

So the way users will experience the editor for pages will change quite a bit in 6.8 :)

I think there is one pretty important piece missing from the doc currently though. Besides just making the "Preview Template" option more visible in the UI, it also makes it the new default experience for editing pages. And the setting now persists in the users preferences.

@bph.social As always, love these posts and especially thank you for continuing doing it even in these times of reduced sponsored contributions :) ❤️

Not sure how much preact there is to actually learn for this :) should work the same as in react with these functions like useEffect.

Most of what we need to learn are interactivity api specifics… :/

Essentially it is a lightweight ~3kb alternative to react with the same API.

The interactivity API uses it to handle a lot of what it does.

The main difference is that today it doesn’t actually support rendering full on components like we are used to because those cannot be server rendered

I haven’t worked with any of the interactive stuff in Woo yet… cart block seems like it may need each…

Sadly don’t have enough insight here to be very helpful…

But for inner blocks you can add directives with the tag processor which works quite well

@wordpress/element === react

@wordpress/interactivity === preact

So yes in this case it is rather confusing but they are separate functions from separate frameworks bundled in different ways :)

Not sure what you mean 🤔 the useEffect import from the @wordpress/interactivity package should work inside any script module when it is called inside a function that runs on the data-wp-run directive

What I usually do here is run the $content variable through the WP_HTML_Tag_Processor to manually add any directives to elements that way.

I have yet to come across any instances where I actually needed the each directives

Hadn’t thought of this. I might steal this 👀

I am so ready for this 😉

And having a full REST API to interface with it will be 🤩

I only wish that the source of truth for the block markup of static blocks didn’t require a full browser JS environment to run. Makes dynamically serializing block markup on the server impossible unless you bring in a fake DOM…

Now that is a blogpost I want to read 👀

Huge congrats :) Very excited to see what you will be able to bring to the community from the inside :)

Very cool 😎