These are chat archives for mirumee/saleor
Would adding a "related_objects" (one to many) to the category and collection model sound a weird idea?
To explain the case, let's say: we have a category (or collection) of "Wall mounted lights", user may want to look for mounting accessories, that's where the related objects field enters in action: "you may also be looking for/ be interested for: wall mounting accessories"
It also prevent from adding a child to a category that would mess up the product listing by adding both screws, power supplies, accessories, ... to lights (which is really, really, really a nightmare in saleor as the current customization limits)
Then, of course, we can link specific product accessories compatible to a given produc through the description page. Or a db relation as well.
To disclaim: user may want to look for those accessories, not to buy both the light and the accessories (especially power supplies)
Yes, to allow (and help) the user to bundle a product with potential wanted accessories.
But for the category/ collection side, it would allow to redirect the user to potential stuff they may be wanting to look at. Thing that child categories cannot provide as they would be loaded in the parent category (messy)
draftailby the Wagtail community that allows rendering draft.js blocks using Django on the server