Drupal and Acquia have their own terms and concepts that can be unfamiliar to new users. We have put together the following glossary of terms (including a brief definition for each), and links to more information about each term.
An Acquia Cloud Platform glossary is also available.
Term |
Definition |
---|---|
A container for information (placed in regions) for display on your website. |
|
A generated codebase created as the result of a build process including, but not limited to: |
|
The information you want to provide to your website’s visitors. |
|
A structured data type defining how you create and display content on a website. |
|
The root-level directory of your Drupal installation and its websites, containing files and directories. |
|
A packaged collection of files including Drupal core along with a collection of themes and modules, typically designed to address a particular need. |
|
The section of the server and application stack in which a web application exists. |
|
A group of websites in a single docroot. |
|
An extension or plugin adding features to your Drupal website. |
|
An individual ability relating to website access or administrative access provided to users. |
|
An identifier for the different types of Cloud Platform subscriptions incorporated into a server’s full, unique name, used in certain command-line scripts. |
|
Region |
An area defined by a theme, into which you can place a block of content. |
A collection of permissions applied to a group of website users having similar requirements. |
|
The permanent name used for your application’s default URL and code repository. For information about the sitename naming convention or requirements, see the Sitename definition page. |
|
A description of your server architecture or subscription. |
The Drupal 9 Glossary and Drupal 7 Glossary pages on Drupal.org contain more information about the preceding terms, and other Drupal terms.