<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>ecommercecraft · Blog</title><description>Notes on e-commerce architecture and on working with AI coding agents, written from 17 years of client work on Magento and Adobe Commerce.</description><link>https://www.ecommercecraft.com/blog/</link><language>en</language><item><title>My Adobe Commerce performance checklist</title><link>https://www.ecommercecraft.com/blog/adobe-commerce-performance-checklist/</link><guid isPermaLink="true">https://www.ecommercecraft.com/blog/adobe-commerce-performance-checklist/</guid><description>Twelve checks, in order, that show where most of the page-load time goes on a typical Adobe Commerce store before any code is written.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Performance</category><category>Adobe Commerce</category></item><item><title>How I use AI coding agents on Adobe Commerce projects</title><link>https://www.ecommercecraft.com/blog/ai-augmented-adobe-commerce-workflow/</link><guid isPermaLink="true">https://www.ecommercecraft.com/blog/ai-augmented-adobe-commerce-workflow/</guid><description>Which Adobe Commerce tasks I hand to Claude Code, which I keep, and what changes for the merchant. Hooks, skills and MCP hold the agent to the same review process as any engineer.</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><category>AI</category><category>Workflow</category><category>Adobe Commerce</category></item><item><title>When to go headless on Adobe Commerce</title><link>https://www.ecommercecraft.com/blog/when-to-go-headless-on-adobe-commerce/</link><guid isPermaLink="true">https://www.ecommercecraft.com/blog/when-to-go-headless-on-adobe-commerce/</guid><description>Headless pays off only with a frontend team and a budget for two applications. How I decide between Hyvä and a separate storefront on Adobe Commerce.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>Headless</category><category>Architecture</category><category>Hyvä</category></item></channel></rss>