diff --git a/microsoft-edge/devtools/customize/extensions.md b/microsoft-edge/devtools/customize/extensions.md index 15d783219f..8645070437 100644 --- a/microsoft-edge/devtools/customize/extensions.md +++ b/microsoft-edge/devtools/customize/extensions.md @@ -16,7 +16,7 @@ In addition to the tools available in Microsoft Edge DevTools, you can add new t ## Find an extension that extends DevTools -The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) contains extensions that typically extend DevTools. +The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) contains extensions that typically extend DevTools. There is no way to know whether an extension extends the DevTools **Activity Bar**, without running it or looking at its source code, but the **Developer tools** category at Microsoft Edge Add-ons is a good place to look. @@ -26,7 +26,7 @@ There is no way to know whether an extension extends the DevTools **Activity Bar To install a Microsoft Edge extension that extends DevTools: -1. Go to [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), such as the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category, and go to the extension you want to install. +1. Go to [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), such as the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category, and go to the extension you want to install. For example, go to the [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension, which is the example used for the steps below: diff --git a/microsoft-edge/devtools/remote-debugging/windows.md b/microsoft-edge/devtools/remote-debugging/windows.md index 2b352375f4..421fd0c3ee 100644 --- a/microsoft-edge/devtools/remote-debugging/windows.md +++ b/microsoft-edge/devtools/remote-debugging/windows.md @@ -70,9 +70,9 @@ To set up the host (debuggee) machine, use the following sub-sections, in order. 1. Open the **Settings** app. In **Find a setting**, enter `Developer settings` and select it. Toggle on **Developer Mode**. You can now turn on the **Device Portal** by setting **Turn on remote diagnostics over local area network connections** to **On**. You can then optionally turn **Authentication** on so that the client (debugger) device must provide the correct credentials to connect to this device. -1. If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT). +1. If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt). - If a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead. + If a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead. ![The Settings app with Developer Mode and Device Portal configured](./windows-images/remote-debugging-windows-media-host-settings.png) diff --git a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md index 6f116d1c64..d66e363004 100644 --- a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md +++ b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md @@ -132,7 +132,7 @@ Tree view: ![Heap Snapshot Visualizer in Tree mode](./devtools-109-images/heap-snapshot-visualizer-tree.png) See also: -* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). diff --git a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md index ce9d84545c..b3de77eaad 100644 --- a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md +++ b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md @@ -42,7 +42,7 @@ See also: Prior to Microsoft Edge 116, if you were in Focus Mode while using the React Developer Tools extension, the state of a tool in DevTools wasn't maintained when you switched to another tool and then switched back. This issue has been fixed. See also: -* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). * [What's New entries about Focus Mode](/search/?scope=Microsoft%20Edge&terms=focus%20mode) diff --git a/microsoft-edge/extensions/contact.md b/microsoft-edge/extensions/contact.md index dbb879405b..9059945417 100644 --- a/microsoft-edge/extensions/contact.md +++ b/microsoft-edge/extensions/contact.md @@ -23,7 +23,7 @@ https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#issues Use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page of the **MicrosoftEdge-Extensions** repo for: * Communicating with the Extensions team: - * Report bugs or issues about [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) (the store) that affect all Edge extension developers or all Microsoft Edge extension users. + * Report bugs or issues about [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) (the store) that affect all Edge extension developers or all Microsoft Edge extension users. * Report bugs or issues about Microsoft Partner Center that affect all Edge extension developers or all Microsoft Edge extension users. * Suggest new features that could impact or benefit all Microsoft Edge extension developers. * Inquire about your Partner Center developer account for Microsoft Edge extensions. @@ -50,7 +50,7 @@ Use the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/disc * Discussions with the Extensions team: * Follow the latest announcements and updates from the Microsoft Edge extensions team. * Request a feature for Edge extensions. - * Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). + * Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). * Discuss how to improve extension publishing, management and listing processes or workflows. * Provide feedback about features for extensions publishing, extensions management, or processes or workflows for extensions listings. @@ -67,7 +67,7 @@ See also: ## Report copyright or trademark infringement -If you think an item at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form. When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**. The Microsoft Edge extensions team will review your report and then take the necessary action. +If you think an item at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form. When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**. The Microsoft Edge extensions team will review your report and then take the necessary action. diff --git a/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md b/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md index 9bf0e5f254..fded24756f 100644 --- a/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md +++ b/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md @@ -14,7 +14,7 @@ ms.date: 05/05/2023 per https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions --> -Generally, a Microsoft Edge extension is distributed by publishing it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). There are some scenarios where you might need to distribute an extension by using alternate methods. For example: +Generally, a Microsoft Edge extension is distributed by publishing it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). There are some scenarios where you might need to distribute an extension by using alternate methods. For example: 1. The extension is associated with other software, and it should be installed together with the rest of the bundled software. @@ -34,7 +34,7 @@ See also: ## Gather initial information -Make sure that you publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), or package a `.crx` file and ensure that it installs successfully on your computer. If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL. +Make sure that you publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), or package a `.crx` file and ensure that it installs successfully on your computer. If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL. Also, make sure that you have the following information: @@ -58,7 +58,7 @@ To distribute your extension using the Windows registry: 1. Create a new key, or folder, under **Extensions** with the same name as the ID of your extension. For example, create the key with the name `aaaaaaaabbbbbbbbccccccccdddddddd`. -1. In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`. The `update_url` property points to the `.crx` file of your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +1. In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`. The `update_url` property points to the `.crx` file of your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). ```json { @@ -122,7 +122,7 @@ To distribute your extension by using a preferences JSON file: } ``` - * Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) on macOS and Linux: + * Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) on macOS and Linux: ```json { diff --git a/microsoft-edge/extensions/developer-guide/api-support.md b/microsoft-edge/extensions/developer-guide/api-support.md index dfecb3c11f..71a655dc96 100644 --- a/microsoft-edge/extensions/developer-guide/api-support.md +++ b/microsoft-edge/extensions/developer-guide/api-support.md @@ -133,4 +133,4 @@ This work is licensed under a [Creative Commons Attribution 4.0 International Li * [Chrome Extensions API reference for Manifest V2](https://developer.chrome.com/docs/extensions/mv2/reference/) * [Chrome Extensions API reference for Manifest V3](https://developer.chrome.com/docs/extensions/reference/api/) -* [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md) - to update an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +* [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md) - to update an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). diff --git a/microsoft-edge/extensions/developer-guide/best-practices.md b/microsoft-edge/extensions/developer-guide/best-practices.md index 80eaf57c0d..034f3c20f7 100644 --- a/microsoft-edge/extensions/developer-guide/best-practices.md +++ b/microsoft-edge/extensions/developer-guide/best-practices.md @@ -10,7 +10,7 @@ ms.date: 11/20/2023 --- # Best practices for extensions -Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). diff --git a/microsoft-edge/extensions/developer-guide/match-patterns.md b/microsoft-edge/extensions/developer-guide/match-patterns.md index 96157aba6a..ecf7aad69b 100644 --- a/microsoft-edge/extensions/developer-guide/match-patterns.md +++ b/microsoft-edge/extensions/developer-guide/match-patterns.md @@ -23,7 +23,7 @@ See the License for the specific language governing permissions and limitations under the License. --> # Defining match patterns for an extension to access file URLs -A Microsoft Edge extension can request access to `file` URLs. To enable this feature, you need to explicitly configure this access. Access to `file` URLs isn't automatic. You must visit the **Extensions management** page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs. +A Microsoft Edge extension can request access to `file` URLs. To enable this feature, you need to explicitly configure this access. Access to `file` URLs isn't automatic. You must visit the **Extensions management** page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs. For Microsoft Edge extension, host permission and content script pattern matching works as follows. diff --git a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md index 7e8e08e704..c261b07d84 100644 --- a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md +++ b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md @@ -16,7 +16,7 @@ This article lists important changes being implemented as part of Manifest V3, w ## Remotely hosted code -Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process. Although this offers the flexibility to change code without resubmitting the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), it's possible to exploit the code after installation. +Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process. Although this offers the flexibility to change code without resubmitting the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), it's possible to exploit the code after installation. To ensure that the extensions at Microsoft Edge Add-ons are validated, the Microsoft Edge extensions team disallows extensions from using remotely hosted code. This change makes extensions more secure. diff --git a/microsoft-edge/extensions/developer-guide/native-messaging.md b/microsoft-edge/extensions/developer-guide/native-messaging.md index 9ba11aa131..c7624f6956 100644 --- a/microsoft-edge/extensions/developer-guide/native-messaging.md +++ b/microsoft-edge/extensions/developer-guide/native-messaging.md @@ -18,7 +18,7 @@ To acquire the extension and native app host, there are two different distributi * Package your extension and the host together. When a user installs the package, both the extension and the host are installed. -* Or, install your extension from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), and your extension prompts users to install the host. +* Or, install your extension from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), and your extension prompts users to install the host. To create your extension to send and receive messages with native app hosts, do the following steps. @@ -129,7 +129,7 @@ Sideload your extension to test native messaging with the host. To sideload you 1. Copy the key from `microsoft_catalog_extension_id` (ID) from the extension listing on the page. -When you're ready to distribute your extension to users, publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). The extension ID of the published extension might differ from the ID that's used while sideloading your extension. If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension. +When you're ready to distribute your extension to users, publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The extension ID of the published extension might differ from the ID that's used while sideloading your extension. If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension. @@ -201,7 +201,7 @@ The `HKEY_CURRENT_USER\SOFTWARE\WOW6432Node` registry node is not searched on 64 #### Extension IDs required for both stores -If you have an extension both at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) and the Chrome Web Store, you must add the extension IDs that correspond to both of the stores in the `allowed_origins` of the native messaging host manifest file. +If you have an extension both at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and the Chrome Web Store, you must add the extension IDs that correspond to both of the stores in the `allowed_origins` of the native messaging host manifest file. This is required because only the native messaging host manifest file that corresponds to the first registry location that's found is read. diff --git a/microsoft-edge/extensions/developer-guide/port-chrome-extension.md b/microsoft-edge/extensions/developer-guide/port-chrome-extension.md index 83c92892d7..146ce9b6a4 100644 --- a/microsoft-edge/extensions/developer-guide/port-chrome-extension.md +++ b/microsoft-edge/extensions/developer-guide/port-chrome-extension.md @@ -26,7 +26,7 @@ To port your Chrome extension: 1. If you face any issues, you can debug your extensions in Microsoft Edge by using the DevTools, or [contact us](mailto:ext_dev_support@microsoft.com). -1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). @@ -38,6 +38,6 @@ If your extension exchanges messages with a native app by using `chrome.runtime. ## Next steps -After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/): +After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): 1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md) 1. [Publish a Microsoft Edge extension](../publish/publish-extension.md) diff --git a/microsoft-edge/extensions/getting-started/extension-sideloading.md b/microsoft-edge/extensions/getting-started/extension-sideloading.md index 55055b4539..c2e6af395d 100644 --- a/microsoft-edge/extensions/getting-started/extension-sideloading.md +++ b/microsoft-edge/extensions/getting-started/extension-sideloading.md @@ -10,7 +10,7 @@ ms.date: 01/16/2025 --- # Sideload an extension to install and test it locally -To test an extension quickly and safely, sideload the extension in your own copy of Microsoft Edge, which means locally installing the extension. You can then run and test your extension without having to publish the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) and then install the extension from there. +To test an extension quickly and safely, sideload the extension in your own copy of Microsoft Edge, which means locally installing the extension. You can then run and test your extension without having to publish the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and then install the extension from there. @@ -53,7 +53,7 @@ To sideload an extension into Microsoft Edge, so that it's locally installed in The **Select the extension directory** dialog closes. - The extension is installed in your browser, similar to extensions that are installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/): + The extension is installed in your browser, similar to extensions that are installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): ![Installed extensions page, showing a sideloaded extension](./extension-sideloading-images/installed-extension.png) diff --git a/microsoft-edge/extensions/getting-started/picture-inserter-content-script.md b/microsoft-edge/extensions/getting-started/picture-inserter-content-script.md index 70899a6ca1..3da35def0d 100644 --- a/microsoft-edge/extensions/getting-started/picture-inserter-content-script.md +++ b/microsoft-edge/extensions/getting-started/picture-inserter-content-script.md @@ -173,7 +173,7 @@ See also: ## Install the sample locally -Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. +Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. 1. In Microsoft Edge, click the **Extensions** (![Extensions icon](./picture-inserter-content-script-images/extensions-icon.png)) button, next to the Address bar, if this icon is displayed. Or, select **Settings and more** (![The "Settings and more" icon](./picture-inserter-content-script-images/settings-and-more-icon.png)) > ![Extensions icon](./picture-inserter-content-script-images/extensions-icon.png) **Extensions**. The **Extensions** pop-up opens: diff --git a/microsoft-edge/extensions/getting-started/picture-viewer-popup-webpage.md b/microsoft-edge/extensions/getting-started/picture-viewer-popup-webpage.md index b47c4eea0f..d33a369618 100644 --- a/microsoft-edge/extensions/getting-started/picture-viewer-popup-webpage.md +++ b/microsoft-edge/extensions/getting-started/picture-viewer-popup-webpage.md @@ -148,7 +148,7 @@ See also: ## Install the sample locally -Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. +Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. 1. In Microsoft Edge, click the **Extensions** (![Extensions icon](./picture-viewer-popup-webpage-images/extensions-icon.png)) button, next to the Address bar, if this icon is displayed. Or, select **Settings and more** (![The "Settings and more" icon](./picture-viewer-popup-webpage-images/settings-and-more-icon.png)) > **Extensions**. The **Extensions** pop-up opens: diff --git a/microsoft-edge/extensions/index.md b/microsoft-edge/extensions/index.md index 963735c36d..5df38de425 100644 --- a/microsoft-edge/extensions/index.md +++ b/microsoft-edge/extensions/index.md @@ -11,9 +11,9 @@ ms.date: 08/20/2024 # Overview of Microsoft Edge extensions -A Microsoft Edge _extension_, also called an _add-on_, is a small app that developers use to add or modify features of Microsoft Edge to improve a user's browsing experience. An extension provides a niche experience or function that is important to a target audience. You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +_Microsoft Edge Add-ons_ include extensions and themes. A Microsoft Edge _extension_ is a small app that developers use to add or modify features of Microsoft Edge to improve a user's browsing experience. An extension provides a niche experience or function that's important to a target audience. -In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes Microsoft Edge Add-ons. +You publish a Microsoft Edge extension (or theme) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes the Microsoft Edge Add-ons site. You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers. @@ -55,9 +55,11 @@ The following table isn't exhaustive or definitive; it's just a starting point f -## Why Chromium? +## Benefits of Chromium extensions -If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications. The last four browsers in the previous table use the same code package and minimize the need to maintain parallel versions. These browsers are based on the [Chromium open-source project](https://www.chromium.org/Home). +If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications. + +The last four browsers in the previous table use the same code package and minimize the need to maintain parallel versions. These browsers are based on the [Chromium open-source project](https://www.chromium.org/Home). Benefits of creating a Chromium extension: * Enables writing the fewest lines of code. @@ -91,7 +93,7 @@ You can submit and seek browser extensions in the following browser extension st * [Firefox Browser Add-ons](https://addons.mozilla.org/firefox/extensions) * [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) * [Opera addons](https://addons.opera.com/extensions) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. @@ -101,7 +103,7 @@ Users might need to install your extension in different browsers. In this scenar #### Migrate an existing extension to Microsoft Edge -If you've already developed an extension for another Chromium-based browser, you can submit it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). You don't need to rewrite your extension or verify that it works in Microsoft Edge. However, when you migrate an existing Chromium extension to other Chromium browsers, make certain the same APIs or alternatives are available for your target browser. +If you've already developed an extension for another Chromium-based browser, you can submit it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). You don't need to rewrite your extension or verify that it works in Microsoft Edge. However, when you migrate an existing Chromium extension to other Chromium browsers, make certain the same APIs or alternatives are available for your target browser. For more information on porting your Chrome extension to Microsoft Edge, see [Port Chrome extensions to Microsoft Edge](developer-guide/port-chrome-extension.md). After you port your extension to the target browser, the next step is to publish it. @@ -109,7 +111,7 @@ For more information on porting your Chrome extension to Microsoft Edge, see [Po #### Publish an extension at Microsoft Edge Add-ons -You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To start publishing a Microsoft Edge extension, you must [register for a developer account](https://developer.microsoft.com/registration) with a Microsoft account (MSA) email account to submit your extension listing at Microsoft Edge Add-ons. The email address of a Microsoft account (MSA) includes `@outlook.com`, `@live.com`, or `@hotmail.com`. @@ -130,7 +132,7 @@ After you've successfully submitted your extension, your extension undergoes a r ## The Featured badge -A **Featured** badge is displayed on some extension listings at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). The **Featured** badge indicates that the extension has been determined to follow Microsoft's recommended best practices related to security, privacy, transparency, and user experience. +A **Featured** badge is displayed on some extension listings at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The **Featured** badge indicates that the extension has been determined to follow Microsoft's recommended best practices related to security, privacy, transparency, and user experience. ![The Featured badge to the right of the extension name](./index-images/featured-badge.png) @@ -147,19 +149,23 @@ Just because an extension doesn't have a **Featured** badge, doesn't mean the ex ## See also + + +* [Best practices for extensions](./developer-guide/best-practices.md) +* [Extension concepts and architecture](./getting-started/index.md) +* [Manage Microsoft Edge extensions in the enterprise](/deployedge/microsoft-edge-manage-extensions) + +End-user docs: +* [Everything to know about browser extensions](https://www.microsoft.com/edge/learning-center/everything-to-know-about-browser-extensions?form=MA13I2&msockid=3078d2dac55660f53e4ec6a8c4ec61bf) - introduction for users. +* [Add, turn off, or remove extensions in Microsoft Edge](https://support.microsoft.com/microsoft-edge/add-turn-off-or-remove-extensions-in-microsoft-edge-9c0ec68c-2fbc-2f2c-9ff0-bdc76f46b026) - support steps for users. + +External: +* [Build a Safari App extension](https://developer.apple.com/documentation/safariservices/safari_app_extensions/building_a_safari_app_extension) +* [Your first extension (Firefox)](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension) +* [Extensions > Get started](https://developer.chrome.com/docs/extensions/get-started/) +* [Get started (Opera)](https://dev.opera.com/extensions/getting-started) +* [Port a Google Chrome extension](https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension) -* [Everything to know about browser extensions](https://www.microsoft.com/edge/learning-center/everything-to-know-about-browser-extensions?form=MA13I2&msockid=3078d2dac55660f53e4ec6a8c4ec61bf) - introduction for users. -* [Add, turn off, or remove extensions in Microsoft Edge](https://support.microsoft.com/microsoft-edge/add-turn-off-or-remove-extensions-in-microsoft-edge-9c0ec68c-2fbc-2f2c-9ff0-bdc76f46b026) - support steps for users. -* [Extension concepts and architecture](getting-started/index.md) -* [Manage Microsoft Edge extensions in the enterprise](/deployedge/microsoft-edge-manage-extensions) - -External links: -* [Build a Safari App extension](https://developer.apple.com/documentation/safariservices/safari_app_extensions/building_a_safari_app_extension) -* [Your first extension (Firefox)](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension) -* [Extensions > Get started](https://developer.chrome.com/docs/extensions/get-started/) -* [Get started (Opera)](https://dev.opera.com/extensions/getting-started) -* [Port a Google Chrome extension](https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension) - -Extensions for Visual Studio Code rather than for Microsoft Edge: -* [Microsoft Edge DevTools extension for Visual Studio Code](../visual-studio-code/microsoft-edge-devtools-extension.md) -* [webhint extension for Visual Studio Code](../visual-studio-code/webhint.md) +Extensions for Visual Studio Code: +* [Microsoft Edge DevTools extension for Visual Studio Code](../visual-studio-code/microsoft-edge-devtools-extension.md) +* [webhint extension for Visual Studio Code](../visual-studio-code/webhint.md) diff --git a/microsoft-edge/extensions/publish/aad-account.md b/microsoft-edge/extensions/publish/aad-account.md index 7de96b0b34..fc24e61086 100644 --- a/microsoft-edge/extensions/publish/aad-account.md +++ b/microsoft-edge/extensions/publish/aad-account.md @@ -10,9 +10,6 @@ ms.date: 11/03/2022 --- # Add users to the Microsoft Edge program - - - To help manage your Microsoft Edge extensions, you can add more users to an existing Partner Center account. To manage Microsoft Edge extensions, the Primary Owner of the Partner Center account must be a Microsoft account (MSA). A Microsoft account (MSA) is an Outlook.com, Live.com, or Hotmail.com account. For a summary of the types of accounts used to publish extensions, see [Types of accounts related to publishing Microsoft Edge extensions](create-dev-account.md#types-of-accounts-related-to-publishing-microsoft-edge-extensions). @@ -38,7 +35,6 @@ Also see these articles in the Partner Center documentation: ## Step 1: Enroll in the Microsoft Edge program on Partner Center - First, determine whether you have a Partner Center account. If you have a Partner Center account, determine whether the Primary Owner is a Microsoft Account (MSA), which is required for joining the Microsoft Edge program, to manage Microsoft Edge extensions. Then follow the steps in the section that applies to your type of Partner Center account. @@ -89,14 +85,25 @@ To determine whether the Primary Owner of your Partner Center account is a Micro To enable managing Microsoft Edge extensions, you'll link your Microsoft Entra tenants to your Microsoft Edge Program account. You can use Microsoft Entra ID to add users to your Microsoft Edge Program account and manage those users in that account. You can add individual users, groups of users, or Microsoft Entra ID applications. +Microsoft Entra ID was formerly called Azure Active Directory (Azure AD). Some linked docs still say "Azure AD" instead of "Microsoft Entra ID". + To be able to add users to your Microsoft Edge Program account, and to manage the users in that account, you must first associate your Microsoft Edge Program account with your organization's Microsoft Entra tenant. If your organization already uses Office 365 or other business services from Microsoft, you already have a Microsoft Entra tenant. Otherwise, you can create a new Microsoft Entra tenant for free. -To create an AD tenant, see [Create a new Microsoft Entra tenant to associate with your Partner Center account](/windows/apps/publish/partner-center/create-new-azure-ad-tenant). +To create a Microsoft Entra tenant, see [Create a new Azure AD tenant to associate with your Partner Center account](/windows/apps/publish/partner-center/create-new-azure-ad-tenant). + +See also [Associate an existing Azure AD tenant with your Partner Center account](/windows/apps/publish/partner-center/associate-existing-azure-ad-tenant-with-partner-center-account). Associating a Microsoft Entra tenant with a Microsoft Edge Program account at Partner Center works the same way as associating a tenant with the Windows apps developer program. + + + +#### Changing user roles or permissions + +**Important:** If you added users after associating your Microsoft Entra tenant with your Microsoft account on Partner Center: + +* Changing user roles or permissions isn't supported. -Also see [Associate an existing Microsoft Entra tenant with your Partner Center account](/windows/uwp/publish/associate-azure-ad-with-partner-center), in the Windows UWP documentation. Associating a Microsoft Entra tenant with a Microsoft Edge Program account at Partner Center works the same way as associating a tenant with the Windows apps developer program. +* Adding users is supported. -> [!IMPORTANT] -> If you added users after associating your Microsoft Entra tenant with your Microsoft account on Partner Center, changing user roles or permissions isn't supported. However, you can continue to add as many users as you require and use the filter option of the [user management](https://partner.microsoft.com/dashboard/account/v3/usermanagement) section to locate admins of specific roles. +* You can locate admins of specific roles, by using the filter option of the [User management](https://partner.microsoft.com/dashboard/account/v3/usermanagement) section. @@ -104,7 +111,7 @@ Also see [Associate an existing Microsoft Entra tenant with your Partner Center After you've set up the Microsoft Entra ID association, you can add users at **Account settings** > **User management** on the Partner Center. Each user has full access the extensions available in the program. You can also add groups of users, or add Microsoft Entra ID applications, to grant them access to your Partner Center account. -For more information about adding users, see [Users, groups, and applications in Microsoft Entra ID](/windows/uwp/publish/add-users-groups-and-azure-ad-applications) in the Windows UWP documentation. +For more information about adding users, see [Users, groups, and applications in Azure Active Directory](/windows/apps/publish/partner-center/overview-users-groups-azure-ad-applications). diff --git a/microsoft-edge/extensions/publish/add-ons-badge-images/microsoft-edge-add-ons-badge.png b/microsoft-edge/extensions/publish/add-ons-badge-images/microsoft-edge-add-ons-badge.png new file mode 100644 index 0000000000..2b97d471da Binary files /dev/null and b/microsoft-edge/extensions/publish/add-ons-badge-images/microsoft-edge-add-ons-badge.png differ diff --git a/microsoft-edge/extensions/publish/add-ons-badge.md b/microsoft-edge/extensions/publish/add-ons-badge.md new file mode 100644 index 0000000000..a07b8c5a2e --- /dev/null +++ b/microsoft-edge/extensions/publish/add-ons-badge.md @@ -0,0 +1,74 @@ +--- +title: Use the Microsoft Edge Add-ons badge to promote your add-on +description: Use this badge in your websites, documentation, or tutorials, to promote your extension (or theme) that's at the Microsoft Edge Add-ons site. # key words before col 158 +author: MSEdgeTeam +ms.author: msedgedevrel +ms.topic: conceptual +ms.service: microsoft-edge +ms.date: 09/15/2025 +--- +# Use the Microsoft Edge Add-ons badge to promote your add-on + +To promote your Microsoft Edge extension (or theme), use the Microsoft Edge Add-ons badge in your websites, documentation, tutorials, and other services or integrations. This ensures consistent, accessible, and compliant representation of the Microsoft Edge Add-ons brand. + +The Microsoft Edge Add-ons badge is a visual asset designed to help you promote your Microsoft Edge add-on and build user trust. + +The Microsoft Edge Add-ons badge reads **Get it from Microsoft Edge**, and shows the Microsoft Edge logo: + +![The "Microsoft Edge Add-ons" badge](./add-ons-badge-images/microsoft-edge-add-ons-badge.png) + +The Microsoft Edge Add-ons badge appears in full color with a dark background, and includes a gray border and transparent corners. The badge `.png` files are provided in 41 languages. + +The Microsoft Edge Add-ons badge lets you showcase your Microsoft Edge add-on with Microsoft Edge-specific branding. To prevent confusion with the broader [Microsoft Store](https://apps.microsoft.com), the Microsoft Edge Add-ons badge is intended exclusively for promoting add-ons that are available for Microsoft Edge. This badge helps users clearly identify content that is built specifically for the Microsoft Edge browser. + +The generic Microsoft Store badge reads **Get it from Microsoft**, and shows the Microsoft logo. + +Unlike the generic Microsoft Store badge, the Microsoft Edge Add-ons badge provides a distinct, trusted visual cue that connects your Microsoft Edge add-on directly to the Microsoft Edge ecosystem. + +The Microsoft Edge Add-ons badge is not the same as the Microsoft brand logo, and they cannot be used interchangeably. + + + +## Download the badge image files + +Download the complete set of `.png` files: + +* [Microsoft_Edge_Add-ons_badge_image_files.zip](https://raw.githubusercontent.com/microsoft/MicrosoftEdge-Extensions/refs/heads/main/assets/Microsoft_Edge_Add-ons_badge_image_files.zip) (from the [MicrosoftEdge-Extensions](https://github.com/microsoft/MicrosoftEdge-Extensions) repo). + + + +## Badge usage guidelines + +Follow these guidelines for using the Microsoft Edge Add-ons badge. For detailed usage examples and guidelines, download and read the PDF file: + +* [Microsoft_Edge_Add-ons_badge_guidelines.pdf](https://raw.githubusercontent.com/microsoft/MicrosoftEdge-Extensions/refs/heads/main/assets/Microsoft_Edge_Add-ons_badge_guidelines.pdf) (from the [MicrosoftEdge-Extensions](https://github.com/microsoft/MicrosoftEdge-Extensions) repo). + +For example, the PDF includes the following guidelines: + +* Always use the official badge artwork provided by Microsoft. + +* Do not create your own version, alter the text color, extract the Microsoft Edge logo, or modify the badge in any way. + +* Do not animate, rotate, tilt, stretch, compress, or apply gradients or shadows to the badge. + +* Do not use the badge as a decorative element in any context. + +* The badge must always be an active, clickable link that directs users to your product detail page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). + +* Do not use the badge in static marketing materials, such as posters, flyers, or non-clickable images in presentations or videos. + +* The badge is intended solely to facilitate direct access to your add-ons at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). + + + +#### Minimum size for the badge + +To ensure that the badge text remains readable, display it at a minimum size of 32px. Avoid using smaller sizes. + +When scaling the badge, always maintain its aspect ratio; do not stretch or compress the badge image. This helps preserve visual quality and reinforces your product's credibility. + + + +## See also + +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) diff --git a/microsoft-edge/extensions/publish/add-ons-curation.md b/microsoft-edge/extensions/publish/add-ons-curation.md index a1875a3598..ac7a6b4a10 100644 --- a/microsoft-edge/extensions/publish/add-ons-curation.md +++ b/microsoft-edge/extensions/publish/add-ons-curation.md @@ -10,9 +10,9 @@ ms.date: 10/13/2023 --- # Curation and review process for extensions at Microsoft Edge Add-ons -The Microsoft Edge extensions team curates the experience at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) so that users can find all the items to customize their browser in one place, such as themes, extensions, and apps. +The Microsoft Edge extensions team curates the experience at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) so that users can find all the items to customize their browser in one place, such as extensions or themes. -Available _items_ to customize the user's browser include themes, extensions, and apps. +Available _items_ to customize the user's browser include extensions and themes. Before installing an item from Microsoft Edge Add-ons, users can learn more about the functionality, data permissions, and publisher by viewing the item's description and listing. @@ -20,7 +20,7 @@ Before installing an item from Microsoft Edge Add-ons, users can learn more abou ## How items are organized at Microsoft Edge Add-ons -Items at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), such as themes, extensions, and apps, are organized to help users discover the ones that are relevant to their interests. +Items at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), including extensions and themes, are organized to help users discover the add-ons that are relevant to their interests. Users can discover extensions they're interested in at Microsoft Edge Add-ons in several ways, including: * The home page. @@ -40,7 +40,7 @@ The following factors are used to organize items: ## Security review -The quality and compliance of the item that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) is verified per the guidelines that are set in the developer policy. +The quality and compliance of the item that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) is verified per the guidelines that are set in the developer policy. Extensions that violate the policy guidelines are not allowed at Microsoft Edge Add-ons. There is a standard review process for each new item submission and new versions of items, per the developer policies. @@ -51,7 +51,7 @@ See also: ## Ranking -Every item (such as theme, extension, or app) that's published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) has detailed information about the item's characteristics, such as: +Every item (such as an extension or theme) that's published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) has detailed information about the item's characteristics, such as: * Screenshots. * The description of the item's features and functionality. @@ -64,7 +64,7 @@ The search ranking of the item is based on these characteristics. ## User feedback -At [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), users can provide a rating and a written review for the item they are using. Users and developers can report an abusive review from within the review section of the item listing page. +At [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), users can provide a rating and a written review for the item they are using. Users and developers can report an abusive review from within the review section of the item listing page. Items are ranked for popularity based on user ratings at Microsoft Edge Add-ons. diff --git a/microsoft-edge/extensions/publish/create-dev-account.md b/microsoft-edge/extensions/publish/create-dev-account.md index 7c8d881f83..c59a186f22 100644 --- a/microsoft-edge/extensions/publish/create-dev-account.md +++ b/microsoft-edge/extensions/publish/create-dev-account.md @@ -10,7 +10,7 @@ ms.date: 11/01/2022 --- # Register as a Microsoft Edge extension developer -This article helps you create a Partner Center account that you can use to submit a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). This article covers company accounts (for enterprise developers), and individual accounts (for individual developers), as described in [Account types](#account-types) below. +This article helps you create a Partner Center account that you can use to submit a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). This article covers company accounts (for enterprise developers), and individual accounts (for individual developers), as described in [Account types](#account-types) below. If you have a Partner Center account, but the Primary Owner of the account isn't a Microsoft account (MSA), this article will help you create and link to a suitable account. You'll learn how to create a Microsoft account (MSA) if you don't have one, and help you link the Microsoft account (MSA) to your Partner Center account. @@ -33,7 +33,7 @@ To add and manage users in the Microsoft Edge program to manage extensions, you ## Create a Microsoft account -To submit an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), you must be registered as a developer with the Microsoft Edge program. You register for the Microsoft Edge program at [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). To register for the Microsoft Edge program, you need a Microsoft account (MSA). If you don't have a Microsoft account (MSA), create one. One way to create a Microsoft account (MSA) is to use your existing GitHub account to sign in to Partner Center. Follow the prompts displayed in the dialogs to automatically create a Microsoft account (MSA). +To submit an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you must be registered as a developer with the Microsoft Edge program. You register for the Microsoft Edge program at [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). To register for the Microsoft Edge program, you need a Microsoft account (MSA). If you don't have a Microsoft account (MSA), create one. One way to create a Microsoft account (MSA) is to use your existing GitHub account to sign in to Partner Center. Follow the prompts displayed in the dialogs to automatically create a Microsoft account (MSA). There is no registration fee for submitting extensions to the Microsoft Edge program. @@ -92,7 +92,7 @@ This field is either where you live, or where your business is located. #### Account types -The Microsoft Edge program in [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) offers both individual and company accounts. The accounts are described in detail in the following sections. Both account types enable you to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +The Microsoft Edge program in [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) offers both individual and company accounts. The accounts are described in detail in the following sections. Both account types enable you to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). > [!IMPORTANT] > After enrollment, you aren't able to change the value of this field. @@ -109,13 +109,13 @@ An individual account is appropriate for a developer not associated with a compa A company account is associated with an organization or business. The account verification process is longer and involves confirmation that you're authorized to create the account for your company. The duration of the process can range from a few days to a few weeks. Your company might receive phone calls from Microsoft verification partners. -For a company account, it's crucial to verify your Microsoft Edge program information when you enroll into a new Partner Center program. This verification is needed to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). See [Verify your company account information](./verify-microsoft-edge-program.md). +For a company account, it's crucial to verify your Microsoft Edge program information when you enroll into a new Partner Center program. This verification is needed to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). See [Verify your company account information](./verify-microsoft-edge-program.md). #### Publisher display name -This field contains the name that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). To use a particular name, that name must be available, and you must have the rights to use it. Company accounts must use the registered business name of your organization. +This field contains the name that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To use a particular name, that name must be available, and you must have the rights to use it. Company accounts must use the registered business name of your organization. The maximum length for this field is fifty (50) characters. @@ -162,4 +162,4 @@ Other sites: * [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) * [account.microsoft.com](https://account.microsoft.com/account) * [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) diff --git a/microsoft-edge/extensions/publish/extensions-analytics.md b/microsoft-edge/extensions/publish/extensions-analytics.md index e050f4d8a7..de067c8477 100644 --- a/microsoft-edge/extensions/publish/extensions-analytics.md +++ b/microsoft-edge/extensions/publish/extensions-analytics.md @@ -12,7 +12,7 @@ ms.date: 11/07/2022 Microsoft announced the launch of the Extensions Analytics Dashboard on September 8, 2021. For more information, see the blog post [Track your add-on's performance: extension analytics now available on Partner center](https://techcommunity.microsoft.com/t5/articles/track-your-add-on-s-performance-extension-analytics-now/m-p/2733351). -You can view extension metrics from your [Partner Center dashboard](https://partner.microsoft.com/dashboard/microsoftedge/overview) and evaluate an extension's performance at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +You can view extension metrics from your [Partner Center dashboard](https://partner.microsoft.com/dashboard/microsoftedge/overview) and evaluate an extension's performance at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). For example, you can identify regions in which the number of installations for your extension has increased in the past three months. You can also export this report as a CSV file. @@ -26,7 +26,7 @@ Follow these steps to view your extension's analytics dashboard: ## Analytics dashboard metrics -From the analytics dashboard you can view metrics for the **Last month**, **3 months**, **6 months**, or **All time** (the period since your extension has been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/)). +From the analytics dashboard you can view metrics for the **Last month**, **3 months**, **6 months**, or **All time** (the period since your extension has been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)). @@ -53,7 +53,7 @@ The following screenshot shows the **Weekly users** who have enabled and disable #### Installs -The **Installs** metric displays the total number of successful installs of your extensions per day at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +The **Installs** metric displays the total number of successful installs of your extensions per day at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The following screenshot shows daily successful installations for the last month. @@ -63,7 +63,7 @@ The following screenshot shows daily successful installations for the last month #### Impressions -The **Impressions** metric captures the total number of page views and user visits to your extension product page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). The data points are based on weekly or daily totals depending on the selected time range. +The **Impressions** metric captures the total number of page views and user visits to your extension product page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The data points are based on weekly or daily totals depending on the selected time range. The following screenshot shows **Impressions** for an extension page over a three month period: diff --git a/microsoft-edge/extensions/publish/github.md b/microsoft-edge/extensions/publish/github.md index bd6a5cfb2c..6cba99adf7 100644 --- a/microsoft-edge/extensions/publish/github.md +++ b/microsoft-edge/extensions/publish/github.md @@ -10,7 +10,7 @@ ms.date: 02/14/2024 --- # Register and sign in to Partner Center using a GitHub account -If you're a GitHub user, you don't need to create a new Microsoft account (MSA) and remember extra passwords to sign into Partner Center. You can use your personal GitHub credentials to sign into Partner Center and publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +If you're a GitHub user, you don't need to create a new Microsoft account (MSA) and remember extra passwords to sign into Partner Center. You can use your personal GitHub credentials to sign into Partner Center and publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Currently, you can only use your _personal_ GitHub account to login to Partner Center. Using your _work_ GitHub account isn't supported. diff --git a/microsoft-edge/extensions/publish/hosting-and-updating.md b/microsoft-edge/extensions/publish/hosting-and-updating.md index c8815966e7..4e2ce76a22 100644 --- a/microsoft-edge/extensions/publish/hosting-and-updating.md +++ b/microsoft-edge/extensions/publish/hosting-and-updating.md @@ -10,13 +10,13 @@ ms.date: 12/18/2023 --- # Extension hosting -Most extensions are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), to protect users from malicious extensions. +Most extensions are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), to protect users from malicious extensions. ## Publish options for extensions -All extensions are distributed to users as a special archive (`.zip`) file with a `.crx` suffix. Extensions that are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) are uploaded as `.zip` files. The publishing process automatically converts the `.zip` file into a `.crx` file. +All extensions are distributed to users as a special archive (`.zip`) file with a `.crx` suffix. Extensions that are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) are uploaded as `.zip` files. The publishing process automatically converts the `.zip` file into a `.crx` file. The following two scenarios don't require you to publish your extension at Microsoft Edge Add-ons: * Extensions that are distributed using Enterprise policy. diff --git a/microsoft-edge/extensions/publish/manage-settings.md b/microsoft-edge/extensions/publish/manage-settings.md index 9220573268..9d9584149d 100644 --- a/microsoft-edge/extensions/publish/manage-settings.md +++ b/microsoft-edge/extensions/publish/manage-settings.md @@ -28,7 +28,7 @@ In the **Account details** section, review the type of your account and its stat ## Contact Details -The **Contact info** section displays the details you provided when you created your account. The Microsoft Edge extension team uses the contact details information to contact you about your account. The publisher name that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) is also displayed in the **Contact info** section. +The **Contact info** section displays the details you provided when you created your account. The Microsoft Edge extension team uses the contact details information to contact you about your account. The publisher name that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) is also displayed in the **Contact info** section. If your contact information changes you can edit the **Contact info** section. Select **Update**, make your changes, and then select **Save**. You can also select **Contact info** in the left navigation menu to open the **Contact info** section. diff --git a/microsoft-edge/extensions/publish/publish-extension.md b/microsoft-edge/extensions/publish/publish-extension.md index 7179a1f3b4..57cd4d5e8f 100644 --- a/microsoft-edge/extensions/publish/publish-extension.md +++ b/microsoft-edge/extensions/publish/publish-extension.md @@ -10,7 +10,7 @@ ms.date: 07/23/2025 --- # Publish a Microsoft Edge extension -After you develop and test your Microsoft Edge extension, you're ready to distribute your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). To release your existing Chromium extension for Microsoft Edge users, see [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md). +After you develop and test your Microsoft Edge extension, you're ready to distribute your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To release your existing Chromium extension for Microsoft Edge users, see [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md). Publish your extension at Microsoft Edge Add-ons to increase its reach and make it available to other Microsoft Edge users. This article provides the process to submit your extension at Microsoft Edge Add-ons. @@ -18,7 +18,7 @@ Publish your extension at Microsoft Edge Add-ons to increase its reach and make ## Prepare an extension to be submitted via Partner Center -To prepare an extension to be submitted via Partner Center, to be published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), do the following steps. +To prepare an extension to be submitted via Partner Center, to be published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), do the following steps. @@ -32,7 +32,7 @@ Before publishing your extension, you should have a working prototype of your ex To get started, visit [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). This is where every developer (new or existing) must go to publish or manage their extensions. -Use your active developer account to submit your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). If you don't have a developer account, create a new developer account. To open a new developer account and register for the Microsoft Edge program, see [Register as a Microsoft Edge extension developer](./create-dev-account.md). +Use your active developer account to submit your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). If you don't have a developer account, create a new developer account. To open a new developer account and register for the Microsoft Edge program, see [Register as a Microsoft Edge extension developer](./create-dev-account.md). @@ -48,7 +48,7 @@ Create a zip file for your extension package. Your extension package must inclu #### Review manifest field values -In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). 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** page, as follows. @@ -71,7 +71,7 @@ Later, after you upload your package, you'll have an opportunity to modify some ## Submit the extension at Microsoft Edge Add-ons -After doing the above steps, the extension is ready to be submitted via Partner Center, to be published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +After doing the above steps, the extension is ready to be submitted via Partner Center, to be published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To submit your extension to Partner Center: @@ -132,7 +132,7 @@ On the **Availability** page for the extension, fill in the **Visibility** and * #### Visibility -Select one of the following visibility options to define whether your extension is discoverable at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/): +Select one of the following visibility options to define whether your extension is discoverable at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): * `Public` (default) - Allows everyone to discover your extension through search, browsing at Microsoft Edge Add-ons, or using the listing URL for your extension at Microsoft Edge Add-ons. The listing URL is available on your Partner Center dashboard on the Extension **Overview** page. @@ -150,7 +150,7 @@ Define the specific markets in which you plan to offer your extension. The defa 1. Toggle individual markets to exclude each one or select **Unselect all** and then add individual markets of your choice. - You can change the markets where your extension is offered. A user who installs your extension while it's available in the user's market retains access to your extension. However, the user doesn't have access to any future updates that are submitted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). + You can change the markets where your extension is offered. A user who installs your extension while it's available in the user's market retains access to your extension. However, the user doesn't have access to any future updates that are submitted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). 1. Click the **Save & Continue** button. @@ -177,7 +177,7 @@ Define the specific markets in which you plan to offer your extension. The defa Properties that are not indicated as Required are Optional. - The properties are displayed to users at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). Your developer/organization name, **Website URL**, and **Support contact details** that you submitted during registration are displayed to users at Microsoft Edge Add-ons. + The properties are displayed to users at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Your developer/organization name, **Website URL**, and **Support contact details** that you submitted during registration are displayed to users at Microsoft Edge Add-ons. 1. Click the **Save & Continue** button. @@ -209,7 +209,7 @@ Define the specific markets in which you plan to offer your extension. The defa | **Short description** | Required for at least one language | To edit the `short description`, you must update the description field in your manifest file of your extension package and reupload it. | | **Search terms** | - | `Search terms` are single words or phrases that help discover your extension when a user searches at Microsoft Edge Add-ons. The search terms aren't displayed to users. | - The information provided in the **Store Listings** page is displayed to users who view your listing at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). Even though some fields are optional, you should provide as much information as possible. + The information provided in the **Store Listings** page is displayed to users who view your listing at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Even though some fields are optional, you should provide as much information as possible. diff --git a/microsoft-edge/extensions/publish/submission-states.md b/microsoft-edge/extensions/publish/submission-states.md index 739649d82a..fa1881b60e 100644 --- a/microsoft-edge/extensions/publish/submission-states.md +++ b/microsoft-edge/extensions/publish/submission-states.md @@ -12,7 +12,7 @@ ms.date: 11/04/2022 The overview page on the Partner Center displays the state of your extension in the overall submission flow. This article describes the different states your extension can be in at any time during the submission and certification process. -In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). | # | State | Details | |---|---|---| diff --git a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md index 62f92a7786..6c0573d661 100644 --- a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md +++ b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md @@ -16,7 +16,7 @@ When you enroll in the Microsoft Edge program on Partner Center to publish exten You can go to [Legal info](https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo#developer) in Partner Center to monitor verification status for the Microsoft Edge Developer program. -When account verification is complete, you can use your Partner Center dashboard to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +When account verification is complete, you can use your Partner Center dashboard to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Verification usually takes three to five business days. If more than five days have passed, you can [Contact the Microsoft Edge extensions team](../contact.md) for help. diff --git a/microsoft-edge/extensions/update/api/addons-api-reference.md b/microsoft-edge/extensions/update/api/addons-api-reference.md index ce5b107ad1..154460f3af 100644 --- a/microsoft-edge/extensions/update/api/addons-api-reference.md +++ b/microsoft-edge/extensions/update/api/addons-api-reference.md @@ -10,7 +10,7 @@ ms.date: 09/05/2024 --- # REST API Reference for updating an extension at Microsoft Edge Add-ons -This article is the REST endpoint reference for the Microsoft Edge Add-ons API. This API automates publishing updates to an extension that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +This article is the REST endpoint reference for the Microsoft Edge Add-ons API. This API automates publishing updates to an extension that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). For an overview, see [Use the REST API to update an extension at Microsoft Edge Add-ons](./using-addons-api.md). @@ -227,7 +227,7 @@ See also: ## Publish the product draft submission -Publishes the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +Publishes the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). See also [Publishing the submission](./using-addons-api.md#publishing-the-submission) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. diff --git a/microsoft-edge/extensions/update/api/using-addons-api.md b/microsoft-edge/extensions/update/api/using-addons-api.md index 0b0bfb13ef..4999d1f549 100644 --- a/microsoft-edge/extensions/update/api/using-addons-api.md +++ b/microsoft-edge/extensions/update/api/using-addons-api.md @@ -10,7 +10,7 @@ ms.date: 09/19/2024 --- # Use the REST API to update an extension at Microsoft Edge Add-ons -Use this REST API to programmatically update an extension (or a theme) that's been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), to automate the process of uploading and publishing new versions of your extension. You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at Microsoft Edge Add-ons without using Partner Center. +Use this REST API to programmatically update an extension (or a theme) that's been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), to automate the process of uploading and publishing new versions of your extension. You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at Microsoft Edge Add-ons without using Partner Center. This REST API exposes endpoints for: * [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission) @@ -97,7 +97,7 @@ Details are below. | _operation_ | A REST operation such as GET or POST. | | _operation ID_ | The ID of a REST operation. | | _package_ | The `.zip` package that contains the files for your Microsoft Edge extension. | -| _product_ | A Microsoft Edge extension or theme. Sometimes called a Microsoft Edge _Add-on_. | +| _product_, _add-on_ | A Microsoft Edge extension or theme that's published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). | | _product ID_ | The product ID of the product whose draft needs to be published. The product ID is a 128-bit GUID that is associated with a product at Partner Center. For example: `d34f98f5-f9b7-42b1-bebb-98707202b21d`. | | _submission_ | An update that is being submitted to an existing product at Partner Center. Every update to a product is a submission, regardless of whether the status is `In Draft`, `In Review`, or `In the Store` (published). | @@ -414,7 +414,7 @@ See also: ## Publishing the submission -Use this API to publish the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +Use this API to publish the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). See also [Publish the product draft submission](./addons-api-reference.md#publish-the-product-draft-submission) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. diff --git a/microsoft-edge/extensions/update/auto-update.md b/microsoft-edge/extensions/update/auto-update.md index 71371f8025..9d447a34a6 100644 --- a/microsoft-edge/extensions/update/auto-update.md +++ b/microsoft-edge/extensions/update/auto-update.md @@ -40,7 +40,7 @@ When you set your extension to automatically update on users' machines, your ext * Add new features or performance enhancements. * Improve the user interface. -Your extensions are hosted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), and you can update your extension using the same mechanism as Microsoft Edge. You don't control the update mechanism. +Your extensions are hosted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), and you can update your extension using the same mechanism as Microsoft Edge. You don't control the update mechanism. (Previously, non-store-based extensions were supported. Also, previously, you updated the native binaries and the extension at the same time.) diff --git a/microsoft-edge/extensions/update/update-extension.md b/microsoft-edge/extensions/update/update-extension.md index 3ae6fd68b5..218246a2a8 100644 --- a/microsoft-edge/extensions/update/update-extension.md +++ b/microsoft-edge/extensions/update/update-extension.md @@ -10,7 +10,7 @@ ms.date: 11/04/2022 --- # Update a Microsoft Edge extension -You can update or remove a published extension listing that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) at any time. +You can update or remove a published extension listing that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) at any time. See also: * [Set an externally installed extension to automatically update](./auto-update.md) - for an extension that doesn't use Partner Center and isn't at Microsoft Edge Add-ons. @@ -27,7 +27,7 @@ To update an extension that's at Microsoft Edge Add-ons: 1. After you make the changes, click **Publish** to update your extension listing and start the certification process. The certification process for an update to an extension can take up to 7 business days. -1. After the `Status` column displays `In the store`, your extension update is available at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +1. After the `Status` column displays `In the store`, your extension update is available at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). After your extension has been created initially, you can update your extension by [Use the REST API to update an extension at Microsoft Edge Add-ons](./api/using-addons-api.md). @@ -35,7 +35,7 @@ After your extension has been created initially, you can update your extension b ## Update your extension during the certification step -While your extension is in the certification stage, and before it gets published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), you can update your submitted extension. You might also need to update your extension if your extension fails the certification process. +While your extension is in the certification stage, and before it gets published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you can update your submitted extension. You might also need to update your extension if your extension fails the certification process. To check the status of your extension: @@ -80,13 +80,13 @@ To remove an extension: 1. Select **Unpublish** to remove the listing. -The extension is now removed and is no longer present at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). Users who already installed your extension can continue to use it, but the extension isn't available to new users. +The extension is now removed and is no longer present at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Users who already installed your extension can continue to use it, but the extension isn't available to new users. ## See also -* [Set an externally installed extension to automatically update](./auto-update.md) - for an extension that doesn't use Partner Center and isn't at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +* [Set an externally installed extension to automatically update](./auto-update.md) - for an extension that doesn't use Partner Center and isn't at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). * [Use the REST API to update an extension at Microsoft Edge Add-ons](./api/using-addons-api.md) * [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) diff --git a/microsoft-edge/extensions/whats-new/released-features.md b/microsoft-edge/extensions/whats-new/released-features.md index c1e4c9c026..8b00578de5 100644 --- a/microsoft-edge/extensions/whats-new/released-features.md +++ b/microsoft-edge/extensions/whats-new/released-features.md @@ -41,7 +41,7 @@ Microsoft Partner Center only accepts new Manifest V3 Microsoft Edge extension s ## You can respond to user reviews about your Microsoft Edge extension -At Partner Center, you can reply to user reviews and feedback about your extension that's posted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +At Partner Center, you can reply to user reviews and feedback about your extension that's posted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To share your feedback and comments about this feature, see [You can now respond to user reviews on your Microsoft Edge Add-ons page](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions/18) in **Discussions** in the MicrosoftEdge-Extensions repo. @@ -51,7 +51,7 @@ To share your feedback and comments about this feature, see [You can now respond ## Update an extension by using the Microsoft Edge Add-ons API -You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) without using Partner Center. For more information, see [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md). +You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) without using Partner Center. For more information, see [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md). *Released March 2022* @@ -120,7 +120,7 @@ Microsoft Edge extensions now support Manifest V3. See the blog post [Manifest ## Localization of extension listings at Microsoft Edge Add-ons -You can control localization of extension listings that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). You can choose a subset of languages, instead of manually entering each language in the listing details on Microsoft Partner Center. You can also elect to use the same marketing assets across all marketplaces. +You can control localization of extension listings that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). You can choose a subset of languages, instead of manually entering each language in the listing details on Microsoft Partner Center. You can also elect to use the same marketing assets across all marketplaces. See [Partner Center improvements related to Microsoft Edge extensions store listing and certification](https://techcommunity.microsoft.com/t5/articles/partner-center-improvements-related-to-microsoft-edge-extensions/m-p/2118981). diff --git a/microsoft-edge/extensions/whats-new/roadmap.md b/microsoft-edge/extensions/whats-new/roadmap.md index c2aae187bb..be4c6235a9 100644 --- a/microsoft-edge/extensions/whats-new/roadmap.md +++ b/microsoft-edge/extensions/whats-new/roadmap.md @@ -43,7 +43,7 @@ See [Develop an extension for the Microsoft Edge sidebar](../developer-guide/sid ## Developers can add their contact information -Users of your extension will be able to report issues through the extension's page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). Developer support information will be shown on the product page of an extension. This information will allow users to directly reach out to the extension developer for extension-specific support. +Users of your extension will be able to report issues through the extension's page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Developer support information will be shown on the product page of an extension. This information will allow users to directly reach out to the extension developer for extension-specific support. diff --git a/microsoft-edge/index.yml b/microsoft-edge/index.yml index ab51fd4bbb..70fd3b921b 100644 --- a/microsoft-edge/index.yml +++ b/microsoft-edge/index.yml @@ -5,7 +5,7 @@ summary: Explore documentation, references, and code samples to help you deploy, brand: m365 metadata: title: Microsoft Edge documentation - description: Microsoft Edge information for developers, IT admins, and browser users; including DevTools, Extensions, PWAs, WebDriver, and more. + description: Microsoft Edge information for developers, IT admins, and browser users; including DevTools, Edge Add-ons (such as extensions), PWAs, WebDriver, and more. ms.topic: hub-page author: MSEdgeTeam ms.author: msedgedevrel @@ -168,7 +168,7 @@ conceptualContent: # ----------------------------------------------------------------------------- # Card r2c3 - - title: Extensions for enterprise + - title: Extensions for enterprise # add-ons include extensions, themes, web apps links: - text: Manage extensions for Microsoft Edge for Business url: /deployedge/microsoft-edge-manage-extensions # https://learn.microsoft.com/deployedge/microsoft-edge-manage-extensions diff --git a/microsoft-edge/progressive-web-apps/how-to/app-actions.md b/microsoft-edge/progressive-web-apps/how-to/app-actions.md index 89a38c7d2a..5ffc140994 100644 --- a/microsoft-edge/progressive-web-apps/how-to/app-actions.md +++ b/microsoft-edge/progressive-web-apps/how-to/app-actions.md @@ -356,9 +356,9 @@ If you want to try out the latest capabilities of App Actions in Edge Canary, yo 1. Click the **Details** button. - Your PWA is indicated as installed from Microsoft Store. + Your PWA is indicated as installed from the [Microsoft Store](https://apps.microsoft.com). -Your PWA has now been installed as a Store PWA in Edge Canary. +Your PWA has now been installed as a store PWA in Edge Canary. diff --git a/microsoft-edge/progressive-web-apps/how-to/digital-goods-api.md b/microsoft-edge/progressive-web-apps/how-to/digital-goods-api.md index f357798f2e..5fcb47bece 100644 --- a/microsoft-edge/progressive-web-apps/how-to/digital-goods-api.md +++ b/microsoft-edge/progressive-web-apps/how-to/digital-goods-api.md @@ -10,13 +10,13 @@ ms.date: 06/04/2025 --- # Provide in-app purchases with the Digital Goods API -If your Progressive Web App (PWA) is listed in the Microsoft Store, you can provide in-app products and subscriptions by using the Digital Goods API and the Payment Request API. +If your Progressive Web App (PWA) is listed in the [Microsoft Store](https://apps.microsoft.com), you can provide in-app products and subscriptions by using the Digital Goods API and the Payment Request API. ## Digital Goods API -The Digital Goods API is an interface between your PWA app and the Microsoft Store. The Digital Goods API supports: +The Digital Goods API is an interface between your PWA app and the [Microsoft Store](https://apps.microsoft.com). The Digital Goods API supports: * Querying the details of a digital item from the Microsoft Store backend, such as the item's name, description, and regional price. * Consuming or acknowledging purchases. * Checking the digital items that are currently owned by the user. @@ -30,7 +30,7 @@ See: ## Payment Request API -The Payment Request API⁠⁠ handles the actual payment transaction when a purchase is made by a user. The Payment Request API uses the item details that the Digital Goods API provides, to make the in-app purchase by using whichever billing payment method the user has set up at the Microsoft Store. +The Payment Request API⁠⁠ handles the actual payment transaction when a purchase is made by a user. The Payment Request API uses the item details that the Digital Goods API provides, to make the in-app purchase by using whichever billing payment method the user has set up at the [Microsoft Store](https://apps.microsoft.com). See: * [Payment Request API](https://developer.mozilla.org/docs/Web/API/Payment_Request_API) at MDN. @@ -85,7 +85,7 @@ try { } ``` -This payment method `getDigitalGoodsService("https://store.microsoft.com/billing")` is available only for a PWA that's installed from the Microsoft Store, on Windows. No other settings are needed. +This payment method `getDigitalGoodsService("https://store.microsoft.com/billing")` is available only for a PWA that's installed from the [Microsoft Store](https://apps.microsoft.com), on Windows. No other settings are needed. See also: * [getDigitalGoodsService() method](https://wicg.github.io/digital-goods/#getdigitalgoodsservice-method) of the `Window` interface. @@ -97,7 +97,7 @@ See also: Use the `getDetails` method of the `DigitalGoodsService` interface to query item details. -After connecting the Digital Goods service to Microsoft Store, you can use the API to access product and purchase information. The `getDetails` method lets you get information about the items you've set up in the Partner Center. Display information such as the product title, description, and price in your app UI, so the user knows what's available for purchase. +After connecting the Digital Goods service to [Microsoft Store](https://apps.microsoft.com), you can use the API to access product and purchase information. The `getDetails` method lets you get information about the items you've set up in the Partner Center. Display information such as the product title, description, and price in your app UI, so the user knows what's available for purchase. The `getDetails` method takes a list of item IDs, which correspond to the product IDs of the in-app products and subscriptions you created in the Partner Center. @@ -117,7 +117,7 @@ for (item of itemDetails) { The returned `itemDetails` sequence may be in any order, and might not include an item if the item doesn't exist on the server (that is, if there's not a 1:1 correspondence between the input list and output list). -The item ID is a string that represents the primary key of the items. In the Microsoft Store, the item ID is `InAppOfferToken`. There is no function to get a list of item IDs; item IDs should be hardcoded in the client code or fetched from your own server (the developer's server). +The item ID is a string that represents the primary key of the items. In the [Microsoft Store](https://apps.microsoft.com), the item ID is `InAppOfferToken`. There is no function to get a list of item IDs; item IDs should be hardcoded in the client code or fetched from your own server (the developer's server). The item's `price` is a `PaymentCurrencyAmount` that contains the current price of the item in the user's current region and currency. The `price` is designed to be formatted for the user's current locale by using `Intl.NumberFormat`, as shown above. @@ -247,6 +247,8 @@ See also: ## See also +* [Microsoft Store](https://apps.microsoft.com) + GitHub: * [Digital Goods API For Microsoft Store PWA Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PwaDigitalGoods/explainer.md) * [Digital Goods API specification](https://wicg.github.io/digital-goods/) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 7fffd50e17..e9722f33ca 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -27,7 +27,7 @@ See also [PWAs as URL Handlers](https://web.dev/pwa-url-handler/). The operating system that your PWA is installed on automatically launches your PWA for any link that refers to content that's within the scope of the PWA, when either of the following conditions are met: -* The PWA was installed from the Microsoft Store on Windows. +* The PWA was installed from the [Microsoft Store](https://apps.microsoft.com) on Windows. * The PWA was installed by using Microsoft Edge, and Microsoft Edge is the default browser on the device. No code is required for automatic link handling to work, but end users can opt-out of automatic link handling. To opt-out of automatic link handling: diff --git a/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md b/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md index d1d9786897..e694ac4493 100644 --- a/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md +++ b/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md @@ -10,22 +10,25 @@ ms.date: 10/06/2023 --- # Publish a PWA to the Microsoft Store -Publishing your Progressive Web App (PWA) to the [Microsoft Store](/windows/uwp/publish/index) brings the following advantages: +Publishing your Progressive Web App (PWA) to the [Microsoft Store](https://apps.microsoft.com) brings the following advantages: | Advantage | Description | |---|---| | **Discoverability** | Users naturally look for apps in the app store. When you publish to the Microsoft Store, millions of Windows users can discover your PWA alongside other Windows apps. The Store showcases apps through categories, curated collections, and more. App discovery portals provide an easy browsing and shopping experience for potential users of your app. You can even enhance your Store listing with screenshots, a hero image, and video trailers - see [App screenshots, images, and trailers](/windows/apps/publish/publish-your-app/screenshots-and-images). | | **Trustworthiness** | Windows customers know they can trust their Microsoft Store purchases and downloads, because they adhere to the rigorous [Microsoft Store Policies](/windows/apps/publish/store-policies). | | **Easy install** | The Microsoft Store provides a consistent and user-friendly install experience across [all Windows 10 or later apps](https://apps.microsoft.com). | -| **App analytics** | The [Microsoft Partner Center dashboard](/windows/uwp/publish/index) provides [detailed analytics](/windows/uwp/publish/analytics) about your app's health, usage, and more. | +| **App analytics** | [Partner Center dashboard](https://partner.microsoft.com/dashboard/microsoftedge/) provides detailed analytics (insights) about your app's health, usage, and more; see [Apps and games overview](/partner-center/insights/apps-and-games-overview). | -To publish your PWA to the Microsoft Store, no code changes are required. Instead, you create an app reservation in Microsoft Partner Center, package your PWA using PWA Builder, and then submit your package to the Microsoft Store. The following sections explain these steps. +To publish your PWA to the Microsoft Store, no code changes are required. Instead, you create an app reservation in Microsoft Partner Center, package your PWA using [PWA Builder](https://www.pwabuilder.com), and then submit your package to the Microsoft Store. The following sections explain these steps. + +See also: +* [Get started: Publish your first app in the Microsoft Store](/windows/apps/publish/) ## Create an app reservation -To submit your app to the Microsoft Store, you use [Microsoft Partner Center](https://partner.microsoft.com/dashboard/windows/overview). +To submit your app to the [Microsoft Store](https://apps.microsoft.com), you use [Microsoft Partner Center](https://partner.microsoft.com/dashboard/windows/overview). To create an app reservation: @@ -89,9 +92,11 @@ See also: * [What is a classic package?](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/classic-package.md) * [Bundling MSIX packages](/windows/msix/package/bundling-overview). + + #### Submit your app package to the Microsoft Store -To submit your app to the Microsoft Store: +To submit your app to the [Microsoft Store](https://apps.microsoft.com): 1. Go to [Microsoft Partner Center](https://partner.microsoft.com/dashboard/windows/overview). 1. Select your app. @@ -109,7 +114,7 @@ After you complete your submission, your app is reviewed, typically within 24 to ## Measure usage of your PWA installed from the Microsoft Store -When your PWA is initially launched, if the PWA was installed from the Microsoft Store, Microsoft Edge includes the following `Referer` header with the request of the first navigation of your web app. +When your PWA is initially launched, if the PWA was installed from the [Microsoft Store](https://apps.microsoft.com), Microsoft Edge includes the following `Referer` header with the request of the first navigation of your web app. ``` Referer: app-info://platform/microsoft-store @@ -121,27 +126,33 @@ Use this feature to measure distinct traffic from your PWA that was installed fr ## Redirect to locale-specific domains without displaying additional UI -By default, a PWA that's installed from the Microsoft Store displays an additional UI when the app is redirected to a locale-specific domain. The added UI shows the URL and page title. This UI is added because navigation to the locale-specific domain is considered _out of scope_. +By default, a PWA that's installed from the [Microsoft Store](https://apps.microsoft.com) displays an additional UI when the app is redirected to a locale-specific domain. The added UI shows the URL and page title. This UI is added because navigation to the locale-specific domain is considered _out of scope_. The following figure shows the UI that is introduced when a user moves outside the scope of a PWA. ![The additional UI with URL and page title when the app is redirected to another domain](./microsoft-store-images/locale-redirection-additional-ui.png) + + #### Domain redirection with PWAs installed from the browser A Web App Manifest is tied to a single domain. However, some PWAs use locale-specific domains for their customers in specific regions of the globe. When visiting the PWA in a web browser, customers are seamlessly transitioned from the principal domain (for example, `contoso.com`) to a locale-specific domain (for example, `contoso.co.ke`), because the redirect happens during initial load of that website. Customers who install the PWA from Microsoft Edge would therefore install the PWA from the locale-specific domain. Subsequent launches of the PWA go directly to that locale-specific domain, instead of first going to the principal domain. + + #### Domain redirection with PWAs installed from the Microsoft Store -PWAs that are installed from the Microsoft Store have a hard-coded start URL that is pointed at the principal domain. When the PWA is launched, the PWA initially navigates to the principal domain, and then a customer may (as necessary) be redirected to their locale-specific domain. If that redirection occurs, the navigation is considered "out of scope". As a result, the app displays the URL and page title at the top of the page. +PWAs that are installed from the [Microsoft Store](https://apps.microsoft.com) have a hard-coded start URL that is pointed at the principal domain. When the PWA is launched, the PWA initially navigates to the principal domain, and then a customer may (as necessary) be redirected to their locale-specific domain. If that redirection occurs, the navigation is considered "out of scope". As a result, the app displays the URL and page title at the top of the page. Displaying the URL and page title is a security feature to ensure that users know they have left the context of the PWA. This added UI makes sense when a user loads a page from another website in the context of the PWA. However, that added UI may be inappropriate when a user moves among domains that are all part of the same website. + + #### Prevent the locale-specific URL and title from being displayed -It's currently impossible, for apps installed from the Microsoft Store, to prevent displaying the additional URL and title UI when redirecting to a locale-specific domain. +It's currently impossible, for apps installed from the [Microsoft Store](https://apps.microsoft.com), to prevent displaying the additional URL and title UI when redirecting to a locale-specific domain. In the future, _scope extensions_ will make it possible for a PWA to capture navigation to paths, subdomains, or even sites other than its own scope. The scope extensions feature is in active development and isn't ready to be used yet. To find out more about the state of development of this feature in Chromium, check out the [Web app scope extensions feature](https://chromestatus.com/feature/5746537956114432) at Chrome Platform Status. @@ -151,16 +162,20 @@ Once the feature can be used in Microsoft Edge, we will document it here. In the ## Make updates to your app -Generally, when you update your PWA code, you don't need to create a new app package and submit it to the Microsoft Store again. For example, suppose you make changes to your app's front-end HTML, CSS, or JavaScript code, or to your service worker. The next time the user launches the app, the changes are downloaded by the browser that's running your app from your web server. +Generally, when you update your PWA code, you don't need to create a new app package and submit it to the [Microsoft Store](https://apps.microsoft.com) again. For example, suppose you make changes to your app's front-end HTML, CSS, or JavaScript code, or to your service worker. The next time the user launches the app, the changes are downloaded by the browser that's running your app from your web server. -However, if you make changes to the web app manifest file, you must create a new app package and submit it to the Microsoft Store again. For example, in the manifest, you might change the app icon or app name, or add manifest members such as `file_handlers`, `protocol_handlers`, or `share_target`. Creating and submitting a new app package is required when the manifest is changed, because the information in the web app manifest file is copied to the Windows app package, for better integration with Windows. +However, if you make changes to the web app manifest file, you must create a new app package and submit it to the Microsoft Store again. For example, in the manifest, you might change the app icon or app name, or add manifest members such as `file_handlers`, `protocol_handlers`, or `share_target`. Creating and submitting a new app package is required when the manifest is changed, because the information in the web app manifest file is copied to the Windows app package, for better integration with Windows. ## See also -* [Test and submit your PWA app package](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/next-steps.md) -* [Publish a new PWA to the Store](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/publish-new-app.md) -* [Update an existing Store app to a PWA](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/update-existing-app.md) -* [Image recommendations for PWAs in the Store](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/image-recommendations.md) -* [App packaging explainer](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/classic-package.md) +* [Microsoft Store](https://apps.microsoft.com) +* [PWA Builder](https://www.pwabuilder.com) + +Docs in the PWA Builder repo: +* [Next steps for getting your PWA into the Microsoft Store](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/next-steps.md) - Test and submit your PWA app package. +* [Publish a new app to the Store](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/publish-new-app.md) +* [Update an existing app in the Store](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/update-existing-app.md) - Update an existing Store app to a PWA. +* [Image recommendations for Windows PWA packages](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/image-recommendations.md) - Image recommendations for PWAs in the Store. +* [What is a classic package?](https://github.com/pwa-builder/pwabuilder-windows-chromium-docs/blob/master/classic-package.md) - App packaging explainer. diff --git a/microsoft-edge/progressive-web-apps/how-to/widgets.md b/microsoft-edge/progressive-web-apps/how-to/widgets.md index 0f1a7e451f..41842c92f9 100644 --- a/microsoft-edge/progressive-web-apps/how-to/widgets.md +++ b/microsoft-edge/progressive-web-apps/how-to/widgets.md @@ -27,7 +27,7 @@ An existing PWA cannot simply be placed into the widget dashboard as-is, like yo See also: * [Build a PWA for the sidebar in Microsoft Edge](./sidebar.md) -To build a PWA-driven widget and deliver it via the Microsoft Store, no C++/C# code is required. Once you've produced the widget, and can successfully install and run the widget from a public endpoint, you can package the app by using [PWABuilder.com](https://www.pwabuilder.com) and ship the app to the Microsoft Store without requiring any additional code. The PWA backing the widget must be installable from a public endpoint, because PWABuilder doesn't support packing apps from `localhost`. +To build a PWA-driven widget and deliver it via the [Microsoft Store](https://apps.microsoft.com), no C++/C# code is required. Once you've produced the widget, and can successfully install and run the widget from a public endpoint, you can package the app by using [PWABuilder.com](https://www.pwabuilder.com) and ship the app to the Microsoft Store without requiring any additional code. The PWA backing the widget must be installable from a public endpoint, because PWABuilder doesn't support packing apps from `localhost`. See also: diff --git a/microsoft-edge/progressive-web-apps/index.md b/microsoft-edge/progressive-web-apps/index.md index dc3a09277b..91e54fd5f5 100644 --- a/microsoft-edge/progressive-web-apps/index.md +++ b/microsoft-edge/progressive-web-apps/index.md @@ -33,7 +33,7 @@ When installed on a device, PWAs function just like other apps. For example: * PWAs have their own application icons that can be added to a device's home screen or task bar. * PWAs can be launched automatically when an associated file type is opened. * PWAs can run when the user signs in. -* PWAs can be submitted to application stores, such as the Microsoft Store. +* PWAs can be submitted to app stores, such as the [Microsoft Store](https://apps.microsoft.com). #### Advanced capabilities @@ -88,7 +88,7 @@ There isn't much you can't do today with web technologies. Many features that we Thanks to Microsoft Edge, PWAs on desktop can take full advantage of these capabilities to deliver what users expect desktop apps to be able to do. These capabilities provide more engaging experiences across web and desktop platforms. -To find examples of what PWAs can do, see [Myth Busting PWAs](https://www.davrous.com/2019/10/18/myth-busting-pwas-the-new-edge-edition). +To find examples of what PWAs can do, see [Myth Busting PWAs – The New Edge Edition](https://www.davrous.com/2019/10/18/myth-busting-pwas-the-new-edge-edition). @@ -98,7 +98,7 @@ Because Progressive Web Apps (PWAs) are just like other apps in the [Microsoft S The Microsoft Store provides a trustworthy and familiar experience for users to install your app. Additionally, you can view detailed usage statistics and charts that let you know how your apps in the Microsoft Store are doing. -See [Publish a PWA to the Microsoft Store](how-to/microsoft-store.md). +See [Publish a PWA to the Microsoft Store](./how-to/microsoft-store.md). diff --git a/microsoft-edge/progressive-web-apps/ux.md b/microsoft-edge/progressive-web-apps/ux.md index 585d2d9904..07de6bc9ed 100644 --- a/microsoft-edge/progressive-web-apps/ux.md +++ b/microsoft-edge/progressive-web-apps/ux.md @@ -24,7 +24,7 @@ When Microsoft Edge determines that a website is an installable Progressive Web 1. Click **Install** to complete the installation and run the PWA in Windows. -Many PWAs are also present on the Microsoft Store, and can be installed directly from there, without needing to open Microsoft Edge. +Many PWAs are also present on the [Microsoft Store](https://apps.microsoft.com), and can be installed directly from there, without needing to open Microsoft Edge. To install a PWA from the Microsoft Store, select **Get** on the app page: diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml index 1096ad0b3c..4d7a43dc9c 100644 --- a/microsoft-edge/toc.yml +++ b/microsoft-edge/toc.yml @@ -1106,7 +1106,6 @@ - name: Overview of Microsoft Edge extensions href: ./extensions/index.md - # ------------------------------------- - name: What's new items: @@ -1115,7 +1114,6 @@ - name: Roadmap for Microsoft Edge extensions href: ./extensions/whats-new/roadmap.md - # ------------------------------------- - name: Get started items: @@ -1130,13 +1128,11 @@ - name: Sideload an extension to install and test it locally href: ./extensions/getting-started/extension-sideloading.md - # ------------------------------------- - name: Port an extension to Microsoft Edge items: - name: Port a Chrome extension to Microsoft Edge href: ./extensions/developer-guide/port-chrome-extension.md - # ------------------------------------- - name: Develop an extension items: @@ -1188,7 +1184,6 @@ - name: Developer policies for extensions at Microsoft Edge Add-ons href: /legal/microsoft-edge/extensions/developer-policies displayName: policy - # ------------------------------------- - name: Register as an extension developer items: @@ -1208,7 +1203,6 @@ - name: Manage account settings href: ./extensions/publish/manage-settings.md - # ------------------------------------- - name: Publish an extension items: @@ -1227,6 +1221,8 @@ - name: Curation and review process for extensions at Microsoft Edge Add-ons href: ./extensions/publish/add-ons-curation.md + - name: Use the Microsoft Edge Add-ons badge to promote your add-on + href: ./extensions/publish/add-ons-badge.md # ------------------------------------- - name: Update an extension items: @@ -1246,7 +1242,6 @@ - name: Transfer ownership of an extension href: ./extensions/update/transfer-ownership.md - # ------------------------------------- - name: Analytics and user reviews items: @@ -1256,7 +1251,6 @@ - name: Reply to user reviews of an extension href: ./extensions/publish/reply-user-reviews.md displayName: Respond to user reviews - # ------------------------------------- - name: Best practices items: @@ -1264,13 +1258,11 @@ href: ./extensions/developer-guide/best-practices.md - name: Minimize an extension's impact on page load time href: ./extensions/developer-guide/minimize-page-load-time-impact.md - # ------------------------------------- - name: Samples items: - name: Samples for Microsoft Edge extensions href: ./extensions/samples.md - # ------------------------------------- - name: Contact the Microsoft Edge extensions team href: ./extensions/contact.md @@ -1389,7 +1381,6 @@ - name: Set up your Dev environment for WebView2 href: ./webview2/how-to/machine-setup.md - # ----------------------------------------------------------------------------- - name: Platforms and samples items: @@ -1485,7 +1476,6 @@ - name: WebView2 sample apps href: ./webview2/code-samples-links.md - # ----------------------------------------------------------------------------- - name: Navigation, events, and authentication items: @@ -1498,7 +1488,6 @@ - name: Basic authentication for WebView2 apps href: ./webview2/concepts/basic-authentication.md - # ----------------------------------------------------------------------------- - name: Customization and UI items: @@ -1528,7 +1517,6 @@ - name: WebView2 browser flags href: ./webview2/concepts/webview-features-flags.md - # ----------------------------------------------------------------------------- - name: Web and native interop items: @@ -1550,7 +1538,6 @@ - name: How WinRT types and members are represented in JavaScript href: ./webview2/how-to/winrt-js-conversion.md - # ----------------------------------------------------------------------------- - name: Distribution and SDK versions items: @@ -1592,7 +1579,6 @@ - name: Publish a UWP WebView2 app to the Microsoft Store href: ./webview2/how-to/publish-uwp-app-store.md displayName: Partner Center, Microsoft Store - # ----------------------------------------------------------------------------- - name: Best practices items: @@ -1601,7 +1587,6 @@ - name: Develop secure WebView2 apps href: ./webview2/concepts/security.md - # ----------------------------------------------------------------------------- - name: Test and automation for WebView2 apps items: @@ -1624,7 +1609,6 @@ - name: Self-host by deploying preview channels href: ./webview2/how-to/self-hosting.md displayName: self-hosting - # ----------------------------------------------------------------------------- - name: Debug WebView2 apps items: @@ -1657,7 +1641,6 @@ - name: Remote debugging Xbox WebView2 WinUI 2 (UWP) apps href: ./webview2/how-to/remote-debugging-xbox.md displayName: remotely debug - # ----------------------------------------------------------------------------- - name: Process and threading model items: @@ -1669,7 +1652,6 @@ - name: Threading model for WebView2 apps href: ./webview2/concepts/threading-model.md - # ----------------------------------------------------------------------------- - name: User data and history items: @@ -1685,7 +1667,6 @@ - name: Data and privacy in WebView2 href: ./webview2/concepts/data-privacy.md - # ----------------------------------------------------------------------------- - name: Release Notes items: @@ -1698,7 +1679,6 @@ - name: Archived Release Notes for the WebView2 SDK href: ./webview2/release-notes/archive.md - # ----------------------------------------------------------------------------- - name: WebView2 Reference items: diff --git a/microsoft-edge/web-platform/sidebar.md b/microsoft-edge/web-platform/sidebar.md index 778091c913..d6ad080460 100644 --- a/microsoft-edge/web-platform/sidebar.md +++ b/microsoft-edge/web-platform/sidebar.md @@ -27,7 +27,7 @@ The two different ways in which you can leverage the sidebar are designed to mee | Aspect | Sidebar app | Sidebar extension | |---|---|---| | Term definition | A Progressive Web App (PWA) that runs in the sidebar. | A Microsoft Edge extension that displays content in the sidebar. | -| Distribution | Like a website, the app is hosted on the app's web server. | The extension is distributed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). | +| Distribution | Like a website, the app is hosted on the app's web server. | The extension is distributed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). | | Capabilities | The app can make use of all web APIs and features, as well as PWA capabilities such as offline support, push, or file system access. | The extension can make use of powerful extension APIs, such as reading or modifying the current page. | | Context | The app runs in its own web context, separate from the main tab. | The extension can access the current webpage and modify the webpage via the extension's content script. | | Installation | The user installs the app by interacting with the sidebar when visiting the app's website. | The extension is installed by users from Microsoft Edge Add-ons. | @@ -50,7 +50,7 @@ To learn more about PWAs and how to create them, see [Overview of Progressive We Microsoft Edge extensions can optionally use the sidebar API to show a custom UI in the sidebar in Microsoft Edge. This is in addition to the other places extensions also appear in, such as in the Microsoft Edge toolbar, or as popups. -If your app's experience relies on powerful extensions APIs, for example to read or modify the current page, then a sidebar extension provides these capabilities. Users can find and install these extensions at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/). +If your app's experience relies on powerful extensions APIs, for example to read or modify the current page, then a sidebar extension provides these capabilities. Users can find and install these extensions at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The Microsoft Edge team continues to evolve these sidebar extensibility models and welcomes your feedback. To leave feedback, [create a new issue](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new/) on the repo, or [search for existing issues](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues) and join existing conversations. diff --git a/microsoft-edge/webview2/how-to/publish-uwp-app-store.md b/microsoft-edge/webview2/how-to/publish-uwp-app-store.md index 8632d7aef9..0feda69aa7 100644 --- a/microsoft-edge/webview2/how-to/publish-uwp-app-store.md +++ b/microsoft-edge/webview2/how-to/publish-uwp-app-store.md @@ -10,23 +10,21 @@ ms.date: 04/27/2022 --- # Publish a UWP WebView2 app to the Microsoft Store -A _UWP WebView2 app_ is a Universal Windows Platform (UWP) app that hosts the WebView2 control. To make a UWP WebView2 app widely available, you can publish it to the Microsoft Store, by following the steps below. +A _UWP WebView2 app_ is a Universal Windows Platform (UWP) app that hosts the WebView2 control. To make a UWP WebView2 app widely available, you can publish it to the [Microsoft Store](https://apps.microsoft.com), by following the steps below. -For general background information about publishing to the Windows Store, see [Publish Windows apps and games](/windows/uwp/publish/), at Windows App Development documentation > UWP. The steps below provide the specific details about how to publish a UWP WebView2 app. +For general background information about publishing to the Windows Store, see [Get started: Publish your first app in the Microsoft Store](/windows/apps/publish/). The steps below provide the specific details about how to publish a UWP WebView2 app. ## Step 1: Configure a Microsoft Store account in Visual Studio -* Make sure you have a Microsoft Store account configured in Microsoft Visual Studio. - - If needed, see [Get registered](https://developer.microsoft.com/microsoft-store/register/), about developer accounts for the Microsoft Store. Then continue with the steps below. +Make sure you have a [Microsoft Store](https://apps.microsoft.com) account configured in Microsoft Visual Studio. See [Enroll as a developer for Microsoft Store](https://developer.microsoft.com/microsoft-store/register/). ## Step 2: Test the non-packaged host app -Test for these common basic issues before submitting your app to the Microsoft Store. This will help prevent Store certification failures, which would delay your app from becoming available. +Test for these common basic issues before submitting your app to the [Microsoft Store](https://apps.microsoft.com). This will help prevent Store certification failures, which would delay your app from becoming available. 1. Make sure the app runs correctly on startup. @@ -36,7 +34,7 @@ Test for these common basic issues before submitting your app to the Microsoft S ## Step 3: Package the host app -The Microsoft Store requires submitting a packaged app. Package your app as follows: +The [Microsoft Store](https://apps.microsoft.com) requires submitting a packaged app. Package your app as follows: 1. Update the `package.appxmanifest` with all needed content, such as Visual Assets, Packaging name, and Application information. If you don't do this, the Microsoft Store validation step will fail. Then continue with the steps below. @@ -74,7 +72,7 @@ To make sure that all required content files are present in the package, and to -Windows App Certification Kit (WACK) is an app that's a certification tool. This tool evaluates your host app against the Microsoft Store's requirements. +Windows App Certification Kit (WACK) is an app that's a certification tool. This tool evaluates your host app against the [Microsoft Store](https://apps.microsoft.com)'s requirements. Once you're satisfied that your packaged app works, run the Windows App Certification Kit (WACK): @@ -112,7 +110,7 @@ If your app failed the **Branding** checks, update all the Visual Assets in the ###### App Capabilities -If your app failed the **App Capabilities** tests, turn off any unneeded capabilities. If you need a special use capability you will need to get Microsoft Store approval or use non-Store distribution methods. +If your app failed the **App Capabilities** tests, turn off any unneeded capabilities. If you need a special use capability you will need to get [Microsoft Store](https://apps.microsoft.com) approval or use non-Store distribution methods. @@ -142,7 +140,7 @@ If your app failed the **Supported API** test, update the Windows SDK to version ## See also -* [Get registered](https://developer.microsoft.com/microsoft-store/register/) - Creating a developer account for the Microsoft Store. -* [Publish Windows apps and games](/windows/uwp/publish/), at Windows App Development documentation > UWP. General background information about publishing to the Windows Store. +* [Enroll as a developer for Microsoft Store](https://developer.microsoft.com/microsoft-store/register/) +* [Get started: Publish your first app in the Microsoft Store](/windows/apps/publish/) * [Windows App Certification Kit](/windows/uwp/debug-test-perf/windows-app-certification-kit) * [Partner Center (partner.microsoft.com)](https://partner.microsoft.com).