Adobe Commerce Front-End Dev Expert key terms

An XML file that declares which blocks and containers appear on a page, their parent-child nesting, and which templates they render. Magento merges these files from all modules and the active theme.

A structural layout element that holds child blocks but renders no output of its own. Containers position content, such as header or content, and are addressed by name in layout XML.

A PHP class that supplies data and rendering logic to a template. Blocks are declared in layout XML, can have child blocks, and are cached as part of the page.

A layout XML file or handle that adds, removes, or reconfigures blocks for a specific page type, such as catalog_product_view or checkout_cart_index. Handles are merged in a defined order.

A named identifier, like default or cms_index_index, that groups layout instructions. Magento collects handles for the current request and merges their XML into the final layout.

A PHTML file containing the HTML markup and PHP output for a block. Templates live in a module's view directory and can be overridden per theme.

A class passed to a template through the block's arguments to provide presentation data and helper methods. It keeps templates free of business logic and is a preferred alternative to block methods.

A key-value entry in layout XML passed to a block's constructor, often used to inject a ViewModel or configuration value. Arguments are read from the block's data array.

Replacing a module's PHTML file by placing a file of the same relative path in a theme. Magento resolves templates by theme fallback, so the theme copy wins over the module original.

Applying methods such as escapeHtml or escapeUrl to dynamic values before printing them in a template. It prevents cross-site scripting by encoding characters that could break out of HTML context.

The fallback chain in which a theme declares a parent theme, so files missing in the child are loaded from the parent, then from modules. It enables layered customization without copying every file.

The theme's configuration file declaring its title, parent theme, and optional media or favicon settings. It sits at the theme root and drives inheritance and admin listing.

A JavaScript library using observables and declarative data-bind attributes to keep UI in sync with a view model. Magento uses it heavily for cart, checkout, and customer data rendering.

A Knockout function wrapping a value; reading it returns the value and writing to it notifies subscribers. Observables drive automatic DOM updates when data changes.

A Knockout observable whose value is derived from other observables and recalculated automatically when dependencies change. Useful for totals, labels, and conditional display logic.

A callback registered on an observable that fires whenever its value changes. In Magento it is often used to react to cart or customer data updates and trigger side effects.

The Knockout call that binds a view model to a DOM subtree, activating data-bind attributes. Magento invokes it per component scope rather than once for the whole page.

A reusable JavaScript and XML-configured widget, defined in ui_component XML, that renders grids, forms, and checkout steps. Components bind to Knockout templates and load via RequireJS.

An asynchronous module loader used by Magento to declare and resolve JavaScript dependencies. Modules are configured in requirejs-config.js and loaded on demand by path alias.

A module that wraps another module to extend or override its behavior without editing the original. Mixins are registered in requirejs-config.js under the config mixins key.

A Magento module that exposes private customer data, such as cart totals and messages, to JavaScript via a localStorage-backed registry. Sections are declared in sections.xml and fetched from the server.

A named group of customer data, declared in a module's sections.xml, that is loaded into the browser and refreshed after actions like adding to cart. Invalidated sections trigger a reload.

A CSS preprocessor Magento compiles server-side into CSS. Themes use variables, mixins, and nesting in .less files, with a _module.less file per module for overrides.

Custom properties, such as --color-primary, declared in a theme's _variables.less or CSS and consumed across styles. Blank and Luma themes expose many design tokens this way.

Any file served directly to the browser, such as CSS, JavaScript, images, or fonts, stored under a module's or theme's web directory. Assets are deployed and versioned for caching.

The bin/magento setup:static-content:deploy command that copies and compiles theme assets into pub/static for each locale and theme. It is required in production mode.

A Magento deployment mode in which static files are pre-generated, errors are not displayed, and code is not compiled on the fly. It requires running static content deploy and DI compilation.

A caching layer that stores fully rendered HTML for anonymous visitors and serves it without booting the application. It is pluggable and configured per cache type.

A named cache bucket, such as layout, block_html, or full_page, that can be enabled or disabled independently. Each type is declared in a module's cache.xml.

Marking cached entries stale when underlying data changes, for example after a product save. Magento uses cache tags and identities to invalidate only affected entries.

An identifier attached to a cache entry grouping it with related entries, such as a product ID. Invalidating a tag clears every entry carrying it.

Dynamic, customer-specific page fragments that full page cache cannot store for anonymous users. They are loaded after page load via customer data sections or AJAX.

The server-side model representing a shopping cart before an order is placed. It holds items, totals, addresses, and payment selections, and is converted into an order at checkout.

A line in the quote representing a product with quantity, options, and price. Adding or updating items triggers totals recalculation and customer data refresh.

A class that contributes a line, such as shipping or tax, to the quote totals. Collectors are declared in sales.xml and run in sequence during totals calculation.

A stage in the checkout flow, such as shipping or payment, rendered by a UI component. Steps are defined in checkout_index_index.xml and navigated in sequence.

A carrier option presented to the customer during checkout, backed by a carrier model and rate. Selecting one updates quote totals and can affect available payment methods.