Building a Medusa Storefront in Next.js: Architecture and Patterns
Server components, caching, cart state and the rendering decisions that determine whether your storefront is fast. The architecture we use on every Medusa build.
[ Field notes / page 5 of 5 ]
Field notes — page 5
Migrating to Medusa: How to Replatform Without Losing the Business
The decision framework, the sequence, the costs and the failure modes. A platform-agnostic guide to moving an existing store onto Medusa without breaking revenue.
Medusa Module Links: Relating Data Across Isolated Modules
Modules cannot reference each other's tables, so how do you attach a brand to a product? Links — and the query layer that reads across them.
Medusa Workflows Explained: Steps, Compensation and Why They Matter
Workflows are how Medusa keeps multi-step commerce operations from leaving your data half-written. How steps and compensation work, and how to build one properly.
Medusa v2 Modules Explained: Building Custom Commerce Domains
Modules are the unit of everything in Medusa v2. What they are, why isolation matters, and how to build one that will not embarrass you in a year.
Installing Medusa v2: From Zero to a Running Store
The install that works, the prerequisites people miss, and what to do in the first hour after the seed data loads.
What Is Medusa? The Open-Source Commerce Platform, Explained
Medusa is a TypeScript commerce framework you run yourself. Here is what that actually means, who it suits, who it does not, and how it differs from every hosted platform you have used.