I edit the website and then refresh and changes don’t persist. Obviously they don’t want people editing their production website, but is it otherwise supposed to persist? If not, what’s the point?
For this reason I find the demo a bit confusing.
For this reason I find the demo a bit confusing.
The repo notes that persistence requires editors to in with the (shared?) admin user and password.
Although the pitch is "CMS-free", this is a Postgres- and S3-backed content management system.
The in-place editing is extremely cool.
Glad you like the in-place editing. I'm also for the first time happy with the experience. You can press CMD+E for editing and CMD+S saving, and there's no layout shift, so it's really convenient for quick edits. :)
Cool! Postgres and an S3-compatible object store area are both listed as requirements, so you may want to update that.
So by "does not depend on additional software", does that means I can just use the filesystem?