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.

  • I don't know af any, but cmsmatrix.org is your go to site for all things CMS. Try their CMS selectoin woizard & see if that helps – Mawg Dec 13 '16 at 8:28
  • What CMS features do you need? Is a web UI to edit HTML files enough? – Nicolas Raoul Jul 11 '17 at 5:55

Most staticsitegenerators store their sources in plain files, just put these files in a git.

Or use github pages, technically using the staticsitegenerator Jeykll with out-of-box github support. If you want to host it yourself, use gitlab pages with several other staticsitegenerators.

Or try a look in ikiwiki.

  • 1
    Thank you for your response. I tried to expand on the features I'm looking for in my question. I know that static site generators could be used but (a) I think it would be kind of awkward to support branching per text elegantly with just 1 repository. I'm aware of Github pages but they only show the current version which fails at least at 2 features: Each version being directly accessible and supporting several (current) branches. Similar issue with ikiwiki: It can use git underneath, but only 1 branch/repo for everything. – specialchar Nov 12 '16 at 17:54

Your Answer

 
discard

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.