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 available
MevvBlocks
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.
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 screen size’s value, 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 cannot vary a value by screen size 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 screen limits above are the plugin’s own, and the media queries are the ones it actually writes.
Capabilities
It starts with the phone. It does not end there.
A site needs more than spacing: a contact form, a header and footer it can still edit, a palette it can still change. You may be building from an empty page, or arriving from a page builder — either way, each of these exists because something broke without it.
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 <code>mevvblocks_newsletter_subscribe</code> 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 <code>get_field()</code> 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 <code><picture></code> 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.
The catalogue
A hundred and ten blocks, in five groups.
These are the same five groups the plugin puts on its own showcase pages, and every block below renders on the server: it is in the page before a single script has run. Nothing here is Pro-only except the three blocks that say so.
Text and action
Heading, rich text, an animated headline that can type its words, button, call to action, icon box, icon list and checklist, separator, and an alert you can make dismissible — dismiss it and the focus moves on rather than vanishing. Toggle, nested tabs with their own panels, accordion and FAQ are all built on details/summary and the ARIA tab pattern, so nothing is hidden from a reader whose script never arrived.
Data and pricing
Counter, progress bar, data bar, number box and a pie or donut chart whose values are also printed as a list, because a chart nobody can read is a decoration. Pricing table and price list, testimonial, star rating and testimonial carousel, team member. Pro adds the content switcher: a monthly/yearly tab strip with a badge, over panels that can hold any blocks you like.
Portfolio and map
Timeline — vertical, or horizontal on a wide screen and back to vertical on a narrow one without changing the reading order — steps, an accessible data table with proper column headers, and a comparison block. The map is an OpenStreetMap embed that asks before it loads. Pro adds the portfolio: cards rendered on the server, a taxonomy filter applied in the browser with no outside request, and a link to the archive. There is no modal and no pagination.
Media and forms
Video and audio, a playlist with subtitles and posters where every track is an ordinary link before the script touches it, gallery, before/after, flip box, banner, hotspots and a tooltip that opens on hover, on focus and on tap. Forms: the sixteen-field engine, login and registration, and the newsletter — a signed POST with a honeypot and a rate limit that hands the address to your own list. The social feed is a hand-picked list of links: no API, no token, no request to anyone.
Design and motion
Entrance animation, sticky position and parallax; eight block styles in the core Styles panel — gradient overlay, grayscale, blur, circle and rounded masks, lift, zoom, tilt; an SVG animation shown as an image so nothing inside the file can reach your page, with a still frame swapped in under reduced motion; 94 stroked icons with no icon font; and dynamic text from a custom field, read through Advanced Custom Fields when it is there. There are no scroll-linked animations.
The five groups are open pages on our demo installation: block catalogue — text and action, data and pricing, portfolio and map, media and forms, design. What is deliberately absent is written down too: no modal or pagination on the portfolio, no API adapter behind the social feed, and no scroll-linked timeline.
How it works
The ordinary editor, with the controls a builder has.
No second canvas, no separate application. You select a block and the panel on the right carries what a page builder would give you — for desktop, tablet and mobile separately.
Select a block, the panel is right there
Layout type, direction, minimum height, content width, alignment, gap. Ordinary blocks in the ordinary editor — nothing new to learn, and your content stays standard block markup in post_content.
Transforms, masks and team notes on every block
Rotate, scale, skew, flip and mask — each with separate desktop, tablet and mobile values. And a note pinned to the block for your team: it lives in the editor and is never printed on the page.
And it actually runs on the page
A flip box on a real page: the front face, the back face, and a button that works with the keyboard too — the recording below is a real page, not a mock-up. The block renders on the server, so a lapsed licence never darkens it.
And then it tells you what your visitors actually experienced
LCP, CLS and INP measured in real visitors’ browsers, shown as the 75th percentile over 28 days — field data, the kind Search Console looks at, not a lab run. The screen below is a real installation: note the one cell that refuses to show a number, because fourteen samples is not a percentile.
Images: WebP and AVIF, without touching the originals
One screen. A file that does not shrink is not kept. And if another plugin is genuinely doing this job, MevvBlocks stands down on its own and says why — the question is not "is it installed" but "can it actually run".
We run our own store on it
mevvshop.com is a real WooCommerce store and its pages are built with these blocks — header, footer, product cards and all. Every number on this page was measured there or on our demo installation, not estimated.
In use
Eleven frames from the catalogue pages.
Every frame is a public page of wp-demo.mevvsoft.com with the free plugin and Pro active, captured at 1440 and 390 pixels and cropped to the section it shows. No admin screen, nothing drawn or retouched.
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.
- 110
- blocks — 87 without WooCommerce installed
- 94
- bundled icons, drawn in one 24-pixel box — no icon font
- 8
- block styles in the core Styles panel, every one of them silent under reduced motion
- 42
- rendered checks against the five catalogue pages on the demo installation — 42 passed, none failed
- 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
- 29.828
- bytes of frozen HTML that the menu, image box, social icons and copyright blocks made editable again on our own store
- 0
- layout differences between the editor canvas and the published page, out of 64 properties compared
- 0
- licence checks on the rendering path — enforced by a test
Counted in the plugin source on 8 September 2026. For scale, and only for scale: the free and Pro editions are 1.8 MB and 82 KB of PHP, JS and CSS, while Elementor, Ultimate Addons and Header Footer Elementor together took 178 MB on disk in the installation we measured on 31 August. 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. The forty-two rendered checks are the ones <code>tools/katalog-dogrula.php</code> runs against the five catalogue pages you can open yourself on the demo installation.
Pricing
All prices include VAT.
A lapsed licence never darkens a page. Values written by the Pro editing 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 = 50,7641 ₺ (İşbank rate)
Questions people ask before installing it
Do I have to learn a new editor?
No. These are ordinary WordPress blocks in the ordinary block editor, and your content stays as standard block markup in post_content — not in a table of ours. Remove the plugin and the content is still readable HTML.
What does the free edition leave out?
All 110 blocks, the form engine, the newsletter, the theme templates, the popups, the block styles, the icons, the image optimisation, the block cache and the accessibility audit are free. Pro adds the panel for editing the desktop, tablet and mobile values, per-block custom CSS, the content switcher, the filterable portfolio, the Lottie embed, and conditional logic, auto-reply, webhooks, a file field and CSV export in forms.
What happens when the licence lapses?
Your pages keep rendering exactly as they are, including the tablet and mobile values the Pro panel wrote — the free style engine prints them. What closes is the editing panel. There is not a single licence check on the rendering path, and a test asserts that on every release.
Where do newsletter addresses go?
Into your own site, with the other form submissions. There is no list of ours, no API key and no request to a third party: the block fires a mevvblocks_newsletter_subscribe action with each confirmed address so you can hand it to whatever you already use. The form is a plain POST signed with an HMAC rather than a nonce, because a nonce dies silently behind a full-page cache.
Does anything animate against the visitor’s wishes?
No. Every hover transform in the block styles, the flip box, the marquee, the typing headline and the entrance animations are switched off when the system asks for reduced motion, and an SVG animation swaps to a still frame. The first word of a typing headline is always printed, so the sentence is never a blank.
Does it load anything from a third party?
The plugin makes no request of its own: no library from a CDN, no font from someone else’s server, no telemetry. Three things reach outward and each is your decision — the AI helpers, with a key you enter yourself; the map, an OpenStreetMap embed that asks for consent first; and the Lottie embed in Pro, which asks the same way and shows a still image until you agree. The social feed talks to nobody at all: it is a list of links you picked.
Can a block read one of my ACF fields?
Yes. A heading, text, button or image can take its value from a custom field by key; with Advanced Custom Fields active the value is read through get_field() so you get the formatted one, otherwise it falls back to raw post meta. Keys beginning with an underscore are refused — those are WordPress’s internal fields and printing them would leak what a page never meant to show.
What is deliberately not in it?
The portfolio has no modal and no pagination. The social feed has no API adapter. There are no scroll-linked animations. The map is one marker with no styling and no directions. There is no accessibility overlay, no CAPTCHA and no live search. Each of those is a decision written down in the source, not an omission we discovered later.
Start
From header to footer, inside the block editor.
Install the free edition: all hundred and ten blocks, the forms, the newsletter, the theme templates, the popups, the eight block styles and seventy-six ready sections and pages are already in it. Pro adds the panel for editing the desktop, tablet and mobile values, plus the content switcher, the filterable portfolio and the Lottie embed. What you lose is the panel, not the look of the site: if the licence lapses, those values keep printing.
Product information
- Product type
- WordPress block pack
- What it is
- A page builder inside the block editor
- Blocks
- 110, or 87 without WooCommerce
- Block styles
- 8, offered in the core Styles panel — all reduced-motion aware
- Icons
- 94 stroked SVGs drawn in one 24-pixel box — no icon font
- Patterns
- 76 ready-made: 64 sections and 12 full pages
- Free edition
- Blocks, forms, newsletter, theme templates, popups, block styles, global styles, image optimisation, block caching, custom code, accessibility audit
- Pro
- Desktop/tablet/mobile panel, per-block custom CSS, content switcher, filterable portfolio, Lottie embed, conditional form logic and file field
- Source size
- Free 1.8 MB + Pro 82 KB of PHP, JS and CSS, 8 September 2026
- Requirements
- WordPress 6.0+, PHP 8.1+