Guides
Each guide takes one change from start to a working result in your project. They assume a project that runs; if you do not have one yet, start with Get started.
The guides are grouped by where you make the change.
Frontend
Section titled “Frontend”Your Next.js storefront: the pages, the feature packages on them, and how they look.
Add a feature packageInstall a storefront feature package and wire it into your project, from the backend module to a working page.
Customize a componentChange how a feature component looks or behaves: style it, rearrange its parts, or take over a part.
Use your own iconsRestyle Evolve's icons, swap the icon of one component, or point every feature at your own icon set.
Confirm an add to cartShow the shopper what went into the cart: with the shipped sheet, or with your own toast, dialog or mini-cart.
Extend a feature's dataShow or submit a field that a feature package does not know about, without forking the package.
Style and brandApply your brand to every Evolve component through design tokens, and check its contrast.
Add a languageServe your storefront in another language or market: routing, message files, store context, and CMS content.
Show a facet as swatchesShow the color facet of a product listing as color swatches instead of a list of checkboxes.
Backend
Section titled “Backend”Your services: the GraphQL API they serve and the business rules behind it.
Add a fieldAdd a field to the API and store it in your commerce engine.
Change a module's behaviorAdjust a business rule in an Evolve module without copying the module.
Add your own moduleAdd functionality Evolve does not provide as a module in your own service.
React to eventsRun your own code when something happens, like an order being placed.
Send emailsSend transactional email, such as order confirmations and account mails, from your project and test it locally.
Expose your API to AI assistantsServe the GraphQL operations you choose as tools that AI assistants and agents call over the Model Context Protocol.
Vendors
Section titled “Vendors”The commerce engine, payment providers, search engine, and CMS behind your project.
Switch commerce engineMove a project from one commerce engine to another: commercetools, Medusa, or Salesforce Commerce Cloud.
Add a payment providerAccept payments through a provider such as Mollie, Adyen, or Stripe.
Add searchServe product search from a search engine such as Algolia or Meilisearch.
Add a CMSConnect a CMS such as Storyblok, Contentful, or Payload.
Add a content blockAdd your own block type to the CMS and the GraphQL schema.
Customize the Payload adminAdd plugins, your own admin components, and your brand to the Payload admin your editors use.
Build your own adapterConnect a vendor that Evolve has no package for yet.
Operate
Section titled “Operate”Testing, deploying, and running your project once it is live.
TestingTest your project, from unit tests to end-to-end journeys.
DeployingDeploy your project to production and keep deployments safe.
Deploy to VercelRun the storefront, the gateway and your services as one Vercel project, with a full preview for every branch.
InfrastructureWhat Evolve needs from your cloud, and which services provide it on Google Cloud, Azure, and AWS.
ObservabilitySee what your project is doing in production: traces, logs, errors, and health, and how to find the cause of a slow or failing request.
Looking something up
Section titled “Looking something up”The guides link to the reference for every package, command, and GraphQL operation they use. Go there directly when you know what you are looking for.