You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current situation with images is that the Product generator will "seed" images by querying for existing images in the Media Library (10 by default), and then if there aren't enough existing images available, it will generate some using the Jdenticon library. This seed query happens for every product generated.
The Jdenticon images look like these:
Quite abstract, but they are simple and relatively efficient to generate. Although, from some basic profiling, it looks like the image part of the product generation command is the biggest bottleneck.
I think this situation could be improved in a few different ways, for different use cases, by adding a parameter to the product generation command for images with options for abstract, realistic, existing, and none:
abstract would use the Jdenticon images. But it would generate some up front and stash their IDs in a runtime cache, rather than querying for them every time.
realistic would try to sideload images from a placeholder image generator that uses something like Unsplash for a back end (more on this below). This would obviously not be suitable for large batches, but the images could match the products better, which might be more useful in some cases.
existing would randomly select existing images from the media library, but not generate anything new. This would probably be the default option.
none would not add any images to generated products. This would be useful for large batches of products where the images aren't really the point.
For the realistic option, there are a few different online placeholder image generators available, some of which take a search parameter. This would allow for including the product name in the image query and getting back an image that at least somewhat resembles the generated product. We'd probably want to put a low limit on the number of products that could be generated with this, though (20? 50? 100?). Some placeholder generator options with image querying capabilities:
To compliment the existing option, we could also create a new generator command specifically for product images. That way, images could be generated first, and then could be used when generating products, but much more efficiently.
The text was updated successfully, but these errors were encountered:
The current situation with images is that the Product generator will "seed" images by querying for existing images in the Media Library (10 by default), and then if there aren't enough existing images available, it will generate some using the Jdenticon library. This seed query happens for every product generated.
The Jdenticon images look like these:
Quite abstract, but they are simple and relatively efficient to generate. Although, from some basic profiling, it looks like the image part of the product generation command is the biggest bottleneck.
I think this situation could be improved in a few different ways, for different use cases, by adding a parameter to the product generation command for images with options for
abstract
,realistic
,existing
, andnone
:abstract
would use the Jdenticon images. But it would generate some up front and stash their IDs in a runtime cache, rather than querying for them every time.realistic
would try to sideload images from a placeholder image generator that uses something like Unsplash for a back end (more on this below). This would obviously not be suitable for large batches, but the images could match the products better, which might be more useful in some cases.existing
would randomly select existing images from the media library, but not generate anything new. This would probably be the default option.none
would not add any images to generated products. This would be useful for large batches of products where the images aren't really the point.For the
realistic
option, there are a few different online placeholder image generators available, some of which take a search parameter. This would allow for including the product name in the image query and getting back an image that at least somewhat resembles the generated product. We'd probably want to put a low limit on the number of products that could be generated with this, though (20? 50? 100?). Some placeholder generator options with image querying capabilities:Some other, more basic placeholder generators:
To compliment the
existing
option, we could also create a new generator command specifically for product images. That way, images could be generated first, and then could be used when generating products, but much more efficiently.The text was updated successfully, but these errors were encountered: