docs: audit all links, fix all broken links

[mikehardy]

Description

The reference docs had over time fallen prey to entropy, and contained many broken links

they have been fixed

Related issues

None logged

Release Summary

two conventional commits but neither will trigger a release - a docs and a style commit

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

lots of passes of the docs.page CLI check recently augmented for more thorough checking

additionally, can see the PR in live preview https://rnfirebase.io/~9051

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses documentation entropy by systematically auditing and fixing broken external and internal links across the project's reference materials. These changes improve the overall quality and reliability of the documentation, ensuring that users are directed to the correct resources and up-to-date information.

Highlights

• Link Maintenance: Performed a comprehensive audit of the documentation to identify and resolve numerous broken links, ensuring better navigation and resource accessibility.
• Documentation Structure: Updated navigation paths and sidebar configurations in several MDX files to improve the logical flow of the documentation.
• Tooling Improvements: Adjusted the markdown linting order in package.json to ensure ESLint runs before Prettier, improving the reliability of the documentation build process.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates various documentation files and navigation links across the repository to fix outdated references, correct external URLs, and adjust the sidebar navigation flow. It also swaps the execution order of ESLint and Prettier in the markdown linting script. The review feedback correctly identifies two remaining broken links: an invalid anchor reference to /#expo in the phone authentication documentation and a non-existent /releases path in the platforms documentation.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.