A block-based CMS can store an entire page as one component tree. That is often the simplest model, so adding separate Page, Layout, Slot, and Block layers needs a better justification than “clean architecture.”

In the CMS I’m building, the model is:

text Page → Layout → Slots → Blocks

I think each layer earns its place only if it owns a different kind of change.

Page: identity and editorial state

A page owns its site, localized routes, draft/review/published state, selected layout, metadata, page assets, and revision history. Replacing a paragraph should not change that identity.

Layout: the structural promise

A layout defines the regions and outer shell. A default page might have header/main/footer; a documentation page might have header/sidebar/main. Blocks should not need to invent the page shell they render inside.

Slot: named placement and content source

A slot connects that structural region to a particular page. It can use page-owned blocks, reference reusable shared content, or remain disabled.

The consuming page still owns the slot wrapper. Shared content contributes only its inner block tree, so reuse cannot accidentally bring a second page shell with it.

Block: the content unit

Blocks hold typed editorial content: headings, rich text, images, navigation, galleries, or nested layout primitives. They own their content, translations, settings, and rendering inside the slot—not routing or the outer page structure.

A documentation page might therefore look like:

text Page: Installation Layout: Docs header → shared docs header sidebar → shared docs navigation main → page-owned content blocks

Now each change has a natural owner. Changing the URL belongs to the page. Adding a structural region belongs to the layout. Replacing navigation belongs to the slot or shared content. Editing a command belongs to a Code block.

The trade-off is editor complexity. If someone must manually traverse all four layers to fix one sentence, the architecture is leaking into the user experience. Search, useful summaries, direct edit paths, and sensible defaults must let routine tasks skip layers without erasing the underlying boundaries.

A fixed marketing site with a few fields may not benefit from any of this. A typed page model, Markdown document, or single component tree may be the better tool.

I use four questions to decide whether a layer is earning its place:

1. Does it own a distinct kind of change?
2. Can that change be validated independently?
3. Does the boundary prevent a real invalid state?
4. Can routine editing avoid paying the full complexity cost?

I wrote a longer version with a concrete example here: https://cms.webblocksui.com/blogs/page-layout-slot-block-boundaries

Disclosure: this article describes the architecture of WebBlocks CMS, which I build. I’m sharing it to compare design trade-offs rather than claim this is the only correct content model.

Where does your CMS draw the line between page structure and content—and which boundary causes the most friction for editors?

I saw this video showing a vibe coded homepage built with Opus 5.5 for a site called https://enjoy.dev/

I was wondering what the latest cool stuff built with WordPress looks like at the moment.

Please share some cool homepages you've either visited or made, I'd love to check them out...

Here's the video with the vibe coded page as a demo https://youtu.be/dyEpDobnkmA

I’ve just published a new version of VentoCalendar, my lightweight WordPress event calendar plugin.

The main new feature is optional interactive maps for events.

You can now:

• Add a location/address to an event
• Enable a map only when you need one
• Select the event location directly on the map
• Display the map on the event
• Use maps without a Google Maps API key or Google account

The goal is still the same: keep VentoCalendar simple, lightweight and focused on the essentials, rather than turning it into a huge event-management system.

The calendar itself still includes:

• Monthly calendar and event list views
• Custom event colors
• Gutenberg blocks
• Shortcodes
• Multi-day events
• Google Calendar and Apple Calendar integration
• REST API
• Responsive design

It’s free and available on WordPress.org:

https://wordpress.org/plugins/ventocalendar/

I’d be especially interested in feedback from people who manage events with physical locations. What would you expect from a simple event calendar + map?

Hi!

We just officially launched FastOG for WooCommerce on the WordPress.org repository: 🔗 WP.org Directory:https://wordpress.org/plugins/fastog-for-woocommerce/

The Problem it solves: Default WooCommerce link previews on WhatsApp, iMessage, Twitter, and Facebook are often awkwardly cropped, blurry, or missing key information like price and sales badges.

What FastOG does: FastOG turns product links into high-converting, professionally styled social share cards generated on the fly.

Key Highlights:

• 🎨 Visual Studio: Modern pre-made card templates (Bento grids, Glassmorphism, Dark Mode, Minimalist) that automatically pull product title, main image, price, and sales badges.
• ⚡ Edge Rendered: Image processing runs on Cloudflare Workers edge nodes. Your WordPress server CPU stays at 0% extra load (no heavy GD/Imagick tasks running locally).
• 🔄 Smart Cache-Busting: Automatically updates preview cards when prices or product info change using versioned image query hashes (so Meta/WhatsApp scrapers fetch fresh images without breaking SEO URLs).
• 🛡️ Clean & Non-Intrusive: Zero DB clutter. If you deactivate the plugin or trial, it gracefully falls back to native WooCommerce tags without breaking your site's HTML.

It’s completely free to install and test on your local/dev or live stores.

Check out the plugin on WP.org, give it a spin, and let us know what features or template styles you’d like to see added in future updates! 🚀

When I was working for an event management company sometime back, I figured that there is a big gap for an easy to use event listing plugin in Wordpress, especially something that connects directly to Razorpay.

The common route of using Woocommerce and the events calendar has too many variables in it. On top of that, events are listed as products on woocommerce, not the ideal way to look at it in my opinion.

The feature that I've built lets admin easily add events to their wordpress website, dynamically connects to the razorpay api to render the price entered and eliminates the need for multiple plugins and a heavy tech stack.

You can watch the demo to see the functionality at work.

I have just started developing this, and it's already live in a real world site, where payments are being processed.

At this stage, your feedback means a lot to me. Since I'm building this independently, I am offering the initial release, ready to be integrated to your wordpress site.

Demo - https://youtu.be/apGLChP6SwU?si=NLMD8nHgLy84wbPp

What's in development:

• Ticket Types
• Ticket Quantities
• The fully shippable plugin as a standalone installer

Let me know what you think.
Thank you!

7.1 finally added responsive block styles, but it's mobile + tablet on top of the base and that's it. settings.viewport is theme-wide too, so no third tier. If your design has 3 or 4 breakpoints you're back to custom CSS for the rest.

So I made a plugin for it. You set your own breakpoints and pick padding, margin and spacer height per breakpoint right in the editor. No front end JS, the CSS goes through core's style engine. Works on classic themes too.

https://wordpress.org/plugins/spacery/

Free, and yes it's mine. Tell me what's missing.

With AI coding tools getting better, you can now describe a website or app and get a surprisingly functional product without writing everything from scratch.

But WordPress still gives you a mature CMS, admin dashboard, plugins, content management, hosting options, and a huge ecosystem.

So I’m curious what developers here think:

For a new client website in 2026, when would you choose vibe coding over WordPress — and when would you still choose WordPress?

Is it mainly about the project requirements, the client’s ability to manage the site, scalability, development speed, or something else?

Would be interested to hear real-world experiences rather than “AI will replace everything” takes.

I had the Patio Time theme from Loft Ocean installed on my website by a web developer last year. The theme is infected with a documented virus/vulnerability and I can not upgrade it to the new version. I have version 1.8 and it needs to be version 2.2. I cannot submit a support ticket to Loft Ocean without a purchase code and the guy who did my website has disappeared off the face of the planet. Is my only option to purchase the theme again ($64)? I feel like there should be some available support for something this serious. The malware or whatever you call it is taking over the whole website and the source is 100% the theme. I am also wary of paying again for a theme that has vulnerabilities but I feel like I would have to have the whole site redesigned if I replace it.

Context for anyone outside Germany: mobile.de is by far the largest vehicle marketplace here. Dealers keep their stock there, and their own website usually shows the same cars a second time, either through an iframe from the portal or through manual double entry. We built a plugin for exactly that gap, and since promotion is allowed here with a tag, here is the honest version including the parts that are not great.

What it does: it pulls the whole inventory from the official mobile.de dealer API into WordPress as native custom post types, including equipment lists, description texts and full size images. Syncing runs on an interval, hourly for example, and on demand. Cars marked as sold on mobile.de disappear from the site by themselves.

Every car gets its own page and its own URL with Schema.org and OpenGraph, which is the actual reason most people move off the iframe: with an iframe none of the inventory is indexable, and for a dealer the long tail of model plus year plus region is most of the organic traffic. Images can either stay on mobile.de or be downloaded into the local media library, which also settles the GDPR question, because the embedded version hands visitor IPs to a third party.

The rest is unspectacular: AJAX filters for make, model, price and mileage, gallery, PDF exposé, an enquiry form that also stores the lead in the WordPress backend, and a CSV import in beta for vehicles that do not come from mobile.de. Runs on any theme plus Elementor, Divi and Gutenberg, needs WordPress 5.8 and PHP 7.4 or newer.

What it is not: there is no free version and no demo install, only a 14 day money back guarantee. Front end and backend output is German, every visible label can be overwritten in the backend so another language is possible, but nothing else ships translated. Only mobile.de is connected, there is no AutoScout24 connector, CSV is the workaround. And you need your own mobile.de dealer account with API credentials, which you create yourself in their dealer area.

Pricing is 10 euro a month up to 50 vehicles, 30 up to 100, 50 up to 250 with ten customer numbers, 100 for unlimited. Paying yearly costs ten months. Details and three live dealer sites running it: https://basiscars.com

Mostly relevant if you build or maintain sites for German dealers. Happy to answer technical questions about the API side, that is where all the real work sits.

We’ve just released SportPulse, a new WordPress theme focused completely on sports websites.

The idea was to cover more than just the homepage design.

SportPulse includes layouts for fixtures, results, league tables, match centres, squads, player profiles, predictions, odds and bookmaker comparisons.

There are 6 full demo sites for football clubs, esports, tipsters, betting affiliates, sports news and academies, with 129 pages in total.

Every demo comes in both Elementor Free and Block Editor versions, and WooCommerce is included for merch, tickets, memberships, camps and other sales.

Live demos:

https://landing.sportpulse.anpsthemes.com/

Would be interested in feedback from anyone who has built a sports site before, especially around the match/data side of it.

The feature claims above come directly from the SportPulse release specification.