E-mail
- civi campaign
- general update
- the 'why' as well as the 'what'. i.e. more "If you want to do X, then Y is good approach because.... But one downside of approaching it this way is A." as opposed to. "To configure events click configure events and fill in the event configuration fields"
- more on CiviEngage with some PTP people.
- narratives/strategies (that may span modules) that explain clever ways to use CiviCRM in the real world
- chapter on duplicates handling
- make sure that everything from training is incorperated in book.
- make it easy to cross reference the book from training materials. i.e. for more information on importing, see ***
- audit that all subjects that aren't components are properly covered (e.g. mapping, duplicates, website integration)
- look again at structure. It is pretty good at the mo, but always room for improvement
- advanced search modifier for memberships relationships etc.
- membership price set support (details here :http://issues.civicrm.org/jira/browse/CRM-8483 )
Potentially, it might be good to make a final call about wiki documentation vs. book and use a bit of resources to eradicate duplicate content from the wiki (assuming that book takes precedence).
Labels:
