-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MarkdownIt Plugin #167
Comments
You should copy the supplied example Markdown loader to within your site folder at I don't want Gatsby to have a large API surface area so providing a plugin for the default Markdown loader seems like a mistake. I think actually shipping any loaders at all with Gatsby is a mistake. I think for the next major release I'm going to move loaders out of core and into the starters to make it very clear that hacking the loaders in your project is the right way to modify the loader. The larger issue here is what should Gatsby do and not do. I think Gatsby's role should be kept as minimal as possible to ensure maximum flexibility. What is the minimum thing Gatsby does? Map files to URLs, provide a default Webpack config, ensure a fantastic hot-reloading developer experience, and do production builds. Beyond that I think the project should encourage really good conventions through the default starters but people should be free to swap out loaders any which way they want. |
@cutemachine issue to track moving Markdown loader out of core #168 |
@cutemachine site-specific loaders are now supported properly as of 0.8.10 #188 |
@KyleAMathews You are the man. Thanks. |
Gatsby uses MardownIt. Is there an easy way to configure it to use the footnote plugin?
The text was updated successfully, but these errors were encountered: