Somehow I have a feeling this request overlaps a bit with the request from here where you want to heavily influence the output structure of the resulting representations.
Like Mustafa wondered, the AYON template customization possibilities are currently “per product” and not down to each individual representation. Which of course makes it hard to nudge them into individual folder structures in its current templating design.
Not to say that it never could, but I think some changes would be needed to get to supporting that. (Tagging @philippe-ynput for visibility)
However, I also want to bring up that it seems you’re heavily trying to design the “published” file structure for something to navigate through and I wonder why that is. The aim would be that one never or rarely would need to go those files in explorer - and instead work towards making the files accessible, from anywhere in the pipeline in the means that you need.
Which leaves me to the question: why do you need it structured that way?
Preferably getting to the previews is right at your fingertips, without ever needing to open an explorer and browse to a folder manually.