AEM Sites Developer Expert key terms

The process by which Sling maps an incoming URL path to a resource in the JCR repository, then finds the script or servlet that renders it. Resolution walks up the resource tree when no matching script exists.

A property (sling:resourceType) on a content node that names the component responsible for rendering it. It decouples stored content from the code that displays it, allowing components to be swapped or extended.

A hierarchy declared with sling:resourceSuperType that lets one component inherit scripts, dialogs, and behavior from another. Sling falls back to the super type when the child has no matching script.

A component that extends a core or shared component via sling:resourceSuperType without copying its code. It is the recommended pattern for reusing functionality while customizing dialogs and markup.

Adobe-maintained, extensible components (page, text, image, teaser, and others) distributed separately from the product. They are designed to be proxied and styled rather than edited in place.

A Java class annotated with @Model that adapts a resource or request into a POJO for use in HTL. It exposes data through getters and can inject properties, child resources, and OSGi services.

A map-like interface exposing a resource's properties with type conversion. Sling Models inject values from it, and it lets Java code read multivalued or typed properties without touching the underlying node directly.

A Sling Models feature that serializes an annotated model to JSON for consumption by JavaScript or external systems. It supports Jackson and Gson exporters and is the basis for content services output.

HTML Template Language, a server-side templating syntax that is strictly limited in logic. It enforces context-aware escaping and safe expression evaluation, replacing JSP in modern AEM development.

An HTL attribute that instantiates a Sling Model or helper object and binds it to a variable for the rest of the template. It is the primary bridge between markup and Java logic.

An HTL attribute that includes the rendering of another resource, optionally overriding its resource type or selectors. It is used to compose pages from nested components.

A folder (cq:ClientLibraryFolder) under /etc or /apps that bundles CSS and JavaScript with categories. Pages include libraries by category, and the system merges and minifies them in production.

A template stored in the repository that authors can edit and that holds a structure, initial content, and policies. It enables layout changes and component restrictions without developer involvement.

A template defined in code under /apps with fixed structure and no author editing. It cannot be modified at runtime and is largely replaced by editable templates in modern projects.

A configuration that controls which component can be used as a page template and which policies apply. It determines whether a template is editable and what it is allowed to contain.

A configuration attached to a template or component that defines allowed components, design properties, and behavior. Policies replace the older design mode and are stored in the template's policy mapping.

A responsive grid container that holds components on a page and lets authors drag, resize, and reorder them. It reads column settings and breakpoints from the template's policy.

The node holding a component's edit dialog definition, usually built from Granite UI fields. Authors use it to set properties that are stored on the component's content node.

The touch-enabled UI framework whose widgets (text field, path field, multifield) compose AEM dialogs. Fields are declared as nodes with a resource type and name that maps to a stored property.

A dialog stored on the component but edited through the template's policy, holding design-time settings shared across all instances. Values are read from the policy rather than the content node.

A structured, schema-driven content asset stored independently of pages and reusable across channels. Its model defines fields, and it can be delivered as JSON through the content services layer.

A reusable group of components with its own layout that can be exported as HTML for other channels or included in pages as a variation. It supports variations for different contexts.

An automated process defined as a model of steps and transitions, launched on content to perform review, approval, or asset processing. Instances track state and can include participant and process steps.

A configuration that starts a workflow automatically when content changes in a watched path, matching conditions such as node type or property. It is the usual trigger for approval and activation flows.

The mechanism that copies content from author to publish instances, either on demand or via agents. It includes agents, queues, and the activation actions available to authors.

A configured transport that sends activation or deactivation requests to a publish instance or another endpoint. It defines the URL, credentials, and serialization used for the transfer.

An activation action that publishes a page together with its child pages in one operation. It is useful for launching a section but can be slow and is often replaced by bulk or scheduled activation.

A caching and security layer placed in front of publish instances that serves static and cached responses and filters requests. It reduces load and enforces access rules defined in its configuration.

A replication agent that tells the Dispatcher to invalidate cached pages when content is activated or deactivated. It targets the dispatcher flush endpoint with the affected paths.

Time to live, the duration a Dispatcher keeps a cached response before considering it stale. It balances freshness against origin load and is configured per cache rule.

AEM's framework for sharing structure and content across language or brand sites using blueprints and live copies. It supports inheritance, rollout, and controlled overrides.

A site or page tree linked to a source blueprint so that changes can be rolled out to it. It maintains inheritance relationships and allows local modifications where configured.

The action of pushing changes from a blueprint to its live copies, applying synchronization rules for each property. It can be triggered manually or by configured triggers.

A translation of a site's content into another language, created manually or through a translation workflow. It may be a plain copy or a live copy depending on whether ongoing sync is needed.

A container that groups content pages for translation and tracks their progress through a translation service. It holds language copies, jobs, and the workflow that moves content to and from the provider.

Access control list, the set of permissions granted or denied to users and groups on a repository path. It is evaluated to decide whether a principal may read, write, or replicate content.

A specific right such as read, modify, create, delete, or replicate that can be granted or denied. Permissions combine with path scope and principal to form an access control entry.

A collection of users that shares permissions and roles, simplifying administration. Effective access is the union of group memberships, with deny entries taking precedence.

A publish-side feature that restricts access to a site section so only authenticated members of a specified group can view it. It is configured on the page and enforced at request time.