Docs: Update create block type how to guide for block.json

[mkaz]

Description

The writing your first block type guide was one of the earliest tutorials for creating blocks. This PR updates the guide to match the recommended usage of block.json that is already in the gutenberg-examples repo.

Also, while updating I noticed the create-block scripts included a link to the guide, when it is probably better to link directly to the reference documentation.

How has this been tested?

Documentation changes, check for:

• Clarity: content makes sense and accurate,
• Mistakes: typos or speling issues,
• Complete: Anything missing?

Types of changes

Updates how to guide for creating block type.

Uses new how to guide template and updates for latest development practices.

[gziolo]

I left a few comments with minor things. The changes to the document look great and we should have that applied a long time ago. @mkaz, thank you a lot for spending time bringing it up to date.

[mkaz]

Thanks @gziolo for the review 👏

I think I addressed all the updates, there was still one question around codetabs and the PHP register function, since that code is the same for both JSX/Plain. See if what I put clarifies it enough.

[gziolo]

I think I addressed all the updates, there was still one question around codetabs and the PHP register function, since that code is the same for both JSX/Plain. See if what I put clarifies it enough.

Yes, I'm still trying to understand why the PHP entry and block.json differ in the gutenberg-examples repository for both versions, but I assume that it's required so you could both plugins in one WordPress instance. In theory, for documentation purposes, we could omit this distinction because the reader would stick with one style so it is less of a concern. The only challenge is that the JS entry point has different paths depending on whether you use the build step which is probably why you had two different block.json files in the first place.

[mkaz]

@gziolo Correct, the only difference for the block.json is the editorScript property, since one is in a build directory and the other is not.

[gziolo]

Great, this is ready to go. Thank you for all iterations applied.

Changes resolved.