I'm looking for a content management system (CMS) that kind of provides a hybrid functionality of a wiki and versioning with branching/forking support like github.
The idea is to create for long-form texts what git provides for codebases. I.e. the support for different contributors to evolve a text in different directions which may or may not be merged at some point again.
The difference to a wiki would be that there is not only one current version (and history) but potentially several current versions, e.g. reachable via website.com/slug/hash where the slug is shared for all versions, and each version has its own hash.
To put it another way: I don't just want a version history in the background but
- I want to have the diverging branches to be visible. E.g. a meta information stating "hey, look here, there's a different take on this subject"
- definitely not just 1 current version and using git/etc. for the history.
- being able to link directly to each revision whether current or history (see the link with hash above)
- if an old revision is visited, maybe add a link to the latest versions (there could be several).
Something on a git basis could probably be used, but for branching that would probably mean creating a repository per text and lots of work parsing the repository's commits/history.