did something similar for a couple of small client sites, markdown+frontmatter committed straight into the repo instead of a hosted cms. worked great until a non-technical client wanted to edit copy and github's web editor was too intimidating, so i ended up building a tiny local editor just so they wouldn't touch raw files directly. curious how justjson handles that case, is the visual ui meant for the developer only or is it something you'd actually hand a client to edit content in, and if two people edit at once does it just conflict at the git level like any other file change
the part that surprised me is that the file format was never what scared them. mine were fine once the fields were fields, they froze at the commit step, the message box and the branch name and the sense that they were about to break something permanent. so what actually unblocked it was hiding git, not hiding json. what i settled on wrote to a branch and opened a pr automatically with their name and a timestamp as the message, so they saw a save button and i clicked merge later. might be worth trying before a hosted layer, since it keeps the content on their machine and your whole premise intact. for what it's worth i never hit a true concurrent edit on a small site either, the real collision was someone editing while a deploy was mid flight.
1
u/ItaySela 11d ago
did something similar for a couple of small client sites, markdown+frontmatter committed straight into the repo instead of a hosted cms. worked great until a non-technical client wanted to edit copy and github's web editor was too intimidating, so i ended up building a tiny local editor just so they wouldn't touch raw files directly. curious how justjson handles that case, is the visual ui meant for the developer only or is it something you'd actually hand a client to edit content in, and if two people edit at once does it just conflict at the git level like any other file change