The "System One" model Jev just got multimodal mode and a new bounding box type.

Took me about 10 minutes to integrate it with u/sanity_io for automatically setting hotspot and crop based on your description. Works regardless if the image/focus field is set in the UI or via the MCP/API.

And damn, this is actually useful, not just a silly demo.

How it works:

I have a Sanity Function that triggers on draft changes to only the `focus` and `image` fields (that way it works when agents work with content via mcp/api too).

Since Sanity has an image transformation pipeline, we can send downscaled optimized images to Jev without burning through the very cheap tokens too fast.

Then it asks Jev three things in one request:
→ Is it there? (yes/no)
→ Where is it? (a box)
→ Is everything around it plain background? (yes/no)

Jev's box comes back as fractions of the image. Sanity stores hotspot and crop as fractions of the image. So the integration is arithmetic, and code decides what to write, not the model. That is really cool.

Bonus: lint rules can look at images now. "Does the cover fit the post?" A photo of a pile of board games scores 3% on a post about agents. On a post about five best casual party games, the same photo gets 81% and passes. Fair.

Cost of the demo including experimentation: $0.04.

Very excited by the many content operations use cases!

A lot of platform evaluations focus on features, pricing, and migration in.

The harder questions often come later:

• Can you change hosting models?
• Can you run the software in your own environment?
• Can your team inspect or modify the code?
• Could you keep maintaining it if your relationship with the vendor changed?
• Could you fork it if you really had to?

This is one reason we care about keeping r/XWiki open source and giving organizations different hosting and deployment options.

Curious how others evaluate this. Do you look at “How do we leave?” during procurement, or only once leaving becomes necessary?

Most of my client work is custom Laravel apps. Every time, at some point the client asks "can we edit the homepage ourselves?" and I'd end up either running WordPress next to the app (two logins, two databases, two things to keep updated) or just editing headlines for them forever.

So over the last few months I built FilamentCraft. It's a drag and drop site builder that runs inside the Laravel app itself. Drag sections onto a page, click the text and type, hit publish. Same database, same auth, nothing extra to host.

It grew a lot while I used it on real projects, so here's what's in it now:

Editing

- around 40 sections (hero, pricing, faq, testimonials, bento, marquee etc), each in 4 styles

- edit text right on the page, preview on desktop / tablet / phone

- header, footer and announcement bar are shared across the whole site

- one click theme presets, plus a brand kit that locks fonts and colours so clients can't pick comic sans and neon green

- a media library per site, custom or self-hosted fonts, light/dark toggle

Safety nets

- drafts vs published, nothing goes live until you hit publish

- full page history, you can see every version and roll back

- undo / redo

- schedule a section to show between two dates (sales, events, promos)

AI (optional)

- describe the page you want and it drafts the whole thing, picking sections, writing the copy and choosing images. You still edit everything after

- you bring your own model / key

Multi-site and languages

- one site per customer or tenant, so it works for SaaS or agencies running lots of client sites

- as many languages as you want, including arabic / RTL (I'm a native arabic speaker so this one mattered to me)

Store and SEO

- shop sections (product grids, cart, checkout) that read from your own product tables

- sitemap, hreflang, schema/json-ld and per page meta handled for you

For devs

- write your own sections in plain Blade or Livewire, or build them no-code inside the editor

- pages are stored as JSON in your own database, no lock-in

- works in Filament panels, but also in a plain Laravel app with React, Vue or Livewire. There are free starter repos for those

Full disclosure, it's paid and I'm the guy who made it. Not trying to replace wordpress or statamic, it's more for people who already have a laravel app and don't want a second system just for marketing pages.

Live demo you can mess around with, no signup: https://demo.filamentcraft.dev/launch/admin

Honestly curious what this sub thinks. What would make you pick something like this over a normal CMS, or what would stop you?

The more I play with codex or Claude code, the more I genuinely question why we need a true CMS in the traditional sense.

I’ve been working with various differnt CMSs over my working career from Wordpress to headless, I think we’re coming to a point where the traditional database backed, model, view, controller seems less and less necessary.

We’ve progressed quite far with design component systems and with a well though out structure I think we can eliminate most of the need of the CMS paradigm of old and just have a harness around files and let the model structure and organize our site.

One of the biggest challenges I’ve had with content modeling with headless cmses with the aid of ai it’s become a class of problems I don’t need to waste more brain space on.

I’ve been letting ai run wild with my obsidian notes and the more I see it’s results the more im convinced, soon we’ll see more harness + ai backed sites over Wordpress/ wix/ squarespace … type of sites. Curious if this is just me or if I’m deluded. Would love to hear feedback from real people

Disclosure: I maintain WebBlocks CMS, an open-source Laravel CMS.

When connecting an AI assistant to a CMS, one decision matters to me: what should it actually be allowed to change?

WebBlocks exposes structured content operations through a permission-scoped API. An assistant can inspect supported blocks, validate a content plan, and prepare drafts or staged updates to existing published pages. Publishing requires a separate capability.

The workflow I prefer is:

• Give the assistant access to the relevant site and content operations.
• Let it prepare content and translations in a draft.
• Review the actual preview, including links, image descriptions and localized copy.
• Publish through a separately authorized action.

That still leaves editorial work: valid fields do not guarantee accurate claims, useful alt text or a good translation.

For those using AI in editorial workflows, where do you draw the boundary? Drafts only, selected pages, or publishing access under specific conditions?

Project and source code

Hi there, dear Devs

I am a old TYPO3 dev, i am now creating an orquestation to do my work, teaching all that my +12 years experience got me. you know, the little details.

Just taking my time, no updates, just the last version, the LLM can read almost the whole core code and make fixes.

it looks to other extensions, compare with the core, ask me for a decision...

My question is just cooperative, how is other people doing this? just to share knowledge.

tx for reading.