Acquia Site Studio Site Builder flashcards

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

What is a Site Studio component

A reusable UI building block defined once with an element tree and properties, then placed many times in templates or other components; edits to its definition propagate to all instances.

Site Studio template definition

A page-level layout that defines regions and assigns them to content types or paths, controlling how matched pages are structured and rendered.

Site Studio style guide role

A centralized store of design tokens such as colors, typography, and spacing that components and elements reference, avoiding hard-coded style values across the site.

Site Studio package export

A bundle of Site Studio configuration (components, templates, style guides) exported from one environment and imported into another to promote changes between sites.

Why rebuild Site Studio assets

Site Studio compiles CSS and JS from component and style definitions; the compiled output must be rebuilt before front-end changes reflect the latest configuration.

Global breakpoint configuration

Responsive breakpoints are defined once in Site Studio settings and drive the per-breakpoint style options available on every element and component site-wide.

In-place layout editing

A Site Studio authoring mode where users edit page layouts and component field values directly on the rendered page rather than through separate admin forms.

Site Studio config storage

Components, templates, and style guides are Drupal config entities, so they can be exported, version-controlled, and deployed through standard configuration management.

Element tree in components

The nested structure of elements (containers, text, images, links) that defines a component's markup; each element carries its own configurable properties and styles.

Exposed component properties

Element properties flagged as exposed become editable fields for content authors, while unexposed properties stay fixed by the component builder and cannot be changed in layouts.

Component slots and nesting

Regions inside a component that accept other components, allowing complex layouts to be composed by nesting smaller components within a parent component.

Editing a shared component

Because all instances share one definition, editing the component updates every placement; per-instance field values remain independent of the definition change.

Duplicating a component

Copying a component creates a separate definition that retains the original element structure and styling but diverges independently on later edits.

Deleting a component in use

Removing a component that is placed in templates or other components breaks every layout referencing it, so usage must be checked before deletion.

Content-driven component fields

Component fields can be mapped to Drupal entity fields, letting a component placed in a template render node-specific values at request time.

Standard versus layout component

Standard components are placed into template regions as content blocks; layout or template components define page structure and are assigned to pages.

Component field defaults

Each exposed field can carry a default value used when an instance has no override, keeping new placements rendering sensibly before authors edit them.

Template region purpose

Regions are named areas within a template that hold components; the template's element tree determines the markup wrapping each region.

Template assignment rules

Templates are matched to pages by content type or path, with a default fallback template applying when no more specific assignment matches the request.

Content template behavior

A content template renders the node's fields inside its designated content region, replacing Drupal's default field rendering for that content type.

Master template reuse

A base or master template supplies shared header and footer components so multiple page templates inherit them without duplicating those components in each template.

Template change blast radius

Editing a template affects every page assigned to it; page-specific differences require a separate template or per-instance component values.

Layout canvas reordering

In the layout canvas, builders drag components into regions and reorder them; nesting depth is constrained by which components expose slots.

Template preview context

Previewing a template renders it with selected sample or existing content, so the result depends on the content context chosen for the preview.

Default fallback template

The template applied when no content-type or path assignment matches, ensuring every page receives a layout rather than unstyled default output.

Per-breakpoint element styles

Each element stores style values per breakpoint; base styles apply at all widths and breakpoint-specific values override them at and below that width.

Custom CSS scoping

CSS added at the style guide level affects every page using that guide, while component-level CSS is limited to that component's output.

Design tokens in style guide

Named values for colors, fonts, and spacing stored in the style guide; elements reference tokens so a single change updates all dependent styles.

Theme and Site Studio layering

A Drupal theme supplies base templates and CSS, and Site Studio output is layered over it, so theme changes can affect Site Studio-rendered pages.

Site Studio permissions

Access is permission-based, with distinct permissions for administering Site Studio, building layouts and components, and editing content, assigned through Drupal roles.

Promoting style changes

Style guide and component changes move between environments through package export/import or configuration sync, not by manually recreating settings.

Compiled asset regeneration

Because Site Studio generates CSS and JS from definitions, regenerating compiled assets is required after style or component edits for the front end to update.