Tag drupal

Retroactive Unit Testing

So we all know that we should be writing unit tests for our code, right? And on top of that we should be using behaviour driven tests like Behat as part of our continuous integration.

But what about those libraries, modules and websites you wrote ages ago? They don’t have unit tests…

DrupalCon NOLA Notes. Brainshark - Migration from Sitecore in 90 days

Case Study: Brainshark - Migration from Sitecore in 90 days

Existing Site Challenges

  • No support and maintenance
  • Security risks
  • Poor template implementation resulted in design constraints
  • Not user friendly
  • No batch/bulk item publishing
  • Licensing model
  • Re-directs problematic
  • Didn’t want to host themselves
  • Maintenance issues
  • No wide adoption so finding the right people was a problem

DrupalCon NOLA Notes. Creating Online Stores with Commerce 2.x on Drupal 8

Creating Online Stores with Commerce 2.x on Drupal 8

Lessons from Commerce 1.x

  • Expected site builders to be experts on building a commerce workflow
  • Scalability problems
  • Prioritise UX

DrupalCon NOLA Notes. Drupal 8, where did the code go? From info hook to plugin

Drupal 8, where did the code go? From info hook to plugin

Background

  • Dependency injection container (DIC)
    • Container object that contains instances of stateless services (current user, url generator etc)
  • New routing system
    • Names instead of paths
    • Route name is just a machine name connected to a path and callbacks to provide title, content access
  • Namespaced classes like Drupal\search\Plugin\Block\SearchBlock

DrupalCon NOLA Notes. Drupal.org is Changing - Content Restructure, Issue Credits, Composer and more

Drupal.org is Changing: Content Restructure, Issue Credits, Composer and more

Content Restructure

  • Refresh of documentation
  • UI refresh
  • Blogs