The plugin library is in dark deploy, thanks to @gillkyle and many others!
This fixes Issue #3003.
Next steps based off of discussions w/ @fk, @KyleAMathews, and @calcsam.
@KyleAMathews do these things?
gatsby-library
in addition to gatsby-plugin
and gatsby-component
@jlengstorf do this:
@fk do this:
/plugins/
to /packages/
Shannon do this:
Notes on possible future enhancements to the library:
Community plugins missing the "gatsby-plugin" keyword so not currently showing up in the search. Each one should have a PR adding either gatsby-plugin
, gatsby-component
, or gatsby-library
as a keyword https://github.com/alampros/gatsby-plugin-accessibilityjs/pull/1
Please check them off when you've made a PR!
cc-ing repo owners if you want to fix things yourselves :-D @alampros @crgeary @julien1619 @didierfranc @marcobiedermann @dannywils @angeloocana @rongierlach @jlengstorf @kevzettler @Rulikkk @jcreamer898 @pixelstew @Jedidiah @angeloashmore @G100g @haysclark
Thanks for the heads up! Mine is updated.
Thanks! Mine gatsby-plugin-bugherd
has been updated.
The deed is done -- gatsby-plugin-purify-css
gatsby-remark-emoji
updated with keywords. Thanks.
gatsby-plugin-meta-redirect
has been updated
I added a PR #4472 'Replace main navigation item "Community" with "Plugins"' over the weekend, preview here: https://deploy-preview-4472--gatsbyjs.netlify.com/
Hey @jacobmischka, want to tag https://github.com/jacobmischka/gatsby-plugin-react-svg/?
keyword added on https://github.com/didierfranc/gatsby-plugin-google-fonts
@KyleAMathews all listed plugins have now a PR to add the missing keyword ✅
@DirtyF merged and published ;)
@fk Will do!
Wow, thanks @DirtyF!
Thanks @jacobmischka!
🙏 🤗
Merged PR into gatsby-node-helpers
. Thanks @DirtyF!
Merged in https://github.com/marcobiedermann/gatsby-plugin-svg-sprite/pull/2 for gatsby-plugin-svg-sprite
by @DirtyF
@jlengstorf Opened #4622 before seeing this issue and that the task was already on your roadmap. feel free to adjust/suggest wording or close the issue if it's not what was in mind.
I think we should support versioned plugin, I'm planning publish some of my own plugins but realize that they are for Gatsby V2
for example packages for Sublime Text
@lowmess @jlengstorf I merged #4622 and checked it off at the top of this issue.
@nihgwu Can you explain more about this? Do you mean you want the plugin library to show what version of Gatsby the plugin is compatible with?
@shannonbux exactly
@fk and @jlengstorf and @KyleAMathews Are your checklists at the top of this issue updated? Happy to help where I can.
ALSO Kyle, I just updated the long checklist of plugins to reflect that PR's have been made and/or merged for the entire list of plugins! Wait to go everyone.
@shannonbux I need to write the README template still, and I haven't done anything about the Algolia notes.
I also think we discussed keeping plugins instead of packages even though it's technically more than plugins.
Maybe those should be tracked in separate issues (the README already is) and close this?
will do tomorrow! Thanks!
Fun being able to regularly see the count of plugins now — we're already up 8-10 or so since we launched the library
@nihgwu Just created issue #4671 to add filters to plugin library, which would include version compatibility! Thanks!
Ok closing this issue because I turned the remaining tasks into smaller issues in the UX project.
Most helpful comment
cc-ing repo owners if you want to fix things yourselves :-D @alampros @crgeary @julien1619 @didierfranc @marcobiedermann @dannywils @angeloocana @rongierlach @jlengstorf @kevzettler @Rulikkk @jcreamer898 @pixelstew @Jedidiah @angeloashmore @G100g @haysclark