CMS Attributes + External Data - Part 1

[@rahuli]

This is so exciting! Can't wait to put this into use

[@Finsweet]

Looking forward to seeing what you build with it.

[@albertfranklin2317]

Now, No-Code meets Code. Great stuff Alex and Finsweet. This opens up a lot of possibilities for back-end devs.

[@Finsweet]

When our powers combine! 💪

[@infiltretor287]

With all of the new advancements in Finsweet and Webflow in the past year, does this still work the same way?

[@Vimalanvijay]

Alex can talk code all day and it will never be boring 🔥🔥 greattt stuff!!

[@Finsweet]

We all agree!

[@elchinhuseynli8876]

I want to learn js from Alex 🎉

[@Finsweet]

Get in line!

[@babusgabriel]

Oh god, this day has finally come 😵 So much to learn from this one. More content like this 🔥

[@Finsweet]

We're just warming up

[@frankdrolet9439]

Wooooo, Finsweet killing it as always, much love for ya!

[@Finsweet]

Thank you Frank!

[@ikleveland]

Jesus, this is insane !

[@Raymmar]

You know how we do

[@yash7630]

How does this effect SEO?

[@JamesVreeken]

Mind blown... thanks this is so helpful. I'm going to start using this asap.

[@FramecoreSweden]

Hey guys, thank you for this, very cool stuff! But, I need to ask, what do you mean is the purpose of "replacing" existing CMS collections of data with an external API's data? Wouldn't it be better to just code a solution to display these directly? Or is it to be able to use your attributes-tools on them maybe?

[@rene3646]

Same question here

[@tomvoltz7506]

Great! Thanks! Does this really mean we are no longer limited to 2.000 or 10.000 records inside the CMS?

[@alexiglesias_me]

You can load as many items as you want from an external source

[@erihuynh1905]

thank you so much! It is a good way. I think, can this way work with Slider components? I need to dynamic with external API + webflow?

[@alaindescoux5707]

This is very great and insane, but the page is not crawlable for Google... :'(

[@alexiglesias_me]

Hey Alain! Of course when your rendering external data in the frontend, you'll always give Google a harder time to index your content (although nowadays Google knows how to run JavaScript and does it from time to time). If your main priority is SEO for the data in the Collection List, then you should consider moving it into the native CMS instead of fetching externally!

[@James-om5bj]

This is so hype! Is it possible to hook into the pagination events to fetch more data from the API and append it to the CMSList.items array? Or does pagination require fetching all data before rendering the list?

[@alexiglesias_me]

You can listen to listInstance.on('switchpage', (targetPage) => {}) to detect when the user navigates through the pages using pagination mode, and then you can just add more items using the listInstance.addItems() method. I'll update the docs to add this info!

[@James-om5bj]

@@alexiglesias_me looove that

[@qrtois]

What if item in external JSON data has multiple categories for one item, like a: "t-shirt, polo, underwear" etc. will it work?

[@lucasrochas2008]

You guys never disappoint 🔥🔥🔥

[@Finsweet]

💪

[@elaysoiferman3641]

I love you

[@Finsweet]

We love you too!!!

[@kai4824]

Possible to make a webflow website with headless Magento with this?

[@gmcwhinney]

This is awesome, Alex! Quick question, is this AJAXy in that the external source data can change and Attributes can just pick up on that immediately and update the list?

[@alexiglesias_me]

Hey Glenn! I'm afraid I didn't understand the question, could you rephrase it? Thanks!

[@JamesVreeken]

If the external data changed you would just have to refresh the page for the updated data to be seen. It's not going to be actively listening for the external data to change, however you could do something like that using websockets if you wanted to.