Filters are a bit broken https://www.relume.io/preview?cid=category-filters/section_filters6
yeah so filters are complex. The only bug that I actually see here is the horizontal scrollbar, I don't feel like that should be there, so I'll file that bug with the component team for sure. The rest of this functionality is dependent on using Finsweet Attributes. If you are really new to Webflow, this might be a bit complex, you could also try Jetboost.io depending on your situation. You'll see all of the "Power ups" that you'll need to make the actual filters work. We just provide the markup basically. Hope that makes sense - apologies for the confusion here.
ah okay, I missed that, thanks! also, I'm planning to export the website later, will the exported code include the required javascript etc for these "power ups" to work?
guess that depends on how you export the code. Whats your plan with export? And where will it go?
so if you are just wanting to export using native webflow export, I think there might be just a little bit more risk there for things not being connected versus if you were using something like Udesly or liquify.pro or Shopiflow etc.
But honestly, in theory yes they should work - the power ups depend on certain HTML attributes from existing on the HTML tags, so if those attributes don't exist, the power ups won't work.
And the more I think about it the less confidence I have that it will work because most of the reason these powerups exist in the first place is to work directly with the webflow CMS.
It would be worth a quick discovery on it for sure - super quick test on some other attributes besides the filters - filter attributes are the most complex attributes in the library so I probably wouldn't test it out on that but yeah. I have not personally done this without using some other tool to make all the connections like Udesly for example.
I've exported A LOT of webflow code to bring into react or angular though, but I generally ignore the javascript side of it as we'd build that out on our own once inside the app.
that's probably the easiest way, thanks! last question, as you have experience with exporting the code and using it in react/angular, how do you deal with design iterations?
once you've exported, the webflow project is pretty much throwaway - ping-pong back and forth just isn't worth the risk or effort to maintaining it anymore.
Its a good way to get going really quickly - but once exported yeah...it was just a rental vehicle to get you there quickly.
You could certainly keep designing/building out components within a webflow project though but again you run the risk of certain CSS changing in the destination environment.
It just requires less cooks, more planning, and really thinking about the design of something at the very root component level.
It is way way quicker to build up a component in Webflow than to write the markup/css - and you would just have to copy in the CSS variables that are established in the destination codebase, do any sanitations/linting of the CSS etc after every export.
its similar in a lot of ways of how we have things setup for Webflow though - a style guide, copy in components, style them.
If you set a solid set of variables, and a style guide in your destination codebase, and you are simply building/designing components in Webflow and "pasting" them into that codebase, hooking up the variables. It's still faster IMO. Especially if are not a CSS guru (or hate CSS) - its a viable bootstrap workflow.
I like the thought of thinking about it as a rental vehicle. Thanks again Matt, your support is superb. 🙂
