Hiring AEM talent? Request profiles →

Moving AEM Code to the Cloud with AI: The Cloud Migration Skill, the Cloud Migration MCP, and the Best Practices Analyzer

Moving to AEM as a Cloud Service means reworking Java code, OSGi configurations, Dispatcher setup, and legacy UI, not just content. Adobe documents an agent-based toolset for this: the Best Practices Analyzer’s findings, a hosted Cloud Migration MCP that pulls them from Cloud Acceleration Manager, and a Migration Skill that writes a read-only runbook first, then works one pattern per session in batches of five with a review pause after each. This post covers how the pieces fit, what patterns are named, and what Adobe’s pages leave out: maturity labels, accuracy guarantees, rollback guidance, and MCP data handling.

Moving AEM Code to the Cloud with AI: The Cloud Migration Skill, the Cloud Migration MCP, and the Best Practices Analyzer Read More »

AI-Assisted AEM Development on Your Laptop: AGENTS.md, Adobe’s Agent Skills, and the Quickstart and Dispatcher MCP Servers

Adobe documents local tooling that lets an AI coding assistant see your AEM project’s real state instead of guessing: a project context file, a set of agent skills, an AEM Quickstart MCP server for logs and OSGi diagnostics, and a Dispatcher MCP server for validating configuration against a local Docker Dispatcher. This post summarizes what each piece does, its documented prerequisites and limits (Java stack only), and Adobe’s security notes. It also flags what the page doesn’t say, including any GA or Beta label.

AI-Assisted AEM Development on Your Laptop: AGENTS.md, Adobe’s Agent Skills, and the Quickstart and Dispatcher MCP Servers Read More »

Protecting an AEM Edge Delivery Services Site: Site Tokens, CDN Authentication, and the OIDC Beta

Edge Delivery Services sites are public by default, which is wrong for a staging site, a partner portal, or an intranet. This post walks through the access-control options Adobe documents: token-based site authentication, CDN-level Basic authentication (GA, but not for live production domains), and OIDC sign-in (currently Beta). It also covers the limits Adobe states, like authentication only (no authorization) and whole-site-only protection, plus the documented fix when the Universal Editor starts returning 401.

Protecting an AEM Edge Delivery Services Site: Site Tokens, CDN Authentication, and the OIDC Beta Read More »

AEM + AI Security: Catching Vulnerabilities Before Release, Not After an Incident

Most AEM security incidents aren’t sophisticated zero-days they’re known CVEs that sat in a dependency tree for months, or an injection pattern in custom code that a rushed review missed. This post shows how continuous dependency/CVE scanning on every build, AI-reviewed pull requests for AEM-specific risk patterns (advisory only, human-confirmed), and production anomaly detection close the gap between quarterly audits, without ever auto-remediating a live instance without a security engineer’s sign-off.

AEM + AI Security: Catching Vulnerabilities Before Release, Not After an Incident Read More »

AEM + AI Commerce: Scaling Product Content and Recommendations Across Tens of Thousands of SKUs

A catalog with 40,000 SKUs and a copywriting team of three means most products ship with a manufacturer’s spec sheet as the entire product page. This post shows how Claude API drafts product copy strictly from supplied attributes (no invented specs), Adobe Sensei delivers session-aware recommendations instead of static rules, and AEM keeps AI-generated content and live Adobe Commerce pricing/inventory on separate refresh paths that converge cleanly at render time closing the long-tail content gap without adding headcount.

AEM + AI Commerce: Scaling Product Content and Recommendations Across Tens of Thousands of SKUs Read More »