Nine products,
one WordPress site,
every screen accounted for.

From header to footer, inside the block editor.

The WordPress block editor is fast and native, but it cannot give one measurement a separate value for desktop, tablet and mobile — measured again on WordPress 7.1, and the most common technical reason people install a page builder. MevvBlocks closes that gap and then keeps going: a hundred and ten blocks, theme templates from header to footer, a post grid and loop builder, a form engine, popups, transforms and masks, site-wide custom code, one screen for the site palette, WebP and AVIF for your images, block-level caching, an accessibility audit that tells you the truth instead of covering it up, and a Core Web Vitals screen fed by your own visitors. The catalogue now runs from a toggle and nested tabs to a pie chart, a media playlist, a tooltip, a newsletter form and an SVG animation, with eight block styles in the editor’s own Styles panel — and every one of them stops moving when the visitor has asked for reduced motion. The canvas is no longer an approximation either: the editor asks the server for the same CSS the page will print, so what you arrange is what ships. Twenty-three of those blocks are for WooCommerce, and none of them redraws WooCommerce: they call its own templates, so your theme and your plugins keep working.

Every measurement, per screen size

A padding, a font size, a column count can carry a separate desktop, tablet and mobile value. Core WordPress cannot — that was measured on 7.1, not assumed. The same panel also lifts an element out of the flow with absolute or fixed positioning, and its offsets and z-index are per-device too.

A hundred and ten blocks

Layout, text and media; menu, search, post grid and loop builder; site logo, page title, breadcrumbs, post info and author box for theme templates; video, audio, playlist, gallery, table, FAQ, timeline and code; toggle, nested tabs, pie chart, tooltip, newsletter, social feed, flip box, call to action, animated headline, before/after, hotspots, off-canvas panel and contact buttons — and twenty-three for WooCommerce, from the product gallery to the cart, the checkout and a mini cart. Eighty-seven without WooCommerce.

Eight block styles, in the panel WordPress already gives you

A gradient overlay, grayscale or blur until hover, a circle or rounded mask, lift, zoom and tilt — chosen from the core Styles panel, so there is no new control to learn and the choice is a class in your markup rather than a setting in a table. Every hover transform is switched off when the visitor’s system asks for reduced motion, and the still frame of an SVG animation is swapped in the same way.

A newsletter form that does not need a service

An address, an optional name, a consent box and a plain POST — signed with the same HMAC the form engine uses, so a cached page never dies with an expired nonce. The honeypot is swallowed in silence, the rate limit is per address, and addresses land with your other form submissions. There is no list, no API key and no request to anyone: the mevvblocks_newsletter_subscribe action hands each confirmed address to whatever you already use.

Dynamic text, including your ACF fields

A heading, a text, a button or an image can read its value from the post rather than from what you typed: title, excerpt, author, date, category, tags, archive title, search term, the WooCommerce price, SKU or stock, or a custom field by key. When Advanced Custom Fields is active the field is read through get_field() so you get the formatted value, and keys beginning with an underscore are refused rather than exposed.

What you see in the editor is what the page prints

The canvas no longer shows an approximation: padding, spacing, direction, alignment, background, radius, shadow, transform and position appear with the values the front end will use. One style engine produces that CSS and the editor fetches it from the server — writing a second engine in JavaScript would have given us two copies that drift apart. Measured: the old canvas differed from the page in 24 layout properties; it is now zero out of 64.

Core Web Vitals, from your real visitors

LCP, CLS and INP are measured in the browsers of the people who visit your site, and the 75th percentile over a 28-day window is what the screen shows — field data, the kind Search Console looks at, not a lab run. Below a hundred samples no number is shown at all, because a percentile from a handful of measurements is noise. No IP, no cookie, no identifier is collected, and the data never leaves your own server.

AI with your own key

Write, rewrite, shorten, translate and generate image alt text. You enter your own API key and the request goes from your site straight to the provider — your text never reaches us, and the quota stays yours. The result arrives as a suggestion, not written straight into the block.

Your theme’s palette, without retyping it

Colours and typography can be read out of the active theme’s theme.json and used to fill the empty slots in the plugin’s own palette. The bridge is deliberately one-way: nothing is ever written back into the theme, so a theme update never finds its own file rewritten underneath it. It is off until you turn it on.

A mega panel on the menu you already have

Not a new block — a setting on the navigation block. A submenu opens as a full-width panel of up to four columns, and if you switch the panel on for an item that has no submenu the accessibility check says so instead of printing an empty box.

A first draft of a page, from one sentence

Describe the page and the model picks sections from the plugin’s own template library. It never writes markup, so what lands on the page is editable blocks rather than generated HTML, and a section it names that does not exist is dropped and reported rather than guessed at. The page is always saved as a draft, and the key is yours.

Notes your visitors never see

Pin a note to any block for your team, mark it resolved, delete it. It lives in the editor and there is not a single front-end hook that could print it.

Faster, and measured

Block output is cached and images are converted to WebP or AVIF next to the originals — the originals are never touched. Measured: block render time down 33–72%, image weight down 39–78%. Images are served through a <picture> element so the same HTML reaches everyone; deciding per visitor on the server is what poisons a page cache. You can also serve a different image on phones — not a smaller copy of the same one, a different shot — and the browser still makes the choice.

A form engine, not a dependency

Sixteen field types, validation on the server, a honeypot that is swallowed in silence, and a screen where submissions are kept. The form works without JavaScript, because it is the one part of the page that actually does something.

Theme templates with conditions

Header, footer, single, archive, search and 404 — built in the WordPress editor you already use, not in a second one we would have to keep in step with core.

Popups that survive the switch

Open on load, on scroll depth, on exit intent, on a click or after inactivity. Frequency is counted in the visitor’s own browser, so nobody has to be identified on the server.

One screen for the site palette

Colours and typography in one place, under their original variable names — so pages built before the switch pick up the new palette instead of losing their references.

An accessibility audit, not an overlay

No widget is bolted onto the page claiming the site is accessible. It reports what each block left out — missing alt text, a broken heading order, weak contrast — while you are still editing.

Slider, tabs and accordion without a library

Scrolling is native scroll-snap and the accordion is a details element. If the script never loads, nothing is hidden: hidden content is inaccessible content.

Rendered on the server, never tied to the licence

Saved HTML can only carry one screen size’s value, so the CSS is produced at request time. There is not a single licence check on that path — a lapsed licence never darkens a published page.

Product page ↗ Documentation ↗ Live demo ↗