iansvo

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.
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!
<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>
If you want to disable this meta key’s registration, add the following to your theme or plugin:
<pre><code><?php
add_filter( 'content_area_block_register_default_meta', '__return_false' );
</code></pre>
For advanced users, there is also a filter for the entire block’s output. See the below snippet from render.php:
<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>
The plugin source code may be found here: https://github.com/iansvo/content-area-block.
To build the plugin from source, you must have NodeJS (v24+) installed.
Setup Steps:
<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>
If you’re using wp-env to run the plugin… 
1. Run <code>npm run wp-env start</code> to start the docker container. 
2. Run <code>npm run start</code> to watch for file changes.

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  …

lastsplash (a11n)

When WordPress introduced Full Site Editing (FSE) with block themes, the familiar “Additional CSS” option was moved from the Customizer to the Site Editor’s Styles panel. This plugin brings back easy access by adding an “Additional CSS” link directly to the Appearance menu.
Features:
<ul>
<li>Adds “Additional CSS” link under Appearance menu</li>
<li>One-click access to the Site Editor CSS panel</li>
<li>Only appears when using a block theme</li>
<li>Lightweight and simple – no settings needed</li>
<li>Works with any block theme</li>
</ul>
How It Works:
Simply activate the plugin and you’ll see “Additional CSS” appear in your Appearance menu. Clicking it takes you directly to the CSS editing panel in the Site Editor.

Additional CSS Shortcut

Adds a quick-access link to the Additional CSS panel in the Site Editor for block themes.

Content Area Block vs Additional CSS Shortcut