There are a range of materials that can be distributed to organisations interested in CiviCRM. These are currently available on http://civicrm.org/content/spreadtheword
Blogues
Following a couple of discussions of this, the consensus seems to be that having good coordinated training materials is important to a maturing product to give confidence to organisations buying into the ecosystem. The doumentation has moved along considerably in the new book and this structure seems a reasonable place to start for creating a set of training videos.
Anyone currently working on video?
In doing some research for a potential project, I was exploring what kinds of eAdvocacy options were available to plug in to CiviCRM. Many of the big commercial eAdvocacy tools have big commercial price tags to go with them (and don't integrate directly with CiviCRM besides).
As many of you know with 3.4 & 4.0 a new API came out (APIv3). The new API had a number of improvements over the previous v2 including
Recently on CiviCRM irc and forum few people asked about adding client side validation for phone field. By default CiviCRM packages validate plugin, so this can be easily implemented with minor customization. Below is the example of validating US phone number on new contact form.
Good documentation is mission critical for the success of any software project. As a project we essentially have three audiences for our documentation:
Users Site Builders DevelopersWe have a couple of customers who have been asking to be able to set-up recurring contributions against pledges. This seems to be a possibly contentious improvement so I'm looking for feedback on it.
As part of my final year studying Computer Science at uni I'm required to take on a 400 hour project. I've been wanting to create a mobile app for a while now and given that CiviCRM is lacking such a feature I thought it would be a good idea to embark on developing one. Hopefully the end result will be good enough to incorporate into core!
As of the Bourne, UK sprints last August, bin/cli.php has been completely re-written for 4.1.
If you are an integrator or user, you might not have noticed this file. It used to be a PHP class that was used by many of the individual scripts in the bin directory.
Now, it's a command line program designed to be run directly.
With cli.php you can run any function defined in the API version 3.
If you run the script without any arguments, you'll get a usage statement explaining how it works: