This matters for user security.
I didn't touch blog posts & pages related to past conferences.
The `content/docs` could be HTTPS-ified as well but it contains lots of HTTP
links so maybe that'd be best done in a separate PR.
* Rewrite "adding React to existing app"
Fixes#988
* Some copy
* typo
* Update babel instructions
* Update umd link
* Add prod minification section
* Show "button" example in several targets
* wip
* More
* More
* tweak
* yas
* Multi root tip
* moaar
* alot
* Tweak links
* Explain better
* better lead
* tweaks
* tweaks
* wording
* More reassuring tone
* Grammar
* wording
* feedback from readers
* Use id, not class
* More nits
* Re-add a useful section
* 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
When I was working through this, I found it not completely clear what was meant by 'instead of "6"'. I assumed the document refers to the move numbers in the move list, so that's what this change clarifies.
Adds a new docs website, built with Gatsby JS, to replace the old Jekyll site. Source code for the new site lives in /www (although markdown and YML data still comes from the legacy /docs folder).
Changes to either markdown or website source code can be previewed on Netlify. The react-js bot should automatically add comments to each PR with preview links. (This preview is generated by running the newly-added yarn build:docs command in the root package.json.)
The majority of the changes in this PR are contained within the new /www directory. However some minor modifications have been made to existing content in the /docs directory:
* Modified frontmatter author block to always be an array
* Small markdown formatting tweaks
* "Write Code in Your Editor": Split step 5 into 2 steps
To me it wasn't clear (enough) that I had to copy the file's content from [here](https://codepen.io/gaearon/pen/oWWQNa?editors=0010) *and* add the three lines to the top.
* Update tutorial.md
The tutorial hints that a change can be made that allows you to go back
in time then click in the board to create a new entry, but the change is
already present in the example code.
This fix removes the hint and re-words the explanation of the change the
example code is making.