adobe.com
Replies: 4 comments 5 replies
-
|
Suggestion for the names (extracted from the catalog page):
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks @yesil the only change I would make is to remove "dc" from any of the "acrobat" product names. We had an Acrobat "DC Sku Lineup" project this year and "DC" was removed from the Acrobat product titles across the site. So would be good to avoid adding "dc" in any naming. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I updated the list. |
Beta Was this translation helpful? Give feedback.
-
|
@geri-w I noticed many pages on BACOM have different names than on catalog, can someone from bacom review the list above and approve? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @yesil I don't see Rikio here, so tagged him regarding this in the milo-commerce Slack channel: https://adobedotcom.slack.com/archives/C0475EYRAKA/p1699888970405699?thread_ts=1699865241.146699&cid=C0475EYRAKA |
Beta Was this translation helpful? Give feedback.
-
|
i updated the catalog milo blocks with proper terms! |
Beta Was this translation helpful? Give feedback.
-
|
@yesil I don't know if this is covered already by other means, but the segment type is also a key differentiator as you can have card variations for a single app for individuals, business, students for instance. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @drew-cottrell that's a good point. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the list of all product names and their CaaS tags as shared by Rikio in slack: In this regard, can we ask all BU to provide their actual product titles and tags or a technical name . cc: @geri-w ? |
Beta Was this translation helpful? Give feedback.
-
Addressable product names like
photoshop,acrobat-pro,all-appsare used at several places such as deep-linking, personalisation, etc.Currently, merch-cards blocks are not instrumented with product names.
Given that we know in advance the entire list of products, I propose the following approach for the authoring of merch-cards:
Engineering: keeps the full list of product names in the code and check the merch-card block metadata against this list before assigning product name to a card.
e.g:
GWP: authors cards, and the last
classin the block should correspond to the product name.The latter is not mandatory, but will be needed for both plans and catalog cards.
When used, it can also be leveraged for MEP.
Later we can extend the usage of this list for entitlement awareness, upgrade flow, etc.
Alternatively this list can be maintained in Excel but, for the sake of performance, and given its semi static nature, we can start with keeping it next to the code.
Beta Was this translation helpful? Give feedback.
All reactions