Skip to content

Commit 7a7f142

Browse files
committed
add scrnshts, to place later
1 parent 922ca03 commit 7a7f142

5 files changed

Lines changed: 62 additions & 15 deletions

File tree

102 KB
Loading
102 KB
Loading
22.7 KB
Loading
118 KB
Loading

microsoft-edge/extensions-chromium/publish/publish-extension.md

Lines changed: 62 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
88
ms.subservice: extensions
9-
ms.date: 12/16/2024
9+
ms.date: 12/30/2024
1010
---
1111
# Publish a Microsoft Edge extension
1212

13-
After you develop and test your Microsoft Edge extension, you're ready to distribute your extension. Use the Microsoft Edge Add-ons website to distribute your extension. To release your existing Chromium extension for Microsoft Edge users, see [port your existing Chromium extension](../developer-guide/port-chrome-extension.md).
13+
After you develop and test your Microsoft Edge extension, you're ready to distribute your extension. Use the Microsoft Edge Add-ons website to distribute your extension. To release your existing Chromium extension for Microsoft Edge users, see [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md).
1414

1515
Publish your extension to the [Microsoft Edge Add-ons website](https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home) to increase its reach and make it available to other Microsoft Edge users. This article provides the process to submit your extension to the Microsoft Edge Add-ons website.
1616

@@ -30,37 +30,35 @@ Before publishing your extension, you should have a working prototype of your ex
3030
<!-- ---------------------------------- -->
3131
#### Create a developer account
3232

33-
To publish your extension to the Microsoft Edge Add-ons website, use your active developer account on [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). If you don't have a developer account, create a new developer account. To open a new developer account and register to the Microsoft Edge Add-ons program, see [Developer registration](create-dev-account.md).
33+
To publish your extension to the Microsoft Edge Add-ons website, use your active developer account on [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). If you don't have a developer account, create a new developer account. To open a new developer account and register to the Microsoft Edge Add-ons program, see [Developer registration](./create-dev-account.md).
3434

3535

3636
<!-- ---------------------------------- -->
3737
#### Create a zip file for your extension package
3838

3939
Create a zip file for your extension package. Your extension package must include the following files:
4040

41-
* The extension manifest that specifies details such as the name of the extension, short description, permissions, and default language.
41+
* The extension manifest that specifies details such as the name of the extension, short description, permissions, and default language.
4242

43-
* Images and other files required by your extension.
43+
* Images and other files required by your extension.
4444

4545

4646
<!-- ---------------------------------- -->
4747
#### Review manifest field values
4848

49-
The following fields in the manifest file are automatically included in your store listing details. The fields are read-only on the **Store listings** webpage (described below).
49+
Before uploading your package to Partner Center, inspect the manifest file to make sure that the field values match your preferred display on the **Store Listings** webpage, as follows.
5050

51-
Before uploading your package to Partner Center, inspect the manifest file to make sure that the field values match your preferred display on the store details<!-- todo: what title of webpage? bold --> webpage.
52-
53-
In the manifest file, review these fields:
51+
The following fields in the manifest file are automatically included in your store listing details. The fields are read-only on the **Store Listings** webpage, which is described below.
5452

5553
* The `Name` field, which populates the **Display name** on the store details<!-- todo: what title of webpage? bold --> webpage.
5654

5755
* The `Description` field, which populates the **Short description** on the store details<!-- todo: what title of webpage? bold --> webpage.<!--todo: confirm "description" vs "short description" in manifest vs. store webpage-->
5856

5957
Fill in the `Description` field, to explicitly provide a catchy description that will be displayed at the top of the listing for your extension.
6058

61-
* If you include a `short description` in the extension manifest file, that short description is displayed in your store listing.
59+
* If you include a `short description` in the extension manifest file, that short description is displayed in your store listing.
6260

63-
* If you don't include a `short description` in the manifest file, the first few lines of the `Description` are displayed in your store listing. We recommend providing a `short description`, to avoid content repetition on your store listing webpage.
61+
* If you don't include a `short description` in the manifest file, the first few lines of the `Description` are displayed in your store listing. We recommend providing a `short description`, to avoid content repetition on your store listing webpage.
6462

6563

6664
<!-- ========================================================================== -->
@@ -88,6 +86,30 @@ Details are below.
8886
1. On the **Overview** webpage, select **Create new extension**.
8987

9088

89+
<!-- todo: move to right spot: -->
90+
Editing details from listing page to enter the description: **Extension overview** > **Details for English (United States)** page:
91+
92+
![Edit details from listing page enter desc](./publish-extension-images/edit-details-from-listing-page-enter-desc.png)
93+
94+
95+
<!-- todo: move to right spot: -->
96+
Extension page for a specific extension: **Extension overview** page:
97+
98+
![Extension page for a specific extension](./publish-extension-images/extension-page-for-specific-extension.png)
99+
100+
101+
<!-- todo: move to right spot: -->
102+
Partner Center extensions home: **Overview** page:
103+
104+
![Partner Center extension home](./publish-extension-images/partner-center-extension-home.jpg)
105+
106+
107+
<!-- todo: move to right spot: -->
108+
Store listing section for an extension: **Extension overview** > **Store Listings** page:
109+
110+
![Store listing section for an extension](./publish-extension-images/store-listing-section-for-extension.png)
111+
112+
91113
<!-- ========================================================================== -->
92114
## Step 2: Upload the extension package
93115

@@ -214,9 +236,9 @@ You can duplicate your assets from one language across other languages by using
214236

215237
Make sure your video meets the following requirements.
216238

217-
* Verify that the content of the YouTube video follows the [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies).
239+
* Verify that the content of the YouTube video follows the [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies).
218240

219-
* Turn off advertisements on your video. For more information, see [Set your default ad formats](https://support.google.com/youtube/answer/2531367?ref_topic=7072227) and [Ads on embedded videos](https://support.google.com/youtube/answer/132596).
241+
* Turn off advertisements on your video. For more information, see [YouTube advertising formats](https://support.google.com/youtube/answer/2467968?ref_topic=7072227) and [Ads on embedded videos](https://support.google.com/youtube/answer/132596).
220242

221243
To submit the YouTube video URL of your video:
222244

@@ -284,5 +306,30 @@ If you encounter any issues in the submission or registration process, file a su
284306

285307

286308
<!-- ========================================================================== -->
287-
<!-- ## See also -->
288-
<!-- todo: all links in article -->
309+
## See also
310+
<!-- all links in article -->
311+
312+
Local articles:
313+
* [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md)
314+
* [Extension concepts and architecture](../getting-started/index.md)
315+
* [Developer registration](./create-dev-account.md)
316+
317+
Partner Center:
318+
* [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd)
319+
320+
Edge Add-ons website:
321+
* [Microsoft Edge Add-ons website](https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home)
322+
323+
Developer Agreement & Legal:
324+
* [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905)
325+
* [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies)
326+
327+
Support.microsoft.com:
328+
* [Extensions New Support Request](https://support.microsoft.com/supportrequestform/e7a381be-9c9a-fafb-ed76-262bc93fd9e4)
329+
330+
Support.google.com:
331+
* [YouTube advertising formats](https://support.google.com/youtube/answer/2467968?ref_topic=7072227)
332+
* [Ads on embedded videos](https://support.google.com/youtube/answer/132596)
333+
334+
Extensions Reference:
335+
* [chrome.i18n](https://go.microsoft.com/fwlink/?linkid=2167478) - Chrome Extensions > Reference > API.

0 commit comments

Comments
 (0)