Skip to content
Morgan Hvidt

Conditional Blocks

Create personalized WP content in minutes.

Visit Conditional Blocks

I built Conditional Blocks because I was tired of writing the same visibility logic for WordPress clients.

Show this banner to logged-in users. Hide that section on mobile. Different copy by role. Simple stuff, but WordPress makes you write custom code or drop in a heavy plugin for every toggle.

The Conditional Blocks homepage: "Create personalized WP content in minutes", with a no-code plugin intro and Get Started button.

When everything became a block

The idea came when WordPress released Gutenberg, now called the block editor. Everything became a block, and with full site editing, even the header and footer are blocks.

So I figured if everything is a block, I should be able to choose when each one shows, and to whom. Click any block, set the conditions, and that's it.

What people use it for

It grew into something far more flexible than I first planned, with 36+ visibility conditions. People use it for things I didn't expect:

  • Membership sites, with user roles and membership levels
  • Personalised marketing for stores, with URL query strings for coupons and secret content from emails
  • Content for different places, with geolocation
  • Device, date ranges, and plenty more

I use it on my own sites and still do today, and on sites for several clients I've worked with.

Works with the plugins you already use

A big part of why people picked it up was using it for something specific to their own site. So it connects to the plugins they already run:

  • WooCommerce, to show specific products, upsells or offers based on what's in the cart, the cart total, or what a customer has spent
  • Advanced Custom Fields, to show a block based on a field's value, including fields saved on the user
  • Paid Memberships Pro and ProfilePress, for content by membership level or plan
  • FluentCRM and WP Fusion, for content by CRM tag or list
  • Easy Digital Downloads, for content based on the cart or past purchases

Small on purpose

The point is that anyone can change when something on a site shows, quickly, without diving into the code. That's why I keep the plugin small.

Developers can still add their own conditions with the Conditions API. A sensible default, and a way out.

Get in touch

The best way to reach me right now is on X.

Contact me on X

Join my newsletter

Notes on the products I’m building and what I’m learning.