Results and controls
Build one coherent interface around Listings (Feed). Each companion element reads and changes the state of that faceted result instance.
Result container
In Listings (Feed):
- select the query that matches the context;
- set Use with faceted search? to Yes;
- choose Automatic or Manual under Facet submit mode;
- decide whether Show initial results? should display cards before the first search.
The result element supplies the context for nearby controls. Avoid placing two different faceted result sets in one interface unless their controls are clearly isolated.
Filter and action elements
| Builder element | Purpose |
|---|---|
| Faceted Search Facet | Renders the facet identified by Facet ID |
| Faceted Search Submit | Applies pending selections in manual mode |
| Faceted Search Reset | Clears all, included, or excluded facet IDs |
| Faceted Search Selections | Shows removable active selections |
| Faceted Search Selections Count | Shows the number of active facets |
Faceted Search Reset can target All, Include, or Exclude. Auto hide hides it when there is nothing to clear. Reset extras decides whether sort and per-page state are reset with facets.
Result summary elements
- Faceted Search Counts can use
{{start}},{{end}}, and{{total}}in Label, plus a separate Empty label. - Faceted Search Sort presents allowed order values.
- Faceted Search Per Page presents comma-separated page sizes.
- Faceted Search Pager handles movement between result pages.
Automatic and manual submission
Use Automatic when every selection should refresh immediately. This is suitable for compact facets and quick result rendering.
Use Manual when visitors commonly change several controls before searching. Add Faceted Search Submit and set its Context ID. The listing’s Refresh after reset? setting controls whether reset immediately refreshes results in this mode.
Layout guidance
Place the current selections and reset action close together. Keep counts near the result heading, and keep sorting separate from filters so its purpose is obvious. On mobile, preserve the counts and active-selection summary outside a collapsible filter panel when possible.
Verify that every control updates after filtering. A count or pager that stays static usually indicates that it is outside the intended faceted instance or that the result context does not match.