
App Builder · Ep 0: three questions that decide App Builder or a module
Which Adobe Commerce customisations should leave the monolith for App Builder, which stay as modules, and how this series works: foundations first, then a developer log.
Step-by-step Adobe Commerce, App Builder, AEM and Mirakl tutorials, including the Learn with me series.

Which Adobe Commerce customisations should leave the monolith for App Builder, which stay as modules, and how this series works: foundations first, then a developer log.

What aio app init actually creates, which three files decide how your app behaves, what never goes into git, and how a Commerce admin extension changes the layout.

Three ways to start an App Builder project for Commerce, which one I'd pick for an integration, and the steps from clone to a deployed action on Stage.

Map each part of an Adobe Commerce module to its App Builder equivalent, then build a scheduled stuck-order alert with an alarm trigger, State for de-duplication and a lock against overlapping runs.

App Builder now has a document database for actions. When to use it instead of State, how to provision it, the auth that trips people up, and a sync log to query.

aio app logs is fine on your laptop. For shared Stage and Production workspaces, set up New Relic log forwarding, check that it worked and know the limits.

Move the order-placed observer out of Commerce: connect the workspace, subscribe to only the fields you need, and write a handler that survives duplicates.

A Commerce webhook lets your action block or change an operation before it completes. Declare one, verify the signature, and fail open or closed on purpose.

Commerce GraphQL and a REST API behind one endpoint, joined without N+1 calls, plus the cache model: one response, one Cache-Control, strictest source wins.

Give your integration a home where merchants work: enable the Admin UI SDK, get Adobe's sample showing, then add a stuck-orders page from your App Builder app.

The capstone. Take an observer-based integration module, move it to events, an action and an admin page, and weigh what got better against what got harder.

Every piece of the series, tested three ways: fully local, local code against a Stage workspace, and deployed. A grid of what worked, what failed, and why.

Learn with me, marketplace edition. Who does what in a Mirakl marketplace, and which data each side owns.

How offers, orders and shops move between your platform and Mirakl, how the API codes work, and the calls I reach for first.

Mapping the order lifecycle between storefront and marketplace operator, and the sync points that break first. Mirakl episode 3.