Checklists, reference guides, and cheat sheets that make AEM work easier. Free resources drop alongside the tutorials — subscribers get them first.
EP10: the other half of HTL — the block statements that decide whether markup exists at all, how often, and what shape it takes. data-sly-test, -list, -repeat, -attribute, -element, -resource, -include, -template. No Java. Part 2 of two.
EP09: your .html files aren't HTML — they're HTL. The ${…} expression, the objects it hands you, operators, and the display contexts that keep every value safe by default. Part 1 of two.
EP08: take inline styles and script out of a component and into a clientlib — categories, the head/footer split, allowProxy and the /etc.clientlibs URL, the version hash, and dependencies vs embed.
EP07: the engine behind every episode so far — the five script names Sling tries in order, super types, the /apps and /libs search paths, and why our page component has no page.html.
EP06: an Article Page template built from scratch — structure vs initial content, policies as the guest list, layout mode on the 12-column grid, and the archetype breakpoint bug that makes layout mode look broken.
EP05: a Teaser dialog built from scratch — every Granite UI field you actually need, tabs, validation, and a multifield inside a multifield, traced down to the JCR.
EP04: a Card component built live in CRXDE — dialog, HTL, template policies, the JCR round trip, and exporting it to your codebase with Package Manager.
Points Maven to Adobe's public repository so your AEM builds can download the right dependencies. Required for every AEM Maven project.
The daily build & deploy commands from EP03 — full build, single-module, Author vs Publish — and what to run when. Keep it next to your terminal.
The full mvn archetype:generate command that scaffolds a multimodule AEM project — Mac/Linux and Windows versions, with every parameter explained.
The questions to answer before a single line of code is written on a new AEM build.
Common OSGi configs and what they actually do, in plain language.
What you need to tackle before moving to AEM as a Cloud Service.
Every command to get an AEM SDK instance, WKND, and your project running locally.
The HTL syntax you'll actually use — data-sly blocks, expressions, and context.
