On July 20, 2021, with the release of WordPress 5.8, the new WordPress Block Pattern Directory went live. In case you haven’t yet heard about WordPress Block Patterns or the WordPress Block Pattern Directory, we’ll explain why this is exciting, how it helps you design your website, and just how easy it is to use the directory.
What are WordPress Block Patterns?Source: How to Use the WordPress Block Pattern Directory — WordPress.com
Block Patterns have become integral to the Editor since their introduction last year and their development has been pretty much non-stop. (*See below) If you open the Block inserter these days you’ll find a dizzying number of Patterns ready to enhance your Post or Page. Add into that mix Block Transforms, where you can change one kind of Block to another, and, truly, the possibilities for displaying your content are nearly endless.
Sometimes, however, you need that one special layout to help you tell your story. If you don’t find it in the Block Patterns integrated into the Editor, you now have another resource to use, the WordPress.org Block Pattern Directory.
Navigate to the Block Directory, find your block and then simply hover your cursor over the pattern, click on the copy button that pops up and then paste your desired block to your open post or page in your Block Editor.
I initially inserted the above as a single image, but then used a Block Transform to change it to a Media and Text block.
The most exciting aspect (probably only for me) mentioned in the above Go article is the opening up of block pattern submissions later this year, but only when TPTB on WordPress.com fix the issue of exporting as .json. As I recently learned in a WordPress Watch Party and Discussion on Reusable Blocks, block patterns start life as reusable blocks.
Something to look forward to.
*Update 12 October 2022 – WordPress.com has been introducing more and more (and more!) new block patterns in the Patterns tab of our own Editor. Check out these official News Blog posts:
As always, the information in this post is correct as of publication date. Changes are inevitable.