Configure basic settings which affect performance, and perform basic analysis to understand what might be affecting website performance.

Every Drupal module needs a *.info.yml file; the basic structure of a form controller class and related routing is the same for every form; and much of the code required to create a custom content entity type is boilerplate annotations and extending base classes. Wouldn't it be nice if there was a way to automate some of that repetitive work? Drush can be used to speed up module development by generating scaffolding code for event subscribers, forms, services, module files, routing, and much more. These generators are provided by the Drupal Code Generator project. They're neatly bundled up in Drush under the drush generate command.

Before Drush 9, there were no code generators in Drush, but the Drupal Console project provided them. That project and its code generators, have languished since the release of Drupal 9. While it can still be used, and is often referenced in tutorials about Drupal, we much prefer the code generated by Drush at this point.

In this tutorial we'll:

• Learn about the Drupal Code Generator project
• Learn how Drush integrates with this project
• Demonstrate the drush generate command and its options

By the end of this tutorial, you'll know how to use the drush generate command to speed up development for your Drupal modules.

A multisite Drupal installation allows you to host multiple, separate websites while relying on the same set of code. Large organizations often rely on a multisite installation to cut down on the operational upkeep of multiple sites. Hosting a multisite in Docker poses several additional challenges. Fortunately, the process is not dissimilar from configuring a bare-metal server to run a multisite.

In this tutorial, we'll:

• Outline a multisite's additional requirements for Docker containers.
• Configure alternate, local domain names to resolve each site.
• Learn how to configure a multisite to use alternate domain names.

Drush is the command line shell and Unix scripting interface for Drupal. The most common way to install Drush is to install it on a per-project basis using Composer. We'll walk through the steps to do that, as well as how to set up the Drush Launcher tool (to make it possible to execute Drush commands without having to specify a full path to the executable).

In this tutorial we'll:

• Install Drush
• Verify it worked

By the end of this tutorial you'll have Drush installed.

Every Composer project is made up of a few standard files and directories. This tutorial provides an overview of the anatomy of a Composer project, and the essential files and directories used by Composer, including:

• What are composer.json and composer.lock files?
• What is in a composer.json file?
• What is the /vendor directory?

By the end of this tutorial you should be able to recognize the standard files and directories in a Composer project and know what they are each used for.

This tutorial demonstrates the value of using Composer. This demonstration will employ the most basic use case of using Composer to create a new, non-Drupal application that writes a message to the system log. It will encompass the fundamental concepts of Composer installation, requiring (installing) a new dependency, autoloading it, and implementing it.

In this tutorial we'll:

• Install Composer
• Use Composer to start a new project
• Use Composer to require a 3rd party dependency
• Use the required code in an example application

By the end of this tutorial you should be able to explain the value of Composer, and have Composer installed and working on your local machine.

This tutorial provides an overview of the concept of an "artifact" and provides step-by-step instructions for deploying a Composer-managed Drupal application to a hosting environment.

In this tutorial we'll:

• Define what an "artifact" is
• Look at how to use Composer and a build process to create and deploy an artifact
• Talk about the benefits of this approach

By the end of this tutorial you should have a general understanding of the steps required in order to deploy a Composer-managed project into production.