“We want to make reactjs.org the best place to grok React. We want to be there with you from the moment you make your first component, to well into your career as your React knowledge deepens and advances.” –Rachel Nabors
This GitHub issue on the React repo by Rachel Nabors shares exciting news: over the coming months, the core team is planning to rebuild the React website with brand-new content! Expect this rewrite to put Hooks front-and-center and fill in the gaps between the official docs and the booming React infoproduct space.
As mentioned above, React is working on a major rewrite to its documentation, and needs your help. If you use and appreciate React, consider taking a few minutes and completing the React 2020 Community Survey. It will help the core team learn how you utilize the official docs.
This Reddit r/reactjs thread from u/flyingsky1 explores a common question folks ask when building a significant React application: how do I route? As long as React remains widely considered the V in MVC, without a conventional routing solution, these kinds of answers will remain relevant.
This talk was one of the major sales pitches for React Hooks, on a stage shared at ReactConf 2018 by Sophie Alpert, Dan Abramov, and Ryan Florence. It’s dense, and I’m planning to share it in three parts, starting with part one. Here, Sophie shares how Hooks were the React team’s attempt to answer: “what [in React] still sucks?”
We’re getting into some more esoteric documentation now! displayName is a string used in debugging messages; it helps you identify components. Usually it’s set by React automatically and intuitively. When it isn’t, such as in anonymous functions or HOCs, you can set it yourself.
Do you want to really (really!) learn React, while staying current on this exploding ecosystem? Subscribe to React Explained, a bi-weekly newsletter of amazing, curated React news and resources, simply explained. It’s free! Subscribe now.