Proposed Documentation Plan

[FatherShawn]

This thread is for discussion of the documentation plan proposed in my blog post.

[Dave Greenberg]

Shawn - I'm trying to squeeze in time to update or add pages wiki pages covering new or significantly changed features / functionality as I'm QA'ing 4.1 release issue tracker items. I'm doing this on the 4.1 wiki documentation space (http://wiki.civicrm.org/confluence/display/CRMDOC41). I'm wondering if it makes sense for myself and others to create a list (or somehow flag) the wiki pages that are being updated??

[Dave Greenberg]

Actually, after a quick chat with Michael McAndrew I think it makes more sense to document stuff that "belongs" in the User and Admin Guide directly there using the book editing interface and skip the redundant work :-). The "assumption" is that the next "release" of the FLOSS book will be applicable to 4.1.

[FatherShawn]

Agreed - as part of that I had proposed that we cross-index by adding links to the wiki to http://wiki.civicrm.org/confluence/display/CRM/2011+CiviCRM+user+and+administrator+guide+review.  The idea is to figure out which wiki pages are already covered in the book, pull in any missing tidbits and then prune the wiki...

[Dave Greenberg]

Ok cool. Alice and I also discussed the need to have some other eyeballs review the latest edition of the book for accuracy and relative completeness (i.e. given the functions addressed, that there's no gaping holes). I'm sending out an email (text below) reaching out directly to some folks that I think might be able to help (and who have strong content knowledge). Hopefully that will flush out some more reviewers / potential doc team members.

Anyone reading this who is interested in helping with the review, please add your name to a section on the wiki page:
http://wiki.civicrm.org/confluence/display/CRM/2011+CiviCRM+user+and+administrator+guide+review