Long awaited day came - a bunch of good folks from CiviCRM Community arrived to Truckee to work on CiviCRM book! Some of us have been hanging out in San Francisco for some time already, attending NTEN and CiviCRM Developer and User Meetups, some of us arrived only today. First item of business was finalising book outline so that we can be ready to do actual writing on Monday morning. The outline looks quite detailed, but also realistic - it seems like it will be a busy week, but we should be enjoying the effects on Friday.
Stay tuned for news on the book - new information will be showing up on Twitter, as well as on #flossmanuals and #civicrm channels on IRC.
P.S. Doesn't look like the cover will be looking like anticipated. :-)
A quick reminder that the week long CiviCRM book sprint starts this Monday and you're welcome to participate by writing, reading and commenting on chapters and sections.
We'll be using the Floss manuals infrastructure. The best way start is by saying hello in the IRC chatroom which is available on the Floss manuals site or via an IRC client at #flossmanuals on irc.freenode.net.
Dave Greenberg recently posted about our upcoming book sprint saying "almost every week folks ask whether there is a CiviCRM Book they can read".
So there must be something missing from the documentation. And given that the book will be in addition to what is on the Wiki - not a replacement for it - the two questions I am asking myself are:
'What are we missing in the documentation? And how should the documentation and the book complement each other?'
Here is my initial answer:
'If the documentation is a hands on quick reference where you go to find the answer to a specific question, then the book is the tool that enables you to make effective use of the documentation. It contains all those things you to keep in mind when using (or deciding to use) CiviCRM; the advice and best practices; details of the some of the challenges you may face; the questions you need to ask yourself to get the most out of your CiviCRM installation.'... Read more