UX guidelines

• Use clear and descriptive names for your editor extension collections. Names should clearly describe the customer experience that the collection provides. For example, “Subscription management” or “Loyalty program”.
• Avoid using jargon or technical terms that merchants might not understand.
• Avoid using emojis.
• Editor extension collection names must be 50 characters or less.
• Editor extension collection handles must be 255 characters or less.

• An editor extension collection should consist of two or more extensions that work together. For example, group extensions that are used together in a specific workflow, such as grouping a loyalty banner that is displayed on the Profile page with a Loyalty Full page extension that contains loyalty points details.
• One extension can belong to multiple editor extension collections.
• Avoid grouping by UI type. For example, don't group all banners together.

One extension can target multiple pages. For example, an extension can be added to both the Checkout and Order status page. In this case, the merchant can choose which page to place the extension on.