Ever wanted to know if a Drupal site is configured correctly, secure and uses best development practices? Want to integrate those tests into your continuous integration setup? What about providing Drupal audits as a professional service?
Coding + Development
The Backdrop CMS is an emerging technology born from a Drupal fork. Have you heard of this great new CMS but don't know where to start or what the differences might be between it and Drupal?
In this session we will go over the architectual changes made in Backdrop and what that means for you as a back-end developer. We will go over things like:
GraphQL has been deemed everything from the death knell of RESTful architectures to the query language of the future. Created by Facebook to power its data fetching and coming to Drupal 8 thanks to Sebastian Siemssen, GraphQL portends a dizzying shift in not only how client-side applications request and receive data but also how payloads are interpreted and formatted on the server side. What exactly is GraphQL, and what distinguishes it from the rest (no pun intended)?
The proliferation of testing strategies outside of a broadly agreed set of definitions has not only caused confusion but has caused a waste of effort by choosing the wrong strategy for the goals to accomplish. Learning the principles of solitary unit testing will enable you to make better decisions about the testing strategies you use and save you time.
In this session, we will look at one strategy: solitary unit testing. We will start by defining solitary unit testing and show how it distinguishes itself from other strategies.
Learn how to debug Drupal using modules such as devel, and get a handle on even more powerful tools such as Xdebug with Sublime. When I first got into Drupal as an experienced PHP programmer, I was mystified by the backend of Drupal -- so many multidimensional arrays, so many hooks, so much stuffs! I figured it out fairly quickly, though, with help of a few tools, which I’ll show you.
Technical debt is a common analogy to describe the cost of code mess and poor architecture. However, how far can the monetary analogy go? In this session we will look at insights from the Lorax and “environmental debt”. Specifically, we will build an argument for why the monetary comparison communicates the wrong idea about how technical debt is measured and how it impacts business. We will conclude with identifying measures and practices to mitigate technical debt.
Learn how to build things in Meteor, and how Meteor and Drupal can work together.
This session will give a thorough introduction to Meteor, and includes a demonstration outlining how Drupal and Meteor can work together to create headless Drupal websites and web applications.
Drupal is doing a great job of managing and organizing your content, but your content doesn't have to end at Drupal's front door; how do we get all of that juicy, structured data out of Drupal and into other websites, mobile apps, or other data stores?
You've installed Drupal and you've made a content type with a couple extra fields. You've even managed to create a custom module, and gotten Drupal to recognize it. Now what? You need to make lists, you need to manipulate that content, and you need to know how Drupal treats that content.
Senior Developer Joshua Turton will cover fields, entities, their common functions, and how to make lists . You will learn:
Composer is now required to install Drush, and more and more Drupal sites are using Composer to manage their modules, themes and Drush extensions. In this session, we'll talk about how these developments are affecting the way Drush works, and how you can make sense out of managing your Drush extensions and configuration, whether you are using Composer, or still running your site without it. We will discuss how Drush fits in to your development workflow, when you may have multiple Drupal sites requiring different versions of Drush, and will also review the relationship between Drush and yo