Overview
Experience League is Adobe’s learning and community destination: courses, tutorials, documentation, certification paths, and community content for Experience Cloud and related products. The public site is implemented as an Edge Delivery Services (EDS) project—content-forward, Git-backed front-end code running on Adobe’s AEM Edge Delivery platform (documented on aem.live).
The open-source implementation lives in the exlm repository (“Experience League Modernization”). Authors and pipelines produce HTML that flows through a converter and configuration; the repo supplies blocks, scripts, styles, and routing metadata that shape what visitors see at experienceleague.adobe.com.
Platform: Edge Delivery Services
EDS (described in Adobe’s AEM Edge Delivery documentation) treats familiar documents and structured sources as the starting point for fast, static-friendly pages. Teams pair a content source (for example a converter or upstream HTML pipeline) with a GitHub project that defines presentation: block scripts, shared styles, icons, and build-time configuration such as fstab.yaml (mounting the content root), paths.yaml / paths.json, and Helix-oriented files like helix-query.yaml and helix-sitemap.yaml for indexing and discovery.
That split keeps authoring workflows separate from front-end engineering while still allowing preview URLs, branch previews, and rapid iteration—patterns highlighted across aem.live for performance, preview fidelity, and developer experience.
Architecture
The diagram below is a simplified view of how Experience League fits the EDS model: upstream content is combined with the exlm codebase, then served through Adobe’s edge stack to browsers.
Engineering notes
The exlm tree follows common EDS conventions: blocks map authored sections to JavaScript and CSS; scripts hold shared logic; styles and fonts centralize design tokens and typography. JSON alongside the repo (component-definition.json, component-models.json, component-filters.json) describes authoring surfaces for the CMS side of the stack.
Quality tooling in the project (linting, formatting, path validation) keeps a large surface area consistent—important when many contributors touch blocks and content-driven layouts. Releases and contribution expectations are documented in the repository’s README and CONTRIBUTING.md.
Features
Production Experience League delivers personalized learning entry points, curated paths, community hooks, certification messaging, and event promotion—wrapped in a fast, componentized front-end.
From a developer standpoint, the stack emphasizes plain HTML, CSS, and JavaScript at the edge (as described on aem.live), Git-based workflows, branch previews, and integration with Adobe’s delivery pipeline rather than a monolithic SPA framework for the document shell.
Links
Live Experience League site — end-user learning and community hub.
adobe-experience-league/exlm on GitHub — site implementation source (Apache-2.0).
Adobe Experience Manager — Edge Delivery documentation — EDS concepts, authoring, build, publish, and operations.
The repo README lists preview and live Helix-style URLs for the main branch (for example main--exlm--adobe-experience-league.hlx.page and .hlx.live) for comparing staged output against production.