-
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
Break loaders/wrappers into plugins #29
Comments
/cc @davad |
This is more-or-less fixed as of https://github.com/gatsbyjs/gatsby/releases/tag/v0.7.1 |
KyleAMathews
pushed a commit
that referenced
this issue
Mar 27, 2020
The Gatsby.js docs, while wonderful, are light on coding instructions for contributors. With dedicated sections in the Contributing docs, it will be easier to learn how to clone the repository, where to find certain things like docs or plugins, how to run tests, and insider infrastructure knowledge required to submit a successful pull request on the first try. A lot of this information already lives on the "How to Contribute" page, but it's buried. It would help discoverability if this information lived on separate pages. Doing this means we can easily add a new section on "Setting up test environments", such as using Docker to hook up an easy Wordpress test installation. I would love to hear your feedback as this is my first Gatsby RFC. I'm totally open to suggestions!
This was referenced Mar 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are potentially dozens of different file types people would want to use with Gatsby + many different ways to prepare Markdown and other file formats. To simplify (code + conceptually) adding or modifying how files are loaded/wrapped, we should create a plugin architecture + break out existing markdown/html loaders/wrappers into plugins that are installed separately from Gatsby core.
The text was updated successfully, but these errors were encountered: