-
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
Polishing Plugin library #4394
Comments
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 |
The deed is done -- |
|
|
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 ✅ |
Community plugins needs the "gatsby-plugin" keyword to show up in the search. see gatsbyjs/gatsby#4394 (comment)
@DirtyF merged and published ;) |
@fk Will do! |
Wow, thanks @DirtyF! |
Community plugins needs the "gatsby-plugin" keyword to show up in the search. see gatsbyjs/gatsby#4394 (comment)
Merged PR into |
Merged in marcobiedermann/gatsby-plugin-svg-sprite#2 for |
@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. |
@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 |
Ok closing this issue because I turned the remaining tasks into smaller issues in the UX project.
|
Community plugins needs the "gatsby-plugin" keyword to show up in the search. see gatsbyjs/gatsby#4394 (comment)
Community plugins needs the "gatsby-plugin" keyword to show up in the search. see gatsbyjs/gatsby#4394 (comment)
Description
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 togatsby-plugin
andgatsby-component
@jlengstorf do this:
@fk do this:
/plugins/
to/packages/
Shannon do this:
Notes on possible future enhancements to the library:
The text was updated successfully, but these errors were encountered: