I built it specifically to address shortfalls of other site builders:
- No themes
- Uses 'modules' rather than the strangely popular drag and drop thing with blocks and widgets (which then jumble about the page wildly when resizing). We have 40 modules at the moment and I keep building more.
- 100% mobile optimised. We hide no functionality and most page editing I tend to do side by side, with the CMS in a separate window next to the preview site
- The preview site updates automatically when you hit 'save' so that it can be viewed on many devices in real-time at the same time (and shared easily too)
- It's very fast. No React or other shenanigans. There is JS for the more complex interactions, but it's been applied sparingly. Doesn't work without JS though.
- Sites are deployed to Cloudflare Workers Sites. The SSG behind the scenes is Hugo
I don't advertise this thing anywhere and all my clients are word of mouth. I have yet to hear a single negative thing from anyone.
I live in the countryside so my clients are all pensioners who don't know computers. They've all had run-ins with WordPress and naturally hated it. (though I don't want to knock a properly setup WordPress, IMO you have to be technical to do it and my system is aimed specifically at non technical people)
I don't do shops and even blogs are probably not directly my target audience. But if you just need to make a simple site with pictures, videos and images (maybe a mailchimp signup, instagram gallery or Google calendar signup or showing some PDF newsletters), then I'd challenge you to do it faster in any other system.
I'm doing this on the side, so have no time to build websites, so it takes no time to build websites in my system :) (I've built a lot of websites for free and just end up collecting the hosting charge which is between £8-£13 a month, which is hopefully similar to some sitebuilders, but I can't compete with the £3 per month offerings that tie you into other services and immediately become more expensive as soon as you add any meaningful functionality.)
There are about a billion things I want to improve about it of course. It's certainly not perfect, but finding the time is a challenge. I hope to one day be able to make it my full time job.
I just like to keep it simple and write markdown on a local git repository that is mirrored on github + github pages for viewing (but I'm sure there's other ways to do the same too). You can just commit your changes locally to test that everything works, and then push it to remote and it will get picked up by "production". It works as a single user but I can imagine working for a small team of contributors as well.
Lock down your WP install within your VPC & serve the static pages from S3.
If you do have a dedicated engineering team, the trend now is using headless cms (sanity or contentful) and a ssr platform (Next.js or any of the traditional frameworks).
Depending on your needs, a staging version can be built and hosted. To be promoted to production once chief editor Acks. Or multiple such versions.
You can have multiple stages. Or just one, with a preview on localhost. You can have testsuites crawling a build. Or just a manual quick glance.
This problem is not hard. It is, in fact, much simpler to solve with static sites.
What would you use for this? I wouldn't want to wait a minute for Netlify to build and deploy to staging each time for example.
It seems you want to optimize your frontend-work. Tweaking a live setup that goes `client-> CMS -> Database. [switch-tab] [F5-refresh] -> client -> CMS -> Database -> client` is quite certainly not the direction you want to go.
Instead, most frontend-development optimizes with things like that jekyll --preview: some devserver that autoreload (and autorefreshes!) your website on change.
I now ask you: if you are happy about the changes: How do you save it? How do you reproduce it onto those other two websites? Or, if you were carefull and did the work on test/acceptance/staging, how to reproduce it on production? How do you communicate to your colleagues what has changed? How do you communicate to your future self what you changed?
This stuff commonly lives in code, which is version controlled. Having it in a database is suboptimal, for this reason too.
E.g. bolting together page blocks for testimonials, feature lists and a contact form with some basic customisation like colours and images.
Markdown only support is straightforward but most company websites need a bit more than this. Accurate page previews before production deploys is really important too. Open source preferred as well.