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
In AEM-authoring projects (aem-boilerplate-xwalk) authors fill properties-panel fields instead of a table. AEM renders those properties as the same table structure that document authors would type, so one block serves both. The structure therefore comes from content-modeling; this skill maps it to fields and registers the block. Skip it for document-based projects.
decorate().filter, each item has its own model, one row per item and one column per property.blocks/<name>/_<name>.json with definitions, models and filters. Register it where authors can add it, or they cannot: a block id goes into the section filter in models/_section.json; a custom section type (for example a tab panel) goes into the main filter in models/_component-filters.json. Then run npm run build:json: it regenerates the root component-definition.json, component-models.json and component-filters.json, which you never edit by hand (the pre-commit hook also runs it).template.model or filter to the model or filter id), JSON is valid, and decorate() keeps data-aue-* instrumentation when it moves elements (moveInstrumentation(), defined in scripts/scripts.js of aem-boilerplate-xwalk).The fields produce the same table a document author would type, so content-modeling's rules still apply to it (default content in cells, limited columns, no key/value for content, no nested blocks). The rules below are only the Universal Editor specifics.
core/franklin/components/block/v1/block and a template name; without either the block renders nothing. Do not write custom AEM components. Default content (text, title, image, button) already has components.image + imageAlt become one picture; link + linkText, linkTitle, linkType one link (type primary or secondary adds strong or em); title + titleType one heading. Suffixes are case sensitive: Title, Type, MimeType, Alt, Text.<group>_ (teaserText_title, teaserText_cta1): authors get separate fields, the block gets one cell of semantic elements.classes property (select or multiselect) becomes the options in the block header. classes_<name> fields extend it; a boolean classes_ field adds its name when on. Prefer options to key/value rows.core/franklin/components/section/v1/section) that client-side auto-blocking combines into one block, not as blocks authored inside blocks. Auto-blocking producing a nested result is fine. For tabs, each tab panel is a section whose model has a tab-label field (section metadata); the tab list is auto-blocked from it. This is the maintainers' example pattern (see below), even though a heading would be the preferred label in document authoring.multi: true, as a container with its fields when each entry has several parts (for example image + imageAlt). Use child items (a container block with a filter and an item model) when each entry is rich content. Multi-value fields render as lists only when multi-field is enabled: public.xwalk.multi-field.enabled: true in xwalk.json (or the site config); check it and enable it if you rely on it. Otherwise values arrive as one comma-separated string. Containers cannot nest inside multi-fields.rows, columns and classes, default content in the cells."key-value": true renders name | value rows. Only for configuration-style blocks, never for content.text, textarea, richtext, reference (assets), aem-content (any AEM content, for links), select, multiselect, checkbox-group, radio-group, boolean, number, date-time, container, tab, aem-content-fragment, aem-experience-fragment, aem-tag. Always set valueType as the type requires (string[] for checkbox-group, boolean, number).page-metadata (or <template>-metadata).Before inventing a pattern, read the example PRs in adobe-rnd/aem-boilerplate-xwalk (titles start with "Example:", by the xwalk maintainers; they are best practice): Tabs (#69), Multi-Fields and Composite Multi-Fields (#79), Column Layout (#72), Content Fragment Block (#76), Authoring Governance (#81). gh pr view <n> and gh pr diff <n> show the definition, model, filter and code.
.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