Description: we aim to iterate on the product types step, in order to increase the number of users that select useful extensions
Acceptance Criteria:
Event tracking:
Probably it won't be necessary additional tracking
Additional links:
Design mockup
Estimate: 2
Estimate: 2-3
My only concern is changing and formatting those prices from the wccom REST API as monthly prices instead of annual.
Agree on @becdetat 's estimate of 2 (assuming we can use our existing <Count /> component), and share @joshuatf 's concerns about the potential need to change the WCCOM API. (or can we just divide by 12?)
Question for @jameskoster on the pill/count component color - we just removed a lot of purple from the UI.. are we using purple for this?
(or can we just divide by 12?)
After dividing and parsing, I think we can. It includes an encoded HTML entity for currency that needs to be stripped first and added back on. Nothing too crazy, just not exactly what you'd expect from the API response:
https://woocommerce.com/wp-json/wccom-extensions/1.0/search?category=product-type
Question for @jameskoster on the pill/count component color - we just removed a lot of purple from the UI.. are we using purple for this?
Most likely yes :) The thinking is to be way more intentional when we apply any in-product branding (using purple). The latest direction is essentially to use it around any features that require some interaction or connection with woocommerce.com or wordpress.com. IE purchasing / installing extensions, setting up WCPay, or WCServices.
Display monthly pricing instead of annual
I know this is a much larger discussion, but I am definitely not a fan of our displaying of monthly prices when we bill annually. But, I get it.
Do any of the prices vary based on other options being selected on this screen? Or, are they all completely decoupled?
<Count /> currently only shows a number, correct? So, we'd have to extend it to allow for a formatted string to be passed in. At which point, it isn't really a count anymore. So, it shares styling/layout with <Count />, but seems distinct.
I'd go with an estimate of 2.
Duh! Thanks for catching that @mattsherman.
With #4707 merged, I think we can close this out now.
Most helpful comment
Estimate: 2