-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Closed
Labels
good first issueIssue that doesn't require previous experience with GatsbyIssue that doesn't require previous experience with Gatsbytype: documentationAn issue or pull request for improving or updating Gatsby's documentationAn issue or pull request for improving or updating Gatsby's documentation
Description
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
- Read the Style Guide and follow it in order for your PR to be accepted. Pay special attention to the templates.
- Style Guide: https://www.gatsbyjs.org/docs/gatsby-style-guide/
- Docs Templates: https://www.gatsbyjs.org/docs/templates/
- Example of a guide to imitate: https://www.gatsbyjs.org/docs/deploying-to-s3-cloudfront
-
Create the "Deploying to Now" article by creating a file named
deploying-to-now.mdin this directory. -
Copy and paste this section of the deploying doc: https://www.gatsbyjs.org/docs/deploy-gatsby/#now
-
Make sure you adjust the content to follow the format listed in these resources:
- Docs Templates: https://www.gatsbyjs.org/docs/templates/
- Example of a guide to imitate: https://www.gatsbyjs.org/docs/deploying-to-s3-cloudfront
- Link the new doc in the docs sidebar file, doc-links.yml, under the Deploying section:
- title: Deploying to Now
link: /docs/deploying-to-nowMetadata
Metadata
Assignees
Labels
good first issueIssue that doesn't require previous experience with GatsbyIssue that doesn't require previous experience with Gatsbytype: documentationAn issue or pull request for improving or updating Gatsby's documentationAn issue or pull request for improving or updating Gatsby's documentation