Milo Commerce - Plan type selection

[npeltier]

we have plan type selections at different places with often bound to it:

• a price (that changes depending on the selection, and checkbox state)
• a cta (that changes depending on the selection, and checkbox state)
• a checkbox to add additional stock offer to it

generally, that whole setup is only bound to one product, and the choice is only for plan type. the order of the plans is often the same for every products of a given locale. web commerce service api has been designed to eventually get all plan types in one request, wonder if we should not make that whole one reusable functionality, some kind (sorry for the prehistorical words) of model that would have different possible views.

[honstar]

A big +1 to this! Such a commerce model you're referring to should be built at the heart of milo so that blocks have access to the required data.

[honstar]

How about either extending the section-metadata block or adding a commerce specific metadata block altogether? Guess it probably depends on the number of arguments that need to be passed in, the OSI being the only mandatory one, right @npeltier ?

@auniverseaway @chrischrischris , wdyt?

[auniverseaway]

In general I'm a +100 for having a content model ironed out before any real development work is done. We did this for carousel, tabs, and a few others where there were some different ways we could approach the problems.

For the comments above, these concepts sound a bit abstract and I would want to see what the content model actually looks like.

From the Franklin manifesto:

https://www.hlx.live/docs/manifesto#more-code-less-blah-blah-c