Introducing the Filter Component. Watch the video below to see what it can do and how you can use it in your projects.
Both the Accordion and Filter components will be available in a new beta later this week. We’ll also share the demo files from the videos alongside the beta release.
Two days, two new components. I wonder what tomorrow will bring…
Suggest a Feature
Don’t forget you can vote and suggest the features you want on our open Roadmap page.
Get the Beta
If you’d like an invite to the private beta, just post a reply in this thread, and we’ll email you an invite with all the details!
Thanks for Your Feedback
As always, keep the feedback coming. Your input has made all the difference so far.
@dan
Not, sure yet, as haven’t seen the code, but you kept mentioning ids for targeting for filter. I wouldn’t recommend using multiple instances of same id, which is not following standards compliance, will break screen readers and may cause problems with other 3rd-party scripts in the future. Simple fix, just use a class or data attribute.
It’s great what the filter can do - but is it possible to do a search on a web page and its underlying pages without having to create an ID in all containers?
I just want to say that this Filter component should not be considered as a full site-wide search.
To clarify, the Filter component is designed exclusively for narrowing down content already displayed on a single page—it lets visitors refine what’s visible within a specific container or group. This is different from a Search component, which retrieves content from across an entire website based on user-entered keywords.
Website Search: Retrieves content from the entire site using user queries.
Web Page Filtering: Narrows down content already loaded on the page using predefined criteria.
We want to add full site-wide search functionality to Elements in the future.
