Adds the 0.85 versioned docs to websitev2, following the same process used for 0.84 (#1263).

websitev2/docusaurus.config.js

@@ -37,8 +37,8 @@ const config = {
           sidebarPath: './sidebars.js',
           editUrl:
             'https://github.com/microsoft/react-native-windows-samples/blob/main/docs/',
-          lastVersion: '0.84',
-          onlyIncludeVersions: ['0.84', '0.83'],
+          lastVersion: '0.85',
+          onlyIncludeVersions: ['0.85', '0.84', '0.83'],
           exclude: ['flyout-component-windows.md'],
         },
         blog: false,

websitev2/src/pages/support.md

@@ -15,9 +15,10 @@ The React Native for Windows (RNW) Team strives to provide full support for the
 | Version | Support Phase | Release Date | Active Support Start | Maintenance Support Start | End of Support |
 | -- | -- | -- | -- | -- | -- |
 | [main](https://www.npmjs.com/package/react-native-windows/v/canary) | [Canary](#canary-support) | *N/A* | *N/A* | *N/A* | *N/A* |
-| [0.84](https://www.npmjs.com/package/react-native-windows/v/latest) | [Active](#active-support) | 06/22/2026 | 06/22/2026 | *TBD* | *TBD* |
+| [0.85](https://www.npmjs.com/package/react-native-windows/v/latest) | [Active](#active-support) | 09/10/2026 | 09/10/2026 | *TBD* | *TBD* |
+| [0.84](https://www.npmjs.com/package/react-native-windows/v/v0.84-stable) | [Maintenance](#maintenance-support) | 06/22/2026 | 06/22/2026 | 10/31/2026 | 12/31/2026 |
 | [0.83](https://www.npmjs.com/package/react-native-windows/v/v0.83-stable) | [Maintenance](#maintenance-support) | 05/27/2026 | 05/27/2026 | 07/31/2026 | 09/30/2026 |
-| [0.82](https://www.npmjs.com/package/react-native-windows/v/v0.82-stable) | [Maintenance](#maintenance-support) | 03/16/2026 | 03/16/2026 | 06/30/2026 | 08/31/2026 |
+| [0.82](https://www.npmjs.com/package/react-native-windows/v/v0.82-stable) | [Unsupported](#unsupported) | 03/16/2026 | 03/16/2026 | 06/30/2026 | 08/31/2026 |
 | [0.81](https://www.npmjs.com/package/react-native-windows/v/v0.81-stable) | [Unsupported](#unsupported) | 12/19/2025 | 12/19/2025 | 04/30/2026 | 06/30/2026 |
 
 <!--

websitev2/versioned_docs/version-0.85/app-publishing.md

@@ -0,0 +1,36 @@
+---
+id: app-publishing
+title: Publishing a React Native Windows App to the Microsoft Store
+---
+
+
+> **Architecture Review Needed:** This documentation was written to support development against React Native's "Old" or "Legacy" Architecture. It *may or may not* be directly applicable to New Architecture development and needs to be reviewed and potentially updated. For information on React Native architectures in React Native Windows, see [New vs. Old Architecture](new-architecture.md).
+
+## Steps to Publish a React Native Windows App to the Microsoft Store
+These are the steps to follow if you are looking to publish a React Native Windows app as a third party to the Microsoft Store. Since React Native Windows apps are Universal Windows Platform (UWP) apps, you can also see [Publish Windows apps - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/) for all kinds of documentation on the UWP app publishing process. 
+
+1. Sign-up for a developer account through the Microsoft Partner Center ([Register as an app developer – Windows app development](https://developer.microsoft.com/microsoft-store/register/)). For more guidance on the sign-up process see here: [Opening a developer account - UWP applications | Microsoft Docs](https://docs.microsoft.com/en-us/windows/uwp/publish/opening-a-developer-account).
+2. Sign into the Partner Center. You should now be able to reserve a name for your app ([Create your app by reserving a name - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/create-your-app-by-reserving-a-name)).
+3. Open your app's solution in Visual Studio.
+4. If you haven't already, generate visual assets for your app. You can generate visual assets from a base image in Visual Studio by opening your app's `Package.appmanifest` and navigating to the 'Visual Assets' section. Here you can supply your base image, and Visual Studio will generate the needed collection of assets.
+5. Right-click on your app project and select `Publish > Associate App with the Store…`. After you’ve signed-in (make sure you sign-in with the same account as the one used for the Partner Center) and selected your app, Visual Studio will update your `Package.appxmanifest` file with the new Publisher (a GUID) and the app name. You’ll also get a new `Package.StoreAssociation.xml` file in your project that should not be checked in ([Packaging MSIX apps - MSIX | Microsoft Docs](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#configure-your-project)).
+6. Set your solution configuration to 'Release'. Right-click on your app project and choose  `Publish > Create App Packages`. If you have already associated your project with an app in the Microsoft Store, you should have an option to 'Create Packages for the Associated Store App'. Fill out the form according to your app's information. This process should create an `.appxupload`, which you will upload to Partner Center later ([Packaging MSIX apps - MSIX | Microsoft Docs](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package-upload-file-for-store-submission)).
+7. Run your app through the latest version of the Windows App Certification Kit, and verify that it passes all tests ([Windows App Certification Kit - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/debug-test-perf/windows-app-certification-kit)).
+8. Select your newly reserved app name from the 'Overview' section in Partner Center to begin adding information to your app.
+9. Locate the 'Start a Submission' button on the current webpage. Hitting this button will open up the form for your first submission to the app store. 
+10. The app submission form will contain many questions about your app's age ratings, properties, pricing, etc. Click on each of the sections to fill in the information for your app ([App submissions - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/app-submissions)):
+
+  - Pricing and Availability ([Set app pricing and availability - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/set-app-pricing-and-availability))
+  - Properties ([Enter app properties - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/enter-app-properties))
+  - Age Ratings ([Age ratings - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/age-ratings))
+  - Store Listings ([Create app Store listings - UWP applications | Microsoft Docs](https://learn.microsoft.com/en-us/windows/apps/publish))
+  - Submission Options ([Manage submission options - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/manage-submission-options))
+
+11. Under the packages section you will be asked to upload your `.appxupload`. Make sure that your `.appxupload`…
+
+  - Signed with your desired certificate.
+  - Successfully passes WACK.
+  - Has personalized visual assets.
+  - Has a Display Name that matches the app name you have reserved.
+  - Created from the same developer account as the account where the submission is being made ([Upload app packages - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/upload-app-packages)).
+12. Once your submission form is fully filled out, you can submit your app to the Microsoft Store. It usually takes a couple of hours to run through certification and validation, and then possibly another couple hours for it to actually appear in the app store. ([The app certification process - UWP applications | Microsoft Docs](https://docs.microsoft.com/windows/uwp/publish/the-app-certification-process)).

websitev2/versioned_docs/version-0.85/autolink-windows-cli.md

@@ -0,0 +1,40 @@
+---
+id: autolink-windows-cli
+title: react-native autolink-windows
+---
+
+
+This guide will give you more information on the `autolink-windows` command of the React Native Windows CLI.
+
+## `autolink-windows`
+
+The `autolink-windows` CLI command is used to link the native code and build systems for a React Native for Windows app with any native community modules it uses.
+
+**Note:** Autolinking runs automatically as part of running the [run-windows command](run-windows-cli.md), unless the `--no-autolink` argument is used.
+
+### Usage
+Runs Windows-specific autolinking for your RNW project.
+
+```bat
+npx react-native autolink-windows
+```
+### Options
+
+Here are the options that `react-native autolink-windows` takes:
+| Option                | Input Type | Description                                      |
+|-----------------------|------------|--------------------------------------------------|
+| `--logging`           | boolean    | Verbose output logging                           |
+| `--check`             | boolean    | Only check whether any autolinked files need to change |
+| `--sln`               | string     | Override the app solution file determined by 'react-native config', i.e. `windows\myApp.sln` |
+| `--proj`              | string     | Override the app project file determined by 'react-native config', i.e. `windows\myApp\myApp.vcxproj` |
+| `--no-telemetry`      | boolean    | Disables sending telemetry that allows analysis of usage and failures of the react-native-windows CLI |
+| `-h`, `--help`        | boolean    | Display help for command                         |
+
+## Telemetry Notice
+
+This command sends telemetry to Microsoft by default. You can prevent the telemetry from being sent by using the `--no-telemetry` command line option. See below for more details.
+
+The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft's privacy statement. Our privacy statement is located at https://go.microsoft.com/fwlink/?LinkID=824704. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.
+
+This data collection notice only applies to the process of running the react-native-windows CLI commands.
+

websitev2/versioned_docs/version-0.85/codegen-windows-cli.md

@@ -0,0 +1,78 @@
+---
+id: codegen-windows-cli
+title: react-native codegen-windows
+---
+
+
+This guide will give you more information on the `codegen-windows` command of the React Native Windows CLI.
+
+## `codegen-windows`
+
+The `codegen-windows` CLI command is used to generate some necessary Windows-specific native code for native modules.
+
+### Usage
+Runs Windows-specific codegen for native modules.
+
+```bat
+npx react-native codegen-windows
+```
+### Options
+
+Here are the options that `react-native codegen-windows` takes:
+| Option                | Input Type | Description                                      |
+|-----------------------|------------|--------------------------------------------------|
+| `--logging`           | boolean    | Verbose output logging                           |
+| `--check`             | boolean    | Only check whether any codegen files need to change |
+| `--no-telemetry`      | boolean    | Disables sending telemetry that allows analysis of usage and failures of the react-native-windows CLI |
+| `-h`, `--help`        | boolean    | Display help for command                         |
+
+## Codegen Config
+
+The `react-native codegen-windows` command is configured by the `codegenConfig` object in the project's `package.json` file. This `codegenConfig` object is shared by all platforms, but the relevant parts for React Native for Windows is configured as follows:
+
+| Field | Type| Description |
+|:------|:---:|:------------|
+| `type` | string | `"modules"` for Native Modules, `"components"` for Native Components, or `"all"` for both |
+| `jsSrcDir` | string | Path to the TypeScript spec input files |
+| `windows` | object | Windows-specific codegen configuration |
+
+The `windows` object is configured as follows:
+
+| Field | Type| Description |
+|:------|:---:|:------------|
+| `namespace` | string | The C++ namespace to contain the generated code |
+| `cppStringType` | string | Optional, the string type to use in C++ code, either `"std::string"` or `std::wstring`. Defaults to `"std::string"` |
+| `generators` | array | Optional, array of codegen generator strings, accepting `"modulesWindows"` for Native Modules, `"componentsWindows"` for Native Components. Defaults to `[ "modulesWindows" ]` |
+| `outputDirectory` | string | Optional, path to place the generated code. Defaults to `./codegen/` of the working directory |
+| `separateDataTypes` | boolean | Optional, specify whether to create separate files to define custom data types. Defaults to `false` |
+
+> **Note:** For more information on how to configure the `codegenConfig` object for other platforms, see the [reactnative.dev Configuring Codegen](https://reactnative.dev/docs/the-new-architecture/using-codegen#configuring-codegen) page.
+
+### Example Codegen Config
+
+```json
+"codegenConfig": {
+    "name": "NativeModuleSampleSpec",
+    "type": "all",
+    "jsSrcsDir": "src",
+    "includesGeneratedCode": true,
+    "windows": {
+      "namespace": "NativeModuleSampleCodegen",
+      "generators": [
+        "modulesWindows",
+        "componentsWindows"
+      ],
+      "outputDirectory": "windows/NativeModuleSample/codegen",
+      "separateDataTypes": true
+    }
+  },
+```
+
+## Telemetry Notice
+
+This command sends telemetry to Microsoft by default. You can prevent the telemetry from being sent by using the `--no-telemetry` command line option. See below for more details.
+
+The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft's privacy statement. Our privacy statement is located at https://go.microsoft.com/fwlink/?LinkID=824704. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.
+
+This data collection notice only applies to the process of running the react-native-windows CLI commands.
+