Blocksy and the Block Editor: A Gutenberg Site With No Page Builder Plugin

A Gutenberg stack with no page-building plugin in it

CreativeThemes says Blocksy was built from scratch to be fully compatible with the block editor, and the theme's layout bears that out. Global choices live in the Customizer: colors, typography, widths, the header and footer builders. Page content lives in core blocks. The free Blocksy Companion plugin, at version 2.1.58 with 300,000+ installs as of October 2026, adds a set of theme blocks and the extension framework that Blocksy Pro builds on.

That gives a typical Blocksy site three or four parts: the theme, Companion, core WordPress blocks and, if a feature needs it, Pro. Compare that with a theme plus a builder plus an add-on pack plus a widget library, and the appeal is obvious. Fewer plugins means fewer update collisions, fewer stylesheets and fewer places for a layout to break. The trade-off is that core blocks are plainer than a page builder's widgets, so some layouts take more thought.

The lightest block plugin is the one you never installed.

What Blocksy Companion adds to the block inserter

Blocksy's theme blocks appear in the editor as long as Companion is active. Most are free. The Pro ones lean toward WooCommerce filtering and reusable content. We list them by job, because the names alone do not say much.

Notice what is missing: tabs, accordions, sliders, pricing tables and testimonial carousels. Core WordPress and Blocksy's patterns cover some of that ground, and a block plugin covers the rest. Contact Info and Breadcrumbs are small but useful, because they replace the footer and navigation snippets owners usually paste in as HTML, which then breaks when someone edits the wrong character.

Advanced Posts plus Dynamic Data: listings without a query plugin

The most capable pairing in Companion is Advanced Posts with Dynamic Data. Advanced Posts shows blog posts or any custom post type on any page. Inside it, Dynamic Data blocks pull each item's title, excerpt, date, comments, author and avatar, featured image or terms. Together they build the card grids, related-post rows and service listings that usually require a separate query-loop plugin.

With Blocksy Pro, Dynamic Data can also read custom fields from Advanced Custom Fields, ACPT, Meta Box, Pods, Toolset and JetEngine. That is the point where a Blocksy site starts acting like a small content system: a Locations post type with an address field and a phone field, listed by Advanced Posts and displayed with Dynamic Data, all without code. It is also the point to document the structure, because the next person to edit the site needs to know the fields exist.

1. 1

   Insert Advanced Posts

   Choose the post type and the query options in the block settings.

2. 2

   Design one item

   Arrange Dynamic Data blocks for the image, title and excerpt inside the first card. The rest follow.

3. 3

   Use palette colors only

   Cards repeated twenty times magnify any off-brand color. Pick palette swatches so a later change in the Customizer reaches every card.

4. 4

   Check the phone layout

   Blocksy's mobile breakpoint sits at 689.98 pixels in the theme CSS. Preview at that width as well as at a typical phone width.

Making the editor look like the front end

The fastest way to frustrate an editor is a block editor that looks nothing like the live page. Blocksy narrows that gap in three places. The Global Color Palette, under Customizer > General Options > Colors, starts with eight colors, accepts more through Add New Color, and is exposed to the block editor along with any colors you add. Each color has a CSS variable you can copy from its picker. Under General > Layout, Narrow Container Width sets the reading width and Wide Alignment Offset sets how far wide-aligned blocks extend. And per page, Content Area Style chooses Wide or Boxed.

When the editor and front end still disagree, the usual suspects are fonts loaded on the site but not in the editor, a cached global.css that has not caught up with a Customizer change, or a block plugin's own styles. Blocksy's Dynamic CSS Output writes that global.css by default, so regenerate it and clear the page cache before blaming the editor. The mechanism is explained in block editor not matching the theme, and stale styles in Blocksy CSS not updating.

Content Blocks: templates and hooks built in the block editor

Blocksy Pro's Content Blocks are where the block editor becomes a theme builder. Under Blocksy > Content Blocks you create Hooks, Pop-ups or Templates, and the docs show each one opening on a blank Gutenberg canvas. Template types cover the header, footer, 404 page, single and archive layouts, a maintenance page and the no-results page. All of them run through the Conditions module, which targets pages, post types, taxonomies, user roles and languages.

• Location and priority pick the hook position and the order when several blocks share it. Visiting the front end as an admin and clicking Hook Locations in the toolbar shows every position.
• Container Structure chooses Default, None or Custom, and Custom offers Boxed or Wide width and a Standard or Narrow content layout.
• Dynamic Content Preview loads a real post into the editor so dynamic blocks show actual data while you design.
• Visibility turns the block on or off for desktop, tablet and mobile.
• The Content Block block drops any Content Block into a page, which makes a promo banner or a disclaimer reusable across the site.

Content Blocks work with WPML, Polylang and TranslatePress, with conditions per language. As of October 2026, Blocksy Pro starts at $69 a year for one site, or $199 lifetime; see Blocksy pricing for which plan includes which extensions.

Patterns made of core blocks outlive the theme

Blocksy's Gutenberg Patterns sit in the inserter under a Blocksy category: hero sections, pricing tables, text cards, testimonials and calls to action. The docs stress that they are built entirely from native blocks, with no extra plugin. That detail matters more than it looks. A pattern built from core blocks is just core blocks once inserted. Switch themes, or move the content to another system, and those blocks still mean something.

Compare that with a builder layout stored in a proprietary format, which turns into a page of unreadable data the moment the builder is gone. If you think you might ever leave Blocksy, or WordPress, the core-block route keeps that door open. It is also why Blocksy sites tend to migrate cleanly, as the Blocksy to Next.js plan describes.

If you add a block plugin, choose one and choose carefully

Sooner or later a site wants tabs, an accordion with schema or a fancier slider, and a block plugin arrives. Blocksy's docs say its palette is available in supported third-party block plugins and name Stackable as an example, so palette support is the first thing to check in any candidate. The second is weight: prefer a plugin that loads assets only for blocks a page uses. The third is restraint.

• Install one block plugin, not three. Two plugins with overlapping row and button blocks guarantee two slightly different buttons on the site.
• Switch off the blocks you do not need in the plugin's settings, so editors see a short, sensible inserter.
• Keep structure in core blocks where possible, and use the plugin only for the interactive pieces.
• Test the plugin with Blocksy's patterns, since mixing plugin blocks into core patterns is where spacing drifts.

If the site really wants a full builder experience, Blocksy with Elementor covers that route honestly. Our theme customization team sets up Blocksy block sites to a brand guide, including the inserter cleanup.

Updates, speed and the limits of a lean block stack

A block-only Blocksy site is fast by construction: no jQuery-dependent theme scripts, CSS written to a file, the emoji script one switch away. Two cautions remain. Local Google Fonts is a Pro extension, so free sites load fonts from Google. And Blocksy ships often; the 2.1.58 release stripped input elements from the header builder's HTML element, and 2.1.50 broke some WooCommerce product layouts. Update the theme and Companion together on staging, using Blocksy update broke my site when one slips. The Blocksy speed guide covers measurement.

The limits arrive with features, not weight: logins, member areas, quoting, data that lives outside WordPress. Blocksy vs Next.js weighs that fairly, and the Blocksy review and GeneratePress vs Blocksy help if you are still choosing within WordPress. The full list of reviews is in the WordPress themes section, and stubborn faults go to our theme troubleshooting service.