Session Submissions Closed - Thank you for all your submissions!
The session selection committee will make their decisions by the end of May and speakers will be notified in early June.
Sessions will be selected based ONLY on the title, experience level and description of the proposed session. In the past, we have given preference to sponsors and/or previous speakers before anyone else.
After much discussion, we've decided this isn't the fairest approach. We discovered we were selecting sessions based on criteria that didn't always get us the best content, and this year we're determined to do it differently.
Sessions are organized by track (see below), and experience level (beginner, intermediate, advanced).
The “site builder” audience creates websites using the Drupal UI and contributed modules. Presentations in this category should focus on what comes “out of the box” with Drupal, and less about what can be done with custom code.
Focused on the functionality layer, a “back end” developer gets into the guts of a web application. For Drupal, this means PHP, databases, custom modules, migrations, and headless Drupal (or should the absence of a front end still be considered Front End?).
Probably the least Drupal-specific, this area covers the technical and philosophical practices of deployment processes, servers, continuous integration, testing, etc.
Business (Gov, Non-Profit, Commercial)
We are very interested in sessions pertaining to how you run your Drupal focused business. How you market, manage, and deliver Drupal services and products should be the focus of these non-technical sessions.
End Users / Content Management / Project Management
Content administrators could benefit from beginner-level sessions on the basic concepts of Drupal from the end user’s perspective, along with potentially more in-depth sessions on analytics, search engine optimization, and content marketing. Possible topics on the project management side include building a team, planning/budgeting/estimating projects, resource allocation, project methodologies, or sharing processes.
Designing for the web has evolved as our CMSes have. Topics focusing on designing in the browser, responsive and mobile first design, accessibility in design will be most welcome.
A community session focuses more on the people that make all this happen. Could include lessons from other open-source projects, historical perspectives on the Drupal community, sprint/camp/user group planning tips and lessons learned.