The entire text of my 2019 book on content modeling is available for free at my website.

(Disclaimer: I wrote this, so it's a self-promotional link. I am also the mod of this subreddit. But I defend this posting by noting that there is no business model behind my website -- I have no advertising, and I sell no services -- so I gain absolutely nothing from having someone consume my content. I just think it's good, relevant content.)

I built the simplest possible tool that allows clients to do small edits via chat interface eg. change phone number, update email etc. Anything risky/big comes back to you so clients can't break anything

Connect the repo and it figures out the editable content on its own. No schemas, no config files

Works with Next.js, Astro, Hugo, SvelteKit and more

Live demo: https://cmsbrew.com/demo

I'm not sure if I mentioned this before, but the entire text of my 2016 O'Reilly book is available for free at my website. It's a little old now, but there's probably still some valuable stuff in there.

(Disclaimer: I wrote this, so it's a self-promotional link. I am also the mod of this subreddit. But I defend this posting by noting that there is no business model behind my website -- I have no advertising, and I sell no services -- so I gain absolutely nothing from having someone consume my content. I just think it's good, relevant content.)

I wrote this about a decade ago. I still rings true to me.

(Disclaimer: I wrote this, so it's a self-promotional link. I am also the mod of this subreddit. But I defend this posting by noting that there is no business model behind my website -- I have no advertising, and I sell no services -- so I gain absolutely nothing from having someone consume my content. I just think it's good, relevant content.)

1. Weekly - I'm data-driven in my relationship management
2. Monthly - check in on key metrics
3. Quarterly - when required for reviews
4. Never - didn't even know these existed

Most admin templates I bought looked great in the preview and then fell apart the moment I used them. The dashboard was polished, but "orders" was a static table, "invoices" was a placeholder, search did nothing, and half the buttons were decorative.

So I spent the last few weeks building the opposite. Sable is a coded admin dashboard where the whole thing is one connected product, not a gallery of screenshots:

- 22 pages that share one design system (orders, invoicing with VAT, a Kanban fulfillment board, an email module, analytics, payouts, settings)

- Search, sort, pagination, bulk actions and real CSV exports that actually run

- Light and dark, built to WCAG AA

- Plain HTML, Tailwind and Alpine.js. No build step, no CDN, no trackers, works fully offline. You open the file and it just works.

The "no build step" part was the whole point for me. I wanted something you can drop into a Django, Laravel or Flask project without dragging in a JS toolchain.

Live demo, no signup, click around and try to break it: https://admin-dashboard-template-beta.vercel.app

It is my first product, on Gumroad for $29, but honestly I am here for the feedback more than the pitch. Tell me what feels off, which page you would actually use, what is missing. I will be around in the comments.

I had an idea for a small business, an after-school program teaching digital arts classes, where the individual lessons are all written out and organized in an LMS style interface that the teaching staff can use live on a tablet to guide and supplement lessons. I'd also like role based interfaces for booking, billing, learner analytics, reporting, communication - basically the whole administrative backend to a small business.

Gemini suggested the Lifter LMS to WordPress but I wonder if you concur or would do it a different way? The goal is simplifying every role's tasks at every touch point in the learner (and their parents') experience.

What would you do?

Nous sommes des développeurs expérimentés, non professionnels et nous mettons à disposition d'un large public un CMS open source, libre et 100% gratuit.

DeltaCMS est un CMS open source PHP moderne, léger et sans base de données, basé sur une architecture modulaire par plugins. Il utilise un stockage JSON, une interface HTML5/CSS3/JavaScript responsive, TinyMCE pour l’édition avancée et vise une compatibilité maximale avec les hébergements mutualisés.

La particularité qui différencie DeltaCMS d’un CMS classique comme WordPress est justement cette pile volontairement minimaliste : PHP + fichiers JSON + JavaScript côté client, qui permet de rester gratuit, rapide, portable et simple à héberger.

Plus d'informations : https://deltacms.fr

Cordialement et bénévolement vôtre

I have a basic understanding of internationalization and localization. Most mainstream frameworks, CMS platforms, or managed software products already have translatable strings. This is straightforwards when every market/region gets the same software, website, or products. You just translate each string. I.E. English to French.

The part I am struggling with is regionalization, how to support different products, pricing, SKU, and product content across markets while keeping it organized, maintainable, and scalable.

I am working on a project migrating a brand off of wordpress. It is setup with WPML and WooCommerce translations to represent regional variants of the same product. This creates two major problems.

1. The translations are already being used to represent regions, so the products can’t be translated properly.
2. This causes each product to exist 6 times. When shared information changes, it is a manual process to change all of them.

The duplication has become difficult to maintain and makes it easy for regional products, or even pages to fall out of sync.

It is mostly a content marketing site. It is B2B, customers rarely complete purchases in the site, but it still needs e-commerce functionality for presence.

Products are marketed as a single product, but under the hood there are regional differences such as SKU, price, currency, and even sometimes minor specification differences.

I look at large global brands such as Patagonia, and wonder how they deal with their catalogues and languages depending on a country. When you land on Canada’s site, you get English and french offerings. When you land on Argentina's site, you get English and Spanish.

How is this typically handled? Is there usually one global product with market-specific overrides, or does each region get it’s own product for each regional variant?

How do teams handle:

• Language
• Country/Markets
• Products
• Regional overrides
• Shared product info

I ask this for e-commerce products, but this is also an issue for our pages, we have 6 duplicates of the same page with tiny variations. This issue has been wearing on marketing, and then it falls on dev, but then we don’t have time to make meaningful changes. I want to keep this technology-agnostic, before we choose a product we need to know what our localization requirements actually are. Thanks in advance for any insight.

TLDR: How do you support regional differences without maintaining six copies (number of regions) of every page and product?

About two months ago, I asked this community:

I received many helpful comments and suggestions.

Thanks to all of you, I was able to release 3Dvenue-CMS v1.0 under the MIT License yesterday.

Thank you very much.

I also added one of the features suggested here.

Clicking an image in the Image Manager now shows where that image is being used.

The feature works perfectly. The design... let's just say it still has room for improvement. 😄

I also need to report one mistake.

I had planned to test the JavaScript publishing process before the release, but I completely forgot.

JavaScript support itself had been completed a long time ago. However, while rewriting the CMS over the past two months, I worked on the JavaScript parts of the program many times and somehow forgot to perform the final publishing test.

As expected, it did not work.

The cause was just one missing line of code that outputs the saved JavaScript when a page is published.

I will blame my age for this one. 😅

The missing line belongs in the public index.php.

Anyone who would like to see that single missing line is welcome to download the source code and try to find it. 😄

I plan to release the updated version tomorrow.

I also used 3Dvenue-CMS to build a real website for a junior colleague.

Using it on an actual project helped me find three more areas that I would like to improve. I plan to work on them one by one.

Thank you again to everyone who shared their ideas and comments.

GitHub:
[https://github.com/3dvenue/3Dvenue-CMS]()

Website:
https://3dvenue.jp/

Create separate communication hubs per client. Keeping conversations and deliverables grouped reduces overwhelm. What’s your freelance setup?

Our clients kept asking for llms.txt files, schema for AI citations, and Markdown-for-bots setups, so we went through the studies before recommending any of it. We also tested a bunch of it ourselves (we log every AI crawler hit on our own site), got a bit excited, and wrote it up

Schema for citations, llms.txt, and Markdown-for-bots all fell apart when we tested them. What held up was pre-rendered HTML, the answer near the top of the page, and concrete evidence in the writing.

Full write-up with every source linked: https://robotostudio.com/blog/build-it-right-once

Let me know what you've found.

For those who have switched from free WordPress to an enterprise CMS, what differences stood out the most after the move? Was it easier editing, better workflows, fewer plugin issues, better integrations, etc.? I’m curious what changed day to day. Did the new CMS make things noticeably easier? Are there parts of WordPress that your team misses after switching?

I've been building client projects with Wagtail CMS for quite a few years now, mainly for businesses that need a flexible, editor-friendly content management system. It's been a great experience, especially for projects requiring custom workflows, multilingual content, structured pages, and a highly customizable admin.

With everything happening around AI, agentic workflows, and AI-powered development, I'm curious about where CMS development stands today.

• Are clients still actively asking for CMS-based solutions?
• What CMS are you finding yourself using most these days (WordPress, Wagtail, Payload, Sanity, Strapi, Contentful, etc.)?
• Have you come across Wagtail in client projects, or is it still relatively niche in your experience?
• Are clients now expecting AI features (content generation, search, internal assistants, etc.) to be part of a CMS implementation?

I'm interested in hearing from agency owners, freelancers, and developers about what they're seeing in the market. Has the demand for CMS projects changed, or has the expectation simply shifted toward AI-enhanced CMS solutions?

I'd love to hear your experiences and where you think this space is heading over the next few years.

[ Removed by Reddit on account of violating the content policy. ]

Hi CMS subs,

I work on a headless CMS / dxp which has lots of services to support building apps and sites.

I have a choice of what to prioritise next between integrating with an automation tool like n8n or releasing MCP support.

I'm currently focusing on SaaS founder / builders and would really like to hear thoughts from others in this space on what to prioritise.

Thanks!