* Break out Installation into top-level doc section
* Update navigation (prev/next, nav tree)
- Move Installation section to top
- Add next/prev to install pages
* add links to other install options from try react page
* fix markdown link
* Clarify that Quick Start and Install are optional "next steps"
* Add top-level CDN page
This is useful for Codepen and other Unpkg-y setups
* Add link to Tutorial from Try React
* Update CRA link in tutorial
* Make Try React subheader a proper sentence
* Add "minimal"
* Explain local dev setup is more work than Codepen etc
* Fix typos
* Add : between headings
* add note that CRA is not lightweight
* fix typo
* Update add-react-to-a-new-app.md
* Update add-react-to-a-new-app.md
* Remove the Bower note
* Update try-react.md
* Tweak wording
* Use direct link
Maybe I'm somehow weird, but I lived for some time with an idea that `React.Component` does implement `shouldComponentUpdate` with deep comparison. `React.PureComponent` is faster because it compares shallowly.
The changes I propose should avoid this "implicit" kind of way of thinking, since it would explicitly state that `React.Component` does not compare anything.
The "Browser Support" section of react-dom indicates that IE9 and above
is supported, but fails to note that the support does require additional
polyfills in some cases. A link is added to the javascript environment
docs which already explains the polyfills required (Map, Set and rAF).
A post-merge comment for the original PR for this section mentioned that not all libs actually extract static stylesheets (and docs shouldn't explain implementation details of 3rd party libs unnecessarily, as a rule)
Dan Abramov
Alex
Dzung Nguyen
uberfabulous
Vishal Raj
Victor Hom
Ravshan Samandarov
David Nguyen
Almero Steyn
Szymon Nowicki
Kirby Walls
Iurii Kucherov
Mark Samman
Clement Hoang
Eduard Troshin
Clement Hoang
Aamir Afridi
Brian Vaughn
MICHAEL JACKSON
Liam O'Boyle
Yash Joshi
ksenna