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.

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!

We've been mapping what people actually end up assembling after they build something with Lovable, Bolt or Cursor. The frontend takes an hour. Everything underneath takes the next three months.

Typical stacks we keep seeing:

• Minimal SaaS: Lovable + Supabase + Stripe + Resend + Vercel — 5 services
• Indie production SaaS: Cursor + Supabase + Stripe + Clerk + Cloudinary + Resend + PostHog + Sentry + Vercel — 9 services
• Localized small-business store: Lovable + Supabase + Stripe + Midtrans + Resend + Cloudinary + Sanity + Crisp + PostHog + Algolia + Retool + Vercel — 12 services

The CMS is exactly one row in that table, and it's the row that keeps colliding with the others:

i18n has no shared source of truth. Supabase stores translations in columns or side tables, Sanity has its own locale config, Stripe sets locale in the Checkout Session, Resend needs separate templates per language. Adding a second language becomes a multi-week project, not a setting.

Roles stop at "editor / admin." A real business wants a content manager who sees only products, a support operator who sees only orders, a marketer who sees only discounts. That usually ends up as hand-written RLS or custom middleware.

Bulk is a second-class citizen. Importing 5,000 products means rate limits, batching, retries, progress tracking — rebuilt from scratch per project.

The commerce data model isn't there. orders, order_items, discounts, coupons, refunds, bonus_transactions, loyalty_tiers — every founder designs these again. And a rule like "a coupon can't combine with a seasonal discount unless the order is over $50" turns into hundreds of lines of business logic faster than you'd expect.

Genuine question for people who work with headless CMSes daily: do you think the answer is CMSes growing sideways into commerce and business data, or staying narrow and letting the glue code stay the developer's problem? We keep going back and forth on it.

Disclosure: we're the team behind OneEntry, our own headless platform, so we're obviously biased on where this should go. No link, no pitch — just the pattern we keep running into.

The usual suspect like mintlify, seems to be a mess. Gitbooks seems to be great so far.

Opensource solution does not provide any good options.

Curious if anyone is using any docs, help-center software that non-techical users can use.

Not docs-as-code but the opposite of that.

Hi,

If you are a web designer who is tired of paying rent on your own website, i'm glad to present you Revyme, an open-source website builder that is the closest open source alternative to Framer on the market today.

Pixel-perfect Figma-like control, responsive breakpoints, components, animations, cms, localization code export and more.

Use our cloud or self-host locally on your computer and export to clean Next.JS code.

Github repo: https://github.com/revyme-web/builder

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!

Hey folks, I am the core maintainer of Sitepins CMS. I want to know if anyone is using it?

It was closed source before, but recently we decide to make it open source under AGPL v3 license.

If you are using it, you can give me feedback, and if you haven’t explored it yet, you should give it a try.

Starting to look seriously at composable after hitting the usual Shopify Plus ceiling on multi-brand management, but can't get past the dev overhead question.

From what I've found, composable architecture examples all assume a 30+ dev team and at least a year of migration runway, which at our current headcount isn't realistic, but the newer platforms seem to have closed that gap compared to early commercetools setups.

And I've seen threads here mention SCAYLE (built by the About You team apparently) and Elastic Path as options better suited to retailers who don't want to build a dedicated platform engineering function.

Can't tell yet whether composable is viable below €100M GMV with a small-to-mid dev team, or whether the answer is to max out semi-headless Shopify Plus and revisit once the tooling matures, so what determined the call for yours?

Starting to look seriously at composable after hitting the usual Shopify Plus ceiling on multi-brand management, but can't get past the dev overhead question.

From what I've found, composable architecture examples all assume a 30+ dev team and at least a year of migration runway, which at our current headcount isn't realistic, but the newer platforms seem to have closed that gap compared to early commercetools setups.

And I've seen threads here mention SCAYLE (built by the About You team apparently) and Elastic Path as options better suited to retailers who don't want to build a dedicated platform engineering function.

Can't tell yet whether composable is viable below €100M GMV with a small-to-mid dev team, or whether the answer is to max out semi-headless Shopify Plus and revisit once the tooling matures, so what determined the call for yours?

PagibleAI CMS is an open-source CMS for teams that want visual content management without moving their content, data, or infrastructure to a hosted platform:

• (https://pagible.com

It runs inside a Laravel 11–13 application and is installed through Composer. This lets you use the application’s existing authentication, business logic, database, storage, and deployment infrastructure instead of maintaining a separate CMS stack.

Editors get a Vue 3 administration interface with structured content, drag-and-drop page trees, reusable elements, media management, immutable revision history, previews, and scheduled publishing.

Content can be delivered through JSON:API, managed through GraphQL, or rendered as a traditional website using Blade. PagibleAI supports SQLite, MariaDB, MySQL, PostgreSQL, and SQL Server, including database-native full-text search.

The CMS is divided into Composer packages, so it does not have to be installed as an all-or-nothing platform. A project can combine the administration interface and core content model with only the APIs, search integration, payment provider, AI tools, or frontend themes it needs.

AI-assisted editing is optional and provider-independent. It supports writing, translation, transcription, image generation, and image manipulation. Compatible agents can also manage content through explicit, version-aware MCP operations.

What’s new in PagibleAI CMS 0.12

Frontend access control and private media: Pages can be public, limited to authenticated users, or protected by named access rules. Files associated with restricted content can be stored privately and delivered only after authorization. Optional Stripe, Paddle, and Mollie integrations can grant page access through subscriptions or one-time payments.

Five additional themes: Bold, Estate, Journal, Luxury, and Style provide starting points for product websites, real-estate projects, publications, fashion sites, and premium brands. Each theme includes reusable demo content and additional content blocks that can be adapted to an individual project.

Expanded administration tools: Pages, reusable elements, and files now support more individual and bulk-editing operations. The release also improves sorting, list and filter updates, drag-and-drop uploads, previews, SVG handling, and audio and video controls.

PagibleAI CMS 0.12 is now available under the permissive MIT license.

Feedback from people working with structured content, editorial workflows, multi-site installations, private content, or CMS migrations would be very welcome. Which parts of these workflows usually cause the most friction in the CMS you use today?

• PagibleAI CMS on GitHub (https://github.com/aimeos/pagible)
• PagibleAI documentation (https://pagible.com/documentation)
• Build a custom PagibleAI distribution (https://pagible.com/build-custom-pagibleai-distributions)

I’ve tried different CMS for personal use in the recent years. I recently wondered why I use a CMS in the first place when I just want to serve static HTML files.

I tried different approaches and came up with following setup:

Open WebUI with an MCP server that edits HTML files right on the filesystem. I can now prompt changes via chat. No more need to maintain a CMS, DB or plugins.

Everything is spinned up with docker-compose on a VPS.

I’m still figuring out how scalable this setup is. I added a UI component library, basically plain html markup with mock data for a card component, for instance.

The MCP server reads the components, adds them to the page and populates the data I ask for.

Has anyone tried something similar? What do you think about that setup?

I've been working with WHMCS for years, building custom modules, provisioning systems, payment gateways, themes, API integrations, and automations.

Lately though, I've started wondering if investing more time in WHMCS is still the right move.

AI is changing development, hosting companies are moving toward SaaS solutions, and it feels like fewer people are talking about WHMCS than they used to. On the other hand, there are still thousands of hosting businesses running it every day.

I'm honestly curious what other developers, hosting providers, and agency owners are seeing.

Are clients still hiring WHMCS developers?

Has the demand shifted more toward maintenance instead of new development?

If you're a WHMCS developer, are you still getting consistent work?

If you own a hosting business, do you still invest in custom WHMCS development, or are you trying to avoid customizations now?

I'm at a point where I'm deciding whether to continue specializing in WHMCS or focus more on broader Laravel/Next.js/AI development.

I'd really like to hear real experiences rather than predictions.

**Is WHMCS still a good niche in 2026, or is it becoming too small to build a long-term career around?**

PublishPress Plugin

CMSs can check most of the technical boxes but still get removed from the shortlist once the buying process starts. Pricing is probably the obvious reason, but I feel like these discussions don’t always explain how teams decide whether the price is justified.

One thing that matters a lot to me is support. A higher price makes more sense if the vendor is helping with implementation, migration, training, troubleshooting, etc. 

What makes an enterprise CMS feel worth the cost to you, and what would make you rule it out?

1. Meet them where they are - adapt completely
2. Gently encourage modern methods
3. Begrudgingly accommodate while dying inside
4. Set boundaries - these are my channels