Extreme Makeovers CiviCRM Style... Introducing the Shoreditch theme, CiviCRM's new User Interface Design
Not too long ago, we wrote a little blog post about some of the work we’ve been doing for CiviHR's new user experience and visual design and after months (and months) with our paintbrushes out it’s finally time to take the lid off the next phase of that project... integrating that look and feel into CiviCRM core…
Last year in February we started a series of CiviNYC work days. It consists of an event where we work and learn from each other for an afternoon, usually around 4 hours. Here's what it looks like.
Not too shabby!!!
We’ve talked about and have made some progress on APIv4. Along with a native form builder and an improved UI, a new version of CiviCRM’s API was identified as a key objective our roadmap. While it may be the least glamorous of the three, it is an increasingly important and powerful feature within CiviCRM. And it’s time for an update.
CiviCamp Montreal is a one-day event to discover CiviCRM, learn new tricks and share your experiences. The event will feature two tracks of sessions with a wide array of topics, from beginner to power-user, including a special focus on requirements for organisations North of the border, such as Canadian payment processors, event/membership taxes, tax receipts and translation. Register now, we will close the event once we reach the room's capacity.
Your organization has a solid membership base, but you want to retain members and help it grow. How can CiviCRM help?
The membership renewal process can be daunting, but learning how to best use CiviMember, as well as features of CiviCampaign, CiviMail and CiviReport, will make your membership outreach more targeted, streamline the on-line renewal process, and help you track your progress.
Firefox is at version 52, Chrome is at 55, where does the number inflation game end?
Let the countdown begin! This April, the CiviCRM core team proudly announces we're going negative! It works for politicians, why not your favorite CRM for the Civic sector?
“When they go high, we'll go low.”
From now on, instead of counting up toward ever-inflated numbers, each CiviCRM release will be lower than the previous version. We'll be counting down just like people did in their calendars before the year 0 AD.
“Negative is the new positive.”
I'm sure many CiviCRMers are checking their schedules and and making travel arrangements for CiviCon St. Louis in May. While this post is a bit off-topic, I want to highlight a place in St. Louis like no other place on Earth... the City Museum. It's already on the list of things to do while at CiviCon, but in my opinion it should also be on a list of things to do while you're alive!
Before I started working as a CiviCRM consultant, I was a CiviCRM user at a small nonprofit. We got a large chunk of our revenue through grassroots donations, but we never had an opportunity to see how we compared to other organizations like ours.
(TL;DR – you should install the Individual Donor Benchmark Survey extension, run the report, and submit your survey response.)
CiviCamp 2017, formerly known as CiviDay, took place in Denver on February 22. This is a casual gathering that is organized by CiviCRM experts to create a forum to discuss, discover and evaluate topics related to CiviCRM in a relaxed and candid atmosphere. Denver's CiviCamp, organized and hosted by Cividesk, offered a one-day fast track to learning about CiviCRM and improving overall user skills. The event had a great turnout and was an overall success.
Thursday 23th and Friday 24th of March we are having a mini-sprint in the Ede (NL) in which we will fix CiviCRM bugs. We are with four of us already (Erik Hommel, Alain Benbassat, Klaas Eikelboom and me) so it is going to be fun! That is the main reason and the other reason is that we want to contribute to CiviCRM Core.
Our plan is to have two days for fixing CiviCRM bugs once in the month or once in the two months. But at least regularly and fitting to our busy schedule.
So if you are in the neighborhood we want to invite you for joining us so it going to be more fun.
Some of you will know, use and might even love the CiviRules extension. We certainly do! Quite a few of the organizations we support with their CiviCRM stuff use and love it, and judging by the question on StackExchange and issues and pull requests on GitHub quite a few more do too!
In this blog I want to explain the round up we have done around the refactoring of the acl_contact_cache. In the previous sprints we discovered that a lot of the performance was slowed down by the way the acl_contact_cache was used (or rather not used at all). See also the previous blog post: https://civicrm.org/blog/jaapjansma/the-quest-for-performance-improvements-5th-sprint
Just a heads up for the community that "Using CiviCRM" by Joe Murray and Brian Shaughnessy is Packt Publishing's free book of the day. See https://www.packtpub.com/packt/offers/free-learning.
This book is a good overview of the system despite being written for a much older version of CiviCRM. In particular the early chapter on planning your CRM implementation is still applicable and valuable information that is often overlooked.
If you contribute to CiviCRM, we want to know about it. Now, you might ask "don't you already know given that contributions improve the code, coordinate events, extend the system, etc.?" Well, yes, that is true, but coordinating all of that information in such a way that we, as a small Core Team, can recognize it effectively is no small task.
Over the past year I have been volunteering time to help out in the effort to raise funds for the Hundertwasser Art Centre. In order to help the HAC project I have added a couple of reports that may be useful for other pledge users (or possibly sites that track money received through campaigns).