Articles
The following guide outlines the steps needed to configure a Drupal 8 multisite setup. This guide is a work in progress and includes only sample configurations. Other options—such as HTTPS, different web servers and databases, or advanced virtual host configurations—are available.
The primary reason to use a Drupal multisite setup is to save time when managing multiple Drupal sites running the same core version. Every time a new core update is released, you only need to update one codebase instead of each individual site. However, there are drawbacks. These can be mitigated if you use the Aegir hosting system.
The following is an example of a multisite structure in Drupal 8. For simplicity, other core Drupal folders and files are not listed.
(See original discussion at #3004496: Improve Composer multi-site compatibility.)
While there are various considerations to keep in mind when deciding whether to use Drupal's multisite feature, here are some common reasons developers choose it:
More Semantics
Drupal 8 includes many instances where we’ve implemented more semantic HTML5 elements that can be used by assistive technologies. We’ve extended this by incorporating WAI-ARIA landmarks, live regions, roles, and properties.
The following modules can help improve the accessibility of your Drupal site.
Note: Some of these modules may be outdated and/or not covered by Drupal’s security policy. Please check each module’s project page for more details. For Drupal 7 modules.
Automatic Alternative Text
Latest version: 8.x-1.7
General Resources
- WCAG 2.0 - www.w3.org/TR/WCAG20
- WCAG 2.1 - www.w3.org/TR/WCAG21
- ATAG 2.0 - www.w3.org/TR/ATAG20
- ARIA Authoring Practices 1.1 - www.w3.org/TR/wai-aria-practices-1.1
- General Checklist -
Not all content hiding techniques are suitable for users of screen readers or other assistive technologies. This page outlines the primary methods for hiding content from all users or from screen reader users only.
Making Content Invisible (Visually Hidden)
If an element on the page:
Hiding content is very useful for accessibility. We can visually hide content and display it only to screen reader users, hide content from screen readers and display it only visually, or hide it from both. Drupal comes with some built-in CSS classes to help make intentions clear. We do not recommend using { display: none; } as it is often misused.