I have been involved in the CiviCRM community for over 5 years, and enjoy implementing and programming CiviCRM for a variety of non-profits. I have been amazed at the rapid pace of innovation delivered with each new release, and CiviCRM's flexibility in being able to accommodate a variety of requirements. I have learned a lot about CiviCRM by participating in CiviCon, online forums, and CiviCRM book sprint.
The community provides excellent forum support, new ideas and feedback on suggestions. The CiviCRM software suits many use cases and allows us to support a large number of diverse UK voluntary sector organisations.
Civi is one of those pieces of software that makes you wonder how early humans could have survived without it. Every nonprofit seems to be using Civi for some aspect of their fundraising, and I'm always surprised at the creative ways different people find to make it work for their needs. Happy to be able to help out a bit. There's a lot of energy going into this project--definitely checkout the forums and the IRC channel if you're curious.
I have consistently found the CiviCRM community to be welcoming, inclusive and supportive, and this has inspired me to want to become a part of it. It is great that the open source community allows everyone to benefit from the contributions that each of us is able to make, and I am making my own contributions as I can.
As a software product, CiviCRM is powerful, versatile and extensible and is enjoying active development and growth by the community that uses it.
CiviCRM is seamleassly integrated in Drupal, the world's leading social publishing system. This Open Source combination allows for the most flexible solutions while enjoying continously improved CRM-standards that shorten the time-to-market span of your individual demands.
CiviCRM is one of the core offerings of our company. Remaining close to the CiviCRM community is important to us, as it keeps us close to new developments in the tool, and allows us to offer our feedback for new releases.
<Cross posted from Advomatic.com The code blocks will be easier to read there.>
Sometimes after launching a new site our clients find that there are fields and features in CiviCRM that they don't use. We are working with a client that wants to remove all fields and features that aren't useful in order to simplify their user interface and make it easier to use. This includes things like SMS features, email signatures, and demographics. There are also several fields that they wanted renamed to be more consistent with the legacy system that they migrated from. To fulfill this requirement I used a combination of template overrides, and CiviCRM's translation system.
First up I should point out that if you do want to go down this path you need to make clear to the client that this will take a fair amount of effort up front (hopefully less for you now that you are reading this recipe). Additionally, if/when you upgrade CiviCRM these customizations will need to be reviewed at the very least, and possibly even re-done to some extent. So while this customization will make things more usable for CiviCRM administrators, it will add cost to both the initial site build, and to ongoing maintenance.
By definition CiviCRM is used by many organizations in the political sphere. For those organizations working in the US one useful metric to have on your contacts is their congressional district. Up until now this has usually been accomplished with either custom code, or exporting your contacts, sending them through a bulk lookup tool, and re-importing them. There is now an easier way to get this with the CiviCRM Sunlight Congressional District module.