The Unblock affiliate program is now open 🚀
If you've been spreading the word about Unblock, you can now get paid for it. 30% on every sale you bring in.
Sign up here: https://t.co/XE2R4gEkJ7
Gutenberg Core Blocks are annoying.
Easy to use for non techies, but terrible for html and css oriented devs.
This One Block to rule them all, changes it all.
@o_b@FatonB95 Yes. The goal is code access, but also a two-way sync interface. For styles it already exists, and the same is in the works for everything else: query builder, dynamic data selector, conditions, etc. It's all on the roadmap: https://t.co/2frBN9ZOm2
WordPress plugins give you a block for every element. Unblock has just one. Any HTML element. No restrictions. CSS just works — selectors, pseudo-classes, states. All of it, natively. The block editor, the way it should have been. Coming soon...
#WordPress#Gutenberg
InfluenceWP First Look—Unblock
The Unblock WordPress plugin enhances the native WordPress block editor (Gutenberg), pushing it beyond its boundaries.
- Full Code Access
- Dynamic Content
- Conditional Display
- Queries & Loops
- and more!
https://t.co/Te0zn6Kqdr
Hard to say without testing, but Unblock exposes its own abilities, so any plugin compliant with the WordPress 7.0 Abilities API can tap into them.
Also worth noting, the AI chat inside Unblock is optional and runs on WP 7 AI connectors with your own key. And Unblock has its own MCP feature (built on the official WP MCP), so any agent can build full pages with it directly.
https://t.co/X1AkJlDC2y
Thanks for the thoughtful feedback, you're absolutely right that reusing existing variables matters a lot. For full context: this demo starts from a blank page, so there's nothing to reuse. When variables and selectors already exist, Unblock passes them as context so the AI builds on top of the design system instead of reinventing it.
Built an iOS SaaS hero in the WordPress editor with the new @vercel_dev AI Gateway plugin ⚡
→ 40+ providers, one key (Mistral, xAI, DeepSeek, MiniMax…)
→ One prompt, 96 structured blocks
→ Every selector editable in CSS
Native to the WP 7.0 AI Client. Massive work by @felixarntz on both sides of this bridge 🙌
Yes, this is where it gets interesting.
Generation is easy now. The real work is what happens after: reading the output, changing it, trusting it. WordPress has the right foundation for that. The engine between AI and the CMS, the one that makes generated output editable and trustworthy, is where things are moving now...
Appreciate the honest take. If you've got specifics on what felt disjointed, drop them here, way more actionable than a thread: https://t.co/qLb6cbdnpk
On the "WP way" though, staying native isn't a compromise, it's the whole point. The block you place IS the HTML element, no abstraction layer, no custom blocks to sync, no proprietary syntax, just the open web. Full ecosystem in (themes, ACF, Woo, future core APIs), portable HTML/CSS/JS out. Etch chose to step outside core and build its own expression syntax, legit bet, just a different one.
Twig is battle-tested since 2009, powers Drupal core and Symfony, and has been running WordPress sites through Timber since 2013. LLMs already speak it fluently. Picked precisely to avoid reinventing syntax, every custom one means edge cases to debug, deprecations to manage, and migrations down the road.
Dark mode: noted.
Unblock 1.0 Beta is here 🚀
Shipping today alongside WordPress 7.0, built on its new AI APIs for native AI in the block editor.
→ One universal block, every HTML element
→ Global CSS, tokenized and centralized
→ Dynamic data with Twig + Timber
��� AI assistant, bring your own key
Lifetime Deal now open. 30% off until June 10 ⏳
https://t.co/zB6Mq2wo6K
Yes, several layers already. Non-admins don't see the code editors (CSS, HTML, JS). The whole design system (selectors, variables, fonts, inspector) is locked to admins server-side, not just UI-hidden, and overridable per role (with code currently). Native WP block locking and content-only patterns also work on any Unblock block.
A few users have raised the idea of choosing exactly what to lock and for whom. A direction worth exploring.
Fair question, the HTML/CSS/JS panels look alike because that's the open web showing through (DevTools, CodePen).
The real difference: Etch is a separate editor that authors into its own custom blocks with its own expression syntax. Unblock has no separate editor, you stay in Gutenberg, the block you place IS the HTML element, and the whole stack is open-web standards end-to-end (HTML, CSS, JS, Twig). That means native WP ecosystem compat, nothing to sync, no proprietary syntax, and AI-native by design (LLMs already speak it).
More here → https://t.co/joIA0Y2ZAe
@wpgaurav A plugin. Works with any theme, FSE or classic. Ships with a blank FSE theme as a neutral base so Unblock stays the single source of truth for styling, no theme CSS getting in the way.
Most builders end up inventing their own dialect. A custom schema here, a binding syntax there.
Unblock went the other way. HTML, CSS, JS, Twig. Nothing else underneath.
A bit on how that happened:
https://t.co/WYNPk66S4X
Finally. Unblock is out.
In French, *un bloc* means "one block."
In English, *unblock* means freeing the editor from its limits.
That's the whole pitch: every block in Gutenberg = one real HTML element. No nested wrappers, no abstraction layer. What you build is what ships.
The AI part follows naturally: no custom schema to learn, every LLM already speaks the open web. The chat is Unblock. The model is yours, configured in WP 7.0.
Lifetime Deal opens next week with WP 7.0. Demo is live now.
Meet Unblock.
https://t.co/joIA0Y2rKG
@pootlepress In the meantime I recorded the hero — just one prompt, raw result. The full page is doable but since it’s really long I’d need to split it into around 30 screenshots to keep the LLM interpretation accurate.