Why we are not using booki for TTFA2

From HacktionLab: A UK-wide network tech-activists providing meet-ups, events, workshops, national skillshare gatherings and hacklabs
Jump to navigation Jump to search

The basic reason, we prefer Mediawiki for this particular project.


As an editor Booki has the following issues:

  • the writing column is too small making it tricky to edit in --Gremble 14:58, 17 April 2012 (UTC)


  • this is booki's strength, but its not not good enought that we don't have to do cutting pasting and typesetting, so it doesn't really help --Gremble 14:58, 17 April 2012 (UTC)

Interaction features[edit]

  • comments per page/chapter - our project needs to have a discussion section for each page (killer feature of Mediawiki) --Gremble 14:58, 17 April 2012 (UTC)
  • versioning doesn't work, and isn't on a per chapter basis - I would describe this a as a (killer feature of Mediawiki for our project) --Gremble 14:58, 17 April 2012 (UTC)
  • granular editing - docs and changes are not on a per paragraph basis, shame --Gremble 14:59, 17 April 2012 (UTC)

What Mark Had to say[edit]

Can someone remind me why we're using booki?

I don't like the way the platform handles viewing the current version of the chapter. It opens a javascript sub-window that I can't navigate using my browser controls. It would be much easier to handle the content on either this wiki or we.riseup.net, or if booki opened the chapter for viewing in a new window. Is there a way to make it do so?

Also, it seems to be failing to even display text legibly, are other people seeing things like this: Screenshot.png

(I'm using iceweasel3)

MaRk 10:02, 3 December 2011 (UTC)

Update: I came back for another look to see if there's been any improvement, and I get this: (note that there is no network problem connecting to flossmanuals.net)


Grrrr... MaRk 16:50, 15 January 2012 (UTC)


Booki Developer Interaction[edit]

IRC interaction is recommended and happens at:

server: freenode.net
channel: #flossmanuals