[lioeters]

Thank you for mentioning Grav CMS. It was particularly interesting to hear about the concept of "admin panel as a plugin". I like that idea very much, it's perfect for API-first design.

At work I've been trying to solve the question, how can we let the dev team continue to write documentation as Markdown files in Git repos, while not excluding others in the company who need/prefer GUI and rich text editor. I see now that it's possible to have the best of both worlds, with admin UI as a layer on top of the same underlying system, generating Markdown internally.

Still not sure how such an admin interface will integrate with Git though. I suppose "publish" can trigger a Git commit, but I wonder if it's feasible to ensure no Git push conflict when remote is ahead of local, i.e., someone else pushed a change before you did. Otherwise, I imagine the admin UI can get complex if it needs to provide a way to resolve such conflicting changes, with a side-by-side view of diffs.

[psd1]

Conflicts are not caused by git, they're caused by simultaneous edits. You'd have to solve that problem whatever your backend.