The post asks if it's possible to use Finsweet attributes for filtering in Webstudio. Community members discuss the pros and cons of using Finsweet attributes versus Webstudio's native filtering abilities. Some community members praise the UX of Finsweet attributes and wish for a similar solution for Webstudio, while others suggest using Webstudio's built-in filtering functionality. A community member also shares a plugin called "Filters" that they created, which is described as being better than Finsweet. The discussion includes feedback on the performance and features of the Filters plugin, with the creator providing insights on the design choices and future plans for the plugin.
Nice find Ronald. @viniciusmoreira.me We can see the items are hidden by CSS, Is there any chance we can create something like Finsweet where the items will be removed from the DOM and add when certain filter condition is matched?
Back when I made Sift (which is the codebase that powers the Filters Plugin), my intent was to make a really fast and easy-to-setup realtime filters system.
In addition to being easier to maintain, the approach with CSS is faster and gives a more instant feel, especially with search text input, as the filtering must match the typing speed. The DOM approach would be more beneficial for very large collections, but if your collection is about 1000 items (and maybe even more), you should not have any problems with it.
And about future features, the Filters plugin is and will be constantly evolving, so I'm always on the lookout for ideas to make it better
