[docs] link to plugin README template in Creating a Plugin guide

[gillkyle]

Summary

An important hurdle users trying to leverage plugins encounter is not enough documentation, or difficult to understand documentation on plugins. In the Creating Plugins guide there currently isn't much information (only a few sentences at the end of the Submit to Plugin Library section) guiding a plugin author on what should be included in their README.

There is already a template for plugin READMEs thanks to #4284 that exists but it is not linked to or mentioned in that guide.

What to Do

Some helpful things that could be added:

• linking to the plugin README template from the page Submit to Plugin Library with a note about the template
• (maybe?) adding a page to the Creating Plugins guide that briefly explains the README template and links to it, perhaps also explaining how good documentation can help new users get started with the plugin

[k-conway]

I would like to take this one!

[k-conway]

I have a change ready to go out for PR, but need repo access. Is that something I have to request somewhere other than here?

[gillkyle]

Thanks @k-conway! It looks like you forked the repository (which basically created your own version of Gatsby on your GitHub profile), sounds like you'll need to do a couple things if you haven't already:

1. set your fork to track this repository (run this in your folder with your Gatsby fork):

git remote add upstream https://github.com/gatsbyjs/gatsby.git

2. then you'll need to create your own branch and push your changes to it

3. then you should see the option to create a PR in the GitHub UI with the changes you've made

Let me know if you need any help!

[gillkyle]

Hey @k-conway have you been able to get to this, or need any help? 🙂

[k-conway]

hi! I will be back at this today! sorry for the delay!

…

On Mon, Jun 17, 2019 at 9:11 AM gillkyle ***@***.***> wrote: Hey @k-conway <https://github.com/k-conway> have you been able to get to this? 🙂 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14774?email_source=notifications&email_token=AHLLZXC6CX7ERHOC4O4JGOTP26LRBA5CNFSM4HX3DVOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX3JHRA#issuecomment-502698948>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHLLZXBGWPCGWAOZICHROKTP26LRBANCNFSM4HX3DVOA> .

[gillkyle]

@k-conway no worries, feel free to get to it when you have time, just want to make sure you don't get stuck and/or frustrated 👍

[k-conway]

Thank you so much for reaching out! I just sent in my Pull Request!

…

On Mon, Jun 17, 2019 at 11:16 AM gillkyle ***@***.***> wrote: @k-conway <https://github.com/k-conway> no worries, feel free to get to it when you have time, just want to make sure you don't get stuck and/or frustrated 👍 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14774?email_source=notifications&email_token=AHLLZXDEFW5FYXYRXSZOZZTP262GXA5CNFSM4HX3DVOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX3WAIQ#issuecomment-502751266>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHLLZXG6NJWRL4K2SCN5XOTP262GXANCNFSM4HX3DVOA> .

[gillkyle]

Thanks @k-conway, merged in #14856