Book Image

Modernizing Drupal 10 Theme Development

By : Luca Lusso
4 (1)
Book Image

Modernizing Drupal 10 Theme Development

4 (1)
By: Luca Lusso

Overview of this book

Working with themes in Drupal can be challenging, given the number of layers and APIs involved. Modernizing Drupal 10 Theme Development helps you explore the new Drupal 10’s theme layer in depth. With a fully implemented Drupal website on the one hand and a set of Storybook components on the other, you’ll begin by learning to create a theme from scratch to match the desired final layout. Once you’ve set up a local environment, you’ll get familiarized with design systems and learn how to map them to the structures of a Drupal website. Next, you’ll bootstrap your new theme and optimize Drupal’s productivity using tools such as webpack, Tailwind CSS, and Browsersync. As you advance, you’ll delve into all the theme layers in a step-by-step way, starting from how Drupal builds an HTML page to where the template files are and how to add custom CSS and JavaScript. You’ll also discover how to leverage all the Drupal APIs to implement robust and maintainable themes without reinventing the wheel, but by following best practices and methodologies. Toward the end, you’ll find out how to build a fully decoupled website using json:api and Next.js. By the end of this book, you’ll be able to confidently build custom Drupal themes to deliver state-of-the-art websites and keep ahead of the competition in the modern frontend world.
Table of Contents (21 chapters)
1
Part 1 – Styling Drupal
12
Part 2 – Advanced Topics
17
Part 3 – Decoupled Architectures

Setting up a build process

Every time some new code is pushed to a remote repository, we must run a set of checks to ensure the quality of the code we’re providing. Here and in the following chapters, we set up checks for coding standards and tests for visual regression and JavaScript. Of course, you can (and should) test more (using tools such as Behat (https://docs.behat.org), for example).

As we’re using GitHub as our code repository, we define a GitHub action (https://github.com/features/actions) to run all our checks. GitHub Actions is free for public repositories and is limited to 2,000 minutes of execution every month for private projects.

GitHub Actions basically runs a set of commands on our code base in a Docker container, quite similar to what we’ve done until now on our local environment. To simplify the setup even further, we’re also going to use DDEV in the GitHub Actions pipeline.

GitHub actions are defined as YAML files in the .github...