Case Studies on DrupalCon Baltimore
There was an enormous amount of sessions in the past DrupalCon. They are available online. But to make things easier for you, we’ll simply group them together and add a little overview, so you’ll easily pick the ones that you like. We’ll start with case studies on DrupalCon Baltimore.
Building NBA.com on Drupal 8 by Tobby Hagler from Phase2 and Josh Mullikin fromTurner
A session gives an overview of NBA.com, the reasons why Drupal 8 was chosen for the 2016–2017 season and how Drupal 8 interacts with other systems and stack components. Attendees learned what worked, what they should avoid and also tips and tricks for architecting a complex site build. The reasons for using Paragraphs module, Angular 2 … were also explained. All in all, fans of the best basketball league in the world were given an exceptional game experience and were brought closer to the game.
Cornell University Case Study — Drupal as a centrally-brokered platform for web development at the university by Josh Koenig from Pantheon and Shannon Osburn and Ryann Levo from Cornell.
In this case study, unique challenges Drupal faces in higher education are explored. Moreover, the opportunities to “do it right” by offering a complete Drupal Platform to campus are also presented. Namely, the IT web team at Cornell University has gone through the entire journey, starting with having to deal with Drupal as one of many technologies all the way to promoting Drupal. Therefore, presenting Drupal opportunity to a university audience, satisfying executive needs for security and oversight, walking the line with maintenance and support … were covered.
Building reusable websites on Drupal 8: lessons learned from transforming rednoseday.com by Peter Vanhee from Comic Relief.
In this case study, the process of building reusable websites in Drupal 8 is explained. To be precise, Comic Relief reveals how they rebuild rednoseday.com. The session covers test-driven development with a focus on behat tests, Comic Relief’s git flow model including CI and feature preview branches, following the KISS principle at every step of the way, how Comic Relief deals with configuration and so on…
