JavaScript Search Framework component equivalences
JavaScript Search Framework component equivalences
These tables illustrate how out-of-the-box components in the Coveo Atomic, Headless and Quantic libraries match the functionality of various JavaScript Search Framework components. If there’s no direct mapping to a Headless, Atomic, or Quantic component, you’ll find a link to relevant documentation when possible. If a component is available in Headless but not in Atomic, you can still achieve the functionality by accessing Headless through Atomic. If a component is available in Headless but not in Quantic, you can still achieve the functionality by accessing Headless through Quantic.
Across Atomic, Headless, and Quantic, certain components or controllers offer the same functionality as two or more JavaScript Search Framework components.
For example, the Headless QuerySummary
provides the same features as the JavaScript Search Framework QueryDuration
and QuerySummary
components.
How to read the equivalence tables
-
Identify the JavaScript Search Framework component you want to migrate.
-
Scan the tables by category to find the closest Atomic, Quantic, or Headless equivalent.
-
If you don’t find a direct mapping, open the "components not carried forward" section under the relevant category and follow the migration guidance.
|
Note
Mappings are identical across all categories and may appear more than once because they span UI, template, and navigation use cases. |
|
Disclaimer
The JavaScript Search Framework and Atomic both operate as UI libraries. In contrast, Headless provides controllers and actions with which you can create your own, custom components, even when using Atomic or Quantic. So, if no obvious Headless controller, Atomic or Quantic component matches the functionality you want to replicate from a JavaScript Search Framework component, you can often implement your own. |
Visual
Use this section to map visual and result-template components from the JavaScript Search Framework to their Atomic, Quantic, and Headless equivalents.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
None |
|||
None |
|||
Use Salesforce lightning component: |
None |
||
None |
None |
||
None |
|||
None |
|||
Visual components not carried forward
The following visual components from the JavaScript Search Framework don’t have direct equivalents in Headless, Atomic, or Quantic. If you require similar functionality, consider custom development or alternative approaches in your chosen framework.
JSUI component | Migration guidance |
---|---|
Use your framework’s modal or overlay components for similar UI effects.
The closest alternative is the |
|
Follows a similar rationale to the |
|
Follows a similar rationale to the |
|
Use custom result templates or table components in your framework.
The closest alternative is the |
|
This was used in JSUI to allow users to switch the result layout between list, card, or table. Use your framework’s UI controls to offer layout switching. Atomic supports multiple display types natively. |
|
Implement custom filter preference logic if needed, especially for power users or intranet scenarios. |
|
Use custom settings panels in your UI for advanced user control. |
|
Use your framework’s button components and bind them to search actions. |
|
Implement custom settings panels as needed, especially for advanced user scenarios. |
|
Implement sharing features using your framework’s capabilities. |
|
Atomic and Quantic use a different templating system than that of the legacy JSUI approach.
As a result, this artifact has no equivalent in the modern frameworks with Coveo.
See |
Functional
Use this section to map core search features such as facets, query input, sorting, and result management to their equivalents.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
None |
None |
||
None |
None |
||
None |
|||
None |
|||
Functional components not carried forward
The following functional components from the JavaScript Search Framework don’t have direct equivalents in Headless, Atomic, or Quantic. Consider custom logic or alternative approaches for these features.
JSUI component | Migration guidance |
---|---|
Use facet or group-by features in your framework to aggregate results as needed. |
|
Add follow or subscription features using custom logic or third-party integrations. |
|
Saw very little adoption, and relied on a now deprecated |
|
Atomic and Quantic support |
|
Implement notification or alerting features using your framework’s notification system or external integrations. |
|
Display alert messages using your framework’s notification or messaging components. |
|
Atomic uses a different templating system than that of the legacy JSUI approach. As a result, this artifact has no equivalent in the modern frameworks with Coveo. |
Navigation
Use this section to map navigation helpers such as tabs, pagination, refine toggles, and breadcrumbs to their equivalents.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
None |
|||
Navigation components not carried forward
The following navigation components don’t have direct equivalents in Headless, Atomic, or Quantic. Use your framework’s navigation controls or custom logic as needed.
JSUI component | Migration guidance |
---|---|
This was used in JSUI to allow users to switch the result layout between list, card, or table. Use your framework’s UI controls to offer layout switching. Atomic supports multiple display types natively. |
Notification and alert
Use this section to map attention and status indicators that highlight promoted or special results.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
None |
Notification and alert components not carried forward
The following notification and alert components don’t have direct equivalents in Headless, Atomic, or Quantic. Implement custom notification logic or use external systems as needed.
JSUI component | Migration guidance |
---|---|
Add follow or subscription features using custom logic or third-party integrations. |
|
Provide alerting or notification features using your framework’s notification system or external integrations. |
|
Display alert messages using your framework’s notification or messaging components. |
Analytics and tracking
Use this section to map analytics instrumentation and summary displays that help measure and explain query performance.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
Works in a similar way to Atomic |
|||
Analytics and tracking components not carried forward
The following analytics and tracking components don’t have direct equivalents in Headless, Atomic, or Quantic. Implement custom analytics logic or use external tracking systems as needed.
JSUI component | Migration guidance |
---|---|
A legacy system for query suggestions. This has now been replaced by Coveo’s machine learning model, so you should use the supported machine learning solution for your chosen framework. |
Template and layout
Use this section to map result template elements and layout helpers for rendering search results.
JavaScript Search Framework | Atomic | Quantic | Headless |
---|---|---|---|
None |
|||
None |
None |
||
None |
|||
None |
|||
None |
None |
||
None |
None |
||
Use Salesforce custom labels: |
None |
||
Use custom templates with: |
None |
||
Use custom templates with: |
None |
Template and layout components not carried forward
The following template/layout components don’t have direct equivalents in Headless, Atomic, or Quantic. Use your framework’s template and layout features for similar functionality.
JSUI component | Migration guidance |
---|---|
Use custom result templates or table components in your framework.
The closest alternative is the |
|
This was used in JSUI to allow users to switch the result layout between list, card, or table. Use your framework’s UI controls to offer layout switching. Atomic supports multiple display types natively. |
|
Atomic uses a different templating system than that of the legacy JSUI approach. As a result, this artifact has no equivalent in the modern frameworks with Coveo. |