AEM Sites Business Practitioner Expert key terms

The hierarchical, node-and-property data store where AEM keeps pages, assets, and configuration. Content is organized like a file tree and accessed through the Java Content Repository standard, so structure and metadata live together in one place.

The two building blocks of repository content. A node is like a folder or record that can hold child nodes, while a property stores a single value such as a title or date on that node.

The web framework underneath AEM that maps incoming URLs to repository nodes and resolves which script renders them. It enables content-driven URL resolution, so the same code can serve many pages based on where content lives.

The process of turning a request URL into a specific script or servlet. AEM walks the URL and resource type to find the best-matching rendering script, which explains why component names and folder paths must follow conventions.

A property on a content node that tells AEM which component renders it, usually written as a path to a component. Changing the resource type changes how a piece of content displays without moving the content itself.

A packaged Java module deployed into AEM that provides code such as servlets, services, or schedulers. Bundles can be started and stopped at runtime, and their configuration is managed through the OSGi console rather than code changes.

Runtime settings for AEM services, stored in the repository and editable through a console or config files. These settings control behavior like email servers, workflow timeouts, and replication agents without redeploying code.

The web-based administration interface for managing OSGi bundles and configurations. Practitioners use it to check component status, adjust service settings, and diagnose runtime problems on an AEM instance.

A browser-based tool for browsing and editing the content repository directly. It is useful for inspecting node structure and properties, but direct edits bypass authoring safeguards and are usually reserved for troubleshooting.

The two-tier deployment model where authors create content on an author instance and visitors see approved content on one or more publish instances. Content moves between them through replication, keeping the public site isolated from editing activity.

The mechanism that copies content from author to publish instances. It can be triggered manually by activating a page or automatically by workflows, and its agents and queues are monitored to confirm content reaches the live site.

The author action that publishes a page or asset by sending it through replication to publish instances. Content must be activated before anonymous site visitors can see it, and deactivation reverses the process.

Removing previously published content from publish instances so visitors can no longer see it. It is the counterpart to activation and is often used when retiring pages or pulling incorrect content from the live site.

A configured connection that defines how and where content is replicated, such as from author to a specific publish instance. Agents have queues, and stalled queues are a common cause of content not appearing live.

A caching and security layer placed in front of publish instances. It stores rendered pages and assets to speed delivery, filters suspicious requests, and must be invalidated when content changes so visitors see updates.

Clearing or refreshing cached copies of content on the Dispatcher after a change. AEM typically triggers this automatically during activation, but stale content often indicates a broken or misconfigured invalidation path.

A page-level definition that connects a structure, policies, and allowed components for pages created from it. Editable templates let authors and administrators control layout and styling rules without developer involvement for every change.

A template type whose structure and policies are authored in the browser rather than defined only in code. It supports responsive layouts, per-template component policies, and easier reuse across many pages.

A reusable building block that renders a specific kind of content, such as text, image, or teaser. Components are dragged onto pages in the editor and can be configured through their dialog.

A standard library of flexible, accessible components maintained for AEM projects. They cover common needs like page, text, image, and list, and are often extended or styled rather than rebuilt from scratch.

A project-level component that points to another component, usually a Core Component, so you can customize behavior or policy without editing the original. It keeps upgrades safer because the underlying component stays untouched.

The authoring form attached to a component where editors enter content and settings. Dialog fields map to properties stored on the component's node, so the dialog design determines what authors can control.

A configuration form used by template or administrator roles to set component-wide options, such as allowed image widths or default styles. It differs from the normal dialog, which holds per-instance content entered by authors.

A set of rules attached to a template or component that governs what authors can do, such as which components are allowed or which styles are available. Policies replace older design-mode settings in editable templates.

A responsive grid component that holds other components and controls their placement across screen sizes. Authors use it to build page layouts, and its column behavior is defined by the template's policies.

A organized bundle of CSS and JavaScript that AEM serves to pages, with dependencies and categories controlling load order. Pages include clientlibs by category, so correct categorization affects styling and script behavior site-wide.

The system for storing, organizing, and serving media such as images, videos, and documents. In AEM it includes metadata, renditions, versioning, and permissions so assets can be found and reused across sites.

A defined set of metadata fields applied to assets, controlling which properties appear and how they are edited. Schemas can vary by folder, letting teams capture different information for different asset collections.

A generated version of an asset, such as a thumbnail, web-optimized image, or video preview. Renditions let the same asset be delivered in appropriate sizes and formats without manual rework.

An AEM capability that delivers optimized, responsive media through a delivery service, including smart imaging and interactive viewers. It offloads image processing and adapts assets to device and network conditions.

Automatically applying descriptive tags to assets using machine learning, based on image content or text. It improves search and reuse, though results should be reviewed and can be trained with your own tagged assets.

A reusable group of components and content that can be published as a standalone experience and embedded in multiple pages or channels. It supports variation by channel or audience and reduces duplicated authoring.

Structured, presentation-free content defined by a content model and delivered through APIs or components. It is ideal for reusing the same text and data across web, mobile, and other channels without duplicating entries.

The schema that defines the fields and data types for a type of content fragment. Models let teams standardize structured content so it can be validated, queried, and rendered consistently across channels.

An automated sequence of steps that moves content through review, approval, or processing. Workflows can be started manually or by launchers, and participants act on work items assigned to them.

A rule that starts a workflow automatically when content changes in a specified location or meets a condition. Launchers are common for triggering review or asset processing whenever editors save or upload content.

A single task within a workflow assigned to a user or group. Participants complete work items from their inbox, and an approval step typically pauses the workflow until someone acts on it.

The personal area where users see assigned tasks, approvals, and notifications. Business practitioners use it to review content, take workflow actions, and track what is waiting on them.

A feature for preparing content changes in a parallel copy of a site so they can be reviewed before going live. When ready, the launch is promoted, merging its changes into the published pages.

Keeping historical snapshots of a page or asset as it changes. Versions allow comparison and restoration of earlier content, which helps recover from mistakes or document how a page evolved.

A tool that lets you view a page as it appeared at a past date, using stored versions. It is useful for auditing changes and showing stakeholders how content looked during a campaign or period.

A page or site section linked to a source blueprint so that content can be inherited and rolled out. Live copies support inheritance rules and allow local overrides where needed.

The source structure in Multi Site Manager from which live copies inherit content and configuration. Changes made to a blueprint can be rolled out to connected live copies, keeping multiple sites consistent.

Pushing changes from a blueprint to its live copies. Rollout configurations decide which properties and child pages are synchronized, and conflicts with local edits must be resolved during the process.

Delivering different content to different visitors based on known traits, behavior, or context. In AEM it typically combines audience segments with targeted experiences on a page.

A defined group of visitors who share characteristics, such as location, behavior, or profile data. Segments are used to decide which targeted experience a visitor should receive.

A variant of page content shown only to a matching audience segment. Multiple experiences can be configured for one component, with a default shown when no segment matches.

A framework for storing and managing visitor data in the browser so personalization can react to context. It provides stores and tools for simulating audiences during authoring and testing.

A configured test or targeting campaign in Adobe Target that defines experiences, audiences, and goals. AEM integrates with Target so authors can create and manage activities from within page authoring.

An experiment that shows different variants of content to different visitor groups and measures which performs better. Results guide decisions about layout, copy, or offers based on observed behavior.

A desired visitor action that an experiment or campaign measures, such as a form submission or purchase. Conversion tracking links content decisions to measurable outcomes rather than assumptions.

Connecting AEM content to Adobe Analytics so page views, clicks, and other events are captured in reports. Proper configuration and data layer conventions ensure meaningful, consistent measurement.

How quickly and reliably pages load and respond for visitors, influenced by caching, image size, and code delivery. Practitioners monitor it because slow pages hurt engagement and search visibility.

A rule granting or denying actions such as read, write, or replicate on repository content. Permissions are assigned to users and groups and determine what people can see and change in AEM.

A collection of users that shares permissions and workflow assignments. Managing access through groups rather than individuals keeps administration consistent and easier to audit as staff change.

The set of access control entries attached to a repository path that defines who may perform which actions. ACLs combine with group membership to produce a user's effective permissions.

A feature that lets an authorized user act as another account to troubleshoot what that person sees or can do. It is useful for diagnosing permission issues but should be used carefully and logged.

The AEM capability for managing multiple related sites that share content through inheritance. It reduces duplication across locales or brands while allowing controlled local variations.