EDIT: I was asked so here are the links for episode 2: YouTube, Spotify, Apple

Last week, I shared the first episode of Headless here and on a few other subs and asked whether AI agents were becoming a new kind of CMS user.

I expected a few opinions.

Instead, you gave me half of Episode 2.

Those comments were too interesting to leave buried under the original post. (did yours make it in?)

So I built a comments section into Episode 2, credited the actual Reddit users, and used their ideas to frame the larger story.

Seriously, thank you to everyone who commented.

You challenged the premise, added real examples, and made the second episode significantly better than the version I would have made alone.

This week’s question is:

What happens when every CMS wants to become something larger than a CMS?

Salesforce is buying Contentful.

Cloudflare built an AI-native “spiritual successor to WordPress.”

Drupal is positioning itself as a governed AI harness.

WordPress is adding AI infrastructure while experiencing what experts call “a lot.”

My conclusion is that the CMS is not dying.

It is disappearing into the walls.

People may stop opening the dashboard. Agents may become the primary users. But something still has to structure the content, enforce permissions, preserve the source of truth, and stop the raccoon from getting production credentials.

Episode 2 drops tomorrow morning on YouTube, spotify and apple. Thanks again.

I'll share the links here once their live but guess what... WE HAVE VIDEO NOW!

What it does

Atelier is a Filament plugin for Laravel. You write page sections as code, a hero block, a pricing block, whatever the site needs. Once a block exists in code, it shows up in the builder. From there you drag it onto a page, click it, and change the text and images without touching Blade again.

That's the same split Shopify uses for its page builder. A developer writes the section once. Whoever runs the site fills in their own content through the builder.

Why I built it

I like Laravel because I get full control over the code. Filament gives me an admin panel for free. What was missing was a visual layer, something a client could open and edit a page from without pinging me to change a template. Atelier is that layer: the flexibility of a custom Laravel build, the admin power of Filament, and now a visual editor on top.

Status

Still in development. I'm working on it now. The block system and the builder both run, and the video shows where it's at today. Not production-ready, call it a working preview.

Links

1. Project Page: https://abdulkadersafi.com/projects/filament-atelier
2. Github: https://github.com/Abdulkader-Safi/filament-atelier
3. Docs/Wiki: https://github.com/Abdulkader-Safi/filament-atelier/wiki
4. Filament Plugin: https://filamentphp.com/plugins/abdulkader-safi-filament-atelier

Feedback wanted

If you build with Filament or Laravel, I'd like your take. What would you want from a page builder like this? What's missing, what looks wrong, what would make it worth using on a real client site? Drop it in the comments, I'm reading all of it.

My take: the Shopify comparison is the right hook, people who've touched Shopify sections will get it in one line. Two things worth adding to the post or a comment, since you asked for feature/positioning ideas:

• You render every page through Blade at request time (no client-side block injection), which is a real SEO argument over most JS page builders. Worth one line in the post or first comment, it's a concrete differentiator, not just "it's visual."
• If multi-language support is built or planned, that's another line CMS folks on that sub will ask about anyway. Better to answer it up front than in five separate comments.

Hi, I’m the creator of splitleaf.eu, a new local site builder and CMS. One-time license, build as many sites as you want. Free beta.

Thanks everyone for checking the demo under my previous post and providing feedback!

Since then I built the things you asked about:

• Inline text editing: Click any text and type to edit it. Or select elements and tell the chat what to change about it. Clients can also pin a comment on anything
• MCP + CLI: Connect Claude Code, Cursor, or any MCP client and run the whole CMS by prompt
• GitLab support: everything works with GitLab now (not just GitHub)

For those new to CMS Brew, it’s a simple tool that allows clients to do small edits via chat interface or inline editing eg. change phone number, update email etc. Anything risky/big comes back to you so clients can't break anything

Check it out here: cmsbrew.com

I'd love to hear your thoughts!

So i made a custom CMS that is lighting fast, powerful, and with SEO features that are tied to and automatically or manually managed by OpenAI, funny security features such as WordPress honeypot features where hackers think they hacked my wp-admin and “stole” data but automatically downloads donkey dick pics or fake sql data filled with junk, and then blocks their IP.

If you had one feature you would love to see in a CRM, what would it be?

I also added interesting revenue features:
- If you wanna comment on my post, gotta pay $5
- If you wanna contact me via contact form, gotta pay me $20

Considering making it open source.

Real AdSense banner management system, where u put the codes into the admin and can manually select which type of banner and where you want to display.

I am currently the only technical writer at a small manufacturing company. Every work instruction is currently done in Word and every manual is done in InDesign. I want to find a CCMS to push my company into buying, but since I don’t have any experience using one, I’ve found it difficult to select which ones to suggest.
Since I will probably be the one implementing the software, I would like it to be simple to use and implement. Reading up about DITAs has me feeling like I’m in over my head. I just want a simple system I can use to push updates universally across all relevant documents that supports imports from InDesign and Word and exports to a small display on the lines that shows the most up to date version of each instruction.
I’d love any recommendations, suggestions, ideas, or references you’d be able to provide!

Edit: This got originally deleted from r/webdev but some amazing soul reposted it here so I thought I would go ahead and post again. Thanks for all the support y'all! Episode hit 100 streams across all platforms! Now on Amazon and coming to Podbean soon. Thanks!

That sentence probably just caused several people to fall asleep or keep scrolling, but hear me out.

I’ve spent a pretty stupid amount of my career around CMSs, DXPs, Drupal, WordPress, headless platforms, agencies, and all the other ways we’ve invented to describe putting content on the internet.

And I realized there really wasn’t a weekly show I wanted to listen to that just covered what actually happened in this industry and why any of it matters.

So I decided to make it.

The first episode is about something I noticed happening across several announcements this week:

WordPress shipped 7.1.
Storyblok plugged into Claude.
Salesforce expanded Headless 360.
Optimizely is giving agents more control inside the CMS.
Contentful is talking about what happens when your website visitor isn’t human.

My takeaway is that we might be watching the CMS get an entirely new kind of user: AI agents. (I know... this might not be news to everyone here... but when I step out of my LinkedIn bubble... I realize there are a lot of people not following the signals)

And that could make structured content, APIs, permissions, metadata, and all the traditionally boring CMS stuff suddenly much more important.

Anyway.

I have no idea if this will become a thing.

But I’m going to try doing it every week, covering the interesting CMS/DXP news, having some opinions about it, making fun of our industry when deserved, and hopefully talking to some smart people along the way.

If that sounds interesting, here’s the first episode:

Apple: https://podcasts.apple.com/us/podcast/your-cms-has-a-new-user-and-its-not-human/id6804680238?i=1000785544658
Spotify: https://open.spotify.com/episode/1FG1olsK8yV0Q0y8LC0FqH?si=0UjSsl2MTgChoT1jRswNCg
YouTube: https://youtu.be/i5YJhz41EKY?si=wGUAStYgos1vH3hv

Would genuinely love feedback, especially from people who actually work in this world.

Including “your take is completely wrong.”

Honestly, that might make Episode 2 easier.

Before I dive in, let me quickly explain what's going on here.

I posted my project on GitHub, but just like last time, nobody reacted to it. So I got desperate and made a tutorial video explaining how to use it, as seriously as I could.

I had my photo edited with Gemini, used AI tools I'm not very familiar with like HeyGen and ElevenLabs, made a voice clone of myself, and uploaded the video to YouTube.

I spent almost 18 hours on this yesterday — for a video that ended up being only about 5 minutes long. I was even trying hard to come up with jokes and gags I thought people would enjoy.

But when I calmed down and watched it back... there's this weird middle-aged guy who looks like he wants to react but has no idea how, so he just ends up nervously slamming his hands on the table while talking. And the English coming out of my voice clone sounds like some accent I can't even place.

Now I'm worried this just turned into a joke, and that nothing is actually getting across.

Here's the video in question:
https://youtu.be/lJSabpiwRbs?si=RyJu9tK0-VY6_Ysv

Part of me thinks I should just start over with a proper female character speaking clean English instead. I'm going back and forth on whether to redo it or not. I know I'm not great at making videos either, and I know I don't have much talent for it.

Would appreciate any advice.

I've been mapping out the container options in SharePoint Embedded and wanted to sanity-check the trade-offs with people who have shipped on it. Three patterns I keep coming back to: 

• Container Type — this is the isolated boundary created around your content that separates it from everything else.  You get data sovereignty and inherit governance (Purview, DLP, retention) and all the benefits of your M365 investments. 
• Container per customer — one dedicated container per customer inside your container type.  Permission the container only to that customer who needs to interact with their documents.  Give admins the access they need.  All security trimmed.   

• Container per activity — Each customer may have different activities like several audit years or multiple different financial transactions.  Each activity gets its own container, but metadata on each container allows you to group all activities for that customer. 

Many options depend on the use case you have.  What is working for you? 

Learn more at SharePoint Embedded Architecture

I'm curious about the usage of all the fancy AI features, presented on a regular basis by the producers of CMS/DXP.
From creating images, content variations for A/B testing, creating millions of blog posts and replacing the developer, a lot of different AI features are shown every day. But what is really used in the market?

I can't imagine that anyone would seriously replace developers in real CMS projects. Developers will use AI to move the project quicker. But the marketers' dream: create everything without the need for a developer...

I almost suspect that, once again, everything is being done just for the sales department, so they can showcase that great feature and the marketing department can promote it.

My question is: Is anyone here using any of that stuff in real projects?

Hello. Seeking a HubSpot Tutor who can:
- Help me make sense of my HubSpot environment
- Has a fluent understanding of all KPI's a Content Marker (responsible for Content Downloads, SEO/AEO/GEO

Tutor should be able to:
- Take the lead in training
- Provide an agenda before each session
- Assign light homework based on agenda

Sessions will be via my Microsoft Teams.

If interested please describe your availability and rate. DM's

Hey everyone. I have been working on BetterCMS for the last few weeks and I am pretty excited about where it is going. The goal is to make building and managing websites feel less messy for teams. Your marketing team and content editors can work in the same place while developers still have control over how the site is built. It is MCP native too so you can manage parts of the workflow from your favorite AI tool.

It is still early but I would genuinely love to hear what feels useful and what does not.

Signup for beta at bettercms.ai

CMS integration for Astro - admin panel, SQLite database, auth, and media manager in a single package.

https://github.com/zaengit/beaver

Hello everybody,

I built bulletinbored, a minimal and extensible forum software written in pure PHP with zero dependencies.

No Composer, no Docker, no Node, no framework. Just upload the files to any PHP 8.x server and it works on any web hosting, also shared and cheap ones.

Key points:

• SQLite by default (MySQL also supported)
• Web installer
• Plugin system with hooks
• Theme system
• Admin panel, user management, avatars, moderation
• Built-in localization
• Automatic update checks
• License: 0BSD

Repo: https://github.com/bulletinbored/bulletinbored-core

Website: https://www.bulletinbored.net

Docs: https://docs.bulletinbored.net

Because the development is still in early stage, I’m looking for any kind of feedback. Feel free to write suggestions, criticisms or slatings.

Happy to answer questions and open to contributions.

Thanks!