GeneratePress and GenerateBlocks: Building in the Block Editor the GeneratePress Way

Nine blocks and a philosophy

GenerateBlocks, the free plugin from the GeneratePress team, stood at version 2.4.1 with 200,000+ active installs as of October 2026. Its 2.x block set is short. In the editor you see Container, Text, Image, Shape and Query, plus Looper, Loop Item, No Results and Page Numbers, which live inside a Query. Grid is a variation of Container. Headline and Button are variations of Text. The plugin's description says it outputs minimal CSS, only for what a page needs, and keeps the HTML simple.

That brevity is the point and the price. A Container block can be a section, a card, a flex row or a grid, depending on its settings, which is closer to writing CSS than to picking a widget. Developers and designers who think in boxes love it. An owner who expected an Info Box, a Testimonial and a Pricing Table block will find patterns instead, built from the same few parts. Pro adds Accordion and Tabs blocks, plus Navigation and Site Header blocks, and more than 200 patterns.

GenerateBlocks gives you fewer blocks so that you have fewer things to keep consistent.

Version 1 or version 2: find out which blocks your site actually runs

Any GeneratePress site older than the 2.0 release of GenerateBlocks probably holds version 1 blocks: the old Container, Grid, Headline, Button and Image blocks. They still work, and new installs default to version 2. Upgraded sites keep offering version 1 blocks until someone turns off Use version 1 Blocks in GenerateBlocks > Settings. So a five-year-old site may be adding fresh v1 blocks today without anyone deciding to.

1. 1

   Check the setting

   Open GenerateBlocks > Settings and see whether Use version 1 Blocks is on. If it is, every new block added today is legacy.

2. 2

   Turn it off for new work

   Switching it off makes the inserter offer 2.x blocks. Existing v1 blocks keep rendering where they are used.

3. 3

   Convert where it pays

   Headline and Button blocks transform into Text, and Container, Grid and Image map across. The vendor's migration guide says Query Loop, Accordion and Tabs cannot be transformed, so rebuild those by hand.

4. 4

   Recheck templates and Block Elements

   Headers, footers and loop templates built as Block Elements often use v1 blocks too. GP Premium adds Dynamic data options to v1 blocks, but new templates should use 2.x blocks with dynamic tags.

5. 5

   Test after each GenerateBlocks update

   Layouts disturbed by an update have their own checklist: GenerateBlocks layout broken after update.

Colors as variables, styles as classes, tokens on the way

GeneratePress keeps its palette under Appearance > Customize > Colors. New sites start with seven named swatches: Contrast, Contrast 2, Contrast 3, Base, Base 2, Base 3 and Accent. Each becomes a CSS variable such as var(--accent), and the docs say those variables appear in the block editor's color pickers. Pick the Accent swatch in a GenerateBlocks button and the button follows the Customizer forever. Type a hex value and it does not. One caution from the docs: renaming or deleting a palette color leaves any element using it without a value.

GenerateBlocks Pro adds Global Styles, reusable sets of styles applied as classes, so every card or button carries one shared definition. The September 2026 Pro 2.8 update, called Design Systems, goes further: Design Tokens that name CSS variables (a Primary Color rather than a hex code), global styles that target any selector including plain h1 or a WooCommerce button, a Style Book of common HTML elements and a design workspace under Dashboard > GenerateBlocks > Design. The vendor's own post said 2.8 was still a release candidate on September 22, to be tried on a test site first.

Block Elements: a theme builder made of blocks

GP Premium's Elements module is where GeneratePress becomes a site builder, and Block Elements are its block-based half. Create one under Appearance > Elements > Add New > Block, choose a type, build it with blocks and set display rules. The docs recommend GenerateBlocks for building them, say core blocks work too, and warn that blocks from other plugins may not be styled correctly.

Each Block Element has an Editor Width setting; set it to the real width of the area, such as your sidebar, so the editor shows what visitors will see. Display rules need a Location or the element shows nowhere, and exclusion rules deserve a check after you delete pages, since a deleted excluded page has been reported to blank the rule. Missing elements are covered in GeneratePress Elements not displaying.

Editor Access: the feature agencies waited years for

The oldest complaint about block-built client sites is that the client can change anything. GenerateBlocks 2.4 and Pro 2.7, announced in July 2026, answer it with Editor Access, under GenerateBlocks > Editor Access. It works with Access Profiles, which bind user roles, post types and specific blocks to an editing mode: read-only, content-only (text and media) or unchanged. Profiles also control which blocks a role may insert at all.

Control Sets go further. Instead of the full block inspector, a role sees only the controls you choose, from presets for typography, spacing, colors, layout and borders, or a custom set. The vendor ships starter profiles for client review, blog authors and shop managers. In practice that means a homepage hero can be locked while blog posts stay fully editable for authors. Both GenerateBlocks and GenerateBlocks Pro must be active. As of October 2026, GenerateBlocks Pro costs $99 a year for up to 500 sites; the bundle math is on GeneratePress pricing.

Layout settings that make block pages behave

A few theme settings decide whether GenerateBlocks sections look the way they did in the editor. The Layout meta box, below the content in the block editor, has a Content Container tab with Default, Full Width and Contained. Full Width spans the screen with no padding, which GenerateBlocks full-width sections need. Contained keeps the site width but hands spacing to your blocks. Both remove content padding on purpose, which explains most padding mysteries.

• If the Layout box is missing, open the editor's three-dot menu, then Preferences > General, and switch Layout on under Advanced.
• For many pages at once, a GP Premium Layout Element applies the same choices through display rules.
• For the reading width, Container Width defaults to 1,200 pixels under Customize > Layout > Container; set long-form pages narrower with a Container block rather than a wider site.
• For devices, the docs list mobile up to 768 pixels, tablet from 769 to 1,024 and desktop from 1,025, with hide-on-mobile, hide-on-tablet and hide-on-desktop classes for blocks.

The GeneratePress speed guide covers the theme's CSS print settings and font hosting, which matter more on a block site because there is no builder weight hiding them. Header problems specific to Block Elements are in GeneratePress header not showing, and stale styles in GeneratePress CSS not updating.

The road ahead: a Template Engine, and what to build today

GeneratePress is mid-transition. An August 7, 2026 post on its blog describes GP Premium 3.0 as a reinvention of the Elements module, named Template Engine, for fully block-built sites, and the September GenerateBlocks Pro post calls it upcoming. It had not shipped when we checked. The free theme's last wordpress.org release was 3.6.1 in December 2025, and the vendor has not said how long the classic theme continues alongside the new tools.

Our advice is practical. Build new layouts with GenerateBlocks 2.x blocks and dynamic tags, since that is the direction every announcement points. Keep Block Elements simple and documented, so they can be rebuilt in whatever replaces them. Avoid investing in v1 blocks or elaborate Hook Element PHP. And keep a staging site, because a site that leans on Elements is exactly the kind of site a Template Engine migration will touch. Everything else we have written about the theme is in the GeneratePress repair hub.

Where a lean block site still runs out of road

A GeneratePress and GenerateBlocks site is about as lean as WordPress gets, and for a blog, a publisher or a services site we will often recommend staying. The limits are not about weight. They arrive when the site needs logged-in members, custom data, quote tools or hundreds of pages generated from a database, and every one of those becomes another plugin with its own update schedule.

GeneratePress vs Next.js is the fairest comparison we publish, because the theme is genuinely good. Block content moves cleanly: GenerateBlocks containers and text map to components, and GeneratePress to Next.js covers the plan with every URL kept. Teams who value Editor Access will find the same idea at the center of Athena CMS, where editors fill in approved components and every version is kept. If you are still choosing a theme, start with the GeneratePress review, Kadence vs GeneratePress and the WordPress themes section. For hands-on help with a block build, our theme customization team works in GenerateBlocks daily.