Let's say you're asked to generate a vibrant "print" catalog from a db of 100 consumer products.
It can't look "generated" like a table of products- it has to be a nice layout catalog, NOT something like https://www.mcmaster.com
The goal is to hand somebody a color printed catalog on paper.
The existing print catalog is VIBRANT. Products appear fanned out, display racks are smartly positioned next to products, etc. But it's a nightmare for the designer to make by hand and keep updated x 5 regional versions.
Each product has 5 properties that can be shown in a floating table, which partly overlaps the product pic in a non-critical corner: price, SKU, foo, bar, etc
Question:
Is it possible to programmatically generate something like this without it ultimately looking like grid-based slop?
Would an LLM be able to generate this with content-aware styling per-page, so that one page doesn't look like the next? E.g. if a product has a "freeze/cold/winter" flavor, then that page is ice-blue, whereas the next page is about an egg cooking product so it's orange/yellow.
How would you approach programmatically generating a product catalog that doesn't end up looking generic and ugly?
0 comments
—
Ask HN: Is it impossible to generate this programmatically? · HackerTrans
It can't look "generated" like a table of products- it has to be a nice layout catalog, NOT something like https://www.mcmaster.com
The goal is to hand somebody a color printed catalog on paper.
The existing print catalog is VIBRANT. Products appear fanned out, display racks are smartly positioned next to products, etc. But it's a nightmare for the designer to make by hand and keep updated x 5 regional versions.
Each product has 5 properties that can be shown in a floating table, which partly overlaps the product pic in a non-critical corner: price, SKU, foo, bar, etc
Question:
Is it possible to programmatically generate something like this without it ultimately looking like grid-based slop?
Would an LLM be able to generate this with content-aware styling per-page, so that one page doesn't look like the next? E.g. if a product has a "freeze/cold/winter" flavor, then that page is ice-blue, whereas the next page is about an egg cooking product so it's orange/yellow.
How would you approach programmatically generating a product catalog that doesn't end up looking generic and ugly?