Fabian Kägy
@fabian-kaegy.com
Director of Editorial Engineering @10up | 🐶🐶 | 🇪🇺🌍
Seems to be working even with external plugins that have really custom edit screens 👀
January 26, 2025 at 8:04 PM
Seems to be working even with external plugins that have really custom edit screens 👀
With this redesign and now the editor rendered in an iframe I could even get used to "non full screen mode" in the block editor 😅
Especially with the resizable sidebar. 👀
Especially with the resizable sidebar. 👀
January 26, 2025 at 7:07 PM
With this redesign and now the editor rendered in an iframe I could even get used to "non full screen mode" in the block editor 😅
Especially with the resizable sidebar. 👀
Especially with the resizable sidebar. 👀
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?
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?
January 26, 2025 at 1:58 PM
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?
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?
That doesn't mean you have to do away with these kinds of controls here all together. I've recently built something on top of the query loop that still has these toggles.
But what they do under the hood is just remove / add that block from the template. Rather than just set a boolean flag
But what they do under the hood is just remove / add that block from the template. Rather than just set a boolean flag
January 7, 2025 at 4:57 PM
That doesn't mean you have to do away with these kinds of controls here all together. I've recently built something on top of the query loop that still has these toggles.
But what they do under the hood is just remove / add that block from the template. Rather than just set a boolean flag
But what they do under the hood is just remove / add that block from the template. Rather than just set a boolean flag
Actually I am only partially correct 🤯 Looks like even though it leverages content only locking it does allow me to add a new list item to a list 🤯
It does not allow me to add a new button to a buttons block but I could argue that one. Lists were non negotiable
It does not allow me to add a new button to a buttons block but I could argue that one. Lists were non negotiable
December 17, 2024 at 10:40 PM
Actually I am only partially correct 🤯 Looks like even though it leverages content only locking it does allow me to add a new list item to a list 🤯
It does not allow me to add a new button to a buttons block but I could argue that one. Lists were non negotiable
It does not allow me to add a new button to a buttons block but I could argue that one. Lists were non negotiable
The way we do it is adding the icon as an inline img tag with a base64 encoded source and then also using the same svg as a mask so we can color it.
This image then also has two data attributes for the icon and the size.
These then get replaced via a `render_block` hook for the frontend
This image then also has two data attributes for the icon and the size.
These then get replaced via a `render_block` hook for the frontend
December 10, 2024 at 4:10 PM
The way we do it is adding the icon as an inline img tag with a base64 encoded source and then also using the same svg as a mask so we can color it.
This image then also has two data attributes for the icon and the size.
These then get replaced via a `render_block` hook for the frontend
This image then also has two data attributes for the icon and the size.
These then get replaced via a `render_block` hook for the frontend
Which I sadly have to say is even worse than what I described in my custom example 💀😅
December 4, 2024 at 10:55 PM
Which I sadly have to say is even worse than what I described in my custom example 💀😅
Follow up: The Navigation Post List actually is used by core today.
You get to it if you click the "Manage Menus" link in the Advanced Inspector of the Navigation block.
You get to it if you click the "Manage Menus" link in the Advanced Inspector of the Navigation block.
December 4, 2024 at 10:53 PM
Follow up: The Navigation Post List actually is used by core today.
You get to it if you click the "Manage Menus" link in the Advanced Inspector of the Navigation block.
You get to it if you click the "Manage Menus" link in the Advanced Inspector of the Navigation block.
I will agree with you that in most cases the reason we need this is to fill in for shortcomings in core that should not be needed.
Like this example here.
We are finding many of our users struggle to find where to edit their navigation. So we added back the "Menus" link under Appearance.
Like this example here.
We are finding many of our users struggle to find where to edit their navigation. So we added back the "Menus" link under Appearance.
December 4, 2024 at 10:07 PM
I will agree with you that in most cases the reason we need this is to fill in for shortcomings in core that should not be needed.
Like this example here.
We are finding many of our users struggle to find where to edit their navigation. So we added back the "Menus" link under Appearance.
Like this example here.
We are finding many of our users struggle to find where to edit their navigation. So we added back the "Menus" link under Appearance.
Honestly I'm not sure 🤔
Maybe eventually when we have the full admin redesign this is a non issue.
We already have the concept of pushing into a separate entity and back out via the onNavigateToEntityRecord function that is exposed in the settings of the block editor store.
Maybe eventually when we have the full admin redesign this is a non issue.
We already have the concept of pushing into a separate entity and back out via the onNavigateToEntityRecord function that is exposed in the settings of the block editor store.
December 4, 2024 at 9:56 PM
Honestly I'm not sure 🤔
Maybe eventually when we have the full admin redesign this is a non issue.
We already have the concept of pushing into a separate entity and back out via the onNavigateToEntityRecord function that is exposed in the settings of the block editor store.
Maybe eventually when we have the full admin redesign this is a non issue.
We already have the concept of pushing into a separate entity and back out via the onNavigateToEntityRecord function that is exposed in the settings of the block editor store.