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.
Fixes#1088
This should fix the path issues that people intermittently run into.
Gatsby sees the relative path (and the parent node with an absolute
path), joins on the parent path and the relative path, and presumes it's
a file... which is normally good, but which here is not what we want
beacuse then we're getting a resolver of type file instead of type
string referring to the relative path of the document.
This seems to fix a (long standing?) bug where the "Edit this Page"
button is broken, as well. e.g. see [this page](https://reactjs.org/community/support.html) which _should_ have an Edit this Page button
I'd need to think more as to whether there's a cleaner fix here, but
this seems to work pretty well!
* 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
logo-large was a custom version of the logo made just for the banner background. It was also scaled up manually rather than taking advantage of svg's inherit scaling. This change reduces its size, makes it just a plain white version of the react logo, and moves most of the custom stuff into css. It also moves it from the static folder, over to the icons folder where it can be imported as a url.
Now examples are trasnformed to GraphQL during build and assembled by the index template. This makes them easier to edit and tie in with their associated markdown description.
