WordPress 7.1 · core/group
<!-- wp:group {"style":{"spacing":{"padding":
{"top":"100px","bottom":"100px"}
}}} -->One value. It is 100 pixels at 1440, and it is still 100 pixels at 390.
BLOCKS
Free edition
MevvBlocks
A hundred pixels on desktop, forty on mobile.
The WordPress block editor is fast and native, but it is missing one thing: there are no breakpoints for style values. If a section should have 100 pixels of padding on desktop and 40 on mobile, core cannot express it — measured again on WordPress 7.1. That single gap is the most common technical reason people install a page builder. MevvBlocks closes it first: every measurement can carry a desktop, a tablet and a mobile value, on ordinary blocks in the ordinary editor. Around it sits what a site actually needs to stand on its own afterwards — seventeen blocks, a form engine, theme templates, popups, one screen for the site palette, and an accessibility audit that tells you the truth instead of covering it up.
The gap
A core block can only hold one number.
When you give a section padding in the block editor, that value is a single number. The same number is printed on a 1440-pixel screen and on a 390-pixel phone. The spacing that looks right on a desktop splits the page in half on a phone, and the usual answers are hand-written CSS or a page builder. This is the third answer: the same setting, with a tablet and a mobile value next to it.
MevvBlocks · mevvsoft/container
<!-- wp:mevvsoft/container {"ayarlar":{
"padding": {"top":"100","unit":"px"},
"padding_tablet": {"top":"64", "unit":"px"},
"padding_mobile": {"top":"40", "unit":"px"}
}} -->The same setting, three values. Nothing else about the block changes.
What the server prints
.e-con-1a2b { --padding-top:100px }
@media (max-width:1024px) { .e-con-1a2b { --padding-top:64px } }
@media (max-width:767px) { .e-con-1a2b { --padding-top:40px } }Saved HTML can only carry one breakpoint, so the CSS is produced at request time instead — which is also why these values keep printing when a licence lapses.
- Desktop 100 px
- Tablet · ≤1024 64 px
- Mobile · ≤767 40 px
That core blocks carry no breakpoint attribute was checked against WordPress 7.1 itself, not taken from documentation: core/group supports padding, background, min-height, borders and flex or grid layout — each of them as a single value. The breakpoints above are the plugin’s own, and the media queries are the ones it actually writes.
Capabilities
It starts at the breakpoint. It does not end there.
A site that has just left a page builder needs more than spacing: a contact form, a header and footer it can still edit, a palette it can still change. Each of these exists because something broke without it.
Style per breakpoint
Every measurement can carry a separate desktop, tablet and mobile value. Core WordPress cannot — that was measured on 7.1, not assumed.
Seventeen blocks
Container, heading, text, button, divider, image, testimonial, icon, icon box, icon list, shortcode, form, slider, tabs and accordion — plus products and product categories when WooCommerce is installed.
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 breakpoint, 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.
Measured
Numbers we counted, not numbers we rounded.
Every figure below can be counted in the plugin source. Where a number would sound like a performance claim, it is not made: page weight depends on the theme, the host and the cache, and we have not measured yours.
- 17
- blocks — 15 without WooCommerce installed
- 16
- form field types, plus a file field in Pro
- 6
- template types: header, footer, single, archive, search, 404
- 5
- popup triggers: load, scroll, exit, click, inactivity
- 43
- bundled icons, drawn in one 24-pixel box
- 0
- licence checks on the rendering path — enforced by a test
Counted in the plugin source on 31 August 2026. For scale, and only for scale: the free and Pro editions together are 485 KB and 28 KB of source, while Elementor, Ultimate Addons and Header Footer Elementor together take 178 MB on disk in the installation we measured. That is a difference in surface area, not a claim about speed — and a good part of it is simply the features we do not have.
Pricing
All prices include VAT.
A lapsed licence never darkens a page. Values written by the Pro breakpoint panel keep being printed by the free edition, and the form keeps taking submissions. What closes is the editing panel, not the look of the site.
1 USD = 48,2613 ₺ (TCMB rate)
Scope
What it does, and what it still does not.
It is worth being precise. This closes one specific gap in core WordPress and carries a site that has left a page builder. It is not a replacement for a full page builder, and the list on the right is what you would notice missing if you tried to use it as one.
What it is for
Breakpoints· in ordinary blocks
- ✓Separate desktop, tablet and mobile values
- ✓Seventeen blocks, sliders, tabs and accordions among them
- ✓Forms, popups and theme templates with conditions
- ✓One screen for the site palette and typography
- ✓Nineteen ready sections and pages, plus saved block presets
- ✓Entry animation, sticky position and parallax — off by default
- ✓Landing on a site that has just left a page builder
Blocks live in post_content as standard block markup, not in a private table. Remove the plugin and the content is still readable.
What it is not
Not a builder· seventeen blocks, not fifty
- 1No query or loop builder for custom post listings
- 2No per-block display conditions
- 3No navigation menu, social icons or image box block
- 4No countdown, counter, map or pricing table block
- 5Editor preview is approximate; the front end is the exact one
Elementor’s free edition registers 37 widgets; this is seventeen blocks. Both numbers were counted on installed copies, not estimated — and they are the reason the claim here is kept narrow.
And the part that matters when a licence lapses: values written by the Pro editing panel keep being printed by the free edition. What you lose is the panel, not the look of the site.
Start
A hundred pixels on desktop, forty on mobile.
Install the free edition and the blocks, the forms, the theme templates and the popups are all there. Pro adds the panel that lets you edit the tablet and mobile values — and if it ever lapses, those values keep printing.
Product information
- Product type
- WordPress block pack
- The gap it closes
- Core blocks have no breakpoints
- Blocks
- 17, or 15 without WooCommerce
- Free edition
- Blocks, forms, theme templates, popups, global styles, accessibility audit
- Pro
- Breakpoint panel, per-block custom CSS, conditional form logic and file field
- Source size
- Free 485 KB + Pro 28 KB, measured 31 August 2026
- Requirements
- WordPress 6.0+, PHP 8.1+