Dapo Obembe

<p><strong>Swift FSE Blocks</strong> gives you the freedom to design your WordPress site visually — faster, smarter, and without code.</p>
<p>Built for the <strong>Full Site Editing (FSE)</strong> experience, Swift FSE Blocks offers a growing collection of beautifully designed, performance-optimized blocks that help you create stunning layouts in minutes.</p>
<p>Whether you’re building a landing page, portfolio, or blog, Swift FSE Blocks integrates seamlessly with the WordPress Site Editor to help you bring your creative vision to life.</p>
<h3>Why Choose Swift FSE Blocks?</h3>
<ul>
<li><strong>No code required:</strong> Create professional designs visually inside the editor.</li>
<li><strong>SCF/ACF-COmpatible:</strong> Get and use dynamic data from your SCF fields on any page or templates.  </li>
<li><strong>Blazing fast:</strong> Lightweight and built with performance in mind.  </li>
<li><strong>Modern design:</strong> Stylish, responsive, and mobile-ready out of the box.  </li>
<li><strong>FSE ready:</strong> Works flawlessly with WordPress block and full-site editing themes.  </li>
<li><strong>Seamless customization:</strong> Tweak spacing, colors, and typography with intuitive controls.  </li>
<li><strong>Developer friendly:</strong> Clean, extensible code following WordPress standards.</li>
</ul>
<p>Start designing your site the modern WordPress way — simple, fast, and flexible.</p>
<h3>Additional Information</h3>
<p>Swift FSE Blocks helps you <strong>design faster and smarter</strong> using the power of WordPress Full Site Editing.<br />
Perfect for freelancers, creators, and business owners who want to launch beautiful, high-performing websites — no coding required.</p>


Swift FSE Blocks

Build beautiful, fast WordPress sites with flexible Full Site Editing blocks — made for devs, freelancers, and DIY creators.

iansvo

<p>This block allows you to add an additional block content area to a site-editor template and store the block output inside a meta field. By default, WordPress posts or pages may only store blocks in one place: post_content. These blocks are output on the page using the core/post-content block. This block allows you to have multiple “outlets” where you can add blocks so you can have post-specific blocks appear in more than one location in the template.</p>
<p>The block is a fork of the core/post-content block that uses a customized version of the useEntityBlockEditor hook which supports meta keys. The blocks for your content area are then stored inside that meta key (instead of post_content). This allows you to keep the blocks separate and you can use as many of these on a single template as you want (but in most cases 2 is probably enough). It’s all up to you!</p>
<h3>Requirements</h3>
<ol>
<li>Using this plugin requires you to enable template previews (which will let you visually see the new content area you’re adding). This can be enabled on any given post or page, but you can optionally set it on by default using a filter.</li>
<li>Your theme must be a block theme (i.e. it uses the site editor). This won’t work for a hybrid or classic theme (which has no concept of live template preview in the block editor).</li>
</ol>
<h3>Hooks</h3>
<p>If you want to disable this meta key’s registration, add the following to your theme or plugin:</p>
<pre><code><?php
add_filter( 'content_area_block_register_default_meta', '__return_false' );
</code></pre>
<p>For advanced users, there is also a filter for the entire block’s output. See the below snippet from render.php:</p>
<pre><code><?php
/**
 * Filter the block's frontend output.
 *
 * @param string $parsed_content The parsed block content for output.
 * @param int    $block_post_id  The current post ID the block is displaying in.
 * @param array  $attributes     The block attributes.
 * @param string $content        The original unparsed block content.
 * @param object $block          The current parsed block object.
 *
 * @return The block content for output on the frontend.
 */
$output = apply_filters( 
    'content_area_block_content', 
    do_blocks( str_replace( ']]>', ']]&gt;', $content ) ), 
    $block_post_id, 
    $attributes, 
    $content, 
    $block 
);
</code></pre>
<h3>Contributing</h3>
<p>The plugin source code may be found here: https://github.com/iansvo/content-area-block.</p>
<p>To build the plugin from source, you must have NodeJS (v24+) installed.</p>
<p>Setup Steps:</p>
<ol>
<li>Navigate to the project folder in your terminal.</li>
<li>Run <code>npm i</code> to install dependencies.</li>
<li>Run <code>npm run build</code> to performn the initial build.</li>
</ol>
<p>If you’re using wp-env to run the plugin…<br />
1. Run <code>npm run wp-env start</code> to start the docker container.<br />
2. Run <code>npm run start</code> to watch for file changes.</p>


Content Area Block

Adds a block content area to a site editor template and stores the blocks in a specified meta field. By default, the plugin will add a new meta field  …

Swift FSE Blocks vs Content Area Block