react.dev

section of the docs. That section was _good_, but it made it really hard to continue recommending the React docs as a good starting point for someone new to React. The docs have also skimmed past a lot of important information, usage concepts, and info on how React itself actually works. For example: - React's batching behavior is something that frequently trips people up, but the current docs just have a note that says "updates may be async" - Using the hook dependency arrays correctly is vital, but the current hook docs describe it as sort of an after-thought - There's no information on what a "reducer function" is or how to use one correctly. That's part of why I ended up writing a 9K-word "Guide to React Rendering Behavior" post [1], and Dan wrote a similar "Guide to `useEffect`" [2] article. Fortunately, the new docs address a lot of those concepts directly, which should really help people who are getting started. [0] https://github.com/reactjs/reactjs.org/pull/3965 [1] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-... [2] https://overreacted.io/a-complete-guide-to-useeffect/

g incorporated into the upcoming React docs rewrite [5], which I'm really excited to see go live. [0] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-... [1] https://overreacted.io/a-complete-guide-to-useeffect/ [2] https://overreacted.io/react-as-a-ui-runtime/ [3] https://overreacted.io/before-you-memo/ [4] https://github.com/reactwg/react-18/discussions/21 [5] https://github.com/reactjs/reactjs.org/issues/3308

s in various categories like "state management", "styling", "build tools", and so on, and read descriptions of "what is this tool, what problems does it solve, and when should I consider using it". I _don't_ want to turn it into arguments over "TOOL X IS BETTER THAN TOOL Y!". I _do_ want to get experts from the community involved in writing these pages, like having the maintainers of libraries like Mobx and XState write pages on when their own libraries should be used, as well as when it makes sense to use React component state instead. Yesterday I sat down for a few hours and hammered out a quick draft of the first couple pages for the site - this "State Management Overview" page, and a description of Redux and its use cases [3]. This is absolutely a first draft, and I hope to get the rest of the community involved in building this out! I just wanted to get _something_ written and live as a starting point for discussion and to kickstart the project. *edit* Okay, seriously, let me reiterate: THIS IS A FIRST DRAFT THAT I JUST THREW TOGETHER IN A FEW HOURS. I haven't even had a chance to go back and add more material to this "State Management Overview" page, like some of the info and resources I dug up yesterday [4]. That said, I _do_ want to get the React community involved in fleshing out the categories and material on this site! [0] https://blog.isquaredsoftware.com/2021/01/context-redux-diff... [1] https://github.com/reactjs/reactjs.org/issues/3308 [2] https://github.com/markerikson/react-community-tools-practic... [3] https://react-community-tools-practices-cheatsheet.netlify.a... [4] https://twitter.com/acemarke/status/1368716112469299200