Skip to content

docs(thermidor): Add why.md#7882

Merged
lavoiesl merged 1 commit into
mainfrom
seb-thermidor-why
Jul 9, 2026
Merged

docs(thermidor): Add why.md#7882
lavoiesl merged 1 commit into
mainfrom
seb-thermidor-why

Conversation

@lavoiesl

@lavoiesl lavoiesl commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

While trying to understand thermidor, I wanted to better understand the why and got Kiro to assemble this such that we can align on it.

Rendered version

@changeset-bot

changeset-bot Bot commented Jun 25, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c5aa298

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@svcsnykcoveo

svcsnykcoveo commented Jun 25, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@pkg-pr-new

pkg-pr-new Bot commented Jun 25, 2026

Copy link
Copy Markdown
@coveo/atomic

npm i https://pkg.pr.new/@coveo/atomic@7882

@coveo/atomic-hosted-page

npm i https://pkg.pr.new/@coveo/atomic-hosted-page@7882

@coveo/atomic-legacy

npm i https://pkg.pr.new/@coveo/atomic-legacy@7882

@coveo/atomic-react

npm i https://pkg.pr.new/@coveo/atomic-react@7882

@coveo/auth

npm i https://pkg.pr.new/@coveo/auth@7882

@coveo/bueno

npm i https://pkg.pr.new/@coveo/bueno@7882

@coveo/create-atomic

npm i https://pkg.pr.new/@coveo/create-atomic@7882

@coveo/create-atomic-component

npm i https://pkg.pr.new/@coveo/create-atomic-component@7882

@coveo/create-atomic-component-project

npm i https://pkg.pr.new/@coveo/create-atomic-component-project@7882

@coveo/create-atomic-result-component

npm i https://pkg.pr.new/@coveo/create-atomic-result-component@7882

@coveo/create-atomic-rollup-plugin

npm i https://pkg.pr.new/@coveo/create-atomic-rollup-plugin@7882

@coveo/headless

npm i https://pkg.pr.new/@coveo/headless@7882

@coveo/headless-react

npm i https://pkg.pr.new/@coveo/headless-react@7882

@coveo/shopify

npm i https://pkg.pr.new/@coveo/shopify@7882

commit: c5aa298

@lavoiesl lavoiesl force-pushed the seb-thermidor-why branch from 376c69e to c5aa298 Compare June 29, 2026 12:15
@lavoiesl lavoiesl marked this pull request as ready for review June 29, 2026 12:16

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new Thermidor documentation article explaining the motivation for creating @coveo/thermidor, contrasting it with today’s @coveo/headless architecture, and framing the shift toward unified multi-API experiences and server-progressive (streaming) generative interfaces.

Changes:

  • Introduces a “Why Thermidor?” doc describing Headless’s current multi-engine constraints and the resulting complexity for hybrid experiences.
  • Explains the architectural shift from client-driven request/response to server-progressive streaming, including Mermaid diagrams.
  • Summarizes Thermidor’s design responses (single store, slice adoption, interfaces/facades, hydration) and links to related Thermidor docs.

@lavoiesl lavoiesl added this pull request to the merge queue Jul 9, 2026
Merged via the queue into main with commit cef31b1 Jul 9, 2026
47 checks passed
@lavoiesl lavoiesl deleted the seb-thermidor-why branch July 9, 2026 14:56

| Concern | Headless Today | Thermidor |
| --------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **State stores** | One Redux store per use case (Search, Commerce, etc.) | One store, multiple interfaces |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thermidor - One store, sliced by feature, scoped by interface

Suggested change
| **State stores** | One Redux store per use case (Search, Commerce, etc.) | One store, multiple interfaces |
| **State stores** | One Redux store per use case (Search, Commerce, etc.) | One store, sliced by feature, scoped by interface |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants