docs(thermidor): Add why.md#7882
Conversation
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
@coveo/atomic
@coveo/atomic-hosted-page
@coveo/atomic-legacy
@coveo/atomic-react
@coveo/auth
@coveo/bueno
@coveo/create-atomic
@coveo/create-atomic-component
@coveo/create-atomic-component-project
@coveo/create-atomic-result-component
@coveo/create-atomic-rollup-plugin
@coveo/headless
@coveo/headless-react
@coveo/shopify
commit: |
bcb6648 to
376c69e
Compare
376c69e to
c5aa298
Compare
There was a problem hiding this comment.
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.
|
|
||
| | Concern | Headless Today | Thermidor | | ||
| | --------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------- | | ||
| | **State stores** | One Redux store per use case (Search, Commerce, etc.) | One store, multiple interfaces | |
There was a problem hiding this comment.
Thermidor - One store, sliced by feature, scoped by interface
| | **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 | |
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