by Ted Bergeron
I spent 2-3 hours playing with Federated Wiki last night. It seems to be designed for individual use (or team with one login) It could work as a stand alone wiki, but the real power is using it in conjunction with other Federated Wikis. So it seems like the way it would work is a community or team would each have their own version of Federated Wiki (FW) They would point to the main FW. To edit they would fork, make local changes, notify main FW... that would merge (copy back) the individual changes into the main. I think it is much more suited to individual use. Especially loosely connected to a group. So unless you are a developer and can npm install and run node server in the CLI, the only hope to make this work for normal people is a hosted environment where you allow potential authors to each have their own wiki on 'the farm' as he calls it ... so that they can collaborate together
running it on a laptop is pretty easy. You can specify where you want to store the JSON files at runtime by
$ wiki --data /path/to/directory
this starts up the server and creates a pages and status directories. Within /pages are the individual pages which are just JSON files. I do like how slick that works. However his support for formatting is HTML or Markdown. And the Markdown plugin is very limited. It doesn't look like it supports all of Markdown But they say in their Docs they are 'allergic' to formatting and bulleted lists I do like the drag-and-drop to edit. And it is very cool how you can drag-and-drop content or pages from other FW's into your own FW Overall I like the concept. I'm going to use it for a while. But I feel like it may be too simplistic (which is what he's going for)