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
Decide these from the capture before writing the nav document. Look at the shots yourself: open each image, do not guess from the numbers alone.
For each state of <src>/open/open.json with newLinks > 0, open <src>/open/<file> (the page at
1440x900 with that menu open) and read panel (its box, background, links and text):
| the open panel shows | kind | author it as |
|---|---|---|
| one short list of links under the label | simple list | a nested <ul> under the label in the nav document |
| several columns of links, maybe with column headings | columns | a fragment panel: a columns block, one column per group (heading + list) |
| a list of categories on one side that switches the links shown beside it | tabbed | a fragment panel: optional heading, then a tabs vertical block, one row per category (cell 1 the category label, cell 2 its list of links with their description text) |
| a few featured items with images or icons | cards | a fragment panel: a cards block, or columns |
playwright-cli, your own session) and look at its DOM.From panel.rect at 1440 px wide:
w >= 1368 (95 % of the width): full.header when w > 900, else center.trigger.Use the most common value as the main nav's Dropdown Align. A menu that differs needs its own
CSS.
<src>/open/mobile-menu.png is the burger opened at 390x844, and mobile-item.png is the same
menu after tapping its first item. They set the main nav's metadata:
| tapping the item | Mobile Style |
|---|---|
| expanded it in place: its sub-items appear under it, the other items stay | accordion |
| replaced the list with the item's own content, with a back control | slide-in |
| opened a full-screen layer with the item's content | fullscreen |
Mobile Tools: bar when the mobile header bar shows a search icon, an account icon or a call to
action besides the logo and the burger (<src>/regions/<id>.mobile.png); else drawer, or
hidden when the source's drawer does not show them either.
No mobile-menu.png: the capture could not open the burger. Open it on the live source at 390 px
and decide from what you see.
These come from the capture; do not decide them from the shots:
states[].trigger (hover or click). The main nav's
Dropdown Trigger is hover when any menu opens on hover.header.breakpoint.shownAt.header.scroll is a first guess. Check what each band does on the live
source (rule 5)..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