Hi Guys,
I have a bit of a simple question and maybe I overlooked the obvious, but anyway:
When I get a element like a gallery slider or a product page with some functionallity/interaction there is sometimes attributes like this one: https://finsweet.com/attributes/cms-slider
@Mario I would say generally, that this will just come with time. 99.99% of these attributes are there from Finsweet because of lack of functionality from Webflow.
For instance, with the Slider - it'll work fine right out of the box. But the most common request with the slider is to not have a giant blank area at the end of the slider when you reach the end. No way to control that with the native Slider - so now you have to use a custom slider library. Or Finsweet Slider component. Which actually has nothing to do with attributes, just an example of Webflow limitations.
You can't populate a slider with CMS items with the native Webflow slider.
You can't have more than 1 nested CMS collections on a single page.
You can't have more than 20 collections on a single page.
You can't do this or that...just comes with time.
Now one thing we COULD do better at is signaling this within the Webflow library. We used to have an icon, but I'm not seeing that anymore. But on some components, if you click on it, it opens up a details page and on there, it shows links to the Finsweet attributes that would make sense for this component.
https://www.relume.io/components/blog-67
But its just a lot quicker to know the tool and its limitations and to also really understand the library of attributes that Finsweet has - there's some creative solutions in there. Ultimately, anytime I was stuck because of a Webflow limitation, I would just instantly go to Finsweet because they build a lot of websites and some of the biggest Webflow sites and if I'm facing the issue, they already have.
Hi Matt,
Thank you so much for your very helpful answer! That explains a lot.
ok I'll find my way.
Cheers,
Mario
