Abhishek Kumar

<p>RenderWhen for Blocks adds conditional visibility to every block in the WordPress block editor. Decide who sees what, and when, with a panel that reads exactly how you’d say it out loud:</p>
<blockquote>
<p><em>Show this block when the user is logged in.</em><br />
  <em>Show this block when the date is between March 1 and March 31.</em><br />
  <em>Show this block when the device is mobile.</em></p>
</blockquote>
<p>RenderWhen is built around two ideas that set it apart from other visibility plugins:</p>
<ul>
<li><strong>Server-side rendering only.</strong> When a block is hidden by a condition, it is not rendered into the page output at all. No CSS <code>display: none</code>, no DOM bloat, no leaked content in view-source. Search engines, screen readers, and your page weight all benefit.</li>
<li><strong>Public Conditions API.</strong> The three built-in conditions are registered through the same public API your plugin or theme can use to add your own. No hacks, no internal-only code paths.</li>
</ul>
<p>In the editor, a subtle dashed border marks every block that carries a visibility rule, so a rule-bearing block never disappears from the published page as a surprise. A “Preview as audience” sidebar lets you simulate a logged-out visitor, a specific role, or a different device class right in the editor — blocks whose rule would hide them fade out with a clear badge, no save-and-reload cycle required.</p>
<h4>Built-in conditions (v1.0)</h4>
<ul>
<li><strong>User state</strong> — show to logged-in users, logged-out users, or specific roles</li>
<li><strong>Date range</strong> — show between two datetimes, timezone-aware</li>
<li><strong>Device type</strong> — show on desktop, tablet, or mobile</li>
</ul>
<h4>Designed for</h4>
<ul>
<li>Agencies and freelancers building client sites who want a clean, predictable visibility tool</li>
<li>Developers who need an extension point, not another walled garden</li>
<li>Anyone who cares about page weight and SEO hygiene</li>
</ul>
<h4>What this plugin deliberately does NOT do</h4>
<p>It does one thing well rather than ten things adequately. Out of scope in v1.0:</p>
<ul>
<li>Multi-condition AND/OR groups (planned for v1.1)</li>
<li>URL / cookie / referrer / geolocation conditions</li>
<li>WooCommerce, ACF, or membership integrations</li>
<li>A settings dashboard</li>
</ul>
<p>If you need those today, <a href="https://wordpress.org/plugins/conditional-blocks/" rel="ugc">Conditional Blocks</a> and <a href="https://wordpress.org/plugins/block-visibility/" rel="ugc">Block Visibility</a> are excellent and well-established choices.</p>
<h4>For developers</h4>
<p>Register a custom condition in three steps. Implement the interface, add it to the registry, ship.</p>
<pre><code>add_action( 'renderwhen_register_conditions', function ( $registry ) {
    $registry->register( new My_Plugin\\Conditions\\Country_Condition() );
} );
</code></pre>
<p>Your condition class implements <code>RenderWhen\Conditions\Interface_Condition</code>:</p>
<pre><code>namespace My_Plugin\Conditions;

use RenderWhen\Conditions\Interface_Condition;

class Country_Condition implements Interface_Condition {
    public function get_id(): string {
        return 'country';
    }

    public function get_label(): string {
        return __( 'Visitor country', 'my-plugin' );
    }

    public function get_schema(): array {
        return array(
            'type'       => 'object',
            'properties' => array(
                'countries' => array(
                    'type'  => 'array',
                    'items' => array( 'type' => 'string' ),
                ),
            ),
        );
    }

    public function evaluate( array $settings, array $context ): bool {
        $current = my_plugin_detect_country();
        return in_array( $current, $settings['countries'] ?? array(), true );
    }
}
</code></pre>
<p>The full set of public filters:</p>
<ul>
<li><code>renderwhen_register_conditions</code> — register your conditions here</li>
<li><code>renderwhen_evaluate_{condition_id}</code> — last-mile override of any condition’s result</li>
<li><code>renderwhen_render_block_hidden</code> — fires when a block is hidden, useful for cache busters and SEO tools</li>
<li><code>renderwhen_device_type</code> — swap in your own device detection</li>
</ul>
<p>The plugin is developed openly on GitHub. Issues, PRs, and architecture discussions welcome: https://github.com/abhishekfdd/renderwhen</p>


RenderWhen for Blocks

Show or hide any block when conditions match. Developer-first API and true server-side rendering — hidden blocks never reach the browser.

teamstaccato

<p>Shed Menu adds visibility conditions to WordPress navigation menu items. You can show or hide each item based on three conditions:</p>
<ul>
<li>Login status (logged in / logged out / everyone)</li>
<li>Date range (start datetime, end datetime)</li>
<li>User roles (administrator, editor, author, contributor, subscriber, or custom roles)</li>
</ul>
<p>All conditions are optional and combined with AND logic. This plugin reads the current user’s role information via <code>wp_get_current_user()</code> to evaluate role-based conditions.</p>
<h4>Three ways to use</h4>
<ol>
<li><strong>Standard menus</strong> — Open Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Menus, expand any item, and set the conditions inline.</li>
<li><strong>Hand-coded themes</strong> — Use the helper function <code>shedmenu_visible()</code> in your <code>header.php</code> or other template files.</li>
<li><strong>Block editor</strong> — Wrap any blocks in the “Shed Menu — Conditional” block to show/hide them based on the same conditions.</li>
</ol>
<h4>Helper function example</h4>
<pre><code><?php if ( shedmenu_visible( [ 'login' => 'in' ] ) ) : ?>
    <li><a href="/mypage/">My Page</a></li>
<?php endif; ?>
</code></pre>
<h4>Shortcode example</h4>
<pre><code>[shedmenu_visible login="in" start="2026-04-01" end="2026-04-30" roles="administrator"]
This content is only visible to administrators between April 1 and April 30.
[/shedmenu_visible]
</code></pre>
<h4>日本語の説明</h4>
<p>WordPress 標準ナビゲーションメニューに、メニュー項目単位の表示条件を追加します。</p>
<ul>
<li>ログイン状態（ログイン中 / ログアウト中 / 全員）</li>
<li>表示期間（開始日時・終了日時）</li>
<li>ユーザーロール（管理者 / 編集者 / 投稿者 等）</li>
</ul>
<p>全ての条件は任意で、AND 条件で組み合わされます。</p>
<p>外観 <span aria-hidden="true" class="wp-exclude-emoji">→</span> メニュー画面で各項目に条件を設定できます。テーマで <code>wp_nav_menu()</code> を使わず HTML 直書きしている場合は <code>shedmenu_visible()</code> ヘルパー関数を使ってください。Gutenberg では「Shed Menu — Conditional」ブロックで任意のブロック群を条件表示にできます。</p>
<h3>Third-Party Services</h3>
<p>This plugin does not connect to any external services. All processing happens on your own server.</p>


Shed Menu

Show or hide WordPress menu items based on login status, user role, or scheduled date range. Adds conditional visibility to your navigation.

RenderWhen for Blocks vs Shed Menu