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
Do NOT use for: importing or migrating pages (page-import), applying a brand to a fresh project (brand-setup), or blocks on an existing site (content-driven-development).
gh authenticated (gh auth status) or a token with repo scope.Ask for the GitHub org ({{ORG}}), repository name ({{REPO}}, also the site name), and a display name ({{SITE_NAME}}, derived from the repo name if not given). Ask which content store ({{STORE}}) the site uses, DA or Source Bus; do not guess. Org, repo and branch cannot contain --, and main--{{REPO}}--{{ORG}} must stay within 63 characters.
If the user already made a repository from the boilerplate, confirm which one and go to Step 3.
Tell the user:
- Open https://github.com/apps/aem-code-sync/installations/new
- Choose Only select repositories, select {{ORG}}/{{REPO}}, and save.
- In the setup wizard on tools.aem.live that follows, choose the content source: {{STORE}}. (If the wizard is skipped, a script can set it in Step 4.)
Reply "done" when complete.
Wait for confirmation. Then check, without credentials, that the site exists: curl -s -o /dev/null -w '%{http_code}' https://admin.hlx.page/ping/{{ORG}}/{{REPO}} returns 200 (404 means not set up). Do not use /status/ for this: it returns 401 without a token.
A site's store is content.source in its site config; fstab.yaml is deprecated and ignored once the config service holds the site. Read the config with the IMS token from da-auth (GET https://admin.hlx.page/config/{{ORG}}/sites/{{REPO}}.json):
| Store | content.source |
|---|---|
| DA | {"type": "markup", "url": "https://content.da.live/{{ORG}}/{{REPO}}"} |
| Source Bus | {"type": "sourcebus"} |
To change it (admin or site config permission needed): POST https://admin.hlx.page/config/{{ORG}}/sites/{{REPO}}/content.json (Update Content Location). Send back the full content object you read, with only source changed ({"type": "sourcebus"}, or the DA values above to go back). A changed store gets a new Content Bus ID: nothing previewed or published before is carried over, and index and sitemap config must be recreated. How content moves between stores is not documented: assume it does not move and copy it by hand. Switch before seeding content, not after.
Get a token with da-auth for the chosen API. Create nav, footer and index pages with da-content, which has the write call and HTML rules for each store (DA and Source Bus differ). The homepage needs an <h1>.
aem content only talks to DA: for a Source Bus site write pages through the API.
Preview each page (/nav, /footer, /) with the preview call for the store; see da-content. Expect 200 or 201, then open the site's .aem.page preview.
Hand the user the preview URL, the repo URL and the editing links for the store, and offer next steps: more pages, brand-setup, content-driven-development.
| Symptom | Fix |
|---|---|
| Step 3 ping returns 404 | Code Sync not installed on this repo; resend the link |
| Preview is 404 right after setup | Nothing previewed yet; run Step 6 |
| 401 or 403 on content calls | See da-auth; check the API matches the store |
| Content calls find nothing in a site that has content | Wrong store; read content.source (Step 4) |
.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