fs-cmsslider attribute. list, item, prev, next) to each slider’s elements and include the Finsweet CMS Slider script in the page footer.To manage two different Collection-based sliders on the same Webflow page using Finsweet's CMS Slider, you need to initialize and configure each slider independently with unique attributes.
fs-cmsslider attribute with a different value.
Example:
fs-cmsslider=blogsliderfs-cmsslider=projectsslider
<script src="https://cdn.jsdelivr.net/npm/@finsweet/attributes-cmsslider@1/cmsslider.js"></script>
(Note: this is a reference link, but per guidelines, do not paste as raw code in Webflow. Use Webflow’s Embed element or Page Settings → Custom Code.)
Within each Collection List’s slider:
fs-cmsslider attribute (as above).fs-cmsslider-element="list".fs-cmsslider-element="item" (usually to the Collection Item itself).fs-cmsslider-element="prev" and fs-cmsslider-element="next" on your custom or native arrows for each slider.
Each slider instance must have uniquely named fs-cmsslider values to avoid conflicts.
If needed, you can initialize sliders with custom settings by modifying the script with helper options using window.fsAttributes.
However, for most standard multi-slider setups, using different attribute names is sufficient without needing custom JS.
To use Finsweet CMS Slider with two different Webflow sliders from different Collections:
fs-cmsslider attributes to each slider (like blogslider, projectsslider).
Each slider will function independently, dynamically rendering items from its respective CMS collection.