-
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
Content migration - create "Using service workers with Gatsby" doc #8849
Comments
I would like to work on this |
@shannonbux @NickyMeuleman Hey guys, sorry for this. Got caught up with work, something priority came up. Will not able to work on this right at the moment. (for one week or so). I don't want to block this issue. Let anyone else pick this up. Also lets remove the label |
No problem, thanks for letting us know. 👍 |
Hello @shannonbux @NickyMeuleman, I would be happy to take this up |
Hi @shannonbux I have already worked and gave PR |
Issue Context
This issue is part of the content migration project (#8103), which is meant to take existing content and repurpose it so it's easier to find in the docs.
Motivation
We are doing this because many people have written excellent content that we want to canonize and maintain so more people can find it and benefit from it.
Steps to resolve this issue
Review the Gatsby docs approach
Draft the doc
using-service-workers-with-gatsby.md
in the docs source directory.https://www.gatsbyjs.org/packages/gatsby-plugin-offline/
https://www.gatsbyjs.org/docs/progressive-web-app/#it-must-implement-a-service-worker
https://www.gatsbyjs.org/blog/gatsby-v1/#service-worker-and-offline-support
Make sure you rewrite and adjust the content to follow the format listed in these resources:
doc-links.yml
file so your newly created doc shows up in the sidebar navigation of the .org site!Open a pull request
The text was updated successfully, but these errors were encountered: