From dc53a662a1e176755772cd261d13896b75b76436 Mon Sep 17 00:00:00 2001 From: supun_yasantha034 Date: Tue, 20 Oct 2026 10:36:04 +0530 Subject: [PATCH 1/2] docs: fix broken doc links and anchors in blog, contributing, and architecture --- website/architecture/fabric-renderer.md | 2 +- website/blog/2025-10-08-react-native-0.82.mdx | 2 +- website/blog/2026-10-19-react-native-0.88.mdx | 4 ++-- website/contributing/contributing-overview.mdx | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/architecture/fabric-renderer.md b/website/architecture/fabric-renderer.md index dc24c2d8a92..c9f16d7c7b1 100644 --- a/website/architecture/fabric-renderer.md +++ b/website/architecture/fabric-renderer.md @@ -5,7 +5,7 @@ title: Fabric Fabric is React Native's new rendering system, a conceptual evolution of the legacy render system. The core principles are to unify more render logic in C++, improve interoperability with [host platforms](architecture-glossary.md#host-platform), and to unlock new capabilities for React Native. Development began in 2018 and in 2021, React Native in the Facebook app is backed by the new renderer. -This documentation provides an overview of the [new renderer](architecture-glossary.md#fabric-render) and its concepts. It avoids platform specifics and doesn’t contain any code snippets or pointers. This documentation covers key concepts, motivation, benefits, and an overview of the render pipeline in different scenarios. +This documentation provides an overview of the [new renderer](architecture-glossary.md#fabric-renderer) and its concepts. It avoids platform specifics and doesn’t contain any code snippets or pointers. This documentation covers key concepts, motivation, benefits, and an overview of the render pipeline in different scenarios. ## Motivations and Benefits of the new renderer diff --git a/website/blog/2025-10-08-react-native-0.82.mdx b/website/blog/2025-10-08-react-native-0.82.mdx index d54d2481694..4a4175c3b7a 100644 --- a/website/blog/2025-10-08-react-native-0.82.mdx +++ b/website/blog/2025-10-08-react-native-0.82.mdx @@ -208,7 +208,7 @@ React Native now implements a subset of the performance APIs available on Web: They allow tracking different aspects of performance in your app at runtime (for telemetry) and they will be visible in the performance panel in React Native DevTools (available in a future version of React Native). -They are currently **available only in the [canary release level](https://reactnative.dev/docs/releases/release-levels)**, and will be released as stable in a future version of React Native. +They are currently **available only in the [canary release level](/docs/release-levels)**, and will be released as stable in a future version of React Native. ### Optimized Debug Build Type for Android diff --git a/website/blog/2026-10-19-react-native-0.88.mdx b/website/blog/2026-10-19-react-native-0.88.mdx index 257f1d1cff5..2524250e734 100644 --- a/website/blog/2026-10-19-react-native-0.88.mdx +++ b/website/blog/2026-10-19-react-native-0.88.mdx @@ -33,7 +33,7 @@ Events now travel a real capture path down to the target and bubble back up, ove - **A path to Web-compatible imperative APIs**: Canary builds expose `addEventListener`, `removeEventListener` and `dispatchEvent` on native refs for early feedback. - **One path to maintain**: Removing the legacy plugin registry is the follow-up, leaving a single dispatch path instead of two. -The imperative API is available on the [Canary channel](/docs/releases/release-levels) in 0.88: +The imperative API is available on the [Canary channel](/docs/release-levels) in 0.88: ```tsx const ref = useRef(null); @@ -216,7 +216,7 @@ The following APIs have been deprecated and are due for removal in a future rele ### Developer Tools - **React Native DevTools**: App screenshots via `Page.captureScreenshot` are available by default. -- **React Native DevTools**: WebSocket inspection in the Network panel is on the [CANARY channel](/docs/releases/release-levels). +- **React Native DevTools**: WebSocket inspection in the Network panel is on the [CANARY channel](/docs/release-levels). ## Acknowledgements diff --git a/website/contributing/contributing-overview.mdx b/website/contributing/contributing-overview.mdx index 36bb973f98a..29142b81f86 100644 --- a/website/contributing/contributing-overview.mdx +++ b/website/contributing/contributing-overview.mdx @@ -22,7 +22,7 @@ As a reminder, all contributors are expected to adhere to the [Code of Conduct]( ## Versioning Policy -In order to fully understand the versioning of React Native, we recommend you to check out the [Versioning Policy](/docs/releases/versioning-policy) page. +In order to fully understand the versioning of React Native, we recommend you to check out the [Versioning Policy](/releases/versioning-policy) page. In that page we describe which versions of React Native are supported, how often they're released and which one you should use based on your circumstances. ## Ways to Contribute From 457aabaa64c35c8c52e2416160b565926980f337 Mon Sep 17 00:00:00 2001 From: supun_yasantha034 Date: Tue, 20 Oct 2026 12:37:28 +0530 Subject: [PATCH 2/2] docs: revert false-positive redirect links per review feedback --- website/blog/2026-10-19-react-native-0.88.mdx | 4 ++-- website/contributing/contributing-overview.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/blog/2026-10-19-react-native-0.88.mdx b/website/blog/2026-10-19-react-native-0.88.mdx index 2524250e734..257f1d1cff5 100644 --- a/website/blog/2026-10-19-react-native-0.88.mdx +++ b/website/blog/2026-10-19-react-native-0.88.mdx @@ -33,7 +33,7 @@ Events now travel a real capture path down to the target and bubble back up, ove - **A path to Web-compatible imperative APIs**: Canary builds expose `addEventListener`, `removeEventListener` and `dispatchEvent` on native refs for early feedback. - **One path to maintain**: Removing the legacy plugin registry is the follow-up, leaving a single dispatch path instead of two. -The imperative API is available on the [Canary channel](/docs/release-levels) in 0.88: +The imperative API is available on the [Canary channel](/docs/releases/release-levels) in 0.88: ```tsx const ref = useRef(null); @@ -216,7 +216,7 @@ The following APIs have been deprecated and are due for removal in a future rele ### Developer Tools - **React Native DevTools**: App screenshots via `Page.captureScreenshot` are available by default. -- **React Native DevTools**: WebSocket inspection in the Network panel is on the [CANARY channel](/docs/release-levels). +- **React Native DevTools**: WebSocket inspection in the Network panel is on the [CANARY channel](/docs/releases/release-levels). ## Acknowledgements diff --git a/website/contributing/contributing-overview.mdx b/website/contributing/contributing-overview.mdx index 29142b81f86..36bb973f98a 100644 --- a/website/contributing/contributing-overview.mdx +++ b/website/contributing/contributing-overview.mdx @@ -22,7 +22,7 @@ As a reminder, all contributors are expected to adhere to the [Code of Conduct]( ## Versioning Policy -In order to fully understand the versioning of React Native, we recommend you to check out the [Versioning Policy](/releases/versioning-policy) page. +In order to fully understand the versioning of React Native, we recommend you to check out the [Versioning Policy](/docs/releases/versioning-policy) page. In that page we describe which versions of React Native are supported, how often they're released and which one you should use based on your circumstances. ## Ways to Contribute