HTML Wrapper: bind react router history to links under innerHTML

[cusspvz]

If you place ordinary links on your .html file they will load trough
the browser history, which takes an initial loading of the entire page.

I've rewritten the HTML on ES2015 and added the feature of binding
clicks on ordinary links to the react router's history.

Tested and working.

[KyleAMathews]

Hey @cusspvz, thanks for the PR. We've discussed this issue in the past in #93 and decided that it wasn't something we wanted built into Gatsby core as there's valid reasons for wanting a page refresh e.g. you're messing with page styles on one page. I'd love though to see something like this as an NPM module that could be easily added to a Gatsby site. If you write something like that, add a mention of it to the README here in the FAQ.

[cusspvz]

Where can I find documentation on how to make a pluggable module on gatsby?

[cusspvz]

• Wrappers are being picked up just from ./wrappers/*, should we create a pre-defined npm module prefix as well? Such as gatsby-wrapper-*
• staticFileTypes is static and cannot be modded? It should be exposed as well to allow injection of external wrappers such as ejs, ect, jade and so on (believe me, this would make it different and would bump its popularity).

[KyleAMathews]

I've actually been working on designing the plugin API :-) Right now Gatsby is fairly monolithic and hard to modify but that will be changing soon. I'd love to hear your feedback once I've posted the issue!

I'd love to let you create plugins for ejs, ect, jade, wrappers, etc.

[rileyjshaw]

@KyleAMathews a more pluggable API would be great! Off the top of my head, an optional parsers folder could override Gatsby's parsers for filetypes that are included — similar to how wrappers works.

For this specific link-replacement change, React Markdown may be better-suited than markdown-it. For that reason, it's probably best to send the raw markdown string into parsers/md.js.

[KyleAMathews]

@rileyjshaw the plugin api should come out in the next alpha release of Gatsby! If you haven't checked out the writeup on the graphql work — that's coming out too in the next alpha — I've been basing my markdown processing work on http://remark.js.org/ as it provides a Markdown AST that makes it really easy to make modifications but with the graphql data layer, you can easily add plugins to support other markdown parsers.

I'm also working on a way to compile markdown to a react component (several clients want this) so that will be supported as well.

[rileyjshaw]

@KyleAMathews 😻 exciting, thanks! Great writeup on the GraphQL data layer, I hadn't seen that.