Growing Together

Growing Together

Growing Together is a multilingual community website; a new partnership initiative of community and environmental sector organisations that will unlock income, land and skills for community growing groups to them become financially self-sustaining.

Technology stack:
  • Drupal

About The Client

The client is an experienced JAVA developer. He possesses 10+ years industrial experience. Some other websites development skills client has PHP, Ruby on Rails, HTML/CSS & JavaScript. The client has held a variety of roles, from junior developer through to Project Manager, a Senior Consultant and Freelancer.

Within these functions the client has held various responsibilities, from coding bespoke applications, integrating OTS packages, using frameworks and implementing open source solutions (Joomla, Alfresco, Magento, Drupal, WordPress, etc. Ph.D.). The client is also experienced in information architecture, small-scale solution design, search engine optimisation, client management, sales, training, requirements analysis, post sales support.

With Ph.D.degree in hands, the customer is highly educated and has higher degrees in History and Computing.

The Client’s Requirements

Growing Together

The client had specific requirements for the website. They wanted to have a mobile responsive Drupal 7 website with translations enabled for English and Welsh languages.

The client also needed a CiviCRM integrated to display and register for their events added in their CiviCRM.

The main aim was to make the site live with all content within 1.5 months including design, functionality and testing. The main challenge we faced was in the CiviCRM setup where the client events had different input fields for a user during an enrollment process.

Our Solution

Growing Together

Having fixed requirement with the client the development started immediately where functionality and theming in progress simultaneously to achieve the short deadline. During the development we used locale, content translation, internationalisation (i18n), etc. modules for multilingual setup; and we used CiviCRM modules for the integration with CiviCRM.

The main challenge we faced during the development was with the integration with CiviCRM events, the client required to insert the events in Drupal but relate them directly to their CiviCRM setup. We gave a solution integrated Drupal with CiviCRM using the module and customised with our module to allow a user to list all events from their CIVI setup into Drupal event content type and relate the CIVI & Drupal events. In the front-end using the Civi API, we fetched the CIVI event link to allow a user to redirect to the related CIVI event when clicked on a button in the Drupal event.

Such a solution to CiviCRM was given and not used entire CiviCRM module was because the client wanted to show Drupal events and link them to CIVI events in and not the CiviCRM events directly in Drupal.