When Rippleffect first moved from Pimcore to Drupal, I was leading one of the development teams in my role as head of project management. Always one to rise to a challenge we picked up Drupal and started to pick it apart. It soon became apparent that it was a compelling piece of software. At the time the team’s knowledge was weak – so we invested in a Drupal contractor to help teach the group. This was a game changer, being able to work with someone who had an in-depth knowledge of the mechanisms of the software helped jetpack the project to completion and training.
Having a team who knew what they were doing made it a no-brainer so we could concentrate on the client’s needs and outcomes, rather than worrying about technology.
The three websites went live a day after each other in June 2017 and worked like a dream. Drupal’s back end is easy enough to use, drawing from the user experiences of WordPress and Sitecore – this meant that any issues we had to deal with were mostly technical rather than a training issue. This might sound bad, but bugs are a natural part of development, and it’s possible to lose a lot of time clarifying if a problem is with the user’s actions or the technology.
The number of modules available for Drupal also make it very cost efficient, as you’re not re-inventing the wheel every time you need a solution to a common challenge (e.g. caching or cookie policies).