Link to Microsoft Add-ons site (#3671)

* add links

* linkfix

* alert

* -alert

* apply comments

* merge 2 firstchilds

* apis = features

* OT title

* flag article for re-titling

* correct task title for Ad Selection

* sort cards per audience

* help & support

* OT Detailed contents

* incorp my review

* polish top 2 rows of hub page

* hub infotypes

Author: mikehoffms

microsoft-edge/develop-web-microsoft-edge.md

@@ -23,13 +23,12 @@ To stay up to date with web platform feature changes in Microsoft Edge and the C
 
 
 <!-- ====================================================================== -->
-## Experimental web platform features
+## Experimental APIs for Microsoft Edge
 
-Use origin trials to try out experimental APIs on your own live site for a limited period of time.  When using origin trials, users of Microsoft Edge that visit your site can run code that uses experimental APIs.
+Use origin trials to try out experimental APIs and features on your live site for a limited period of time.  When using origin trials, users of Microsoft Edge that visit your site can run code that uses experimental APIs and features.
 
 See:
-* [Use origin trials in Microsoft Edge](./origin-trials/index.md)
-* [Sign up for the Ad Selection API](./web-platform/ad-selection-api.md)
+* [Test experimental APIs and features by using origin trials](./origin-trials/index.md)
 
 
 <!-- ====================================================================== -->

microsoft-edge/developer/index.yml

@@ -43,7 +43,7 @@ landingContent:
 # =============================================================================
 # Row 1
 # -----------------------------------------------------------------------------
-# Card for toc bucket 1 (Release notes) & 2 (Experimental web platform features) - r1c1
+# Card for toc bucket 1 (Release notes) & 2 (Experimental APIs for Microsoft Edge) - r1c1
   - title: Web platform updates
     linkLists:
       - linkListType: whats-new
@@ -54,15 +54,21 @@ landingContent:
           - text: Site compatibility-impacting changes
             url: ../web-platform/site-impacting-changes.md
 
-          - text: Use origin trials in Microsoft Edge
+          - text: Test experimental APIs and features by using origin trials
             url: ../origin-trials/index.md
 
+          - text: Provide user-relevant ads with the Ad Selection API
+            url: ../web-platform/ad-selection-api.md
+
           - text: Prompt a built-in language model with the Prompt API
             url: ../web-platform/prompt-api.md
 
           - text: Summarize, write, and rewrite text with the Writing Assistance APIs
             url: ../web-platform/writing-assistance-apis.md
 
+          - text: Translate text with the Translator API
+            url: ../web-platform/translator-api.md
+
 # -----------------------------------------------------------------------------
 # Card for toc bucket 3 - r1c2
   - title: Microsoft Edge DevTools
@@ -265,9 +271,6 @@ landingContent:
           - text: View a JSON file or server response with formatting
             url: ../web-platform/json-viewer.md
 
-          - text: Sign up for the Ad Selection API  # todo: moved to "Experimental web platform features" toc bucket, delete?
-            url: ../web-platform/ad-selection-api.md
-
 # -----------------------------------------------------------------------------
 # Card for toc bucket 9 - r3c2
   - title: Microsoft Edge IDE integration

microsoft-edge/extensions/developer-guide/manifest-v3.md

@@ -12,6 +12,8 @@ ms.date: 04/26/2024
 
 A _manifest file_ is the blueprint of an extension.  A manifest file for an extension includes information such as the version number of the extension, the title of the extension, and permissions needed to run the extension.  The manifest file follows the format specified by Manifest V2 or Manifest V3.
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 
 <!-- ---------------------------------------------------------------------- -->
 ## Overview of changes in Manifest V3
@@ -76,3 +78,4 @@ Microsoft continues to iteratively improve the platform and address the feedback
 * [Migrate an extension from Manifest V2 to V3](./migrate-your-extension-from-manifest-v2-to-v3.md)
 * [Manifest V2 support timeline](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline)<!-- chrome link ok, section is re: v2-v3 migration in chromium -->
 * [The phase-out timeline](https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline)<!-- chrome link ok, section is re: v2-v3 migration in chromium --> in _Resuming the transition to Manifest V3_.
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.

microsoft-edge/extensions/getting-started/extension-sideloading.md

@@ -12,6 +12,8 @@ ms.date: 01/16/2025
 
 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.
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 
 <!-- ====================================================================== -->
 ## Prerequisite: Have an extension to install
@@ -136,3 +138,4 @@ If running an extension causes an error, in some cases, an **Error** link is add
 
 * [Sample: Picture viewer pop-up webpage](../samples/picture-viewer-popup-webpage.md)
 * [Sample: Picture inserter using content script](../samples/picture-inserter-content-script.md)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Users install Edge Extensions

microsoft-edge/extensions/getting-started/index.md

@@ -11,30 +11,53 @@ ms.date: 02/06/2022
 # Extension concepts and architecture
 <!-- https://aka.ms/EdgeAddonsLearn -->
 
-This article introduces concepts about building a Microsoft Edge extension.  Follow along to understand how multi-tab browsers work.
+This article introduces Developer concepts about building a Microsoft Edge extension.  As an extension Developer, you can follow along to understand how multi-tab browsers work.
 
 A Microsoft Edge *extension* is a small app that users can opt into that adds or modifies features of Microsoft Edge to provide a specialized experience or function that is important to a target audience. For an introduction, see [Overview of Microsoft Edge extensions](../index.md).
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
+**Detailed contents:**
+* [Understand how browsers work](#understand-how-browsers-work)
+   * [Browser tabs are isolated threads](#browser-tabs-are-isolated-threads)
+   * [Each tab handles one GET request](#each-tab-handles-one-get-request)
+   * [Communication occurs between each tab and a remote server](#communication-occurs-between-each-tab-and-a-remote-server)
+   * [Communication model](#communication-model)
+* [Extension architecture](#extension-architecture)
+   * [Extension web server bundle](#extension-web-server-bundle)
+   * [Launching the extension server](#launching-the-extension-server)
+   * [Communication with tabs and browser toolbar](#communication-with-tabs-and-browser-toolbar)
+   * [Opt-in permissions at install time](#opt-in-permissions-at-install-time)
+* [See also](#see-also)
+
 
 <!-- ====================================================================== -->
 ## Understand how browsers work
 
 The following list outlines helpful information to understand before building your extension.
 
+
+<!-- ------------------------------ -->
 #### Browser tabs are isolated threads
 
 Each browser tab is isolated from every other tab.  Each tab runs in a separate thread that is isolated from other browser tabs and threads.
 
 ![One thread per browser tab](./index-images/index-image1-browsertabs.png)
 
+
+<!-- ------------------------------ -->
 #### Each tab handles one GET request
 
 Each tab handles one GET request.  Each tab uses a URL to get a single stream of data, which is normally an HTML document.  That single stream or page, includes instructions like JavaScript include tags, image references, CSS references, and more.  All resources are downloaded to that one tab page, and then the page is rendered in the tab.
 
+
+<!-- ------------------------------ -->
 #### Communication occurs between each tab and a remote server
 
 Communication occurs between each tab and a remote server.  Each tab runs in an isolated environment.  Each tab is still connected to the internet, but each is isolated from other tabs.  A tab can run JavaScript to communicate with a server.  The server is the originating server for the first GET request that was entered into the URL bar of the tab.
 
+
+<!-- ------------------------------ -->
 #### Communication model
 
 The extension model uses a different communication model.  Similar to a tab page, an extension runs in an individual thread that is isolated from other tab page threads.  A tab sends single GET requests to remote servers, and then renders the page.  However, an extension works similar to a remote server.  Installing an extension in a browser creates a standalone web server in the browser.  The extension is isolated from all tab pages.
@@ -47,30 +70,39 @@ The extension model uses a different communication model.  Similar to a tab page
 
 The following list outlines helpful information as it relates to the architecture of an extension.
 
+
+<!-- ------------------------------ -->
 #### Extension web server bundle
 
 An extension is a bundle of web resources.  The web resources are similar to other resources that you (the web developer) publish to web servers.  You bundle the web resources into a zip file when building an extension.
 
 The zip file includes HTML, CSS, JavaScript, and image files.  One more file is required in the root of the zip file.  The other file is the manifest file that is named `manifest.json`.  The manifest file is the blueprint of your extension and includes the version of your extension, the title, permissions needed for the extension to run, and so on.
 
+
+<!-- ------------------------------ -->
 #### Launching the extension server
 
 Web servers contain your web bundle.  A browser navigates to URLs on the server, and downloads the file to render in the browser.  A browser navigates using certificates, configuration files, and so on.  If an `index.html` file is specified, the file is stored at a special location on the web server.
 
 When you use an extension, the tab page of your browser gets to the web bundle of your extension using the extension runtime.  The extension runtime serves the files from the URL `extension://{some-long-unique-identifier}/index.html`, where `{some-long-unique-identifier}` is a unique identifier assigned to the extension during installation.  Each extension uses a different unique identifier.  Each identifier points to the web bundle that is installed in your browser.
 
+
+<!-- ------------------------------ -->
 #### Communication with tabs and browser toolbar
 
 An extension can communicate with tabs and the browser toolbar.  An extension can interact with the toolbar of your browser.  Each extension manages running tab pages in separate threads, and DOM manipulation on each tab page is isolated.  An extension uses the extensions API to communicate between the extension and tab pages.  The extensions API provides extra capabilities that include notification management, storage management, and so on.
 
 Just like web servers, an extension waits for notifications when the browser is open.  An extension and tab pages run in threads that are isolated from each other.  To allow an extension to work with any tab page, use the extensions API and set the permissions in the manifest file.
 
+
+<!-- ------------------------------ -->
 #### Opt-in permissions at install time
 
 An extension provides opt-in permissions at install time.  You specify the extension permissions in the `manifest.json` file.  When a user installs an extension, information about the permissions that the extension requires is displayed.  Based on the type of permission required, the extension can extract and use information from the browser.
 
 
 <!-- ====================================================================== -->
-## Next steps
+## See also
 
 * [Sample: Picture viewer pop-up webpage](../samples/picture-viewer-popup-webpage.md)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.

microsoft-edge/extensions/index.md

@@ -11,9 +11,11 @@ ms.date: 08/20/2024
 # Overview of Microsoft Edge extensions
 <!-- https://aka.ms/AboutEdgeAddons -->
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 _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.
 
-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.
+As a browser extension developer, 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.
 
@@ -184,6 +186,7 @@ To improve your extension's quality and eligibility for the **Featured** badge,
 * [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)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.
 
 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.

microsoft-edge/extensions/landing/index.yml

@@ -225,3 +225,18 @@ landingContent:
 
           - text: Minimize an extension's impact on page load time
             url: ../developer-guide/minimize-page-load-time-impact.md
+
+# -----------------------------------------------------------------------------
+# Card r3c3
+  - title: User docs and resources
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: Microsoft Edge Add-ons site  # store
+            url: https://microsoftedge.microsoft.com
+
+          - text: Everything to know about browser extensions  # introduction for users
+            url: https://www.microsoft.com/edge/learning-center/everything-to-know-about-browser-extensions
+
+          - text: Add, turn off, or remove extensions in Microsoft Edge  # support steps for users
+            url: https://support.microsoft.com/microsoft-edge/add-turn-off-or-remove-extensions-in-microsoft-edge-9c0ec68c-2fbc-2f2c-9ff0-bdc76f46b026

microsoft-edge/extensions/publish/create-dev-account.md

@@ -45,6 +45,8 @@ If you have a Partner Center account, but the Primary Owner of the account isn't
 
 To add and manage users in the Microsoft Edge program to manage extensions, you can associate your Partner Center account with your organization's Microsoft Entra tenant.
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 
 <!-- ====================================================================== -->
 ## Types of accounts related to publishing Microsoft Edge extensions
@@ -248,5 +250,6 @@ Entra:
 
 Other Microsoft.com sites:
 * [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login)
+   * [Account settings | Legal info](https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo)
 * [account.microsoft.com](https://account.microsoft.com/account)
-* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.

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

@@ -12,6 +12,8 @@ ms.date: 11/24/2025
 
 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 increase the extension's reach and make it available to other Microsoft Edge users, publish the extension at Microsoft Edge Add-ons, through Partner Center.
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 If you have an existing Chrome extension and you want to release it for Microsoft Edge users, first see [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md).
 
 **Detailed contents:**
@@ -473,7 +475,7 @@ Partner Center:
 * [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd)
 
 Microsoft Edge extensions:
-* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.
 
 Developer Agreement & Legal:
 * [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905)

microsoft-edge/extensions/whats-new/released-features.md

@@ -13,6 +13,8 @@ ms.date: 02/05/2025
 
 The following features or updates have been launched on [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/) for Microsoft Edge extensions.
 
+Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+
 
 <!-- ====================================================================== -->
 ## Transfer ownership of a Microsoft Edge extension
@@ -136,3 +138,4 @@ By clicking the extension certification report link, you can view and download t
 ## See also
 
 * [Release notes for Microsoft Edge web platform](../../web-platform/release-notes/index.md)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge.