Experience League site implementation on https://aem.live
- Preview: https://main--exlm--adobe-experience-league.hlx.page/
- Live: https://main--exlm--adobe-experience-league.hlx.live/
ensure you have nodejs 22. do this manually or install nvm and run
nvm install
thennvm use
on this directory and node 22 will be installed and used.
- Clone or fork this repo (see note below on forking)
- Create your brannch - (keep it < 18 chars to avoid domain length limits)
- Install the AEM CLI:
npm install -g @adobe/aem-cli
- Install dependencies
npm i
- Start Local Proxy:
npm run up
(opens your browser athttp://localhost:3000
) - Start coding!
If you want/need to fork this repository remember to add the AEM Code Sync GitHub App to the fork repository. Also please be sure to name the repo exlm
for consistency.
The default content source is set in fstab.yaml
, by default it's pointing to the main exlm-converter action.
The action is the entry point for all HTML delivered to https://aem.live services.
while developing, and if you need to update the source HTML, you are free to deploy exlm-converter action to your own project on Adobe Runtime. (Remember to point your forked repon
fstab.yaml
to your own action).
Command | Usage |
---|---|
npm run up |
Runs aem up |
npm run quality |
Code quality check: format and linting |
npm run format |
Format code |
npm run lint |
Run JS/CSS linters |
Use this only if you need sign-in to work locally for development purposes.
- add this entry to
hosts
file (/etc/hosts
on mac)127.0.0.1 experienceleague-local.adobe.com
(you likely will needsudo
to save this file) - run
npm run up-secure
(instead ofnpm run up
)you can use
npm run up-secure-prod
if you want to use production content. - Browser should automatically open at
https://experienceleague-local.adobe.com
if asked to trust the certificate on the browser, do trust it. Might also need to allow runnig as admin (
sudo
)
If you have a Windows machine, please add any learnings to this Doc. The current dev team uses MacOs.