Thanks to @SAWARATSUKI for updating the logo!

Change the tense of "build" to "building".

* Update synchronizing-with-effects.md

Currently documentation says:

By default, your Effect will run after every render.

Which is in contrast with another section of the same page where it says:

Effects run at the end of a commit after the screen updates

* Update src/content/learn/synchronizing-with-effects.md

---------

Co-authored-by: Ricky <[email protected]>

* Fix #6854: node.js version upgrade

* Fix #6854: node.js version update

Co-authored-by: Rajat Jindal <[email protected]>

* Update team.md: Jason Bonta

* Update src/content/community/team.md

Lauren's suggestion

Co-authored-by: lauren <[email protected]>

---------

Co-authored-by: lauren <[email protected]>

* Add initial skeleton

* Scaffold compiler docs structure

* Braindump for getting started

* Add intro

* tweaks

* add experimental tag

* flesh more out of index page

* flesh out installation

* add installation intro

* update install instrs

* add section on eslint plugin

* reorg

* add incremental guide

* [debugging] Add section about devtools badge

* [debugging] Add section about using logger

* Update next.js instructions

* reporting issues

* [debugging] Add section on useEffect over firing

* [debugging] Add section about conditional hook call

* Latest updates

* Remove ununsed reference pages

* adding extra context for Remix

---------

Co-authored-by: Sathya Gunasekaran <[email protected]>
Co-authored-by: Lauren Tan <[email protected]>
Co-authored-by: Jason Bonta <[email protected]>

Using "off", "warn", "error" has been supported for many years now - I think this helps improve the readability :) 

I completely forgot what rule: 2 meant - had to find it at 

https://eslint.org/docs/latest/use/configure/rules

Removed ; as it's unnecessary in jsx component

Front end nation is covering a full track of React talks including speakers such as:

* Kent C Dodds
* Sara Vieira
* Tejas Kumar

Co-authored-by: OH HYUN KEUN <[email protected]>

This upstreams some of the [introduction
post](reactwg/react-compiler#5) into the
docs since this knowledge is quite fundamental to understanding the
compiler, and it's confusing to not have it linked in the canonical
source for the docs. It also adds more information about
[debugging](reactwg/react-compiler#7) and
reorganizes a few sections to make things clearer

ghstack-source-id: ef32fc723722eb5119529abcc572dd2bcf2b1cab
Pull Request resolved: reactjs/react.dev#6895

* Add React Conf 2024 Recap post

* Spelling and links

* Apply suggestions from code review

Co-authored-by: lauren <[email protected]>

* Edits

* Edits

* better link

* Update date

* Update date and nits

* feedback

---------

Co-authored-by: lauren <[email protected]>

* Add codemods to upgrade guide

* Update src/content/blog/2024/04/25/react-19-upgrade-guide.md

Co-authored-by: Ahmed Abdelbaset <[email protected]>

* Add benefits

---------

Co-authored-by: Ahmed Abdelbaset <[email protected]>

The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences

* FIX: Typo in useEffect.md caveats

* Fix another typo

* Add act documentation

* Update structure based on feedback

* Add usage examples and async act

---------

Co-authored-by: Rick Hanlon <[email protected]>

…-b12743c3