Acquia Site Builder D10 key terms

A named bundle of the Node entity that defines a distinct kind of editorial content, such as Article or Page. Each content type has its own fields, display settings, and comment configuration.

A subtype of an entity that groups similar items and can carry its own fields and settings. Nodes, taxonomy terms, users, and blocks all use bundles to separate configurations.

A structured data object in Drupal that has a type, optional bundles, fields, and identifiers. Content, users, taxonomy terms, and configuration objects are all entities managed through a common API.

A reusable, typed data component attached to an entity bundle, such as a text field, image field, or date field. Fields store content values and control how editors enter data.

The site-wide definition of a field's machine name and data type, shared across every bundle that uses it. Storage settings, such as cardinality, live at this level rather than per bundle.

The form element used to capture a field's value on an entity edit form. Widgets are chosen per bundle and determine whether editors see a text box, autocomplete, checkbox, or media selector.

The output renderer that controls how a field's stored value appears on the front end. Each view mode can assign a different formatter, such as an image style or a linked label.

The setting that limits how many values a single field can hold. A cardinality of one allows a single value, a higher number allows multiple values, and unlimited permits any count.

A field type that stores a link to another entity, such as a node, user, taxonomy term, or media item. Reference fields power relationships like related articles or author profiles.

A container that groups a set of taxonomy terms used for classifying content. Vocabularies can be single or multi-level and are attached to content through term reference fields.

An individual category or tag inside a vocabulary. Terms can be hierarchical, have their own fields, and be referenced by content to enable filtering and grouped listings.

A named set of display settings for an entity, used to render the same content differently in different contexts. Common examples are Full content, Teaser, and custom modes for cards.

A configuration entity that builds lists of content or other data using a query, filters, fields, and display types such as page, block, or feed. Views drive most archive and listing pages.

A View filter whose value is supplied at runtime rather than fixed in configuration, often taken from the URL. It lets one View serve per-term or per-author listings.

A View setting that joins another entity into the query so its fields and filters become available. For example, a relationship to a referenced author lets a View show author data.

A bundle of the Media entity that defines a kind of reusable asset, such as Image, Document, or Video. Each media type has its own source plugin and fields.

A Drupal entity that stores reusable assets separately from the content that displays them. Media items can be referenced by many nodes and swapped without editing each node.

A bundle of the Paragraphs entity that defines a reusable component, such as a text block, accordion, or hero. Editors compose pages by stacking paragraph items in an ordered field.

A contributed module that provides an entity for building structured, repeatable page sections. A paragraph reference field with unlimited cardinality lets editors assemble layouts from components.

A core module that lets site builders design entity or template layouts visually with sections and blocks. Layouts can be overridden per node, giving editors control over individual pages.

The administration page where blocks are placed into theme regions for all pages. It controls the default placement of menus, branding, and custom blocks across the site.

A configurable piece of content or output placed in a theme region or layout section. Blocks can be custom, generated by modules, or built from Views displays.

A named area declared by a theme where blocks can be placed, such as Header, Sidebar, or Footer. Regions appear in the block layout interface for each enabled theme.

A collection of templates, styles, and configuration that controls a site's visual presentation. Themes declare regions and can be set as default or used for administration.

A file using the Twig syntax that renders markup for a theme or module. Template naming suggestions let site builders override output for specific content types or fields.

A configuration object with a schema and identifier that stores site-building settings, such as content types, views, or date formats. These can be exported and imported between environments.

An entity whose data is editorial and stored in database tables, such as nodes, terms, or media. Unlike configuration entities, content is not moved by configuration synchronization.

The process of exporting configuration to YAML files and importing it into another environment. It keeps settings identical across development, staging, and production without copying the database.

A Drush command that writes the active configuration to the sync directory as YAML files. It is typically run after making site-building changes and before committing them to version control.

A Drush command that applies YAML files from the sync directory to the active configuration. It is used to deploy configuration changes to another environment after code is updated.

The filesystem location, defined in settings, where configuration YAML files are written and read during export and import. It is usually a path outside the web root under version control.

A runtime change to configuration values made in settings or a module without altering stored configuration. Overrides are not exported and are useful for environment-specific values like API keys.

The internal, programmatic identifier for a configuration object or field, using lowercase letters and underscores. It is set at creation and is difficult to change later without migration.

A universally unique identifier assigned to configuration and content entities. Configuration synchronization matches objects by UUID, which is why the same site should not be cloned without care.

A core workflow module that assigns editorial states, such as Draft, Review, and Published, to content. Transitions between states are limited by permissions and configured workflows.

A configuration entity in Content Moderation that defines states and allowed transitions for one or more content types. It determines which roles may move content between editorial states.

A saved historical version of a content entity. Revisions let editors compare changes, revert to earlier versions, and keep unpublished drafts alongside the live version.

The practice of moving code and exported configuration from one environment to another, usually followed by a configuration import and cache rebuild. Content is generally not part of a deploy.

A numbered function in a module's install file that alters configuration or data when the module is updated. Update hooks run with the database update command during deployment.