Now, building on the idea above, @postzilla.app, it occurs to me that one of the problems with “order” fields and the idea above is… WHAT IF I don’t want to manually reorder every damn product in my database. That seems oppressive, right?
So, instead of thinking of my “Default Product List” as a list of ALL products in a special order, instead I can consider as a “Featured Product List” (and I’d change its name to that). Now, what this list is going to represent is any product I want featured at the top of the Products list when a user hasn’t otherwise sorted or refined it (and the products in that list appear in an order of my choosing).
And now what I do is I only put Products into that list that I want to feature. So, again, with my admin page, I build a little widget that lets me put any Product into that list (it’s just like a cart, right? but it has shifting features). Here’s a really shitty example of doing that – when the FTR button is clicked, I toss that item into the “Featured Products” object’s list of products:
And now, I just take that truncated list… Dog Dogs, Canned Cat, maybe Gun Brand Cigarettes (which, truth be told, may possibly be dangerous) and save that as the Products field on my “Featured Products List”.
And now, when the user visits my store page, I populate the “products” repeating group with:
Do a Search for Featured Products :first item's Products :merged with [some search or a list shifter or whatever that has ALL products in it]
And now we see how damn clever it is that Bubble lists don’t hold duplicates… Because what happens is now my featured items are at the top of the list and my other items are in whatever order the :merge part is in. Just to prove this works, here’s a picture!:
And my featured items only appear once, in the top of the RG. Cool, right?
“Featured Items” is totally something I can get behind, BTW.