r/cms • • Sep 21 '25

Each self-hosted CMS in 2025 is horrible

39 Upvotes

I will try to be short.

For my startup about quality of products in the supermarket ohmygoods.app, I need to host posts somewhere that describe additives, products, some marketing stuff - and do it in different languages, to display them in the mobile app and website.

When I started, I didn't have much time, so I just picked Wordpress with a bunch of plugins I knew from my childhood, ran it self-hosted and it was pretty ok. But in a world where even the 'M1' chip is no longer the most powerful, Wordpress still feels slow when you work with content every day. It requires pressing a ton of buttons and installing countless plugins just to cover basic needs of almost every content creator.

So recently, I decided to look around and check what we have in 2025 to solve this pretty easy task in the CMS world:

Requirements

CMS should be:

  1. self-hosted

  2. single pay or free of charge

  3. with multi-language support

  4. able to retrieve content with some API

Only four requirements.

Actually, today only a few CMS in the world support this simple set and each of them is bloated. Let me explain:

Directus

You will struggle when you try to localize your content the first time, but it's possible - here's the direct link for you. You'll need Content Translations, hidden somewhere deep inside the documentation. Just follow the video and you'll be fine.

The second thing is the API, which is overwhelming. When you try to fetch posts for a specific language, it will return translations for every language. So instead of 10 posts for a single language, you get 10 posts * number of languages in your CMS.

You can tweak it by building your own API Extension (that you need to create and deploy, of course), where you still get the whole list of posts but filter them to return only the necessary ones.

These examples show that the market is targeting very wide user needs, but forgetting about basic things that should work out of the box.

Strapi

Strapi does localization better than Directus, because it's already a built-in feature - all you need to do is just select languages.

But the hidden "gem" is Deployment. Even with Docker it doesn't look simple, and overall you still need to manage and host images yourself (that is expected).

The second thing is that Strapi tries to charge you for features like "history", "release" and others, and you need to create an account to use them.

Still, I like it more than Directus, because it tries to simplify these basic things that should just work.

Wordpress (still)

Slow, bloated, requires a lot of plugins to be installed and tweaked to work as expected. And each plugin is bundled with vulnerabilities that will be discovered in a month or two - that's just how the plugin system is designed.

So by using Wordpress you basically subscribe yourself to endless plugin updates.

But it actually works 🙌. It's very popular and you can deploy it in 5 minutes on almost any hosting. You'll get your basics, and then you can upgrade it however you want.

Ghost

Fresh and very (very) modern. You can even self-host it, but the actual vision of developers about multi-lingual content is basically "self host a few instances and juggle them like a clown". Meh.

So you need to know how to build your own infrastructure to link the same post with different translations.

Payload CMS

Very polished website and clear offer, but it requires knowledge of deployment, TypeScript and development. The learning curve is steep and time-consuming, but it's very flexible. If I were in an enterprise with a few full-time developers on my team, I'd definitely choose Payload CMS.

I have only one issue: localization is not working properly with SQLite (didn't test with other DBs, not sure if related). Even if you have multiple languages and switch between them, your changes are applied to every language. So not working. Maybe it's only me

Try it yourself on their website: just select a blank project with SQLite and add localisation by the docs.

Keystone

Multi-lingual support issue is still open since 2018.

It's the end of 2025, and people are still creating CMSs without multilingual support by design. |
Who is the target audience for such CMSs?

Final thoughts

I've spent around 2 days playing with each "promising" CMS on the market, and that's why I'm not ready to switch from Wordpress.
It's working, it's kinda terrible like the others, so there's no clear reason to choose something different.

👉 If I would like to start from scratch and setup it fast, I will go with Strapi. It has mostly everything that you need.

👉 If I had a lot of time, I think I would choose Payload CMS and only because I'm a developer with some experience and not scared of deployment solutions focused on Vercel things.

The current state of self-hosted CMS is horrible, especially for a solo devs. And I think there's nothing we can do, other than create yet another horrible CMS to suit your exclusive needs.


r/cms • • Jun 29 '26

First peek at Instatic - fully open-source, self-hosted CMS

30 Upvotes

Take a first look at Instatic - https://youtu.be/zyjCF_TaLlg?si=WZBxxqmsIo0gZ_zY

Instatic brings the whole website workflow into one product: visual editing, structured content, media, forms, reusable components, templates, publishing, plugins, HTML import and AI-assisted page building — all running from one Bun server backed by SQLite or Postgres.

Unlike most visual builders, Instatic does not ship the editor and CMS bloat to your visitors. Published pages are plain semantic HTML and compact CSS, with no React runtime unless you need one, no builder attributes, no hydration step, and no platform lock-in. Sites are baked and served as static files, so the public site stays fast, portable, and easy to inspect.

This is a pre-1.0 open-source project, and the goal is to build the foundation in public: no legacy platform constraints, no open-core pricing tricks, no forced SaaS model, and no compromise on output quality

Check out the repo https://github.com/CoreBunch/Instatic


r/cms • • Sep 03 '25

AI is changing how websites get found, are you ready for Project Mariner?

30 Upvotes

More and more people are skipping Google and going straight to AI tools for answers. Google knows this, and that’s why they’re pushing Project Mariner, making AI the first place people go for answers.

That shift changes the game for websites. Design matters less. Content quality and structure matter more. AI doesn’t care how slick your homepage looks, it cares about how well your content is organized and whether it understands it.

The problem is that most websites aren’t ready. Tools like WordPress themes or Webflow focus mainly on visuals. They look great to people, but under the hood the content is often just a flat wall of HTML. To a machine, it has little meaning and little value.

A headless CMS with structured content works differently. Content is stored in a way that machines can understand through things like schema.org and JSON-LD. Whether it’s opening hours, product specs, or FAQs, AI systems can actually use it. That means teams who invest in structured content become easier to find, not because they trick search engines with hacks, but because the machines know what their content actually means.

You can try to patch this with plug-ins and short-term fixes, but if your CMS is built around design rather than data, you will eventually hit a wall. The future belongs to websites that treat content as structured, reusable and machine-readable.

It might sound abstract, but it’s happening faster than most people realize. The real question is whether you are building a site that works for the next year, or for the next five.


r/cms • • Dec 14 '25

"You should never build a CMS"

Thumbnail
sanity.io
28 Upvotes

Cursor migrated off Sanity and wrote about it. So I wrote about why building your own CMS on top of markdown, GitHub, and Vercel might not be a good idea for everyone.


r/cms • • Jan 27 '26

Flexible CMS for large government agency website

27 Upvotes

I work for a government agency with a very large website - at least 250K pages. The site covers many different topics; economic news and reports; economic development programs, financial reports, purchasing, local and state taxes to name just a few. We get more than 5M pageviews per month.

We are forever getting new programs and other curve balls from the legislature and expanding the use of data visualization tools and having to integrate with enterprise management tools on the back end. Our team is purely front-end and rarely consulted on changes to the back end or the addition of these new tools.

We are looking at options for a major redo of the site. We tried Drupal years ago but we always get tripped up at the taxonomy because it requires new additions on a regular basis. Commercial CMS systems tend to be prohibitively expensive because of the size and amount of traffic.

Any suggestions?


r/cms • • Jan 14 '26

I built my dream personal site CMS

Thumbnail ava.addy.zone
27 Upvotes

Hey everyone!

In a sea of flat-file, PHP CMS' I always found myself wanting for something a little different that nobody else nailed for me.

- I don't like complicated templating engines, just give me markdown and HTML/PHP for anything extra

- I want completely flexible content types, not just posts/pages.

- I like the idea of scalability, even if it will never happen, it's nice to know you have room for thousands of content pieces

- Searching, sorting, filtering, forms etc. should not need 3rd-party services, this rules out a lot of static site generators

- Complicated hosting setups, complicated dependencies and 3rd-party reliability annoys me

- I like to use my own editor, but an admin panel for quick edits on the go without my normal setup is a must

- No manual build steps, compiling, deployment processes, etc.

- Being able to check everything in to Git for version control is ideal

- A nice but optional CLI for when I am in the flow

- Easily extendable with plugins, hooks, etc.

I solved all of these for myself with Ava CMS. It's probably a pretty niche window of people as I know lots of people love templating engines and abstractions or prefer everything to be in a UI, but I'm very excited to move more of my personal websites and portfolio to it.

The docs are built in it already and available on GitHub. :)

Not expecting anyone to jump ship at this early stage, but I would love your thoughts and feedback on the pitch and if the lander/documentation piques any interest!

https://ava.addy.zone/


r/cms • • Sep 17 '26

CMS for SEO and AI search

26 Upvotes

I used to pick a CMS based on how easy it was to publish and edit pages now I’m noticing a different problem a site can be easy to manage and still make SEO work annoying once you start caring about schema, internal links, titles structured content and whether AI search can understand what each page is even about

I’ve been going back through a few older pages and some of the information is there it’s just buried in weird fields or written in a way that only makes sense after reading the whole page so it makes me wonder if the CMS matters more now not because Google prefers one platform, but because some setups make it way easier to keep the content clean and structured as the site grows.

I don’t know if headless fixes that or just gives you more control and more stuff to maintain. Curious where people here draw the line between a CMS that’s nice for editors and one that’s nice for SEO and AI search too.


r/cms • • 14d ago

State of CMS 2026

Post image
23 Upvotes

The developer community has conducted an annual survey of frameworks and programming languages since 2016. Many of you have probably even participated in State of JS, HTML, or CSS. But not one for CMS.

2026 has been a year of change for those of us who build and manage websites; I have a feeling that many of you are on the move, migrating from one CMS to another or even building your own. Broad market-share numbers tell us very little about your experiences building and managing websites with different tools; that is why I hope that we, as a community, can close this information gap with our own State of CMS survey. Starting this year.

stateofcms.com

The anonymised results will be freely available on GitHub. I will create a visual representation of them, but I really look forward to seeing what the community does with the data.

My resources are limited, so to get started, I have created an English version of the form. I did not want to blindly trust AI to translate; that is why I'm looking for people who can help with translations. You can reach me here on Reddit or through the email on the site.

To reach every nook and cranny where people who build and publish websites hang out, I need your help. If you believe that this will bring value to the community, I hope you will help us spread the word.


r/cms • • Sep 07 '26

We're re-platforming 20 enterprise websites across 20 countries — which CMS platforms should we be evaluating?

19 Upvotes

I work at a large, publicly listed European financial services company and we're about to kick off a proper evaluation of enterprise CMS platforms. Currently running on Umbraco, but we've outgrown our setup and it's time for something more modern.

Here's our situation:

  • 20 websites across 20 European markets (mix of group-level and local market sites)

  • 50+ editors in different countries, varying levels of technical skill -- so editor UX is critical

  • Strong roles, permissions, workflows and governance

  • Publicly listed, so security, stability and compliance (GDPR etc.) are non-negotiable

  • Good integration capabilities with analytics, DAM, CRM, marketing tools etc.

  • Ideally modern architecture/API capabilities without making everyday content management overly technical

  • Multilingual and multi-site management out of the box, not bolted on

  • Enterprise SLAs, proper vendor support, and a strong partner ecosystem

We're a publicly listed company, so security, governance, stability and long-term maintainability are particularly important. At the same time, we're trying to avoid the classic enterprise CMS problem where the platform is incredibly powerful but painful for marketers to actually use.

Specific things I'd love input on:

  • What have you actually run at enterprise scale with non-technical editors?

  • Headless vs. traditional CMS -- worth the tradeoff for a team with limited dev resources?

  • Anything we should be evaluating that's not on my radar?

Not looking for vendor pitches -- just honest experience from people who've been in the trenches.

Many thanks 😄


r/cms • • Nov 12 '25

What are the best alternatives to WordPress?

19 Upvotes

Looking for some good options, would like to hear about different features, ease of use, etc. Thanks in advance!


r/cms • • Dec 08 '25

What are the new changes you have observed in CMS?

17 Upvotes

Hi,

I am working on a piece to talk about the changes or how CMS has evolved. Please, share some features that you have observed. It can be for both GUI-based and code-based. Headless cms preferred.


r/cms • • Jul 30 '26

I built a simple chat CMS that my clients can actually use

16 Upvotes

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


r/cms • • Jun 23 '26

Grav 2.0 Released - An established open source flat-file CMS for the modern ai-enabled era

15 Upvotes

Grav 2.0 is a modern update to the venerable Grav 1.7 release that was launched in 2021 and has received over 50 point releases since then. Grav 2.0 is a whole new take on Grav, it's still a PHP-based flat-file CMS that focuses on speed, extensibility and flexibility, but now it has a first-party API that makes it a full-featured "headless" CMS, as well as a new SvelteKit5-powered SPA-based Admin2 plugin. Still fully customizable via 3rd party plugins, just like you would expect of Grav, but faster, and more secure.

Grav 2.0 also has an MCP server that works in conjunction with the API, to make it super easy for AI agents to work with. AI already has a great understanding of Grav as it's been around for over a decade, but we now have dedicated Agent "Skills" that enable the easy porting of 1.7 plugins and themes to 2.0, as well as useful skills that help review plugins for correctness and functionality.

The getgrav.org site also got a major redesign as it had not been updated in years. As part of this I migrated our Discourse based forum back to a Grav-native "forum-pro" (will be released publically soon) solution. Another service we have brought in-house, is our translations.getgrav.org which replaces our Crowdin solution we have used in the past.

Grav has always been a great platform for documentation, and now our Docs are powered by Grav 2.0 and our latest Helios documentation theme as well as our own YetiSearch search engine to make them even more readable and functional. I've been blogging about the process and here's a few posts that will give you a good idea:

And of course, the Grav 2.0 release article: https://getgrav.org/blog/grav-2-stable-released

Find out everything you need to know about Grav and the 2.0 release on the official site: https://getgrav.org

Thanks!

-- Andy


r/cms • • Oct 18 '25

Builder.io headless team s*cks

15 Upvotes

Okay, lil context here I run a dev agency and we’ve used Builder.io for a lot of projects. We even work with enterprise clients and are official partners with several other headless CMS platforms like Sanity, Directus, Payload, etc. With all of those, the partner experience has been awesome responsive teams, proactive support, actual collaboration.

But Builder.io? Holy sht, it’s been the total opposite. We’ve reached out multiple times through all the proper channels, trying to collaborate, ask for help, or discuss enterprise-level stuff and it’s like they don’t give a single f**. Zero response, zero interest. It honestly feels like they couldn’t care less about the partners who are literally implementing their solutions and bringing them customers.

Is anyone else dealing with the same nonsense? Are we just unlucky, or is this a known issue with their partnerships team? 🤷‍♂️

And if someone from Builder.io is lurking here seriously, fire whoever’s running your partner success program. They’re doing a terrible job.


r/cms • • Oct 25 '24

I Built a Headless CMS For Blogs

15 Upvotes

r/cms • • May 08 '26

Big news for Grav CMS

14 Upvotes

It's been 12 years since the first beta of Grav CMS was initially announced, and nearly 5 years since the last major version 1.7 was released. After some false starts, namely with Grav 1.8, I'm proud to announce the release of Grav 2.0 RC.

It's a major upgrade with PHP 8.3 minimum, but support through PHP 8.6, completely upgraded packages including latest Symfony. Grav 2.0 features an new headless-first approach with first-party API layer, an all new SvelteKit5 SPA Admin v2, MCP server, Skills + more. It's faster and more secure, but still backwards compatible with content, plugins and themes. Built for Humans & Agents! https://getgrav.org/blog/grav-2-rc-released

You can read more details about how we got to this point: https://getgrav.org/blog/state-of-grav-2026


r/cms • • 8d ago

I've been building an open source CMS for client sites for months. The code is public now, no release yet

13 Upvotes

I'm a full stack engineer, and over the years I've helped with a lot of sites running on WordPress. It's usually the same story: a pile of plugins that don't know about each other, a page builder that fights the theme, and a client who's scared to touch anything in case it breaks. So I started building Kestello, a self-hosted CMS for the people who actually edit the site.

The main idea is that the editor edits the real page. There's no separate preview that looks almost like the site. Around that there are content types, forms, a media library with cropping, menus, redirects, search and backups. Plugins and themes are written in Vue, and there's a REST API if you want to go headless.

A few decisions I'm happy with:

- No Composer dependencies. It's PHP 8.4, and everything on the server side is written in-house, so updating the site doesn't mean updating 60 packages.
- It runs on plain shared hosting, not only Docker, with MySQL, MariaDB, Postgres or SQLite.
- Updates are signed and come straight from GitHub releases.
- It's GPL with no paid tier, and none is planned.

Things I learned along the way: building the visual editor took longer than everything else combined. Writing the docs at the same time as the code also caught a lot of confusing behavior before anyone else hit it.

There's no release yet, since 0.1.0 is close but not out. The whole codebase is public, though, and there's a docker-compose setup if you want to run it locally. Feel free to look around, open issues or send PRs (against develop).

Code: https://github.com/kestellohq/cms

Docs: https://docs.kestello.com

I'd love honest feedback on two things in particular:

- Does the README make it clear what this is and who it's for within the first 30 seconds?

- If you've dealt with WordPress sites, what would stop you from trying this on a real one?

A few updates on Kestello:

  • kestello.com – The main website is now fully powered by Kestello CMS itself.

  • demo.kestello.com – Updated the demo site, now running a custom-built Kestello theme.

  • docs.kestello.com – Completely revamped the documentation to be more beginner-friendly and focused on actual features and real-world problems. Added visuals, diagrams, and clearer explanations to make life easier for both developers building with Kestello and clients managing their content.

Still plenty to improve, but things are coming together nicely! :)


r/cms • • Jun 27 '26

VonCMS v1.25.1 Is Now Open Source (GPL-3.0)

Post image
13 Upvotes

Hi everyone,

It's been a while since I last posted here.

As promised, VonCMS v1.25.1 is now officially open source under the GPL-3.0-only license.

You can now fork the project, contribute new features, fix bugs, submit pull requests, or use it as the foundation for your own publishing platform.

VonCMS is still evolving, and there's plenty of room for improvement. Opening the project to the community marks the beginning of a new chapter, and I'm excited to see where it goes from here.

The project is primarily built for publishers, bloggers, and news websites. The idea is simple: focus on writing and publishing instead of spending hours configuring plugins, page builders, or complicated publishing workflows.

It is built with React, Vite, PHP, and MySQL, while remaining lightweight enough to run comfortably on traditional shared hosting. The goal is to provide a modern publishing experience without unnecessary bloat

If you encounter bugs, have ideas for improvements, or would like to contribute, feel free to open an Issue or submit a Pull Request. Community contributions are always welcome.

If you discover a security vulnerability, please do not report it publicly. Instead, contact me directly via email so the issue can be investigated and fixed responsibly before public disclosure.

I'd really appreciate any feedback, suggestions, or contributions from the community. Whether it's your first impression, a bug report, or a new feature idea, every contribution helps make VonCMS better.

Thanks for checking it out, and I hope you enjoy the project!

Official website: https://getvoncms.com/

https://github.com/Vondereich


r/cms • • Oct 10 '25

Built FoldCMS: a type-safe static CMS with Effect and SQLite with full relations support (open source)

13 Upvotes

Hey everyone,

I've been working on FoldCMS, an open source type-safe static CMS that feels good to use. Think of it as Astro collections meeting Effect, but with proper relations and SQLite under the hood for efficient querying: you can use your CMS at runtime like a data layer.

  1. Organize static files in collection folders (I provide loaders for YAML, JSON and MDX but you can extend to anything)

  2. Or create a custom loader and load from anything (database, APIs, ...)

  3. Define your collections in code, including relations

  4. Build the CMS at runtime (produce a content store artifact, by default SQLite)

  5. Then import your CMS and query data + load relations with full type safety

Why I built this

I was sick of the usual CMS pain points:

  • Writing the same data-loading code over and over

  • No type safety between my content and my app

  • Headless CMSs that need a server and cost money

  • Half-baked relation systems that make you do manual joins

So I built something to ease my pain.

What makes it interesting (IMHO)

Full type safety from content to queries
Define your schemas with Effect Schema, and everything else just works. Your IDE knows what fields exist, what types they are, and what relations are available.

const posts = defineCollection({
  loadingSchema: PostSchema,
  loader: mdxLoader(PostSchema, { folder: 'content/posts' }),
  relations: {
    author: { type: 'single', field: 'authorId', target: 'authors' }
  }
});

// Later, this is fully typed:
const post = yield* cms.getById('posts', 'my-post'); // Option<Post>
const author = yield* cms.loadRelation('posts', post, 'author'); // Author

Built-in loaders for everything
JSON, YAML, MDX, JSON Lines – they all work out of the box. The MDX loader even bundles your components and extracts exports.

Relations that work
Single, array, and map relations with complete type inference. No more find() loops or manual joins.

SQLite for fast queries
Everything gets loaded into SQLite at build time with automatic indexes. Query thousands of posts super fast.

Effect-native
If you're into functional programming, this is for you. Composable, testable, no throwing errors. If not, the API is still clean and the docs explain everything.

Easy deployment Just load the sqlite output in your server and you get access yo your data.

Real-world example

Here's syncing blog posts with authors:

import { Schema, Effect, Layer } from "effect";
import { defineCollection, makeCms, build, SqlContentStore } from "@foldcms/core";
import { jsonFilesLoader } from "@foldcms/core/loaders";
import { SqliteClient } from "@effect/sql-sqlite-bun";

// Define your schemas
const PostSchema = Schema.Struct({
  id: Schema.String,
  title: Schema.String,
  authorId: Schema.String,
});

const AuthorSchema = Schema.Struct({
  id: Schema.String,
  name: Schema.String,
  email: Schema.String,
});

// Create collections with relations
const posts = defineCollection({
  loadingSchema: PostSchema,
  loader: jsonFilesLoader(PostSchema, { folder: "posts" }),
  relations: {
    authorId: {
      type: "single",
      field: "authorId",
      target: "authors",
    },
  },
});

const authors = defineCollection({
  loadingSchema: AuthorSchema,
  loader: jsonFilesLoader(AuthorSchema, { folder: "authors" }),
});

// Create CMS instance
const { CmsTag, CmsLayer } = makeCms({
  collections: { posts, authors },
});

// Setup dependencies
const SqlLive = SqliteClient.layer({ filename: "cms.db" });
const AppLayer = CmsLayer.pipe(
  Layer.provideMerge(SqlContentStore),
  Layer.provide(SqlLive),
);

// STEP 1: Build (runs at build time)
const buildProgram = Effect.gen(function* () {
  yield* build({ collections: { posts, authors } });
});

await Effect.runPromise(buildProgram.pipe(Effect.provide(AppLayer)));

// STEP 2: Usage (runs at runtime)
const queryProgram = Effect.gen(function* () {
  const cms = yield* CmsTag;
  
  // Query posts
  const allPosts = yield* cms.getAll("posts");
  
  // Get specific post
  const post = yield* cms.getById("posts", "post-1");
  
  // Load relation - fully typed!
  if (Option.isSome(post)) {
    const author = yield* cms.loadRelation("posts", post.value, "authorId");
    console.log(author); // TypeScript knows this is Option<Author>
  }
});

await Effect.runPromise(queryProgram.pipe(Effect.provide(AppLayer)));

That's it. No GraphQL setup, no server, no API keys. Just a simple data layer: cms.getById, cms.getAll, cms.loadRelation.

Current state

  • ✅ All core features working

  • ✅ Full test coverage

  • ✅ Documented with examples

  • ✅ Published on npm (@foldcms/core)

  • ⏳ More loaders coming (Obsidian, Notion, Airtable, etc.)

I'm using it in production for my own projects. The DX is honestly pretty good and I have a relatively complex setup:

  • Static files collections come from yaml, json and mdx files

  • Some collections come from remote apis (custom loaders)

  • I run complex data validation (checking that links in each posts are not 404, extracting code snippet from posts and executing them, and many more ...)

Try it

bun add @foldcms/core
pnpm add @foldcms/core
npm install @foldcms/core

In the GitHub repo I have a self-contained example, with dummy yaml, json and mdx collections so you can directly dive in a fully working example, I'll add the links in comments if you are interested.

Would love feedback, especially around:

  • API design: is it intuitive enough?

  • Missing features that would make this useful for you

  • Performance with large datasets (haven't stress-tested beyond ~10k items)


r/cms • • Nov 28 '20

Blogging vs. blog setups | Honestly Undefined

Post image
13 Upvotes

r/cms • • Aug 15 '26

Open Source Framer Alternative: Revyme

Thumbnail
revyme.com
12 Upvotes

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


r/cms • • Jul 30 '26

Free book online: "Web Content Management: Systems, Features, and Best Practices"

Thumbnail
deanebarker.net
12 Upvotes

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.)


r/cms • • Oct 16 '25

Need simple advice: Best CMS for a multi-country website

12 Upvotes

What’s the best CMS for a global company website (multi-country, SEO, easy to manage, no coding)? Which CMS would you recommend?

We’re using WordPress but exploring Storyblok, Sanity, Strapi, Drupal, and CrafterCMS.

P.S. I’m not a developer, just looking for simple advice. Thank you!


r/cms • • Jun 26 '25

Help, Im looking for CMS that does not suck!!

12 Upvotes

I want to actually manage content and then integrate those content with various products of mine.

I want to have an admin panel and just create content that can be used for social media posts, websites, emails, sms, marketing campaigns, etc.

I dont want some website-first bullshit. I can hire developer that can integrate these contents with various tools and allow me to just focus on managing content to run my business.

Whats out there that can help me? So far i only found fracture tools that either require me to have some technical skills, do some web development, or learn a bunch of shit that only will lock me into their platform.

I want to be in charge of my content, take it anywhere when i need to, and have 100% freedom on how i integrate them with whatever tool i like.

Please help me! Im fed up with a saturated CMS market that suck.