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  …

Weston Ruter

<p>This plugin extends the core Post Date block variation, specifically the “Post Date” variation of the Date block. It appends the modified date to the block whenever it differs from the published date (when rendered in the provided date format). You can configure prefixes and suffixes for both dates, and you can display the modified date on a separate line.</p>
<p>For a full writeup of this plugin, see my <a href="https://weston.ruter.net/2026/01/19/post-date-block-published-modified/" rel="nofollow ugc">blog post</a>.</p>
<p>This is a prototype or stopgap for <a href="https://github.com/WordPress/gutenberg/issues/53099" rel="nofollow ugc">gutenberg#53099</a> (Post date: It is not clear that “display modified date” replaces the publishing date). See also <a href="https://github.com/WordPress/gutenberg/pull/61920" rel="nofollow ugc">gutenberg#61920</a> (Add prefix / suffix to Post Date block). What eventually lands in core will hopefully leverage “<a href="https://github.com/WordPress/gutenberg/issues/73929" rel="nofollow ugc">shortblocks</a>” so that the conditional prefixes and suffixes needn’t be provided in a block settings panel.</p>
<h4>Usage</h4>
<ol>
<li>Open the Site Editor to edit a block template.</li>
<li>Insert a Date block.</li>
<li>In the block settings, click the “Transform to variation” button and select “Post Date”.</li>
<li>A new “With Modified Date” panel appears in the settings. Enable the “Show modified date when different from published date” toggle.</li>
<li>Configure the prefixes and suffixes for the published date and modified date when the two differ for the selected date format; optionally enable the toggle to show the modified date on a separate line.</li>
</ol>
<p><strong>Note:</strong> There is currently no preview in the editor. To see the changes, save the block template and navigate on the frontend to a post that has been modified at least a day after publishing.</p>


Post Date Block: Published & Modified

Appends the modified date to the Post Date block when different from the published date.

Content Area Block vs Post Date Block: Published & Modified