Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Content migration - add "Deploying to Now" doc #8737

Closed
amberleyromo opened this issue Oct 3, 2018 · 1 comment
Closed

Content migration - add "Deploying to Now" doc #8737

amberleyromo opened this issue Oct 3, 2018 · 1 comment
Labels
good first issue Issue that doesn't require previous experience with Gatsby type: documentation An issue or pull request for improving or updating Gatsby's documentation

Comments

@amberleyromo
Copy link
Contributor

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

  1. Read the Style Guide and follow it in order for your PR to be accepted. Pay special attention to the templates.

  1. Create the "Deploying to Now" article by creating a file named deploying-to-now.md in this directory.

  2. Copy and paste this section of the deploying doc: https://www.gatsbyjs.org/docs/deploy-gatsby/#now

  3. Make sure you adjust the content to follow the format listed in these resources:

  1. Link the new doc in the docs sidebar file, doc-links.yml, under the Deploying section:
- title: Deploying to Now
  link: /docs/deploying-to-now
@amberleyromo amberleyromo added type: documentation An issue or pull request for improving or updating Gatsby's documentation Hacktoberfest good first issue Issue that doesn't require previous experience with Gatsby labels Oct 3, 2018
@amberleyromo
Copy link
Contributor Author

Open PR: #8729

@shannonbux shannonbux mentioned this issue Oct 3, 2018
Closed
51 tasks
@romulomachado romulomachado mentioned this issue Oct 4, 2018
Merged
shannonbux added a commit that referenced this issue Oct 19, 2018
@shannonbux
Delete doc since it was broken into smaller docs
6a9902c 
This is a proposal to delete this doc now that we have broken all the deployment options into separate docs and I just added them to the sidebar. If this PR gets merged I'll also delete this doc from the sidebar.

Taken from #8103: 

### Deploying
- [x] Deploying to S3/Cloudfront
- [x] Deploying to Netlify
- [x] Deploying to Aerobatic #8736
- [x] Deploying to Heroku #8721 (PR)
- [x] Deploying to Now #8737
- [x] Deploying to GitLab Pages #8738
@shannonbux shannonbux mentioned this issue Oct 19, 2018
Merged
6 tasks
shannonbux added a commit that referenced this issue Oct 22, 2018
@shannonbux
Delete doc since it was broken into smaller docs (#9262)
5de6815 
This is a proposal to delete this doc now that we have broken all the deployment options into separate docs and I just added them to the sidebar (commit 1af244b). If this PR gets merged I'll also delete this doc from the sidebar.

Taken from #8103: 

### Deploying
- [x] Deploying to S3/Cloudfront
- [x] Deploying to Netlify
- [x] Deploying to Aerobatic #8736
- [x] Deploying to Heroku #8721 (PR)
- [x] Deploying to Now #8737
- [x] Deploying to GitLab Pages #8738

<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
jedrichards pushed a commit to jedrichards/gatsby that referenced this issue Nov 1, 2018
@shannonbux @jedrichards
Delete doc since it was broken into smaller docs (gatsbyjs#9262)
74ff3b1 
This is a proposal to delete this doc now that we have broken all the deployment options into separate docs and I just added them to the sidebar (commit gatsbyjs@1af244b). If this PR gets merged I'll also delete this doc from the sidebar.

Taken from gatsbyjs#8103: 

### Deploying
- [x] Deploying to S3/Cloudfront
- [x] Deploying to Netlify
- [x] Deploying to Aerobatic gatsbyjs#8736
- [x] Deploying to Heroku gatsbyjs#8721 (PR)
- [x] Deploying to Now gatsbyjs#8737
- [x] Deploying to GitLab Pages gatsbyjs#8738

<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
gpetrioli pushed a commit to gpetrioli/gatsby that referenced this issue Jan 22, 2019
@shannonbux @gpetrioli
Delete doc since it was broken into smaller docs (gatsbyjs#9262)
fb179fd 
This is a proposal to delete this doc now that we have broken all the deployment options into separate docs and I just added them to the sidebar (commit gatsbyjs@1af244b). If this PR gets merged I'll also delete this doc from the sidebar.

Taken from gatsbyjs#8103: 

### Deploying
- [x] Deploying to S3/Cloudfront
- [x] Deploying to Netlify
- [x] Deploying to Aerobatic gatsbyjs#8736
- [x] Deploying to Heroku gatsbyjs#8721 (PR)
- [x] Deploying to Now gatsbyjs#8737
- [x] Deploying to GitLab Pages gatsbyjs#8738

<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Issue that doesn't require previous experience with Gatsby type: documentation An issue or pull request for improving or updating Gatsby's documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amberleyromo