Migrate to Gatsby/Netlify CMS plugin #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erquhart
force-pushed
the
gatsby-plugin
branch
from
d593533
to
3e79cde
Compare
Closed
|
Thanks Shawn, I agree that |
csw1995
pushed a commit
to csw1995/unused-blog
that referenced
this pull request
Aug 14, 2019
Migrate to Gatsby/Netlify CMS plugin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created a Gatsby plugin for the CMS when I realized how rough integrations were (requiring a separate build system). This PR drops integration code in favor of the plugin. It also reverts
jsxextensions back to the more standard.js- I'd like to propose that such a change be discussed and agreed to in its own PR.Didn't want to muck up the changeset with a bunch of format fixes, but we should run prettier after this is merged.
Closes #24