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 overview issue #8103

Closed
44 of 51 tasks
shannonbux opened this issue Sep 13, 2018 · 14 comments
Closed
44 of 51 tasks

Content migration overview issue #8103

shannonbux opened this issue Sep 13, 2018 · 14 comments
Labels
good first issue Issue that doesn't require previous experience with Gatsby stale? Issue that may be closed soon due to the original author not responding any more. type: documentation An issue or pull request for improving or updating Gatsby's documentation

Comments

@shannonbux
Copy link
Contributor

shannonbux commented Sep 13, 2018 •
edited by marcysutton
Loading

Summary

Lots of content in our blog, plugin and starter READmes, and other external resources have valuable content we could pull into the docs.

  1. If you'd like to write one of these docs, pick one from the list below
  2. Then click on this URL to check what existing content can be repurposed in the article you're writing: https://airtable.com/shrU9erBeq1lhDy1Z
  3. Then, open a PR with your article and mention this Issue Content migration overview issue #8103 in the PR description!

Note -- These docs may be in one of three states:

  1. No doc exists yet (no corresponding file/page exists)
  2. A stub article exists (the file is created and needs to be filled out)
  3. A doc exists, but there is additional content we've identified that could possibly be used to make it better.

Sourcing

Deploying

Hosting

Styling

Building pages

Building a page with a GraphQL query (Duplicative. Already exists)
Rendering sidebar navigation dynamically (New doc, not migration)

Performance + Optimization

Overviews

How Gatsby Works Diagram (hold, needs clarification; missing link in airtable)

Plugins

Headless CMS

GraphQL

  • Introducing GraphiQL*
  • Querying data with GraphQL (overview)

Process

How to submit a PR*

Testing

[ ] Test configuration with Gatsby (hold, needs clarification; not scoped narrowly enough, all external sources)

Misc

Interactive pages* #8739

Motivation

We are doing this to bring valuable content into the docs so that it is more centralized, maintainable, and discoverable.
@shannonbux shannonbux added type: documentation An issue or pull request for improving or updating Gatsby's documentation good first issue Issue that doesn't require previous experience with Gatsby labels Sep 13, 2018
@shannonbux
Copy link
Contributor Author

@calcsam

@didacta

This comment has been minimized.

Sign in to view
injoongy added a commit to injoongy/gatsby that referenced this issue Sep 13, 2018
@injoongy
Create using-gatsby-image.md
6370feb 
Issue gatsbyjs#8103: This is for the second task, "using gatsby-image to prevent image bloat". I did my best to make sure the links from the original article were still present.

Not sure how to navigate the fact that in the original article, it's specifically Kyle talking, so right now everything's still in first-person. I also cut the last line, which was leading to the next section of the article so wouldn't be relevant here (unless I should have included that next section as well?).

Let me know if there's anything you'd like me to change - this is my first-ever contribution to an open source project (currently in a web dev bootcamp), so I'm sorry if I screwed anything up!
@injoongy injoongy mentioned this issue Sep 13, 2018
Merged
@shannonbux
Copy link
Contributor Author

Hi @didacta! Would you mind opening a PR and mentioned this issue #8103 in the PR description to add the doc you added above?

This was referenced Sep 18, 2018
Closed
Merged
KyleAMathews pushed a commit that referenced this issue Sep 19, 2018
@injoongy @KyleAMathews
Create using-gatsby-image.md (#8131)
aedf814 
* Create using-gatsby-image.md

Issue #8103: This is for the second task, "using gatsby-image to prevent image bloat". I did my best to make sure the links from the original article were still present.

Not sure how to navigate the fact that in the original article, it's specifically Kyle talking, so right now everything's still in first-person. I also cut the last line, which was leading to the next section of the article so wouldn't be relevant here (unless I should have included that next section as well?).

Let me know if there's anything you'd like me to change - this is my first-ever contribution to an open source project (currently in a web dev bootcamp), so I'm sorry if I screwed anything up!

* Update using-gatsby-image.md

Updated with suggested changes!

* just added one more link

* fixes
jonathanvoelkle added a commit to jonathanvoelkle/gatsby that referenced this issue Sep 21, 2018
@jonathanvoelkle
Create deploy-to-netlify.md
1edf802 
Issue gatsbyjs#8103: this is for the "Deploy using Netlify". I tried to write a short beginner-friendly easy to follow guide for using Gatsby with Netlify.

The "Getting Started - Netlify" is copy-and-pasted of the "Deploy to S3" site, 
the introduction from the original "Deploy and Build" page.
@jonathanvoelkle jonathanvoelkle mentioned this issue Sep 21, 2018
Merged
calcsam pushed a commit that referenced this issue Sep 23, 2018
@jonathanvoelkle @calcsam
Create deploying-to-netlify.md (#8406)
d3874e3 
Issue #8103: this is for the "Deploy using Netlify". I tried to write a short beginner-friendly easy to follow guide for using Gatsby with Netlify.

The "Getting Started - Netlify" is copy-and-pasted of the "Deploy to S3" site, 
the introduction from the original "Deploy and Build" page.

I don't see any need for an additional "Hosting on Netlify" article.

<!--
  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/
-->
shannonbux pushed a commit that referenced this issue Sep 25, 2018
#8103 rfc process doc draft
e2436cd
shannonbux added a commit that referenced this issue Sep 25, 2018
@shannonbux
Rfc process doc (#8537)
7955fbb 
* #8103 rfc process doc draft

* simplified headers
oorestisime pushed a commit to oorestisime/gatsby that referenced this issue Sep 28, 2018
@jonathanvoelkle @oorestisime
Create deploying-to-netlify.md (gatsbyjs#8406)
117710e 
Issue gatsbyjs#8103: this is for the "Deploy using Netlify". I tried to write a short beginner-friendly easy to follow guide for using Gatsby with Netlify.

The "Getting Started - Netlify" is copy-and-pasted of the "Deploy to S3" site, 
the introduction from the original "Deploy and Build" page.

I don't see any need for an additional "Hosting on Netlify" article.

<!--
  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/
-->
@ghost
Copy link

ghost commented Oct 2, 2018 •
edited by ghost
Loading

Oops, sorry. Checked How Gatsby Changes Teams' Website Development Workflow accidentally. Removed it again. Before someone gets crazy about my edit. 😆

Should we (the random contributors) have such permissions at all?

Edit: @shannonbux Isn't Typography.js already in the docs or am I getting something wrong?

Also, as a next step I would suggest that all contributors who work on articles should mention that in the comments to avoid duplicates.

This was referenced Oct 2, 2018
Closed
Closed
Closed
Closed
@OrthoDex
Copy link
Contributor

OrthoDex commented Oct 2, 2018

Hi @shannonbux! I'll make a PR for the Deploying to Heroku doc.

@OrthoDex OrthoDex mentioned this issue Oct 2, 2018
Merged
This was referenced Oct 2, 2018
Closed
Closed
This was referenced Oct 5, 2018
Closed
Closed
Closed
Closed
Closed
@amberleyromo amberleyromo mentioned this issue Oct 9, 2018
Merged
@dakebl dakebl mentioned this issue Oct 11, 2018
Closed
@ManoelLobo ManoelLobo mentioned this issue Oct 17, 2018
Merged
@amberleyromo amberleyromo mentioned this issue Oct 18, 2018
Closed
7 tasks
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/
-->
shannonbux pushed a commit that referenced this issue Oct 24, 2018
@ManoelLobo @shannonbux
Authentication tutorial (#9179)
23bda33 
Regarding #8103 

Starting the authentication tutorial. (Misc/Making a site with user authentication*)

Mostly setting intro and starting to work into content.

cc @shannonbux
@ManoelLobo ManoelLobo mentioned this issue Oct 25, 2018
Merged
shannonbux pushed a commit that referenced this issue Oct 30, 2018
@caseychien @shannonbux
Fill out "Sourcing from the filesystem" stub article (#8777)
ef998ab 
This issue (#8730) is part of the content migration project [#8103](#8103), which is meant to take existing content and repurpose it so it's easier to find in the docs.
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/
-->
jedrichards pushed a commit to jedrichards/gatsby that referenced this issue Nov 1, 2018
@ManoelLobo @jedrichards
Authentication tutorial (gatsbyjs#9179)
8acc0c5 
Regarding gatsbyjs#8103 

Starting the authentication tutorial. (Misc/Making a site with user authentication*)

Mostly setting intro and starting to work into content.

cc @shannonbux
jedrichards pushed a commit to jedrichards/gatsby that referenced this issue Nov 1, 2018
@caseychien @jedrichards
Fill out "Sourcing from the filesystem" stub article (gatsbyjs#8777)
1ed19f3 
This issue (gatsbyjs#8730) is part of the content migration project [gatsbyjs#8103](gatsbyjs#8103), which is meant to take existing content and repurpose it so it's easier to find in the docs.
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/
-->
gpetrioli pushed a commit to gpetrioli/gatsby that referenced this issue Jan 22, 2019
@ManoelLobo @gpetrioli
Authentication tutorial (gatsbyjs#9179)
912a855 
Regarding gatsbyjs#8103 

Starting the authentication tutorial. (Misc/Making a site with user authentication*)

Mostly setting intro and starting to work into content.

cc @shannonbux
gpetrioli pushed a commit to gpetrioli/gatsby that referenced this issue Jan 22, 2019
@caseychien @gpetrioli
Fill out "Sourcing from the filesystem" stub article (gatsbyjs#8777)
31352f5 
This issue (gatsbyjs#8730) is part of the content migration project [gatsbyjs#8103](gatsbyjs#8103), which is meant to take existing content and repurpose it so it's easier to find in the docs.
@gatsbot
Copy link

gatsbot bot commented Jan 28, 2019

Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!

@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Jan 28, 2019
@isaac-martin isaac-martin mentioned this issue Feb 4, 2019
Merged
@gatsbot
Copy link

gatsbot bot commented Feb 8, 2019

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

@gatsbot gatsbot bot closed this as completed Feb 8, 2019
This was referenced Mar 28, 2019
Merged
Merged
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 stale? Issue that may be closed soon due to the original author not responding any more. 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
10 participants
@jlengstorf @jkjustjoshing @dougajmcdonald @amberleyromo @DSchau @CanRau @didacta @kakadiadarpan @OrthoDex @shannonbux