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
Layout view runs the site's own loadPage() and block code on the page, then makes elements editable. Read the current rules and examples at https://www.aem.live/docs/ew/developing/layout-view. The points agents miss:
head.html loads /scripts/scripts.js, and scripts.js defines a top-level loadPage, as in the boilerplate.https://{BRANCH}--{SITE}--{ORG}.preview.da.live. This is not fixable in the repo: tell the user whose host to change.data-prose-index (text) or data-image-index and data-image-version (img) onto the replacement.>, +, ~, :first-child or :nth-child on those elements. While an author types they sit in extra divs. Use descendant selectors or a class on the cell.block.isConnected is false. In scripts.js (loadEager, loadLazy), guard what is added to document, window or head so it is added only once. Auto-blocking checks for an existing block before it adds one.main. Try a branch with the developer plugin (https://www.aem.live/docs/ew/developing/developer-plugin), then type into each text field, replace each image and move the block..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