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
A content model is the structure authors see and manage in Word, Google Docs or Experience Workspace. It is also the markup delivered to browsers before decoration, so it matters under WYSIWYG editing too (Universal Editor, Experience Workspace layout view): search engines and AI crawlers read it.
Skip this skill when the block's structure does not change (CSS or code only).
text, heading or image block. Forms, search, calculators and similar apps are widgets: authors paste the widget URL alone in a paragraph and author no table. Their editable text (topic lists, messages) lives with the widget, for example in a spreadsheet, so authors can still change it without a developer. A block is for repeating or interactive content that authors fill in. Look for an existing block with the same job first (block-collection-and-party) and reuse its model.h2, picture, a, strong), never by cell index or order. One cell per field breaks when an author skips or reorders a cell, loses the meaning when content is copied between tools, and gives search engines and AI crawlers nothing to read.label | value. Section Metadata is key/value too: use it for styles and settings, never for content. A tab title or any label for the content below it is a heading in default content.table block. Large or reused data goes in a spreadsheet (published as JSON) that the block links to.featured-2), text suffixes like "(open)", or image alt text.Return this to the caller or the user:
## Content Model: [Block Name]
**Default content, widget or block:** [why]
| Block Name (variants) |
|---|
| [what the author types in each cell, as the author sees it] |
### How authors use it
[what each row and cell holds; which parts are optional; what the code infers]
### Assumptions
- [decisions made without the author]
### Questions for the author
- [open questions that would change the model]Draw cells as the author sees them. When a cell has several paragraphs, show each paragraph on its own line (for example in a code block under the table). Never use <br>, <p> or other HTML tags in the examples.
The caller (content-driven-development or the user) decides what happens next: test content, then block code. In AEM-authoring (Universal Editor) projects, ue-component-model maps this model to editor fields.
.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