jbunik Schedule

Watch the session video here.

Is your team gearing up to migrate a site into Drupal 8? In this presentation, I’ll walk through the steps I’ve taken to prep my developer for a Drupal 8 migration. Topics covered will include the following:

Watch the session video here.

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.

React started as a way to build apps. People soon discovered that React's ability to render to string meant that React could be used for building websites where shipping a fast HTML version of the site was necessary.

Gatsby is a very popular way to build websites with React and recently became a company with VC backing to take React deep into the world of CMSs.

Watch the session video here.

Since the release of Drupal 8, great strides have been made to develop a component based theming workflow that takes advantage of the best that Twig has to offer and also plays nice with living style guides and pattern libraries. Gone are the days of redundant styles and markup, making way for the efficiencies found when Drupal and tools like Pattern Lab can share the exact same code. That said, handling the mapping of data between Drupal and your component library can still be quite complicated and difficult to coordinate on larger cross-functional teams.  

Watch the session video here.

The Drupal 8 configuration system can provide great advantages to managing the configuration of a site, but it can also cause massive headaches if used improperly. This presentation will provide an overview of how the Drupal 8 configuration system works, best practices on basic workflows to utilize it effectively, and a small sampling of some of the contributed modules available to enhance it.

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?