Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Facets for specific Devices in Strapi #587

Open
jeffsnyder opened this issue Aug 4, 2022 · 3 comments
Open

Define Facets for specific Devices in Strapi #587

jeffsnyder opened this issue Aug 4, 2022 · 3 comments
Labels
external_block QA is not testing this (yet?) needs_more_spec

Comments

@jeffsnyder
Copy link

jeffsnyder commented Aug 4, 2022

We want to set facets on specific ProductLists and, if possible, have all children and grandchildren inherit the given facet.

Per our Samsung partnership, we cannot link from Samsung to pages that show Aftermarket parts. A solution would be to add a facet for our OEM partnerships and pre-select the preferred option via the URL like we can do with https://ifixit.com/Parts/Google_Phone?filter%5Boem_partnership%5D%5B0%5D=Genuine%20Google%20Pixel%20Part . But unless we add the facet to the facet list, shoppers won't be able to unselect the option. And if we add "OEM Partnership" to our standard list of facets right now, the whole browse tree will get this option, and I'd rather not draw attention to the fact that a very small percentage of our parts are genuine OEM parts.

So we need to do two one things:

  1. Build a feature that allows facets to be added to the standard list of facets in Strapi. If possible, these custom definitions would be inherited down the tree. This feature would be very useful, we dropped many facets because they were too device-specific.

2) We should consider making selected filters persist when clicking on a model drilldown. Clicking any of these models takes you to an unfiltered ProductList. (Maybe what we're doing right now is most correct. I'm trying to anticipate Samsung objections, and they likely will not be ok with switching from OEM to all parts without the customer specifically turning off the OEM filter.)

image

@sterlinghirsh

@sterlinghirsh sterlinghirsh added the external_block QA is not testing this (yet?) label Aug 10, 2022
@sterlinghirsh
Copy link
Member

Let's consider just adding OEM Partnership at the top level and decide if we want to whitelist/blacklist and how inheritance should work.

@dhmacs
Copy link
Contributor

dhmacs commented Oct 26, 2023

Is this still relevant?

cc @sterlinghirsh @jeffsnyder

@sterlinghirsh
Copy link
Member

I think generally we'd still like to do it, but I don't know what the priority is. I'll defer to Jeff here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external_block QA is not testing this (yet?) needs_more_spec
Projects
None yet
Development

No branches or pull requests

3 participants