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

Styling the error pages

Drupal provides some suggestions for typical 4xx errors, such as File not found or Access denied.

Every time an error occurs on Drupal, the system triggers a redirect to one of those routes:

  • system.401: The user is trying to access an unauthorized resource
  • system.403: The user is trying to access a forbidden resource
  • system.404: The user is trying to access a resource that doesn’t exist

Every time the page for one of those routes is rendered, the system looks for a related page template:

  • page--401.html.twig
  • page--403.html.twig
  • page--404.html.twig

For example, for a Page not found error, Drupal checks whether a template called page--404.html.twig exists in the currently enabled theme.

To see this in action, follow these steps:

  1. Create a templates/layout/page--404.html.twig file with this content:
    {{ include('@organisms/page-error.html.twig', {
      srMessage: 'Error'|t...