Fabian Kägy
@fabian-kaegy.com
Director of Editorial Engineering @10up | 🐶🐶 | 🇪🇺🌍
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?
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?
June 10, 2025 at 6:42 AM
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?
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? :)
@permanenttourist.ch I take it I’ll see you there though? :)
May 24, 2025 at 8:05 PM
Yeah definitely… would have loved to catch up :)
@permanenttourist.ch I take it I’ll see you there though? :)
@permanenttourist.ch I take it I’ll see you there though? :)
You aren’t staying over here for WCEU are you? :)
May 24, 2025 at 9:55 AM
You aren’t staying over here for WCEU are you? :)
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 :))
(I can still see many really useful use cases for this. Just wondering about this particular one :))
April 23, 2025 at 7:45 PM
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 :))
(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.
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.
April 23, 2025 at 7:45 PM
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.
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.
I agree with all you are saying.
Still they just look soo much better the way they are 🫣😅
Still they just look soo much better the way they are 🫣😅
April 12, 2025 at 6:35 PM
I agree with all you are saying.
Still they just look soo much better the way they are 🫣😅
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 😅
Just had another new project opt to install gravity forms and it just makes me sad 😅
April 11, 2025 at 8:37 PM
Oh boy do I want to see that 👀
Just had another new project opt to install gravity forms and it just makes me sad 😅
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…
As soon as you edit them in the site editor they just become static…
March 25, 2025 at 7:43 PM
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…
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...
You can hide that pattern from the inserter…
See github.com/WordPress/tw...
twentytwentyfive/templates/404.html at trunk · WordPress/twentytwentyfive
Contribute to WordPress/twentytwentyfive development by creating an account on GitHub.
github.com
March 25, 2025 at 6:35 PM
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...
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 :)
March 18, 2025 at 10:17 AM
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.
March 18, 2025 at 10:17 AM
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 :) ❤️
March 18, 2025 at 10:17 AM
@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… :/
Most of what we need to learn are interactivity api specifics… :/
February 28, 2025 at 10:36 PM
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… :/
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
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
February 28, 2025 at 10:35 PM
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
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
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
February 28, 2025 at 10:32 PM
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
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 :)
@wordpress/interactivity === preact
So yes in this case it is rather confusing but they are separate functions from separate frameworks bundled in different ways :)
February 28, 2025 at 10:30 PM
@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 :)
@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
February 28, 2025 at 10:24 PM
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
I have yet to come across any instances where I actually needed the each directives
February 28, 2025 at 10:22 PM
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
I have yet to come across any instances where I actually needed the each directives
Hadn’t thought of this. I might steal this 👀
February 17, 2025 at 10:05 AM
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 🤩
And having a full REST API to interface with it will be 🤩
February 15, 2025 at 1:02 PM
I am so ready for this 😉
And having a full REST API to interface with it will be 🤩
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…
February 13, 2025 at 2:31 PM
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…