docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
{
"context": "This criteria evaluates how well the engineer uses MJML's mj-html-attributes component to inject custom HTML attributes into rendered email templates. The focus is on proper usage of mj-html-attributes, mj-selector, and mj-html-attribute components to achieve post-render DOM manipulation.",
"type": "weighted_checklist",
"checklist": [
{
"name": "mj-html-attributes usage",
"description": "Uses the <mj-html-attributes> component correctly within the <mj-head> section of the MJML template",
"max_score": 20
},
{
"name": "mj-selector implementation",
"description": "Properly uses <mj-selector> components with the 'path' attribute to target HTML elements using CSS selectors",
"max_score": 25
},
{
"name": "mj-html-attribute injection",
"description": "Correctly uses <mj-html-attribute> components with 'name' attribute to inject custom data attributes (e.g., data-track-id, data-analytics-type) into targeted elements",
"max_score": 25
},
{
"name": "Multiple selector mappings",
"description": "Implements multiple <mj-selector> blocks to handle different attribute mappings for different CSS selectors as specified in the configuration",
"max_score": 15
},
{
"name": "mjml2html integration",
"description": "Uses the mjml2html() function to compile the MJML template into HTML and properly extracts the html property from the result",
"max_score": 15
}
]
}