Component-based Theming with Twig
In order to fully take advantage of Drupal 8 and Twig, it helps to have an understanding of components, patterns and the differences between tradi
In order to fully take advantage of Drupal 8 and Twig, it helps to have an understanding of components, patterns and the differences between tradi
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.
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.
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.
Watch the session video here.
As a site-builder-turned-developer, I know just how intimidating the command line can be. In this session, I'll demystify the command line, and empower YOU, the site builder. With a basic grasp of the command line, you'll work more quickly, do more, and understand some of the tech behind your Drupal site.
We'll cover:
* The basics of the command line: What's a terminal? How is this thing a text editor? How do I navigate my file structure?
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.
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.
Pattern libraries (living style guides) have existed for years as a way to formalize design systems across applications. In the past year or so a number of compelling modules and themes have emerged to integrate pattern libraries with Drupal 8.
Watch the session video here.
As developers we struggle everyday to solve problems and we rely on development tools to help us puzzle through those problems. Years ago, I adopted PhpStorm to augment my skills and in doing so I've learned a lot of ways how to gain the most out of the tool.
Come as we break through the levels of complexity and level up your skills as we talk about: