Attributes do not collect any sort of user data.
There's two different concepts here:
The a11y package doesn't add any ARIA attributes to any element. It just reads the existing ARIA Attributes on the page and runs the dynamic ARIA attributes (like aria-expanded, where its value depends on if the element is visible or not).
Each of the Finsweet Attributes is in charge of adding the proper ARIA attributes to the elements affected by the Finsweet Attribute.
Any element that is not affected by a Finsweet Attribute, it's up to the developer to ensure it has the proper ARIA Attributes.
Currently the Number Count attribute does not support decimal points
All scripts are loded asynchronously using defer or async tags, they never block the main thread. Each solution is self-contained and can run independently as soon as it’s loaded without causing waterfalls.
They all are intercompatible and couple together once they run. Each script is strongly cached on a CDN and on the user’s browser.
Bundling multiple scripts would lead to an exponential amount of variations that could be very hard to cache effectively, as an update to one of them would require invalidating all variations that include it since HTTP/2 concurrent requests are very performant, and edge cases like slow networks are likely to improve with HTTP/3.
This also serves as a version control system using @ 1 in script tag allows us to push updates to solutions without requiring users to update script tags. If something breaks with CMS Nest, we can push a fix to all CMS Nest implementations.
Give your sidebar a defined height, this will allow you to scroll up or down.
Currently we do not support <script> tags inside collection items when using cmsload, give us some time to work on this.
This is Native behavior, you will get this with either native load more or attributes, each page query combination returns html that contains the Collection Items for that specific page of the Collection. If you are worried about crawling, you could try to add rel=nofollow to the Next and Previous buttons and submit your sitemap.xml to Google Search Console so the bots can still discover the Collection Items from there.
This can be achieved with a little custom JS, basically follow these steps:
1. Add the CMS Sort script after the CMS Combine script
2. Set up the sort attribute using this docs https://www.finsweet.com/attributes/cms-sort/
3. Set the sort button to display:hidden and give it a unique class name (ie. ".fs_cmssort_button"). Add the script below before the </body> tag
Our filter is designed to filter CMS collection items, if you are listing a collection list on the template page, it should work with just the normal implementation.
By default CMS filter will sort the list by alphabetical order, you can change this to chronological order by targeting the date which will change the sort order. However there is no current way to combine both sorting options.
First you have to use CMS combine then you will be able to filter both collections, this cannot be possible without CMS combine
There is no current workaround for this, please use this attribute carefully as to not cause major issues with your page’s interactions
Nest and Combine do not work together, Filter will work with either Nest or combine.
Trying to use the three at the same will not work.
1st activate SHOW QUERY , then apply the filters you wish and copy the URL then make it the link to the articles page. It will load the page with the filters preselected.
This is not posible because load under relies on webflow´s native pagination to work
Just set the checkbox’s state as checked on the designer
Add a “0” to the paragraph, text block or headline where you want to display your count then set it as the “fs-countitems-element=value”
Combine does not work with pagination at the moment
Then add the following script to the footer code.
It should be possible, just be sure that the template page has all the items that you need nested referenced on sthe page.
You can create a div with a message, image or just leave it empty and apply the “fs-cmsfilter-element=initial” attribute to it
Sure they can!
Yes, Attributes do work with API content/data, it is not limited to Webflow CMS content.
Yes, you can have several triggers for one target.
Yes, you are able to use them on all kind of pages.
This is the behaviour of webflow slider, we hope to have a solution soon.
Yes, they will not work together.
They are mandatory for the system. It was built as a solution that can manage enterprise-level filters. Forms allow for natural accessibility and screen reader functions. This also takes out the requirement to have multi and exclusive labeled filter groups.
The biggest update you have to make to go from CMS Library to Attributes is rebuilding any buttons/link-blocks/divs in your Filter UI to checkboxes or radios. Attributes using a form-based system for Filter UI.
Yes, up until December 31 - 2021. Starting Jan 1 - 2022, there will be no support given. Attributes will now be the product we support and continue development of.
You can if you want to. However, we highly recommend building any new projects with Attributes. Once we understand the difference between CMS Library and Attributes, you won’t want to use CMS Library. We also recommend converting active development projects that use CMS Library. Converting to Attributes is going to make everything look, feel, and function better.
Absolutely yes. CMS Library will not be turned off. Scripts will still work as normal. CMS Library will never be shut down since it is live on thousands of websites.
We recommend to use the native "Start checked" feature native in Webflow Settings.
This can easily be done using attributes, for your second slider onwards you need to add -x to the end of the value, "x" being a unique numeric identifier. Example for your second instance of the slider "fs-cmsslider-element = list-2" and "fs-cmsslider-element = slider-2" and so on.
This is caused by the threshold that has been set for when the infinite scroll is triggered (fs-cmsload-threshold = -20) play around until you find a value that works best.
The fs-cmsfilter-match attribute default is any, this will return any item that matches at least one filter from your search. The all value needs to be an exact match to return an item.
Yes. If you are using attributes, CMS Filter will work with CMS Load.
Define both filters under the same form block and hide/show respectively for either desktop or mobile.
Yes you can, add fs-cmsfilter-type = date to your element with fs-cmsfilter-field = "IDENTIFIER".
Use the fs-cmsload-resetix = true option on your list. This restarts Webflow’s interaction engine, which is required for newly rendered items.
This can be done with instances, you would need to add a new list to the page for each slider.
No it must be a form element for filtering, dropdown can be used for sort.
It uses the current state as if it were styled for a page. Choose your filter element, in the settings set it to the current page you’re on - it will show the ‘current’ state in the styles panel. Style accordingly then remove the link to the page.
Add this class to a blank div on the page, then set the background color. On the published page, the highlight color will be that new background color.
This is not possible with the current system. We have built is specifically to show and hide based on if it’s needed on the page.