MLK Student Union - East Pauley Ballroom

The first challenge of any Front-end Developer is knowing when to stop theming a page and to start building a design system.  It is too easy to focus on the homepage, landing page or detail page of a site without ever thinking how the components on a page may be used.  This often leads to extraneous markup, bloated CSS and technical debt that increases the complexity of your Drupal 8 site.

Whether your designer uses Fractal or PatternLab, implementing Atomic Design Patterns can be challenging within the Drupal landscape.

Many Site Builders take full advantage of the Display Modes for Entities making our job as a Frontend Developer much more complex. If the build solution includes Display Suites, Panels, or other such module then our job becomes increasingly more difficult.

Enter UI Patterns!

In Drupal 7, we front end developers could hack away a most themes and modules to get the output we needed with dpm and a little hutspa. Drupal 8's sophisticated code base means we need a few more tools to get and modify our data beyond what Twig provides. This session will be a survey of browser extensions, modules, applications and PHP tricks that will make debugging and variable inspection a great deal easier. Each tool will be shown with a video demonstration.

Tools we'll cover:

In Drupal 8, we have a very flexible theming system that allows you to override the front-end output of your site. At the same time, we have site building techniques and modules that give us lots of flexibility over the display of content, forms, navigation, Views, webforms, layouts and other components. Sometimes, it’s easy to know when site building stops and theming begins, but other times we have to decide which approach is the best.

Drupal 8 has changed a lot and the process for creating, building, testing and deploying a site is not the exception.

During this session, you will understand the process of creating, building, testing and deploying Drupal 8 sites, and learn which tools you can use to improve your development workflow and reduce project setup and on-boarding time, implement automated analysis tools for code review, code coverage and finally how to build and artifact and deploy your project.

The ideas of Atomic Design and component based design allow one to create an established structure within which a large scale front end project can be built. The CMS space hasn’t always been the most friendly toward implementing these types of patterns. Whether it’s difficulty in creating a content architecture that models your front end design system within Drupal or the feeling of lack of control over generated markup, it can feel like an uphill battle.

We wear a lot of hats as front-end developers. Depending on the client or company you work for, you may be the designer, UX/UI specialist, site-builder, QA tester, and developer all rolled into one. How can we possibly add the accessibility hat on top of all that? What accessible pieces should we even include? Which pieces are easy wins vs. impossible juggernauts? How do we implement inclusive development when a project does not have a lot of time or budget to include that piece? One way we can tackle these issues is by using an accessible component driven approach.

This session will detail the mind shift in the Drupal community around how Drupal software is released. Drupal 8 is the first major release under this new philosophy, which frees users to focus on innovating instead of waiting when it comes to features and functions. Angie Byron discusses how the Drupal community has changed the way we think about software releases.

Learn how to combine the power of the world's most popular front end framework, Bootstrap with Drupal Paragraphs, the powerful module that allows content creators to build layouts and structured pages.

Configuration management has been a hot topic since it was first announced as an initiative. Unfortunately, our dream of being able to save configuration directly to files didn't materialize, and the community has created many complex workflows to work around the problem of storing configuration in the database.

Drupal’s authentication process can be expensive and difficult to scale. What do you do when you need to plan for an unknown but large number of authenticated users?

This presentation will show you the approach we took on the new D8 based wholefoodsmarket.com to allow Drupal to work with lots of authenticated users without taking down servers. We'll walk you through how we used an approach called session-less authentication to avoid database calls and the ways we are storing PII user data outside of Drupal.

This session will give an overview of the Field API in Drupal 8, and show how to create custom compound fields (fields with multiple data values). These fields can initially be used in content types, and then further extended to be used in Form API forms.

What's a Compound Field? Imagine a cake recipe. It consists of ingredients to bake this cake. Every single ingredient consists of multiple atomic values: amount, metric (tsp, tbsp, cup, gram, ml), a description, calories, etc. In a recipe, however, an ingredient is a single, cohesive field that consists of combined data values.