Important
You need Java™ 21 and Maven 3.9.4+ to build the main branch of this project.
WKND versions are compatible with the following versions of Adobe Experience Manager:
| AEM version | WKND version |
|---|---|
| AEM as a Cloud Service (2025.6.21193.20250609T124356Z) & AEM 6.5 LTS | 4.x |
| AEM as a Cloud Service | 3.x |
| 6.5 SP17 | 2.x, 3.x |
This is a sample Adobe Experience Manager project for a full stack Sites implementation for a fictitious lifestyle brand, WKND.
View the live demo at https://www.wknd.site/
A corresponding tutorial is available where you can learn how to implement a website using the latest standards and technologies in AEM Sites.
To deploy WKND to AEM as a Cloud Service, this project's source code must be deployed to AEM via Cloud Manager.
- Clone this Git repository
- Push the
mainbranch to your Cloud Manager's Git repository - Ensure a deployment pipline is configured to deploy the target branch/repo to the desired AEM as a Cloud Service env
- Run the Cloud Manager pipeline
- WKND will now be deployed to the target AEM as a Cloud Service environment
Pre-compiled AEM packages are available under the latest release for easy installation on local environments using CRX Package Manager
aem-guides-wknd.all-x.x.x.zip: AEM as a Cloud Service, default buildaem-guides-wknd.all-x.x.x-classic.zip: AEM 6.5.x+
For AEM as a Cloud Service SDK:
$ cd aem-guides-wknd/
$ mvn clean install -PautoInstallSinglePackage
For AEM 6.5.x:
$ cd aem-guides-wknd/
$ mvn clean install -PautoInstallSinglePackage -Pclassic
| WKND Version | AEM as a Cloud Service | AEM 6.5 | Java SE | Maven |
|---|---|---|---|---|
| Latest (main branch) | Continual | 6.5 LTS | 21 | 3.9.4+ |
| v3.2.0 | Lowe than 2025.5.21005.20250522T173058Z | Lower than 6.5.23 | 8, 11 | 3.3.9+ |
| v1.1.0 | Continual | 6.5.10+ | 8, 11 | 3.3.9+ |
| v1.0.0 | Continual | 6.5.4+ | 8, 11 | 3.3.9+ |
Setup your local development environment for AEM as a Cloud Service SDK or for older versions of AEM.
Pages that use Content AI Search V1 now expose header search through a single
accessible magnifying-glass icon (cmp-button--header-search) that links to the
central Content AI Search page, instead of a duplicate inline search field. The
duplicate auto-generated navigation entry for the central search page is hidden
so it isn't listed twice.
On desktop, the header layout groups the navigation links and the 48px search icon together instead of reserving two full grid columns for the icon, closing the large gap that previously appeared between the nav links and the search control. Existing mobile/tablet layouts, and headers that don't use this component, are unchanged.
The Cypress publicsite spec covers desktop/mobile icon navigation, the V1
AI-summary checkbox toggle, and an end-to-end search against the real Content
AI endpoint (asserting non-empty results and an AI answer with source hits).
By default, sample content from ui.content.sample will be deployed and installed along with the WKND code base. The WKND reference site is used for demo and training purposes and having a pre-built, fully authored site is useful. However, the behavior of including a full reference site (pages, images, etc...) in source control is unusual and is not recommended for a real-world implementation.
Including ui.content.sample will overwrite any authored content during each build. If you wish to disable this behavior modify the filter.xml file and update the mode=merge attribute to avoid overwriting the paths.
- <filter root="/content/wknd" />
+ <filter root="/content/wknd" mode="merge"/>The default all package continues to embed ui.apps, core, ui.content,
ui.config, ui.content.sample, and the shared WKND content package, exactly
as before. For environments with authored content you don't want a deployment
to overwrite (for example, a shared development environment), build with the
codeOnly Maven profile to produce an all package that embeds only ui.apps,
core, and ui.config:
mvn -PcodeOnly clean install
Use this profile deliberately; it is not active by default and should not be used for the initial/full installation of this project.
Many of the images in the WKND Reference website are from Adobe Stock and are Third Party Material as defined in the Demo Asset Additional Terms at https://www.adobe.com/legal/terms.html. If you want to use an Adobe Stock image for other purposes beyond viewing this demo website, such as featuring it on a website, or in marketing materials, you can purchase a license on Adobe Stock.
With Adobe Stock, you have access to more than 140 million high-quality, royalty-free images including photos, graphics, videos and templates to jumpstart your creative projects.
- This project was generated using the AEM Project Archetype.
- This project relies on AEM Core Components.