This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 50
Home
Oleksandra Marchenko edited this page Sep 20, 2022
·
51 revisions
The below lists Adobe replacement terms for Magento in our support knowledge base.
Notes about rebranding:
- For now do not rebrand/rename Magento modules as in general modules have not been renamed.
- Avoid making changes to steps to reproduce or solution steps: apart from replacing "the Magento admin" with "the Commerce Admin".
- DO NOT change names that refer to click-able elements in the Magento interface, code, modules, directory names, keywords that are used for search etc
Note about article labels:
- Do NOT remove labels from old articles. We need to keep them because our customers may still be searching for our articles using terms like “Magento Commerce”. You can add like new labels “Adobe Commerce”.
- Also add a “Magento” label to any new articles for the same reason, SEO, as well as the other new branded name labels.
- Do not add "Adobe Commerce" label several times, if the article applies to both on-premises and cloud, add "Adobe Commerce", "on-premises","cloud infrastructure".
- When articles mention pro and starter just say "Pro" and "Starter" in labels. However, the full name which should be used in the body of articles is "Adobe Commerce on cloud infrastructure Pro plan architecture" in the first instance and then in rest of the article "Pro architecture" to keep it short. For starter it is "Adobe Commerce on cloud infrastructure Starter plan architecture" but in rest of the article, we say "Starter architecture" to keep it short.
- Use "Magento Open Source" as a label, not "open source".
| Current content example | Content example (rebranded) |
|---|---|
| Magento Commerce Cloud | Adobe Commerce on cloud infrastructure |
| The Magento Enterprise Cloud Edition | Adobe Commerce on cloud infrastructure |
| Magento Commerce On-Premise | Adobe Commerce on-premises |
| Magento Commerce (all deployment methods) | Adobe Commerce (all deployment methods) |
| Magento code | code for Adobe Commerce & Magento Open Source (assuming works for both) |
| Magento status | Adobe Commerce status |
| Magento Knowledge Base | Adobe Commerce Support Knowledge Base. When citing "in our support knowledge base". |
| Experience League | Adobe Experience League. Example: "Refer to ... in the Adobe Experience League documentation". |
| Magento support | Adobe Commerce support |
| Magento patch | Follow style guide in devdocs release policy https://devdocs.magento.com/release/policy/ So can say "This article explains how to use a new security patch from Adobe Commerce..." or "This article explains how to solve with a hotfix provided by Adobe Commerce.." |
| Magento Quality Patches tool | Quality Patches Tool (most common name in MQP articles) |
| Magento Quality Patches | quality patches for Adobe Commerce and Magento Open Source / Quality Patches |
| Magento marketplace | Commerce Marketplace |
| Citing from DevDocs | Simple citation: <Article topic> in our developer documentation / <Topic title> in our developer documentation. To differentiate between instructions in devdocs for cloud vs on-premises users you can say:
or
|
| Citing from Magento User Guide | <Article topic> in our user guide / <Topic title> in our user guide. |
| Magento Commerce Cloud Pro | Under Affected versions and products we say "Adobe Commerce on cloud infrastructure Pro plan architecture". But in rest of the article we say "Pro architecture" to keep it short. |
| Magento Commerce Cloud Starter | The first instance in an article, for example under Affected versions and products, we say "Adobe Commerce on cloud infrastructure Starter plan architecture". But in rest of the article we say "Starter architecture" to keep it short. |
| Magento certification | Adobe Commerce certification |
| the Magento Admin | If the article is clear that it is describing an issue/problem in Adobe Commerce just say "the Admin" but if not clear consider saying "the Commerce Admin". |
| Magento B2B | B2B for Adobe Commerce. Then just say "B2B functionality". |
| Magento PWA | PWA Studio for that tool/feature. When talking about PWA or other PWA elements OUTSIDE of PWA Studio use "PWA for Adobe Commerce". |
| Magento Venia storefront | Shorthand say "Venia storefront". Long definition: "Venia storefront is a PWA Studio based proof-of-concept designed specifically for Adobe Commerce and is built using PWA Studio Buildpack tool and PWA Studio Peregrine components". |
| Magento account | If this is only for paid licenses, it should be Adobe Commerce Account, if it can be for Magento Open Source also, you can use Commerce Account. In most cases, you will be writing about issues with Adobe Commerce Account. |
| Magento Business Intelligence | Magento Business Intelligence |
| Magento U / University | Adobe Learning Services |
| Magento extensions | Extensions |
| Magento store | "Adobe Commerce or Magento Open Source store", and then just "store" or "Commerce store" |
| Magento documentation | Adobe Commerce documentation |
| Magento installation | Adobe Commerce or Magento Open Source installation / Commerce installation |
| Magento data or Magento database | Adobe Commerce data / Adobe Commerce database |
Magento <2.x.x> release |
<2.x.x> release Adobe Commerce and Magento Open Source <2.x.x> release Magento Open Source <2.x.x> release Adobe Commerce <2.x.x> release |
| Magento CLI | Adobe Commerce or Magento Open Source CLI / Commerce CLI |
| Magento instance | Adobe Commerce or Magento Open Source instance / Commerce instance |
| Magento integration | Adobe Commerce or Magento Open Source integration / Commerce integration |
| Magento catalog | Adobe Commerce or Magento Open Source catalog / Commerce catalog |
| Magento P1 notification hotline | Adobe Commerce P1 notification hotline |
| Magento Services(when talking about https://docs.magento.com/user-guide/system/saas.html) | Commerce Services |
| Magento Order Management System (OMS) | The first time the term appears in an article we introduce the product as “Magento Order Management System (OMS) for Adobe Commerce” and then just refer to “OMS” in the rest of the article |
| Magento 2 | Adobe Commerce |
| Magento module | The first time in an article say Adobe Commerce module and then add limit to "module" |
| Magento Inventory (MSI) | Inventory Management (MSI) |
| Magento ID | Magento ID |