
This project required redesigning, unifying the Drupal code base and building the FOCUS website in Drupal 7 and migrating a constituent relationship management system for the organization.
- Secure
- Accessible anywhere
- Flexible for current and future database needs
- Functional/Minimalist design
- Staff editable content
- Easily attainable, organized information for end user
- Contact tracking
- Event tracking
- Donation tracking
- Bulk Mailings
How does a growing organization with differing design ideas and 15 years of scattered information/data create a minimalist website that accurately promotes the organization while satisfying the aesthetic and functional needs of its employees and users?
When I joined the FOCUS team, FOCUS had contracted with a developer to rebuild the FOCUS website using Drupal 6, CiviCRM and Amazon EC2 to satisfy the needs of all parties and left the management of the project to me. Ultimately, as you will find out, development fell to me.
Initially, despite the reluctance on the developer’s part, I decided to put the project on hold for several weeks while I interviewed each employee and created office workflow diagrams that would more easily map FOCUS’ needs to the CMS/CRM project we were undertaking.
Once I had a better understanding of what FOCUS needed and we reassessed our timeframes and deliverables, I began the process of collecting and submitting the data to the developers. The data mapping project went fairly smoothly and development began on the developer’s part.
Shortly thereafter, things began to unravel. FOCUS’s executive director was unhappy with the theme that the developer had made and asked me to create a new one. We had problems with the data upload matching our needs and development began to slow to a crawl.
Things came to a head when our Director of School Quality joined the project, cancelled the contract with the developer and gave me the project to finish.
Once I was given the reins, I divided the project into 3 phases: Theme and Drupal release, CIVICRM cleanup and fundamental portions release, and secondary portions release.
Phase 1 proved to be difficult due to differing design thoughts by the stakeholders. It took 19 separate psd mockups and about a dozen revisions to the sitemap before I found a version that was acceptable to all parties involved. Once I found a consensus, the creation of the theme went smoothly (I have since redone the theme 3 times, to get to the current version).
I then delegated website page revisions to departmental staff and focused on getting the public facing portion of the website up to meet our timeframe.
Setting up the fundamental portions of the CRM proved fairly simple and we began sending bulk mailings and setting up events. However, the database was outdated and jumbled mess of 15,000 contacts with little connection between them. Ultimately I started from scratch and reimported all contacts to create a clean database. The process was time consuming but cut out almost 5,000 unnecessary contacts and gave a solid base to build from.
Once things were running in the second phase, I began tackling the views that the developer had created. Unfortunately, routine Drupal core and module updates began breaking the custom code used in the creation of several of these views. I ultimately decided to rebuild these views from scratch and minimize the custom code needed to create these views. Fortunately, I was able to recreate most of these views using Drupal’s views and CiviCRM profiles, but I did have to modify and use some of the custom code to adhere to FOCUS’ needs.
Next, I redesigned focusdc.org/data to unify the various data visualizations we had been building into a single repository. After several mock ups, the current version with thumbnail representations which open lightboxes was approved and implemented.
The final piece of the puzzle was to migrate the donor data into the CRM. This process went smoothly, but continues to raise challenges as we put more and more data into the CRM. This includes customizing the PHP based reports and integration with events to satisfy FOCUS’ ever changing needs.
FOCUS now has a unified, web based location for tracking constituents and easily allowing charter schools to interact with our organization. The website has seen a 64% increase in page views and 49.4% increase in users. For the first time, FOCUS can track donations, sign someone up for an event, and send them an email all from one location. Ultimately, the success of this project is that FOCUS has now used this system for five years for its daily needs with very few stoppages due to the streamlined workflow.
