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.

LaughterOnWater

<p>TimeFly adds powerful time-based visibility control to WordPress through a custom block that automatically shows or hides content based on your schedule. Perfect for announcements, seasonal promotions, business hours, and any content that should only be visible during specific times.</p>
<h4>Key Features</h4>
<ul>
<li>
<p><strong>Three Visibility Modes:</strong></p>
<ul>
<li>Show Until – Content visible now, hidden after specified date/time</li>
<li>Show From – Content hidden now, visible after specified date/time</li>
<li>Show Between – Content only visible within specific date/time range</li>
</ul>
</li>
<li>
<p><strong>Flexible Scheduling:</strong></p>
<ul>
<li>One-time schedules for specific dates</li>
<li>Recurring weekly schedules for business hours or regular events</li>
<li>Support for complex recurring patterns</li>
</ul>
</li>
<li>
<p><strong>User-Friendly Interface:</strong></p>
<ul>
<li>Real-time visibility status preview in editor</li>
<li>Site timezone awareness with current time display</li>
<li>Visual status indicators (visible/hidden/misconfigured)</li>
<li>Validation to prevent invalid date ranges</li>
</ul>
</li>
<li>
<p><strong>Developer Features:</strong></p>
<ul>
<li>Clean, semantic HTML output</li>
<li>SEO-friendly (hidden content absent from HTML)</li>
<li>Works with any WordPress block inside</li>
<li>Professional code quality and documentation</li>
</ul>
</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Display “We’re Open!” during business hours</li>
<li>Show seasonal promotions during specific dates</li>
<li>Hide outdated announcements automatically</li>
<li>Display event information only until event date</li>
<li>Show different content for weekdays vs weekends</li>
<li>Create time-sensitive calls-to-action</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Add a TimeFly block to any page or post</li>
<li>Select your visibility mode (Show Until, Show From, or Show Between)</li>
<li>Choose one-time or recurring weekly pattern</li>
<li>Configure your dates and times</li>
<li>Add your content inside the block</li>
<li>Publish – content automatically appears/disappears on schedule</li>
</ol>
<p>All scheduling uses your WordPress site timezone for accurate visibility control.</p>
<h4>Technical Details</h4>
<ul>
<li>Uses WordPress block editor (Gutenberg)</li>
<li>Server-side rendering for security and performance</li>
<li>Transient caching for efficient block scanning</li>
<li>No database tables created</li>
<li>Lightweight with minimal performance impact</li>
</ul>
<h3>Support</h3>
<p>For support, feature requests, or bug reports, please visit the <a href="https://wordpress.org/support/plugin/timefly/" rel="ugc">WordPress.org support forum</a>.</p>
<h3>Developer Information</h3>
<p>TimeFly is built with modern WordPress development practices:</p>
<ul>
<li>React-based block editor interface</li>
<li>Server-side rendering with PHP</li>
<li>WordPress coding standards compliant</li>
<li>Comprehensive PHPDoc documentation</li>
<li>Security-first approach with proper sanitization</li>
<li>Performance-optimized with transient caching</li>
<li>Accessibility-ready with ARIA attributes</li>
</ul>
<h4>Source Code</h4>
<p>The compiled JavaScript in <code>/build/index.js</code> is built from human-readable source files in the <code>/src</code> directory of the plugin. Source files include block.json, edit.js, save.js, render.php, and SCSS stylesheets. The build process uses @wordpress/scripts. All source code is included in the plugin distribution.</p>
<p>The plugin is open for contributions and feature suggestions. Visit the support forum to participate in development discussions.</p>
<h3>Privacy Policy</h3>
<p>TimeFly does not collect, store, or transmit any user data. All scheduling information is stored locally in your WordPress database as part of block content. No external services are contacted. No cookies are set. No analytics are tracked.</p>
<h3>Credits</h3>
<p>Developed by LaughterOnWater with a focus on code quality, user experience, and WordPress best practices.</p>


TimeFly

Control when content appears on your WordPress site with dynamic time-based visibility scheduling.

RenderWhen for Blocks vs TimeFly