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
./content/ for the library pages of other blocks. /docs/library/blocks/<block> is the most common location. Put the new page next to them.blocks sheet in the library folder lists the blocks, and the site config at https://da.live/config#/{org}/{site}/ has a library tab that points to it.tools/sidekick/library.html in the repo, and a library workbook with a helix-blocks sheet. The page loader needs no change for a new block.content/drafts/.library-metadata block with a description row that says when to use the block.testimonial (dark)) and becomes a class. Content variants (same markup, different content) get a heading above the block.blocks sheet: name, and path as https://content.da.live/{org}/{site}/{path of the new page}, in the format of the existing rows (the page is in the folder the existing block pages are in).library tab of the site config needs a row (title, path = the sheet's .json URL). It exists already if other blocks show up; check and don't duplicate it. It lives outside the repo./tools/sidekick/blocks/<block>. Each variant is its own section (section break after it).helix-blocks sheet: name, and path relative, as /tools/sidekick/blocks/<block> (no host, so it works on page, live and prod).library metadata takes name, description and searchtags. Default content and auto-blocks need their own section with a library metadata block that has a name./tools/** from indexing with bulk metadata if it is not already.Local ./content/ edits are not visible to authors. Tell the user what remains.
library tab.helix-blocks row in the content source (SharePoint or Google Drive), then previews and publishes both. Follow a project-specific transfer workflow if one exists..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