Limit contributor cleanup to factual corrections

Author: aurorascharff

.github/workflows/analyze.yml

@@ -18,15 +18,15 @@ jobs:
       - name: Set up node
         uses: actions/setup-node@v4
         with:
-          node-version-file: .nvmrc
+          node-version: '20.x'
           cache: yarn
           cache-dependency-path: yarn.lock
 
       - name: Restore cached node_modules
         uses: actions/cache@v4
         with:
           path: '**/node_modules'
-          key: node_modules-${{ runner.arch }}-${{ runner.os }}-${{ hashFiles('.nvmrc', 'yarn.lock') }}
+          key: node_modules-${{ runner.arch }}-${{ runner.os }}-${{ hashFiles('yarn.lock') }}
 
       - name: Install deps
         run: yarn install --frozen-lockfile

.github/workflows/site_lint.yml

@@ -13,22 +13,22 @@ jobs:
   lint:
     runs-on: ubuntu-latest
 
-    name: Lint on Node.js 24.x and ubuntu-latest
+    name: Lint on node 20.x and ubuntu-latest
 
     steps:
       - uses: actions/checkout@v4
-      - name: Use Node.js from .nvmrc
+      - name: Use Node.js 20.x
         uses: actions/setup-node@v4
         with:
-          node-version-file: .nvmrc
+          node-version: 20.x
           cache: yarn
           cache-dependency-path: yarn.lock
 
       - name: Restore cached node_modules
         uses: actions/cache@v4
         with:
           path: '**/node_modules'
-          key: node_modules-${{ runner.arch }}-${{ runner.os }}-${{ hashFiles('.nvmrc', 'yarn.lock') }}
+          key: node_modules-${{ runner.arch }}-${{ runner.os }}-${{ hashFiles('yarn.lock') }}
 
       - name: Install deps
         run: yarn install --frozen-lockfile

.nvmrc

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code when working with this repository.
 
 ## Project Overview
 
-This is the React documentation website (react.dev), built with Next.js and React. See `package.json` for dependency versions and `.nvmrc` for the Node.js version used in development and CI. Documentation is written in MDX format.
+This is the React documentation website (react.dev), built with Next.js 15.1.12 and React 19. Documentation is written in MDX format.
 
 ## Development Commands
 
@@ -13,7 +13,6 @@ yarn build         # Production build
 yarn lint          # Run ESLint
 yarn lint:fix      # Auto-fix lint issues
 yarn tsc           # TypeScript type checking
-yarn ci-check      # Run the same validation checks as CI
 yarn check-all     # Run prettier, lint:fix, tsc, and rss together
 ```
 
@@ -48,6 +47,6 @@ When editing files in `src/content/`, the appropriate skill will be auto-suggest
 For MDX components (DeepDive, Pitfall, Note, etc.), invoke `/docs-components`.
 For Sandpack code examples, invoke `/docs-sandpack`.
 
-See `.claude/skills/docs-voice/SKILL.md` for shared writing conventions, and the `docs-writer-learn`, `docs-writer-reference`, and `docs-writer-blog` skills for page-specific guidance.
+See `.claude/skills/` for comprehensive style guidelines.
 
 Prettier is used for formatting (config in `.prettierrc`).

CLAUDE.md

@@ -38,15 +38,15 @@ Ignore this if you're specifically describing `createElement`.
 
 Ignore this if you're specifically writing about ES5.
 
-#### Prefer readable JavaScript.
+#### Don't use ES6 features when equivalent ES5 features have no downsides.
 
-Use modern JavaScript when it makes an example clearer. Prefer named `function` declarations for components and top-level functions. Use arrow functions for inline callbacks where they improve readability.
+While we use ES6 in many places (`const` / `let`, classes, arrow functions), if the equivalent ES5 code is just as straightforward and readable, consider using it.
 
-#### Don't use features that aren't standardized yet.
+In particular, you should prefer named `function` declarations over `const myFunction = () => ...` arrows for top-level functions. However, you *should* use arrow functions where they provide a tangible improvement (such as preserving `this` context inside a component). Consider both sides of the tradeoff when deciding whether to use a new feature.
 
-Use standardized JavaScript features in examples. Class fields are standardized and may be used when documenting class components. Prefer function components and Hooks for new examples, unless the page documents a class-specific API.
+#### Don't use features that aren't standardized yet.
 
-If you're specifically describing an experimental proposal, mention its experimental nature in the code and surrounding text.
+Ignore this rule if you're specifically describing an experimental proposal. Make sure to mention its experimental nature in the code and in the surrounding text.
 
 ### Style
 

CONTRIBUTING.md

@@ -7,25 +7,20 @@ This repo contains the source code and documentation powering [react.dev](https:
 ### Prerequisites
 
 1. Git
-1. Node.js 24.x (LTS), matching [`.nvmrc`](./.nvmrc) and CI
-1. Yarn Classic 1.22.22: See the [installation instructions](https://classic.yarnpkg.com/en/docs/install/)
+1. Node: v18.18.0 or greater (see supported versions in [`package.json`](./package.json))
+1. Yarn Classic 1.22.22: See [Yarn website for installation instructions](https://classic.yarnpkg.com/en/docs/install/)
+1. A fork of the repo (for any contributions)
+1. A clone of your fork of the [react.dev repo](https://github.com/reactjs/react.dev) on your local machine
 
 ### Installation
 
-1. [Fork the repo](https://github.com/reactjs/react.dev/fork), then clone your fork. Replace `YOUR_USERNAME` with your GitHub username:
-
-   ```bash
-   git clone https://github.com/YOUR_USERNAME/react.dev.git
-   cd react.dev
-   git remote add upstream https://github.com/reactjs/react.dev.git
-   ```
-
-1. `yarn install --frozen-lockfile` to install the website's dependencies
+1. `cd react.dev` to go into the project root
+3. `yarn` to install the website's npm dependencies
 
 ### Running locally
 
 1. `yarn dev` to start the development server (powered by [Next.js](https://nextjs.org/))
-1. Open [http://localhost:3000](http://localhost:3000) in your browser
+1. `open http://localhost:3000` to open the site in your favorite browser
 
 ## Contributing
 
@@ -35,36 +30,36 @@ The documentation is divided into several sections with a different tone and pur
 
 ### Create a branch
 
+1. `git remote add upstream https://github.com/reactjs/react.dev.git` to add the source repo as a remote (only needed once)
 1. `git checkout main` from any folder in your local `react.dev` repository
-1. `git fetch upstream` to get the latest changes from the source repo
-1. `git merge --ff-only upstream/main` to update your local `main`
+1. `git pull --ff-only upstream main` to ensure you have the latest main code
 1. `git checkout -b the-name-of-my-branch` (replacing `the-name-of-my-branch` with a suitable name) to create a branch
 
 ### Make the change
 
 1. Follow the ["Running locally"](#running-locally) instructions
 1. Save the files and check in the browser
-   1. Changes to React components in `src` will hot-reload
-   1. Changes to Markdown files in `src/content` will hot-reload
-   1. If changes to MDX plugins aren't reflected, stop the server, remove `node_modules/.cache/react-docs-mdx`, and restart it
+  1. Changes to React components in `src` will hot-reload
+  1. Changes to markdown files in `src/content` will hot-reload
+  1. If working with plugins, you may need to remove the `node_modules/.cache/react-docs-mdx` directory and restart the server
 
 ### Test the change
 
 1. If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
-1. Run `yarn ci-check` to run the same checks as CI: formatting, ESLint, local ESLint rule tests, TypeScript, heading IDs, RSS generation, and internal links.
-1. To apply formatting and ESLint fixes, run `yarn check-all`. This command modifies files and also checks types and generates RSS. Review the resulting changes before committing.
+2. Run `yarn check-all`. (This will apply Prettier and ESLint fixes, validate types, and generate RSS.)
+3. Run `yarn ci-check` to run the same checks as CI.
 
 ### Push it
 
 1. `git add -A && git commit -m "My message"` (replacing `My message` with a commit message, such as `Fix header logo on Android`) to stage and commit your changes
-1. `git push -u origin the-name-of-my-branch` to push the branch to your fork
+1. `git push origin the-name-of-my-branch`
 1. Go to the [react.dev repo](https://github.com/reactjs/react.dev) and you should see recently pushed branches.
 1. Follow GitHub's instructions.
 1. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub.
 
 ## Translation
 
-If you are interested in translating `react.dev`, see the [translation guide](https://react.dev/community/translations) and [current translation progress](https://translations.react.dev/).
+If you are interested in translating `react.dev`, please see the current translation efforts [here](https://react.dev/community/translations).
 
 ## License
 Content submitted to [react.dev](https://react.dev/) is CC-BY-4.0 licensed, as found in the [LICENSE-DOCS.md](https://github.com/reactjs/react.dev/blob/main/LICENSE-DOCS.md) file.

README.md

@@ -111,7 +111,7 @@
     "webpack-bundle-analyzer": "^4.5.0"
   },
   "engines": {
-    "node": ">=24.0.0"
+    "node": "^18.18.0 || ^19.8.0 || >=20.0.0"
   },
   "nextBundleAnalysis": {
     "budget": null,