Frequently Asked Questions

Why is Blockade better than other visual editors?

Blockade is lightweight, and works within the WordPress framework, rather than replacing it. Most visual editors attempt to be a one-size-fits-all solution for all tasks. Blockade is different. Blockade knows it’s just one of the tools in your arsenal, and helps you make all of them more effective.

Why not formatting shortcodes, then?

With wp_autop making it so you can’t even add whitespace around shortcodes without inserting unwanted tags, formatting shortcodes can quickly turn your content into an unreadable mess.

What’s wrong with entering raw HTML in Text mode?

Beside the fact that your clients probably don’t know HTML, WordPress seems to take pride in its ability to mangle raw HTML on save, or any time a user switches to Visual mode.

Is Blockade going to cost me anything?

The Blockade core is free and open source, and the development team is committed to keeping it that way. You will never have to pay a cent for the core plugin. The Blockade team has also developed an API to assist in creating add-ons to provide additional functionality to Blockade. Some of these add-ons may be sold for a fee. However, unlike many other plugins of the sort, the core plugin is not intentionally crippled in any way.

What browsers are supported by Blockade

The admin interface for Blockade is designed to be used in evergreen browsers, and is tested in:

  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge

However, pages designed using Blockade should work for all browsers back to IE8 (the same minimum compatibility as Bootstrap 3.3.7).  Older browsers may, however, see degraded effects and features to match their capabilities.  As always, if you find a bug, please let us know.

I found a bug! What do I do now?

  1. Figure out how to reproduce the bug and take detailed notes on the steps involved.
  2. Try to reproduce the bug in different browsers or on different operating systems, if possible, and take notes on the results.
  3. Disable all non-Blockade plugins and change your theme to Twenty Fifteen, to verify that the bug still exists.  Take notes on the results.
  4. If the issue is related to a plugin or theme, attempt to identify which plugin or theme causes the bug to appear. Take notes on the results.
  5. Either post your bug to the Support section of the WordPress plugin page, or contact us directly, with all notes.
  6. Watch the thread and check your email. We may reach out for additional information or assistance to isolate and resolve the bug.
  7. Be patient. We are a small team and Rome wasn’t built in a day, but we are listening

Why did Blockade reset all my fonts?

If Blockade cannot verify that your theme includes the Bootstrap framework, it will add a version of Bootstrap, that is wrapped in the wp-blockade class. Either declare Bootstrap in the theme, with add_theme_support('bootstrap', '3.3.7');, or override the font for the following selectors:

.wp-blockade h1, .wp-blockade h2, .wp-blockade h3, .wp-blockade h4, .wp-blockade h5, .wp-blockade h6, .wp-blockade .h1, .wp-blockade .h2, .wp-blockade .h3, .wp-blockade .h4, .wp-blockade .h5, .wp-blockade .h6, .wp-blockade samp, .wp-blockade .tooltip, .wp-blockade .popover

How do I add Blockade to a custom post type?

Simply add the following code to your functions.php file (rename the function and replace foo and bar with the slugs for your post types):
// Add Blockade to the custom post types "foo" and "bar"
add_filter('wp-blockade-override-post-types', 'add_my_blockade_post_types');
function add_my_blockade_post_types( $post_types ) {
    $post_types[] = "foo";
    $post_types[] = "bar";
    return $post_types;

Why isn’t my Breakout block spanning the viewport?

The breakout block is subject to a few unique limitations, that your theme can interfere with. It cannot expand outside a block which has its overflow property set to anything except visible. It also may seem obvious, but Breakout blocks will interfere with sidebars.

Can I add Blockade to a site that already has content?

Yes! Unlike some visual editors, Blockade will easily work with existing content. Your pages’ content will automatically be placed in an Editable Content block. From there, you can cut and paste portions of your content into other blocks, for rearrangement and formatting.

How can I speed up a Blockade site?

Blockade is a modular system, and as such can enqueue several different scripts and styles that can affect your loading time. We recommend using a minifying plugin such as Autoptimize or W3 Total Cache to combine and compress these resources.

What should I NOT use Blockade for?

Unlike other visual page builders, Blockade is not meant to be a one-stop solution for designing your entire site.  There are several situations where we recommend using different tools, along side Blockade, to bring your design to life.

  1. Common design elements that will appear on every page are best to build with custom fields and templates, or even with shortcodes. Since Blockade creates your design directly in HTML, redesigning a site that uses Blockade for every repeated element is a pain, as the elements will need to be modified or replaced on each page where they appear.  This is acceptable for small sites (such as this one, where all page headers were built in Blockade), but quickly becomes unmanageable as the size of the project increases.
  2. Searchable or Indexable data, like product attributes or biographical data are best stored in custom fields and retrieved by custom templates or shortcodes.  This data may need to be accessed on archive pages, or used to filter posts, so it makes sense to break it out from the post content.
  3. Some animated features are much better served with shortcodes than Blockade. For example, Slider Revolution and Layer Slider have put a huge amount of effort into their slider plugins, and it makes much more sense to use them as is, than to attempt to recreate that functionality in Blockade. Some type of simple slider may eventually be included in Blockade as an addon, but in most cases, it’s a good idea to stick with the existing solutions.
  4. Data that draws from other posts or database structures, like lists of related posts or archives, should be built using taxonomy archives, shortcodes, or custom templates. Since this data changes over time, it makes much more sense to manage it in a central codebase, rather than manually updating it on every page change.

These limitations are by no means absolute, and every site is different.  For example, a ten page site can get away with building every page element in Blockade, without too much technical debt being accrued, but a large organization with hundreds of pages shouldn’t do the same.  In addition, some of these limitations are a matter of the current state of Blockade, and may be addressed in future builds.

The primary point to take away is that Blockade is not meant to be a one-size-fits-all solution. It’s simply a new (and powerful) tool for Developers, Designers, and Users, to help make WordPress a more flexible CMS for everyone.

How can I help develop Blockade?

Easy as pie! Fork Blockade on Github, and start making changes. Then simply commit your changes and issue a pull request. The Blockade team will review your changes, and if they fit with the internal roadmap, they may be accepted into the core.

How can I join the Blockade team?

Blockade is a product of Burlington Bytes, a full-service digital marketing firm in Burlington, VT. If you have the chops to work on cool projects like Blockade, and you like the idea of joining a healthy, outdoorsy team of extreme nerds in one of the best cities in America, check out our careers page.