AEM Business Practitioner key terms

A page template created and stored in the repository that lets authors change layout, components, and policies without developer involvement. It separates structure from content and supports inheritance to child pages.

A developer-built template defined in code and configuration files rather than in the authoring interface. It cannot be edited by authors and is typically used for legacy projects or fixed page structures.

A configuration attached to a template or component that controls allowed behavior, such as which components can be placed in a layout container or which image widths are permitted.

A configuration dialog used with static templates and legacy designs to define component-level settings shared across pages. It is largely replaced by policies in editable templates.

A responsive grid component that holds other components and lets authors arrange them into columns and rows. Its allowed content is governed by the template policy.

A layout system that reflows page content across breakpoints such as phone, tablet, and desktop. Authors define column placement per breakpoint so pages adapt to different screen widths.

A mechanism for bundling and delivering CSS and JavaScript assets to pages, organized into categories that templates and components reference. It controls loading order and dependency handling.

A component that inherits from another component and points to it via a resource type property, allowing reuse of logic while overriding dialogs or behavior. It avoids duplicating code across projects.

A set of standardized, extensible components maintained for common page elements like text, image, and teaser. They support accessibility, responsive behavior, and integration with the template editor.

A reusable, self-contained building block that renders a piece of page content and can be configured through a dialog. Authors drag components onto a page to compose the layout.

An authoring form attached to a component that collects configuration values stored as properties on the content node. It defines the fields authors see when editing a component.

A structured, headless content item built from a content fragment model, composed of elements and variations without layout. It can be delivered to channels via APIs or referenced on pages.

A schema that defines the elements, data types, and variations available in content fragments created from it. It enforces consistent structure across many fragments.

A reusable group of components and content that can be used across pages and channels, including external systems. It supports variations for different layouts or audiences.

A named version of an experience fragment that presents the same content differently for a channel, layout, or audience. Authors select which variation to render at the point of use.

A page or tree that stays linked to a source blueprint so content changes can be rolled out. Authors can break inheritance or selectively cancel inheritance on individual properties.

The source configuration in multi-site management that defines content and structure rolled out to live copies. It centralizes maintenance for sites sharing common content.

The process of pushing content changes from a blueprint or source to its live copies. It can run automatically on modification or manually on demand.

Multi Site Manager, the feature set for managing multiple sites that share content through blueprints and live copies. It reduces duplication by centralizing shared pages and assets.

A translated copy of a site tree created for a specific locale, often generated through translation workflows. It may or may not remain linked to the source for updates.

A workflow-driven project that sends selected content to a translation service and imports the translated results. It tracks scope, target languages, and job status.

An automated sequence of steps applied to content, such as review, approval, or asset processing. Steps can be assigned to users or groups and can include automated processes.

The design-time definition of a workflow, describing its steps, transitions, and participants. It is created by administrators and then started as instances against content.

A running execution of a workflow model against a specific payload such as a page or asset. It has a current step, history, and participants who act on it.

The personal area where users see workflow tasks and notifications assigned to them or their groups. From here they complete, delegate, or comment on tasks.

A single unit of work within a workflow instance that requires a participant to act, such as approving content. It appears in the assignee's inbox until completed.

The act of publishing content from the author instance to the publish instance, or removing it via deactivation. It can be triggered manually or by workflow.

The specific replication action that copies content to the publish environment so it becomes publicly available. Deactivation removes it from publish.

A configured connection that defines how and where content is replicated, including the target URL and credentials. Agents can be set to trigger on modification or on demand.

The environment that serves public-facing content to visitors, receiving content through replication. It typically does not allow authoring changes.

The environment where content is created, edited, and approved before publication. It hosts authoring tools, workflows, and the content repository used for editing.

The practice and toolset for storing, organizing, and retrieving media such as images, video, and documents. It covers metadata, renditions, versioning, and controlled access.

A defined set of metadata fields applied to assets, controlling which properties authors see and edit. Schemas can be targeted to folders so different asset types capture different information.

A generated version of an asset, such as a thumbnail, web-optimized image, or video proxy. Renditions are produced by processing profiles and used for display in different contexts.

A configuration that determines which renditions are generated for uploaded assets, such as resized or watermarked images. It is applied to folders and runs during upload.

An automatically assigned keyword generated by analyzing an asset's content with machine learning. Smart tags improve search and discovery without manual keyword entry.

A curated grouping of assets that can be shared with others for review, download, or reuse. Collections can be static or dynamic based on search criteria.

A named set of users that receives permissions collectively, simplifying access management. Assigning rights to groups rather than individuals keeps administration consistent.

A specific right granted on a repository path, such as read, write, or replicate. Permissions combine with group membership to determine what a user can do.

Access Control List, the set of entries that records which users or groups have which permissions on a path. Entries can allow or deny and are evaluated together.

A feature letting an authorized user act as another user to verify their access and experience. It is useful for troubleshooting permissions without sharing passwords.

The practice of showing different content to different audiences based on known attributes or behavior. It relies on audience segments and targeting rules applied to components or pages.

A defined group of visitors who share characteristics, used to decide which personalized content they see. Segments can be built from profile data, context, or behavior.

A component that displays different experiences depending on which audience segment the visitor belongs to. Authors configure the variants and the targeting rules together.

A framework for storing and accessing visitor context data such as location or browsing history in the browser. It supplies the signals used to resolve audience segments.

A coordinated marketing effort that groups related experiences, segments, and offers with defined timing. It helps teams plan and measure targeted outreach in one place.

Within campaigns, a set of content variations shown to a specific audience segment for a period. Experiences are the deliverable units that campaigns organize and schedule.

The hierarchy of pages and folders that organizes a website, defining parent-child relationships and URL paths. A clear structure supports navigation, search, and permission scoping.

The menus and links that help visitors move through a site, often generated automatically from page structure. Authors can configure which pages appear and how deep the menu goes.

The primary content unit in the site tree, built from a template and containing components. Pages have properties such as title, URL, and navigation settings.

A feature for preparing content changes for a future release in a separate copy, then promoting them live at a chosen time. It allows review without affecting the current published site.

The practice of saving snapshots of content or assets so earlier states can be restored or compared. Versions capture who changed what and when.

A sidebar view showing the history of a page or asset, including versions, workflow events, and comments. It lets authors compare or revert to earlier states.

The collection and reporting of visitor behavior data such as page views, traffic sources, and conversions. Teams use it to evaluate content performance and guide improvements.