Articles

This document was used throughout most of the Twig conversion process for Drupal 8 and may also be useful to you when updating your own themes and modules to use the Twig template engine in Drupal 8.

Note: all Twig-related work is now done in the Drupal core issue queue. Use the Twig conversion sandbox only to find previously converted templates and functions.

Steps for core contributors:

Using automation tools simplifies the task of theme development. Here we’ll use Gulp.js to build an automation tool for a custom theme.

Works with Gulp 3.x and Node 10.x or lower

Steps:

1. Install Node.js
Download and install the latest version of NodeJS from nodejs.org. The installation process may vary depending on your operating system.

2. Install Gulp

npm install gulp-cli -g

3. Set up gulpfile.js
Navigate to the custom theme directory.

In the previous section, we explored how a sub-theme is created along with the inheritance of various properties.

The list below summarizes the inheritance properties:

Working with z-index (layers) in Drupal, developers may need to experiment to determine whether an element they move up or down in the stack will cover or be covered by an element themed by a core module or theme.
To save time figuring out what’s happening at the stacking level, the table below lists all instances of z-index values in core. A module or theme with inherited cells includes only a few entries if inheritance doesn't alter the z-index value; otherwise, it receives a new row.

Upgrade your Drupal 6/7 site to Drupal 11

Upgrading a Drupal site means changing its major version, such as going from Drupal 6 to Drupal 11 or from Drupal 7 to Drupal 11. This documentation guide focuses on upgrading a Drupal 6 or 7 site to Drupal 11.

 

Updating a Drupal site means updating from one minor version to another, such as from “8.0.2” to “8.3.0”. Please refer to the Drupal 11 site update documentation for more details about updating.

Before upgrading a Drupal 6 or Drupal 7 site to Drupal 11, it is recommended to take several steps to ensure the process goes smoothly and produces the desired results.

Note: The topics on this page are not directly related to migrating configuration or content to Drupal 11. They are included to help site developers preparing for an upgrade to Drupal 11 understand these areas and choose the most appropriate approach.

Drupal 8 Configuration Management System

One of the most powerful new features in Drupal 11 is its enhanced configuration management system, which can be used to deploy an entire site's configuration from one environment to another, such as DEV - STAGING - PROD.

Overview

When preparing to upgrade to Drupal 8, it's worth spending some time planning the upgrade approach. While the content of your previous Drupal site can likely be migrated without issues, your Drupal 8 configuration will likely require some manual work. For example, the Views module does not yet support automatic upgrades in core, which means you'll need to recreate views manually on your Drupal 8 site. The best upgrade approach should be evaluated on a case-by-case basis.

This documentation page provides an overview of multilingual upgrades from Drupal 6 to Drupal 8. A similar page for Drupal 7 to Drupal 11 will be created soon. In the meantime, refer to the multilingual migration meta issue.

Before You Begin: Enable D8 Modules

Drupal 8 offers comprehensive multilingual support in Core. As explained in the Drupal 8 Multilingual Guide, multilingual capabilities are provided by the following core modules: