luzidmedia

Luzid Content Scheduler controls when a specific frontend block is visible — and can also output the next scheduled date(s) via shortcode.
This gives you two complementary ways to use a scheduler:
<ol>
<li>
Show / hide a block (banner, alert, section, popup wrapper, …) 
Add the generated CSS class <code>luzid-cs-<slug></code> to the element. The plugin adds body classes and a tiny frontend helper so the block is only displayed while the schedule is active.
</li>
<li>
Display dates in the frontend 
Use the shortcode to print the next event (or a list of upcoming events) anywhere in your content.
</li>
</ol>
<h4>Typical Use Cases</h4>
<ul>
<li>Maintenance banners: Show a “We’re updating our systems” notice only during scheduled maintenance windows.</li>
<li>Seasonal content: Display holiday greetings, special offers, or seasonal menus during specific date ranges.</li>
<li>Event announcements: Print “Next event: Saturday, March 15th at 7 PM” dynamically on any page.</li>
<li>Recurring schedules: Show “Happy Hour specials” every Friday from 5 PM to 8 PM.</li>
<li>Multi-stage visibility: Use Event Classes to show a popup 4 days before an event, the full content 2 weeks before, and a menu item 11 days before — all independently controlled.</li>
<li>Event calendars: Generate a table of all upcoming events across multiple schedulers.</li>
</ul>
<h4>Core Concepts</h4>
<ul>
<li>A scheduler becomes active when at least one rule matches (single dates/ranges or recurring rules).</li>
<li>Exceptions override everything: if “now” is inside an exception range, the block is hidden even if other rules match.</li>
<li>Event Classes (new in 1.4) allow multiple independent visibility windows with different offsets — each generating its own CSS class.</li>
<li>The shortcode reads the same event logic and outputs formatted dates with full control over separators and formatting.</li>
</ul>
<h3>Features</h3>
<h4>Scheduling</h4>
<ul>
<li>Single dates & date ranges: Define specific days or periods when content should be visible.</li>
<li>Recurring rules: Weekly (every Monday), Monthly (every 15th), Weekday in month (2nd Thursday), Yearly (February 14th).</li>
<li>Exceptions: Override all rules — content stays hidden during exception periods.</li>
<li>Event Classes: Create multiple CSS classes per scheduler, each with independent visibility offsets.</li>
</ul>
<h4>Shortcode Output</h4>
<ul>
<li>Flexible date/time formatting: Choose from short, medium, long, or full date formats.</li>
<li>Separators: Control exactly what appears between date, time, and text parts.</li>
<li>Lists: Output multiple upcoming events with customizable separators.</li>
<li>Event Table: Generate a sortable table of all upcoming events from multiple schedulers.</li>
<li>Time offset: Shift the displayed time (e.g., “doors open 30 minutes before”).</li>
</ul>
<h4>Administration</h4>
<ul>
<li>Card-based UI: Clean, modern interface for managing rules.</li>
<li>Live preview: See upcoming events and visibility windows instantly.</li>
<li>Bilingual: Full German and English support with one-click language switching.</li>
</ul>
<h3>Usage</h3>
<h4>Adding CSS Classes to Blocks</h4>
<ul>
<li>Gutenberg: Select block → “Advanced” → “Additional CSS class(es)” → <code>luzid-cs-<slug></code></li>
<li>Elementor: Widget → “Advanced” → “CSS Classes” → <code>luzid-cs-<slug></code></li>
<li>Divi/others: Module settings → “CSS Class” → <code>luzid-cs-<slug></code></li>
</ul>
<h4>Basic Shortcode</h4>
<pre><code>[luzid_cs slug="your-scheduler"]
</code></pre>
Outputs: The next event date in the default format.
<h4>Shortcode Parameters</h4>
 Parameter 
 Default 
 Description
 <code>slug</code> 
 (required) 
 Scheduler slug
 <code>date</code> 
 (empty) 
 Date format: <code>short</code>, <code>medium</code>, <code>long</code>, <code>full</code>
 <code>time</code> 
 (empty) 
 Time format: <code>auto</code>, <code>raw</code>, <code>prefix</code>, <code>range</code>, <code>range_long</code>
 <code>list</code> 
 <code>false</code> 
 Output as list: <code>true</code> or <code>false</code>
 <code>count</code> 
 <code>10</code> 
 Number of events for lists (max 200)
 <code>text</code> 
 <code>false</code> 
 Include event text: <code>true</code> or <code>false</code>
 <code>sep1</code> 
 (space) 
 Separator between date and time
 <code>sep2</code> 
 (space) 
 Separator between time and text
 <code>sep3</code> 
 (empty) 
 Separator between list items
 <code>timeoffset</code> 
 <code>0</code> 
 Time offset in minutes (can be negative)
 <code>lang</code> 
 (current) 
 Force language: <code>de</code> or <code>en</code>
<h4>Date Formats</h4>
 Value 
 Output Example
 <code>short</code> 
 14.02.2026
 <code>medium</code> 
 Sat, 14.02.2026
 <code>long</code> 
 Saturday, 14.02.2026
 <code>full</code> 
 Saturday, 14 February 2026
<h4>Time Formats</h4>
 Value 
 Output Example
 (empty) 
 No time output
 <code>raw</code> 
 18:00
 <code>prefix</code> 
 from 18:00
 <code>range</code> 
 18:00 to 20:00
 <code>range_long</code> 
 from 18:00 to 20:00
 <code>auto</code> 
 Intelligent format based on data
<h4>Shortcode Examples</h4>
Simple date output: 
 [luzid_cs slug=”maintenance” date=”long”] 
→ Saturday, 15.03.2026
Date with time: 
 [luzid_cs slug=”event” date=”long” time=”auto”] 
→ Saturday, 15.03.2026 from 18:00 to 20:00
Only time output: 
 [luzid_cs slug=”event” time=”raw”] 
→ 18:00
Multi-line output: 
 [luzid_cs slug=”event” date=”long” time=”auto” text=”true” sep1=” ” sep2=” “] 
→ Saturday, 15.03.2026 
 from 18:00 to 20:00 
 Valentine’s Dinner
List of next 5 events: 
 [luzid_cs slug=”concert” date=”long” text=”true” list=”true” count=”5″ sep2=” ” sep3=”
“]
With custom separators: 
 [luzid_cs slug=”event” date=”long” time=”raw” text=”true” sep1=” | ” sep2=” – “] 
→ Saturday, 15.03.2026 | 18:00 – Valentine’s Dinner
<h4>Event Table Shortcode</h4>
<pre><code>[luzid_cs_eventtable]
</code></pre>
Outputs a table of all upcoming events from schedulers with “Include in Event Table” enabled.
 Parameter 
 Default 
 Description
 <code>cols</code> 
 <code>date_medium,time_auto,text</code> 
 Columns (comma-separated)
 <code>count</code> 
 <code>30</code> 
 Maximum number of events
 <code>headers</code> 
 (automatic) 
 Custom column headers
 <code>noheaders</code> 
 <code>false</code> 
 Hide table headers
 <code>class</code> 
 (empty) 
 Additional CSS class
 <code>empty</code> 
 “No events” 
 Text when no events found
 <code>order</code> 
 <code>asc</code> 
 Sort order: <code>asc</code> or <code>desc</code>
Available columns: 
 date_short, <code>date_medium</code>, <code>date_long</code>, <code>date_full</code>, <code>weekday_short</code>, <code>weekday_long</code>, <code>time_raw</code>, <code>time_auto</code>, <code>time_prefix</code>, <code>time_range</code>, <code>time_range_long</code>, <code>text</code>, <code>scheduler</code>
Example with custom columns: 
 [luzid_cs_eventtable cols=”weekday_short,date_short,time_range,text” count=”10″ headers=”Day,Date,Time,Event”]
<h4>Event Classes (New in 1.4)</h4>
Event Classes allow you to create multiple independent visibility windows for a single scheduler. Each class has its own CSS class and offset settings.
Example setup:
 Class 
 CSS Class 
 Days Before 
 Use Case
 Standard 
 <code>.luzid-cs-dinner</code> 
 14 
 Main content
 popup 
 <code>.luzid-cs-dinner-popup</code> 
 4 
 Announcement popup
 menu 
 <code>.luzid-cs-dinner-menu</code> 
 11 
 Navigation menu item
This allows you to control when different elements appear, all based on the same event schedule.
<h4>CSS Hooks</h4>
Shortcode output: 
* <code>.luzid-cs</code> — Wrapper (plus <code>.luzid-cs--single</code> / <code>.luzid-cs--list</code>) 
* <code>.luzid-cs-item</code> — Single event in list 
* <code>.luzid-cs-date</code> — Date part 
* <code>.luzid-cs-time</code> — Time part 
* <code>.luzid-cs-text</code> — Event text 
* <code>.luzid-cs-sep</code> / <code>.luzid-cs-sep1</code> / <code>.luzid-cs-sep2</code> — Separators
Event table: 
* <code>.luzid-cs-eventtable</code> — Table wrapper 
* <code>.luzid-cs-eventtable__head</code> / <code>__body</code> / <code>__row</code> / <code>__cell</code>
Body classes (for conditional CSS): 
* <code>.luzid-cs-active-<slug></code> — Added when scheduler is active 
* <code>.luzid-cs-active-<slug>-<classname></code> — Added when specific event class is active
<h3>License</h3>
This plugin is licensed under the GNU General Public License v2.0 or later.
All code in this plugin is GPLv2-or-later compatible.
Assets: 
* Luzid Logo and Flag icons are SVG assets shipped with the plugin (assets/img/).

Luzid Content Scheduler

Show/hide frontend content blocks (banners, alerts, divs) with schedules, recurring rules and exceptions — via CSS class or shortcode.

Sofia Sousa

foadyousefi

Frontkom

ajotka

Gutenberg Cloud: Your online library of blocks! Cloud Blocks is the only plugin you need to browse and install new blocks:
<ul>
<li>Discover and install custom blocks with a click</li>
<li>Install only the blocks you need – no huge plugin collections needed</li>
<li>Reuse blocks between WordPress and Drupal</li>
<li>Serve the blocks from a CDN</li>
</ul>
<h3>Why use Gutenberg Cloud?</h3>
Installing an actual plugin for each block or block collection easily leads to managing lots of code that you don’t really need. It’s like having one app for each website you visit, instead of just installing a web browser. With the block manager, you have a growing library at your fingertips, without the bloat.
<h3>Getting started</h3>
<ol>
<li>Install the plugin</li>
<li>Click the new cloud icon in the main menu</li>
<li>Browse around and click a block to see description, version and bigger screenshot</li>
<li>Activate a few blocks. Voila – these are now available to you in the Gutenberg editor!</li>
</ol>
<h3>How it works under the hood</h3>
Gutenberg Cloud is a service that fetches Open Source Gutenberg blocks hosted on NPM. The assets from these are served from CloudFlare using jsdelivr.com. The Cloud Blocks plugin provides an interface in WordPress for Gutenberg Cloud.
Code once, use everywhere: Since the blocks are JS/CSS only, they are CMS agnostic. This means you can develop a block for a Drupal site, and reuse it later on a WordPress blog.

Cloud Blocks

This concept, having a common repo for blocks, accessible directly from WP admin, just like for plugins and themes, is the way to go. You can select exactly the blocks you neeed with a click and disable them also with a click. No need to have users see a lot of listed blocks that just happen to be installed by plugin that has only one block you really need.

Nothing is downloaded, they work from the cloud.

Can be network activated.

But more, as you can add local blocks that become visible in special tab on the Cloud Blocks activation/deactivation screen.

And you can contribute to the global repo through NPM.

Fantastic, almost unbelievable

Your online library of Gutenberg blocks! Browse and discover new blocks, and install with a click.

Luzid Content Scheduler vs Cloud Blocks