3 ms·

Given the requirement that non-technical users should be able to use it, a wiki seems like a better model: GUI editing and version control.

• ComputerGuru 15y ago
  How well do concepts like forking and branching work with wikis, though? You can create categories and place the pages in them (to put the different editions for each title), but you can't really "link" revisions and branches to one another or indicate where they were derived from. And forking is absolutely out of the question.
  • RyanMcGreal 15y ago
    That is a limitation, but I'm not sure the marginal benefit of forking and merging functionality justifies the significant added complexity. Each edition gets its own page, and the revision history of each edition reflects versioning. On the rare occasion that changes in one edition need to cross over to another, a non-technical user should be able to copy/paste the changes across the two edit pages.
  • lazerwalker 15y ago
    It seems that something like GitHub's wikis would be a great compromise: a simple web-based editing interface, but backed by a Git repo that you can also access as a vanilla Git repo with plaintext files.
  • joh6nn 15y ago
    there are more than a few wikis that use version control for their backends. i'm aware of at least 2 that use git; branching and forking in that case would simply be UI issues, and could be handled the same way that github does.