fix typo and link in static-dynamic-rendering.md

[janpfeil]

What?

Why?

How?

Testing Instructions

Testing Instructions for Keyboard

Screenshots or screencast

[github-actions]

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 props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @janpfeil.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: janpfeil.

Co-authored-by: tyxla <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @janpfeil! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[tyxla]

Hey @janpfeil, thanks a lot for your contribution!

I've suggested a few improvements - let me know what you think!

[tyxla]

A few things I'm suggesting here:

• The link seems to be incorrect - instead of linking to the customizer's partial render callback, we should lead to either register_block_type or WP_Block_Type that both document the render_callback function.
• There's a missing closing > of the opening <a> tag.
• We should keep the wrapping <code></code>.

Suggested change

WordPress provides mechanisms like the <a href="https://developer.wordpress.org/reference/functions/render_block/"><code>render_block</code></a> and the <a href="https://developer.wordpress.org/reference/classes/wp_customize_partial/render_callback/"render_callback</a> function to alter the saved HTML of a block before it appears on the front end. These tools offer developers the capability to customize block output dynamically, catering to complex and interactive user experiences.

WordPress provides mechanisms like the <a href="https://developer.wordpress.org/reference/functions/render_block/"><code>render_block</code></a> and the <a href="https://developer.wordpress.org/reference/classes/wp_block_type/#source"><code>render_callback</code></a> function to alter the saved HTML of a block before it appears on the front end. These tools offer developers the capability to customize block output dynamically, catering to complex and interactive user experiences.

Let me know what you think!

[janpfeil]

Glad you reviewed it with care. I was missing the link to render_callback. I'm not familiar with the concepts. Decide for yourself which link makes more sense.

[tyxla]

The thing is that neither of the links I provided specifically documents the render_callback argument of register_block_type.

Instead, maybe we can link to https://developer.wordpress.org/block-editor/how-to-guides/block-tutorial/creating-dynamic-blocks/ which does contain a good explanation with examples on how to use render_callback.

Feel free to go with that one.

Thanks @janpfeil!

[janpfeil]

@tyxla done, please review for correctness

[tyxla]

Looks great! 🚀

I appreciate your help improving the docs, @janpfeil 🙌