Skills for building AEM Edge Delivery Services sites — site creation, block development, content modeling, code review, testing, and page import.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Local tooling for AEM Edge Delivery Services: aem up (dev server), aem content (da.live
content sync), aem import (importer UI). Needs Node 18+.
Check the version before relying on ./content/ or aem content, or when a content
operation returns 403: compare aem --version with npm view @adobe/aem-cli version;
upgrade with npm install -g @adobe/aem-cli@latest. aem content and ./content/
serving need 16.18+, explicit IMS login 16.22.3+, worktree port handling 16.22.12+.
For persistent 403s, invalidate the active project/environment’s cached token and
retry with the intended IMS org before assuming DA permissions need changing.
aem upaem up --no-open --no-stop-otheraem up picks a port from the branch
name and logs Git worktree detected. Using port N. Always use the port it logs.aem up stops it, even another checkout's.
--no-stop-other exits with Port N already in use instead: reuse that server if it is
this checkout's, otherwise pass --port <free port>.aem up serves ./content/ before proxying, with no flag:
content/drafts/x.html is at /drafts/x (and /drafts/x.plain.html). The file is a full
document (<body><header></header><main>…</main><footer></footer></body>). Use
--html-folder <dir> only for HTML outside ./content/, such as import output.
Local pages are not indexed: /query-index.json is proxied from the remote site unless
content/query-index.json exists, so find local pages on disk in ./content/.--url https://main--<site>--<org>.aem.page (e.g. stage)..env: every flag has an AEM_ variable read from the project's .env: AEM_PORT,
AEM_PAGES_URL, AEM_TLS_CERT, AEM_TLS_KEY, AEM_NO_OPEN=true (not AEM_OPEN=false).--tls-cert <crt> --tls-key <key> (mkcert or openssl).aem content (da.live)Clone da.live pages to preview, inspect or edit them locally; aem up serves them from
./content/:
aem content clone --path /drafts # or --all; browser sign-in; writes ./content/To send edits or new pages back:
aem content add drafts/page.html # paths relative to ./content/
aem content commit -m "Add test page"
aem content pushclone fails if ./content/ exists (--force deletes it). Clone first, then add pages;
move existing local pages aside and copy them back in.--org / --site.admin.da.live only (AEM_DA_ADMIN overrides the host, 16.22.18). A site whose content is in Source Bus (api.aem.live) cannot be cloned or pushed this way; use the API in da-content..hlx/.da-token.json (git-ignored). Don't ask for a token by hand.push writes the DA source only. Preview the page (Sidekick, or
POST https://admin.hlx.page/preview/<org>/<site>/main/<path> with an IMS
Bearer token, see da-auth) before https://main--<site>--<org>.aem.page/<path>
shows it.aem content push can report success without storing media files (PNG/SVG
verified on 16.22.16). Upload them with a DA Source API PUT using multipart
field data; see da-content.aem importaem import --no-open serves the importer UI on port 3001. For writing import.js use
page-import.
| Symptom | Fix |
|---|---|
Unknown argument: content | CLI too old; upgrade |
| Local page 404s | Put it under ./content/ (or --html-folder for other dirs) |
| Live page 404s locally | Wrong origin: --url https://main--<site>--<org>.aem.page |
Pushed page not on .aem.page | Preview it (see above) |
.tessl-plugin
skills
aem-block-library
aem-cli
aem-layout-view
block-collection-and-party
brand-setup
references
building-blocks
code-review
content-driven-development
references
content-modeling
create-site
da-auth
figma-to-content
find-test-content
generate-import-html
identify-page-structure
migrate-header
page-decomposition
page-import
preview-import
scrape-webpage
slicc-handoff
snowflake
assets
substrate
substrate-milo
examples
knowledge
scripts
testing-blocks
ue-component-model