At first look, you'd say I'm using @WebStormIDE .
But it's not. It's my own vibe-coded IDE.
With only the features I need.
And super fast b/c it's a native app built with rust + GPUI (wanted to use the same tech stack as @zeddotdev).
A bit of polishing still, but works great!
Webiny is on fire with updates - if you need "agentic" or AI CMS that can power monstrous enterprise websites (or website networks, publishing workflows, you name it) - look no further. Retweet for more karma :D
As much as I love @Zellij_dev , I still felt making the functionality it has directly in my agentic coding app was a better UX overall.
And it was. Loving the new addition. 🤗
Basically cmd+d/cmd+shift+d for new panes. Cmd+arrow to move around. Cmd+shift+enter for full screen.
Summer’s hot. So is our release cycle. :fire:
6.4 was a big one. 6.5 is shaping up to be even bigger.
AI showing up in more places — entry creation, page translation, revision comparison. A brand-new CMS content model editor. CMS Live Preview for Next.js. New Asset field type. Image cropping in File Manager. A GraphQL playground built from scratch.
Landing hopefully next week. More on each of these soon. :eyes:
In Webiny’s AI Power Ups you configure your AI setup once — Writer Personas that define the tone, and Projects that bundle instructions and context (there are Reader Personas too, for audience).
Here’s the fun part: you can apply that setup to your content in bulk.
Over on the Products list, select a few entries, open the “Generate AI summary” bulk action, and pick one of your Projects or Personas. That’s it. Each product gets summarized following exactly the setup you chose — and it runs as a background task, so you can keep working while it churns through the batch. Open any product afterwards and the AI field is filled in.
The nice bit for developers: there’s no prompt-engineering plumbing, no API keys, no model juggling in the bulk action. It just hands the entry to AI Power Ups, which uses the provider and instructions you already configured. :robot_face:
Same bulk-action → background-task pattern as the discount demo from before; the only difference is that the per-entry step is an AI call.
#headlesscms #cms #C09ET2Z2UAF
One other quirk I wanted to tackle with this feat is me accidentally hitting a key on keyboard and not noticing it.
And then often agents would just go nuts / had to discover where the change came from. 😄
Since long gone are the days of manually writing code, I made sure my code editing app is in READ-ONLY mode by default. If you start typing on purpose (or accidentally), then a tooltip will remind you of that.
Pretty awesome addition!
One of the things I wanted to have in my IDE is a nice code review exp. Features I wanted:
- select file/cmd+d to see the differences
- continue diffing in diff window if you like
- filter all/viewed/unviewed or by search string
- nice progress bar at the bottom🤩
- sync with gh
At first look, you'd say I'm using @WebStormIDE .
But it's not. It's my own vibe-coded IDE.
With only the features I need.
And super fast b/c it's a native app built with rust + GPUI (wanted to use the same tech stack as @zeddotdev).
A bit of polishing still, but works great!
Did you know that you can add your own custom bulk actions to any CMS model in Webiny?
Here’s one in action. Select a few product entries, hit “Apply -10%,” and confirm. The discount runs as a background task, so you’re free to keep working right away.
It’s also powered by real-time notifications — a “Discount task started” message tells you it’s underway, then each entry reports back as it updates: -10% applied, new price 53.96, and so on.
And this is just one example. The discount is something we built, but you create your own — whatever action makes sense for your models. :rocket:
At first look, you'd say I'm using @WebStormIDE .
But it's not. It's my own vibe-coded IDE.
With only the features I need.
And super fast b/c it's a native app built with rust + GPUI (wanted to use the same tech stack as @zeddotdev).
A bit of polishing still, but works great!
At first look, you'd say I'm using @WebStormIDE .
But it's not. It's my own vibe-coded IDE.
With only the features I need.
And super fast b/c it's a native app built with rust + GPUI (wanted to use the same tech stack as @zeddotdev).
A bit of polishing still, but works great!
@pierskarsenbarg That does make sense.
What's also interesting to me is that, previously, I was kinda leaning more towards less-verbose method naming. But now, I don't mind it at all.
AI is going to use that anyways and the more descriptive the name - the better.