Acquia Site Builder D10 flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Content entity vs config entity

Content entities hold user-created data in database tables; config entities hold site structure as exportable YAML configuration. Nodes are content; content types are config.

Bundle

A bundle is a subtype of a content entity, such as a content type for nodes or a vocabulary for taxonomy terms. Fields and displays are attached per bundle.

Field storage vs field instance

Field storage defines the shared database column and field type; the field instance attaches that storage to a specific bundle with its own label, widget, and required setting.

Cardinality

Cardinality sets how many values a field accepts. A value of one means single-value; -1 means unlimited; higher integers cap the number of allowed values.

View mode

A view mode is a named set of field formatter settings used to render an entity, such as Teaser or Full. Layout Builder and templates can target specific view modes.

Form display

A form display configures which widgets appear on an entity edit form, their order, and their widget settings for a given bundle and form mode.

Text format

A text format combines enabled filters, such as converting line breaks or limiting allowed HTML, with permissions controlling which roles may select it.

Entity reference field

An entity reference field stores IDs of other entities, such as taxonomy terms or users. Entity reference revisions additionally stores a specific revision ID.

Layout Builder

Layout Builder lets editors compose entity or bundle displays from blocks arranged in sections and responsive grid columns, storing overrides separately from default config.

Block layout

Block layout places blocks into theme regions for all pages of a theme. It is theme-level configuration, unlike Layout Builder, which is entity-level.

Paragraphs

Paragraphs is a contributed module providing a bundleable entity for reusable content components referenced from nodes, often rendered through Layout Builder or view modes.

Taxonomy vocabulary

A vocabulary is a bundle of the taxonomy term entity. Terms form hierarchical or flat lists used for categorization and exposed as entity reference targets.

Media type

A media type is a bundle of the media entity defining source plugin, such as image or file, plus fields and display settings for reusable media items.

Responsive image style

A responsive image style maps breakpoints to image styles and fallback images, letting formatters output srcset and sizes attributes for adaptive delivery.

Content moderation

Core workflow module assigning editorial states, such as Draft and Published, to content; transitions are permission-gated and revisions track each state change.

Configuration dependency

Config entities declare dependencies on modules, themes, and other config. Missing dependencies prevent deletion and cause import errors until resolved.

Sync directory

The filesystem path set by $settings['config_sync_directory'] where exported YAML config lives and from which imports read. It must be writable for export.

drush config:export

Command that writes active configuration to the sync directory as YAML files, one per config object, including UUIDs and dependency metadata.

drush config:import

Command that applies YAML from the sync directory to active config, creating, updating, and deleting config so active state matches the files.

drush config:status

Command listing config objects that differ between active storage and the sync directory, showing only-in-active, only-in-sync, and changed states.

Config UUID matching

Each exported config object carries a UUID. Importing files from a different site with mismatched UUIDs causes errors unless the UUIDs are reconciled first.

Config override

Values set in $config within settings.php override active configuration at runtime. Overrides are environment-specific and are never written by config export.

Config split

Contributed module that excludes or splits selected configuration per environment, keeping development-only config out of production exports.

Configuration entity deletion

Removing a config entity in the UI deletes it from active config only. A later import restores it if its YAML remains in the sync directory.

Content staging

Moving content between environments uses database sync, the Migrate API, or default-content tooling, because content is not part of configuration export.

drush sql:sync

Command that copies a database between aliased environments, commonly used to pull production content down to local or to push content upward.

Migrate API

Core module set that imports content and config from source plugins into Drupal using migration YAML, process plugins, and destination plugins.

Default content

Contributed module that ships content entities inside a module or profile, exporting and importing them as structured files alongside configuration.

Config import validation

Before applying changes, import validates schema and dependencies. Failures abort the import and leave active configuration unchanged.

Single config import

The Synchronize configuration UI and drush config:import support importing a single named config object, useful for targeted fixes without a full sync.

Settings.php overrides

The $config array in settings.php sets runtime config values, such as system performance caching, that differ per environment without altering exported YAML.

Config ignore

Contributed module that excludes specified config objects from export and import, useful for config that changes constantly, such as contact form recipients.