Blockify

<p>Pattern Editor is a plugin to help you create and edit patterns for WordPress block themes. It automatically exports patterns on save as PHP files to the active themes <code>patterns</code> directory.</p>
<p>It works with the built-in <code>wp_block</code> post type and adds some minimal UI features to make working with patterns easier. The new Block Pattern editor UI in the Site Editor is supported, and the <code>wp_block</code> post type screen is exposed in the admin menu for quick access.</p>
<h4>Features</h4>
<ul>
<li>Exports assets (images, SVGs, videos) to the active theme’s <code>assets</code> directory.</li>
<li>Pattern front end previews.</li>
<li>Export patterns as PHP files.</li>
<li>Import patterns from PHP files.</li>
<li>Edit patterns in the block editor.</li>
<li>Can export to category subdirectories or a single directory.</li>
<li>Supports the new Block Pattern editor UI in the Site Editor.</li>
</ul>
<h4>Filters</h4>
<pre><code>blockify_pattern_export_use_category_dirs - Enable or disable the use of category directories for pattern exports. Default is `true`. If enabled, patterns will be exported to `patterns/{category}/{pattern-name}.php`. If disabled, patterns will be exported to `patterns/{category}-{pattern-name}.php`.

blockify_image_export_dir - Set the directory where images and assets are exported to. Default is `themes/$stylesheet/assets`. Images are saved to the `img` subdirectory, SVGs to the `svg` subdirectory, and videos to the `video` subdirectory.

blockify_pattern_export_content - Allows you to modify the content of the exported pattern file. The first parameter is the content of the pattern file, the second parameter is the pattern post object, and the third parameter is the pattern category slug.
</code></pre>
<p>More documentation coming soon.</p>


Pattern Editor

Import, export and edit patterns with the Block Pattern custom post type with additional settings and UI features that makes working with WordPress bl …

Mervin Praison

<p>This plugin contains patterns for you to check out, ranging from a simple text pattern to a more complex pattern containing both images and text.</p>
<p><a href="https://mer.vin/wordpress/plugins/patterns/#create" title="Create WordPress Block Patterns" rel="nofollow ugc">Create WordPress Block Patterns</a></p>
<h4>Add your block patterns to this plugin</h4>
<ol>
<li>
<p>Fork</p>
<pre><code>https://github.com/Praison/Patterns
</code></pre>
</li>
<li>
<p>Clone your new fork locally</p>
<pre><code>git clone https://github.com/YOUR_USERNAME/Patterns.git
cd Patterns
</code></pre>
</li>
<li>
<p>Connect to original repository https://github.com/Praison/Patterns</p>
<pre><code>git remote add --track master upstream https://github.com/Praison/Patterns.git
git fetch upstream
</code></pre>
</li>
<li>
<p>Create a new branch for your changes</p>
<pre><code>git checkout -b YOUR_USERNAME upstream/master
</code></pre>
</li>
<li>
<p>Add your block patterns in <code>index.php</code></p>
<pre><code>register_block_pattern(
    'praison-gutenberg-block-patterns/TITLE-OF-YOUR-BLOCK-PATTERN',  # Add Hyphens between lowercase words
    array(
        'title'   => __( 'TITLE_OF_YOUR_BLOCK_PATTERN', 'praison-gutenberg-block-patterns' ),
        'content' => "BLOCK_PATTERN_GOES_HERE",
        'categories' => array("CATEGORY"), # eg: columns, text ..etc
    )
);
</code></pre>
</li>
<li>
<p>Add, Commit, Push</p>
<pre><code>git add .
git commit -m "Added block pattern TITLE_OF_YOUR_BLOCK"
git push -u origin YOUR_USERNAME
</code></pre>
</li>
<li>
<p>Submit your <a href="https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request" title="Creating Pull Request" rel="nofollow ugc">pull request</a></p>
</li>
</ol>


Pattern Editor vs WordPress Block Patterns Plugin