@pootlepress Eg the navigation system (which is why we built our own), theme based synced patterns (which seems to have lost momentum) and responsive controls. Also more ways to restrict editing for clients would be nice.
I have plenty of other thoughts, but that will do for now!
@pootlepress Our agency went all in on native blocks maybe 3-4 years ago, and have been building exclusively with FSE for clients for 2 years. We've had to build a lot of tooling (block extensions, block libraries), but overall we really like it, with some caveats.
@fabiankaegy@justintadlock That's great to see progress in this area Justin thanks for sharing, I'm really looking forward to it!
Now if the issue Fabian mentioned could some how get into 6.5 I'd be a happy bunny 🙂
@briancoords Great writeup. I've gradually been transitioning to full block themes for client builds at work, and your conclusion is virtually identical to mine in terms of what I'd like to see/what I'd considered building, because a git workflow is quite crucial for me.
@keithdevon The way I've done this is by extending the group/column/cover blocks with a link control, which adds a pseudo element over the top as a link.
I created a gist of the various code parts, but it needs further explanation:
https://t.co/KdUvCfLaH6
Happy to explain if needed.
@justintadlock You want a nice layer of cream then jam (or jam then cream depending on who you believe, but they are wrong!) on each half 😛 Hope you had a good time!
If you use Hybrid Core for building themes, we have some pretty exciting stuff coming in v6.0 next month. Mostly, the framework is shifting gears so that it is 100% modular and can be used as the foundation for both themes and plugins.
See the latest: https://t.co/1Wc6uBVZd0
So, it's time for that huge WordPress news I mentioned. I'm publishing the 2nd edition of Professional WordPress Plugin Development alongside @williamsba and @JJJ. https://t.co/EYSvOThMMy
#PluginDevBook