Skip to content

Reorganize team page by working group#8522

Merged
mattcarrollcode merged 7 commits into
mainfrom
team-page-working-groups
Jul 10, 2026
Merged

Reorganize team page by working group#8522
mattcarrollcode merged 7 commits into
mainfrom
team-page-working-groups

Conversation

@mattcarrollcode

@mattcarrollcode mattcarrollcode commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Overview

Restructures the Meet the Team page around React's working groups and Leadership Council, and refreshes team membership.

What changed

Page structure

  • Leadership Council — the representative for each working group. Their represented group's badge is listed first and marked with a ★.
  • Working Group members — everyone else contributing to a working group, in alphabetical order.
  • Advisors — people who support React day to day outside the technical working groups (React Foundation, security reviews, etc.).
  • Emeritus — former team members who are no longer active.

Preview

Restructure the Meet the Team page around React's working groups and
Leadership Council, and refresh membership.

- Add a Leadership Council section (working-group representatives) and a
  Working Group members section, replacing the single flat team list.
- Tag each member with their working groups via a new group prop on
  TeamMember, with a star marking Leadership Council representation. For
  representatives, their represented group is listed first.
- Add an Advisors section for people who support React outside the
  technical working groups (React Foundation, security reviews, etc.).
- Move former members who are no longer active to Emeritus.
- Add new members with GitHub profile photos; fall back to a neutral
  placeholder avatar where no photo is available.
- Make the TeamMember bio optional so members without a bio render
  cleanly.
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Five Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/404 127.56 KB (🟡 +325 B) 242.71 KB
/500 127.57 KB (🟡 +325 B) 242.72 KB
/[[...markdownPath]] 130.01 KB (🟡 +325 B) 245.16 KB
/errors 127.81 KB (🟡 +325 B) 242.96 KB
/errors/[errorCode] 127.79 KB (🟡 +325 B) 242.94 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

The /errors/[errorCode] page fetches React's error codes from GitHub raw
at build time. When that endpoint returns a non-JSON body (e.g.
'404: Not Found' or a rate-limit message), calling .json() throws and
fails the whole build during page-data collection.

Validate the response and retry a few times, and fall back to a bundled
snapshot of codes.json if the fetch is still unusable, so a transient
GitHub hiccup no longer breaks the build.
@mattcarrollcode mattcarrollcode requested a review from eps1lon July 8, 2026 23:47
@mattcarrollcode mattcarrollcode marked this pull request as ready for review July 8, 2026 23:47
Comment thread src/content/community/team.md Outdated
Comment thread src/content/community/team.md Outdated
Comment thread src/content/community/team.md Outdated
Comment thread src/content/community/team.md Outdated
mattcarrollcode and others added 2 commits July 9, 2026 06:24
Co-authored-by: Sebastian "Sebbie" Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: MaxwellCohen <to.email.max@gmail.com>
</Intro>

## React Core {/*react-core*/}
React work is organized into working groups, each responsible for an area of the project such as Server, DOM, Fiber, Docs & Community, Compiler, DevX, and React Native. Each working group is represented on the React Leadership Council, which coordinates direction across the project.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To me, Fiber is still an internal codename. Does it have to be public-facing? Could be “Client” if we don’t like “Core”.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Fiber" is the name of the working group itself. I agree the name is not great for public consumption but we probably need to change the name of the working group first. I think we should change the name of the working group before we change it here in the docs.

FWIW we did have a discussion of "Core" and "Client" when we named working group Fiber. The name Fiber was chosen primarily to make the boundaries clearer between the Fiber, Server and DOM working groups.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see... I guess it makes sense though Server/Client has a nice symmetry to it. And DOM spans across both anyway so I don't think it conflicts with Client.

@gaearon

gaearon commented Jul 9, 2026

Copy link
Copy Markdown
Member

Tangent, but would it be possible to fix the preview deployment thing so that all team members are able to see previews? It’s hard to review based on markdown, and I don’t understand why these previews aren’t just public.

@mattcarrollcode

Copy link
Copy Markdown
Contributor Author

I don’t understand why these previews aren’t just public.

Fixed! We recently moved from a Meta-owned Vercel team to the React Foundation Vercel team and it looks like Vercel Authentication was re-enabled in the transfer. I've turned it off now.

@gaearon

gaearon commented Jul 9, 2026

Copy link
Copy Markdown
Member

Fantastic!!!

Comment thread src/content/community/team.md Outdated
@mattcarrollcode mattcarrollcode merged commit 6be2b02 into main Jul 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants