You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by justintadlock March 1, 2024
In #222 and #225, I introduced the Block Bindings API. But I should stress that these were merely very basic introductory posts on a vast subject that will empower developers to do some really powerful things with WordPress 6.5+.
With the introduction out of the way, it's time to showcase what folks can really do with this API in more of a real-world use case. I still need to map out the full plan for this, but my general idea is this:
Developer is building a site that is slightly more complex than a regular blog. Book review website?
Requires custom post meta for data (e.g., rating, ISBN number, etc.).
Uses a custom Editor Plugin to add fields for entering metadata in the post sidebar.
Needs a custom post template for different structure.
Needs a custom archive template with custom Query Loop variation.
Uses the Block Bindings API to render post metadata.
Needs the Block Variations API for inserting blocks that are bound to post meta.
Could use some patterns for use in the theme and by the user with the Block Bindings already in place.
It could also showcase Block Locking to control what the user can change.
Essentially, this post (maybe even series) could touch on a lot of features in WordPress and show how developers could bring them together from Point A to Point B.
The text was updated successfully, but these errors were encountered:
This is part 2 of a series. The ticket for part 1 is here: #238
Discussed in #231
Originally posted by justintadlock March 1, 2024
In #222 and #225, I introduced the Block Bindings API. But I should stress that these were merely very basic introductory posts on a vast subject that will empower developers to do some really powerful things with WordPress 6.5+.
With the introduction out of the way, it's time to showcase what folks can really do with this API in more of a real-world use case. I still need to map out the full plan for this, but my general idea is this:
Essentially, this post (maybe even series) could touch on a lot of features in WordPress and show how developers could bring them together from Point A to Point B.
The text was updated successfully, but these errors were encountered: