I need help designing a search feature for my CMS where users can select multiple keywords like 'adventure' or 'vacation' instead of typing in a text box. Currently, I'm struggling to implement a tagging system that allows for this functionality. I can filter items, but I'm not sure how to save the selected keywords within the articles that match. This needs to function like a non-text input survey. I'm using Framer and it's quite urgent that I figure this out!
4 Answers
To implement multi-keyword filtering in Framer, just store the selected keywords in an array and filter your CMS items by checking if their tags include all (or any) of the selected keywords. Using multi-reference fields in Framer CMS is a smart way to tag each journey with multiple keywords, and then you can filter using that selected array.
This seems less like a search bar issue and more like a data modeling challenge. If the tags aren’t stored consistently in your CMS, the filter will likely feel clunky. I'd recommend addressing the content structure first; once that's sorted, the UI becomes much easier to handle.
Great point! I've tackled something similar not long ago. If you need any extra tips, feel free to reach out!
Hey, as far as I know, Framer doesn't natively support multi-select for CMS fields yet. But, there's a workaround! You can use a Plain Text field in your CMS and write your tags separated by commas (like: adventure, vacation, nature). For the interface, you can utilize a Code Override. Store the clicked tags in an array using Framer Data and then apply a filter override to your Collection List. Since you need this done quickly, search for 'Framer multi tag filter code override' on the Framer Community forum or YouTube; there are snippets available that will fit your needs perfectly! Good luck!
I figured it out! By creating a CMS for keywords and linking it to my articles, I can now use multi-reference tags as filters. I'm currently working on the search modal.
You're right! Instead of using plain text for keywords, I changed it to a CMS structure, and now it works perfectly. Thanks for the advice!