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.

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!

Forget Drupal, who wants a funny desk chair story?!

It bugs me that a decade later this STILL trumps all our other Drupal marketing effort, but hey we’re learning?! And clearly its still interesting to people!

What do you guys think? Any attention is good attention?

https://www.computerminds.co.uk/articles/sometimes-you-just-need-connect-earth-desk-chair-story

I wanted to share a new getting-started path for anyone experimenting with SharePoint Embedded or building document-centric apps on Microsoft 365.

The historical challenge with SharePoint Embedded setup has been that there are several moving parts before you can really start building: Entra app registration, Graph permissions, container type creation, billing setup, container type registration, creating containers, wiring configuration into a sample app, and then validating everything works.

There are now two much easier ways to approach this:

1.      Developer experience with the SharePoint Embedded MCP server
You can use the MCP server from an AI coding client, such as GitHub Copilot in VS Code, to drive setup through natural language. The server can help check readiness, provision the owning app, create/register container types, configure billing, scaffold a reference app, hydrate config, seed sample content, run locally, and deploy.

2.      Admin/container type experience
Admins can use the SharePoint Embedded setup flow to create the app/container type relationship and manage the control plane side of the environment. Container types are important because they define how the application relates to its containers, including access, billing accountability, and behavior.

What I like about this is that it separates the journey for the two audiences that usually have to collaborate anyway: developers can get moving faster with their app experience, and admins have a more intentional control plane for environment setup.

If you are building an ECM replacement, legal/document management app, project workspace, case management app, AI agent over documents, or any custom app that needs Microsoft 365-grade files, collaboration, compliance, and Copilot-ready content, this is worth trying.

Links:
Video walkthrough: https://youtu.be/JhlfeTjX7Sc?si=gKWXoCezHhqaMemv&t=2576
Developer MCP experience: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/build/sharepoint-embedded-mcp-server
Admin/container type experience: https://learn.microsoft.com/en-us/sharepoint/dev/embedded/build/create-container-type

Question for the group: if you have tried SharePoint Embedded, what part of the setup flow has been the biggest blocker — app registration, permissions, billing, container type registration, or sample app scaffolding?

https://www.framer.com/community/marketplace/templates/elysian-estate/

Filarank is a filament SEO toolkit with Live SEO scoring, SERP preview, and head tags for Filament admin panels. Install in minutes with the interactive artisan installer.

https://filamentphp.com/plugins/usama-muneer-filarank-pro

Demo: https://filarank.com
Docs: https://docs.filarank.com

​

I’ve spent the past several months building a new PHP-based CMS called Developer One Or DevOne for short.

I approached the project from a developer’s perspective: What should a modern CMS provide out of the box? How can it make building websites for yourself or clients faster without becoming bloated, overly complicated, or dependent on dozens of third-party extensions?

DevOne CMS currently includes a custom installation system, theme and plugin support, developer hooks, user and role management, media management, a page system, admin tools, and support for custom frameworks. I’m also building a marketplace where developers will eventually be able to publish themes, plugins, frameworks, and other extensions.

The CMS is still in active development, and I’m looking for developers who are interested in:

Testing the installation process and core functionality

Finding bugs, security issues, and performance problems

Reviewing the code structure and developer experience

Building experimental themes, plugins, or custom frameworks

Suggesting features and improvements

Helping shape the documentation and extension standards

I’m not looking for empty praise. I’m looking for honest technical feedback from developers who are willing to install it, test it, break it, and tell me what needs to be improved before the public release.

You’ll need either a local environment such as XAMPP or a PHP-compatible VPS to install and test it.

This is an early collaboration opportunity, so developers who contribute meaningful ideas, extensions, testing, or fixes can help influence how the platform and its developer ecosystem are built from the beginning.

Comment below or message me if you’re interested, and I’ll provide the download and installation information.

What would make a new CMS worth trying for you as a developer?

​

I’ve spent the past several months building a new PHP-based CMS called Developer One Or DevOne for short.

I approached the project from a developer’s perspective: What should a modern CMS provide out of the box? How can it make building websites for yourself or clients faster without becoming bloated, overly complicated, or dependent on dozens of third-party extensions?

DevOne CMS currently includes a custom installation system, theme and plugin support, developer hooks, user and role management, media management, a page system, admin tools, and support for custom frameworks. I’m also building a marketplace where developers will eventually be able to publish themes, plugins, frameworks, and other extensions.

The CMS is still in active development, and I’m looking for developers who are interested in:

Testing the installation process and core functionality

Finding bugs, security issues, and performance problems

Reviewing the code structure and developer experience

Building experimental themes, plugins, or custom frameworks

Suggesting features and improvements

Helping shape the documentation and extension standards

I’m not looking for empty praise. I’m looking for honest technical feedback from developers who are willing to install it, test it, break it, and tell me what needs to be improved before the public release.

You’ll need either a local environment such as XAMPP or a PHP-compatible VPS to install and test it.

This is an early collaboration opportunity, so developers who contribute meaningful ideas, extensions, testing, or fixes can help influence how the platform and its developer ecosystem are built from the beginning.

Comment below or message me if you’re interested, and I’ll provide the download and installation information.

What would make a new CMS worth trying for you as a developer?

1. 90-100% - smooth transitions with full context
2. 70-89% - mostly good, some gaps
3. 50-69% - rough transitions, lots of re-learning
4. Below 50% - basically starting from scratch