[Feature request] Unified resource shapes and input types

Shopify has 4 resource types that are returned in search results and commonly displayed in a card format: product, collection, article, page.

Product, collection, and article all have “featured media” associated with them. Page does not.

When building card-based layouts in the theme editor we have:

  • product and product_list
  • collection and collection_list
  • article but no article_list
  • page but no page_list

Adding article_list, page_list and page.image would be a big win.

Type Single Input List Input Media
Product :white_check_mark: :white_check_mark: :white_check_mark:
Collection :white_check_mark: :white_check_mark: :white_check_mark:
Article :white_check_mark: :cross_mark: :white_check_mark:
Page :white_check_mark: :cross_mark: :cross_mark:
1 Like

Seconded, that would be helpful and unified structures is a definite win !

Hey folks :waving_hand: - thanks for flagging this. As always, I can’t guarantee anything, but I’ll do some digging into this to see if it’s on our roadmap/if we can share any further info with you folks or at the very least set up an official feature request on our end.

I’ll loop back with you all here once I have more info :slight_smile:

1 Like

Hi all, just wanted to follow up here. I was able to touch base with our product team, and did confirm that this isn’t currently on our roadmap, but I will log a feature request on my end for you folks so that we have this documented.

I can’t guarantee when/if this would be implemented, but it is something that is now on our radar.

Hope this helps a little bit, please feel free to share any additional info and I’d be happy to add it to the feature request on my end.

1 Like

The best solution though would be that the search would work the same way as the predictive search, so instead of returning for instance 50 results with everything mixed up, it would return 50 per resource.

We’re using a tab approach for all our themes as we feel that mixing products, blog posts or page in the same list makes no sense, but this approach requires us a ton of hack and JS based approach that would be so much better solved in Liquid:

Thanks @bakura10 , appreciate you following up here as always :+1: . Wanted to confirm that I’ve logged this request and added the additional details you shared.

1 Like