Term index

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.




A container for information (placed in regions) for display on your website.

Build artifact

A generated codebase created as the result of a build process including, but not limited to:

  • Any third-party packages or libraries managed by Composer or NPM.

  • CSS or JavaScript files compiled by task runners, such as Grunt.

  • The results of custom processes scripted and carried out as part of the build process.


The information you want to provide to your website’s visitors.

Content type

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.


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.

More resources