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.
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+, AEM 6.4.x+
For AEM as a Cloud Service SDK:
$ cd aem-guides-wknd/
$ mvn clean install -PautoInstallSinglePackage
For AEM 6.4.x and 6.5.x:
$ cd aem-guides-wknd/
$ mvn clean install -PautoInstallSinglePackage -Pclassic
| AEM as a Cloud Service | AEM 6.5 | AEM 6.4 | Java SE | Maven |
|---|---|---|---|---|
| Continual | 6.5.7.0+ | 6.4.8.4+ | 8, 11 | 3.3.9+ |
Setup your local development environment for AEM as a Cloud Service SDK or for older versions of AEM.
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"/>- This project was generated using the AEM Project Archetype.
- This project relies on AEM Core Components.