Block development: static vs dynamic blocks#24
Open
luisherranz wants to merge 3 commits intoWordPress:trunkfrom
Open
Block development: static vs dynamic blocks#24luisherranz wants to merge 3 commits intoWordPress:trunkfrom
luisherranz wants to merge 3 commits intoWordPress:trunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Member
Author
|
@Jameswlepage, any guidance on how to run the evals to test that they work? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Teach the block-development skill how to choose between static and dynamic rendering when creating a new block, and add eval scenarios to verify the decision.
Why
The skill had no guidance on this decision. Agents would default to whichever pattern they'd seen most in training data, leading to inconsistent choices: sometimes static when dynamic was clearly needed (e.g., Interactivity API blocks, blocks in template parts), and sometimes dynamic for simple presentational blocks where static is fine. A priority-ordered checklist eliminates the guesswork.
How
references/static-vs-dynamic-blocks.md: a "first YES wins" decision checklist covering external data, evolving markup, Interactivity API, block themes, server-side needs, content portability, and simple presentational blocks.SKILL.mdstep 3 ("Pick the right block model") to point to the new reference and simplify the interactivity guidance into a single line that loadswp-interactivity-api.block-create-interactive-inner-blockseval to include the static-vs-dynamic decision step, since Interactivity API requires dynamic rendering.