Ability to add columns to "grid" DPF/outcome product containers

Hey Jon,

Thanks for the explanation. I would argue that a max of the ability to add at least 4 columns would be a sweet spot, and the client can add or remove as needed on a case-by-case basis for their product possibilities.

If a user is only matched with 1 product, then it technically defaults to 1 column. I see the logic behind having a default of 2x2, and I think it should be maintained, but the option to add more columns would be a nice customization capability. Shane Company is requesting this, and we are having to use CSS.

Hi Sav! Great suggestion. I just wanted to explain why it works the way it does and why this is tricky. With the product feed, because the matching is dynamic, we don't know how many slots will actually be filled (with exact match). So you would need to plan your columns/grid for every permutation of matched products. What we tried to do was come up with a logical default structure based on the number of matched products and the container size. At a certain point adding too many products to one row doesn't look right, so our out of the box sizing seems to work nicely most of the time.
I was curious how you would attack this problem, and what didn't size properly for you.

Thanks for the idea!