Overview

This overview describes the Commerce boilerplate repository and how it fits Edge Delivery Services and drop-ins. Start with the definition below, then follow First steps when you are ready to clone, run locally, or dig into architecture.

What is the Commerce boilerplate?

The Commerce boilerplate is Adobe’s supported starter/reference codebase for storefronts on Edge Delivery ServicesAdobe's hosting and delivery infrastructure that turns authored documents into fast HTML pages served from servers close to the shopper. You push code to GitHub; Edge Delivery Services builds and publishes automatically. (EDS). You clone it from GitHub, connect your Commerce backend, and customize blocks, scripts, and styles in that repository instead of tying together every Commerce integration yourself.

The boilerplate repository lives at hlxsites/aem-boilerplate-commerce . EDS hosts and publishes your site from that repo. The boilerplate also bundles Drop-in componentsNPM packages that provide core Commerce storefront features such as cart, checkout, product details, and account flows. for cart, checkout, product listings, and related Commerce flows so you theme and configure shipped UI rather than building those screens from scratch.

One supported boilerplate

aem-boilerplate-commerce is the only Adobe-supported Commerce starter/reference storefront. Demo storefronts (for example Citisignal) are forks for events or showcases. They often lag behind this repository and are not a safe starting point for your own project.

First steps

1. If you still need a site, follow Create a storefront. When you already have a repo, open Boilerplate getting started to run npm install and npm start, and explore blocks/, scripts/, and styles/.

2. Read Storefront Architecture when you need the full picture of how authoring, blocks, drop-ins, and Commerce APIs connect.

Other topics in this section

Use these when you already have a project open on disk:

• Configuration — Commerce backend endpoints, headers, and storefront settings.
• Blocks reference and Blocks customization — Block behavior and layout.
• Universal Editor — Optional authoring path alongside Document Authoring.
• Boilerplate updates — Staying current with upstream changes.
• AI agent skills — Optional skills for coding agents.

Related areas outside this section

• Commerce configuration — Wire the storefront to your Commerce backend after the boilerplate runs.
• Commerce blocks (merchants) — How merchants work with blocks in authoring tools.
• Drop-ins introduction — Technical reference for each drop-in.

Packages and block wiring

When you trace npm dependencies or debug install issues, open Getting started for the key runtime packages the boilerplate adds. When you need each Commerce block’s drop-ins, GitHub source folder, and merchant-facing topic in one place, open Blocks reference.