philoSurfer Schedule

Watch the session video here.

Themes can become a beast. Over time, features get added and new patterns get introduced. Tight deadlines may also cause you to make inefficient decisions with the desire to one day go back and refactor. There are also times you will inherit a project built by another team and need to understand how to add on and reduce duplication. How do you size up a theme to ensure you are efficient and not growing out of proportion?

Watch the session video here.

Watch the session video here.

The "JAMstack" is some great branding that describes websites that are built entirely by javascript, API calls, and served as completely static pages.
Compared to LAMP platforms like Drupal and Wordpress, JAMstack has four huge things going for it:

1. High traffic sites that cost thousands of dollars a month could transition to a single server + CDN on low tier hosting (under 100 dollars a month)

How and why to decouple your Pattern lab from your theme. In this case study I will be talking about the decisions taken in the architecture of this solution for the City of San Francisco.

https://github.com/SFDigitalServices/sfgov-pattern-lab

Watch the session video here.

How many times have you ever heard? "Choose the right tool for the job" or "When all you have is a hammer, everything looks like a nail."

The Drupal community is embracing the "Get off the island" mantra. Modernizing Drupal was the goal of the latest Drupal 8 release, but technology moves faster than the awesome community could improve our beloved platform.

Watch the session video here.

Watch the video session here.

This case study will cover how the architecture of Drupal 8 enabled our web development team at UC Davis to quickly build a highly functional, customized web application that enabled the UC Davis Human Rights Studies Program to implement their Article 26 Backpack Tool for Universal Mobility (article26backpack.ucdavis.edu). 

Watch the session video here.

Come get an all access preview of how your next generation Drupal sites are going to work with Layout Builder.

Description

Layout Builder is a new experimental module for Drupal 8 and its implications are vast. In this session we're going to dig into the site builder implications of this new tool and how it's going to change your builds for the better.

Drupal 8's Configuration Management System is a modern marvel. We now have a standard way to export, store, and import configuration files.

When working on a single site, built on a fresh Drupal 8 install, the process is pretty straightforward and there are many tools to help along the way.

But what if you're building lots of similar sites? Like a multi-site? Or maybe a Drupal Distribution? Or Install Profile? Or Sub-Profile? In Drupal 7 we had Features. Do we still need that?

Watch the session video here.

We'll review some of my findings while learning and building web applications in Drupal 8.

We'll go over architecture options for web applications built in Drupal 8. Modern PHP dependency management with Composer, Content Entities vs Nodes and when each is appropriate. We'll look at some excellent combinations of contrib modules and glue code to create flexible architectures.

Who is this for?

Watch the session video here.

The Webform module for Drupal 8 provides all the features expected from an enterprise proprietary form builder combined with the flexibility and openness of Drupal. Everything and anything is customizable in the Webform module. You can build any type of form that pushes submission data to any system.

Watch the session video here.

Configuration management has only gotten more complex as Drupal 8 has matured. With Config 2.0 going full speed ahead, some improvements are coming. Unfortunately, our dream of being able to save configuration directly to files won't happen, and the community has created complex workflows to work around the problem of storing configuration in the database.

But, the workflow has been automated for you in Contrib.

Watch the session video here.

You know how your content looks on your own website, on desktops, laptops and phones, but how does it look when it leaves your site? Using open source protocols like Schema.org, Open Graph, and W3C specified meta data to markup your structured data, you can help boost your content’s chances of outperforming its competition in search engines, and shared on social media sites.

Watch the session video here.