* Add React v16.6.0 blog post
* Two hyphens so close is noisy
* Tweak links
* Let it breathe a little
* Update 2018-10-23-react-v-16-6.md
* Credit Alex
We might want to open an RFC for fragment refs which could solve the one
remaining use case in a better way but at least let us get the deprecation
in.
* Document React.lazy
Suspense is documented here since it's the only built-in way so far to
use it. In the future it'll likely be documented on its own more like
Error boundaries.
This hoists React.lazy as the primary way to do code splitting. However,
before getting into it we keep the recommendation to use react-loadable
for server-side rendered apps since Suspense is not yet ready for the
server.
* Tweaks
* Tweaks
* nits
Just two small changes on "Styling and CSS" page:
* tip regarding "classnames" has been placed in quote box to visually emphasize it
* link to "classnames" package now points to React related section on the page
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!