Streaming live at 10am (PST)

Community Campaign For Feature Advancement: Tags! (Nested References)


#1

I have a dream… a dream wherein I could rally the Webflow community to hasten the development of nested collection lists!

The feature is marked “Planning” in the Wishlist (see it here: https://wishlist.webflow.com/ideas/WEBFLOW-I-15), but it desperately needs YOUR VOTE to help the company recognize the importance of delivering this basic feature that has been so sorely overlooked/delayed in what is otherwise an amazing advancement of a product in the most rapid way possible.

Seriously, how is the (IMHO) overly-upvoted “ecommerce” feature suppose to function without this feature?! A product page without categories, tags, or similar/suggested items?! Duh! I have had to steer away 4+ clients from the platform over the last few years because of this simple limitation, and these aren’t even ecommerce clients!

We need Webflow to roll this feature out as a priority! Perhaps if you all could list your plethora of examples that you’ve been stymied with in the comments as well, we’d get some faster traction on this feature (beyond voting of course.)

/end_rant


#3

Hi @chriscarlston – I’m one of the product managers here at Webflow, and am specifically focused on continuing to build out our CMS and Ecommerce functionality.

We completely understand, and share your strong desire to have Nested Collection Lists available for your projects. Honestly, it’s a limitation that I think I have personally run into and been frustrated by in almost all of my own CMS-based projects as well :sweat:

One of the big technical challenges that has stood in our way with this feature has been performance concerns. As you can imagine, with the ability to nest collection lists without any intelligent limitations, users can quickly get into situations where they are exponentially increasing the number of ‘dynamic’ elements that need to be queried for, rendered, and interacted with on their pages.

Unchecked, this could not only hurt the performance on the live published sites, but the Designer and Editor workflows for building out these sites as well. So we have wanted to proactively address some of these performance concerns prior to building out this feature.

The good news is that we are truly planning on pushing it forward in the near future!

First, though, we are tackling another major gap in our CMS functionality – the ability to paginate collection lists in your sites. Not only is this specific feature important on its own, however, it also will actually help address the performance concerns for nested collection lists in a way as well – by offering designers the ability to limit the number of collection list items being displayed in a page at any given time, but NOT limiting the ability for the end users of their sites to access more of the collection content through the pagination.

Second, we are continuing to invest more time/energy into further performance investigations and improvements that will help us with our development of Nested Collection Lists as well.

So… while it’s not yet imminent, this is definitely something that we are actively working on making possible as soon as we can based on these directly related projects, and balancing the other big initiatives that we are pushing forward as well.

I hope that helps at least provide a little more context, even if it isn’t exactly the answer you were hoping for. Just know that we hear you – and really do want this feature just as strongly!


Using multi-references to create tags
Categories and Subcategories
#4

@kkilat first off, thanks for taking time to address my rant in length!

Good insight in how it relates to pagination (workflows, server load, etc.). Small steps, I get it, I think.

I understand the need to throttle the exponential nature of database queries, especially with this feature request/need. Perhaps instead of hard limits, I wonder if some sort “score” metric could pop up when things get “heavy”… metered with a warning, escalating to a forced limit to paginate/limit queries on a single page.

All this is also needs to take into account the “invisible” state of server-side rendering of pages… which is complicated with the existing feature of setting any list call to “random.” I would gladly give up “random” for nested references!

I may be way off, but thanks again for the reply and know that I am eager for the feature! In the meantime, I still think if this feature gets more votes, it will help everything along!


#5

Perhaps instead of hard limits, I wonder if some sort “score” metric could pop up when things get “heavy”… metered with a warning, escalating to a forced limit to paginate/limit queries on a single page.

Yeah, there are definitely some interesting ideas to consider here around providing more information and guidance rather than hard limits. Thanks for sharing!

I still think if this feature gets more votes, it will help everything along!

:100: I voted!