Roadmap

The framework started as an in-repo extraction and has since become a standalone, versioned product. This page tracks what has shipped and what is still ahead. No dates — items land when they are ready.

Delivered

Framework extraction

The framework lives in its own repository (evolve-framework) instead of a vendor/packages/ directory inside each implementation. Implementations consume it as a regular dependency; the migration guide covers moving over.

Registry publishing

Packages are published as @evolve-framework/* to the Evolve registry (npm.registry.evolve-platform.com). Releases are driven by changesets: merged changesets accumulate into a release PR on main, and every push that does not cut a stable release publishes snapshot versions (0.0.0-<sha>-<timestamp>, dist-tag snapshot) for early testing.

Implementation packages

The package family the original roadmap promised largely exists:

• Commerce: @evolve-framework/commercetools and @evolve-framework/sfcc (Salesforce Commerce Cloud)
• CMS: @evolve-framework/contentful and @evolve-framework/storyblok
• Payments: Adyen, Stripe, Buckaroo, Pay.nl, Invoice, and Mollie — each as its own @evolve-framework/commercetools-* package
• Cloud adapters: @evolve-framework/cloud-adapter-aws, -azure, and -gcp abstract messaging and storage per cloud

All build on the same @evolve-framework/core and @evolve-framework/schemas layers.

Gateway extraction

The gateway is extracted — but not as the @evolve-framework/gateway npm package once planned here. The Node/Apollo gateway was replaced by a custom Rust Hive Router binary (backend/services/graphql-gateway):

• The @labdigital/federated-token gateway behaviour is reimplemented as a compiled-in Rust plugin (federated_token, maintained in its own repo, evolve-platform/hive-router-federated-token) with a byte-for-byte compatible wire format, so subgraphs are unaffected.
• Trusted documents come from Hive Router’s native persisted_documents support against the Hive CDN, replacing the hand-rolled plugin.

A project’s gateway is now the router binary plus a router.config.yaml and a supergraph — configuration rather than code, which was the point.

Upcoming

Evolve CLI

Scaffolding and maintenance tooling: create-evolve-app to generate a project from choices (commerce backend, CMS, payment providers, deployment target), evolve upgrade for version bumps and codemods, and evolve add for dropping modules into an existing composition. Not started — @evolve-framework/packager exists but is a build/deployment packager, not this CLI.

Frontend framework package

The extraction pattern applied to the storefront: shared UI components, hooks, and utilities as framework packages so a project’s frontend carries only project-specific code.

Authoring stack

An AI-assisted content authoring layer, currently on feature branches and not yet released: an authoring console and in-storefront chrome with review/publish workflows, a ContentfulAuthoringModule (@evolve-framework/contentful/authoring) exposing the authoring queries, mutations, and OAuth routes, and a gateway authoring_token plugin that propagates the editor’s CMS token to subgraphs.