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.

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 "How to run a Gatsby workshop" doc #8847

Closed
6 tasks
shannonbux opened this issue Oct 5, 2018 · 8 comments · Fixed by #11812
Closed
6 tasks

Content migration - create "How to run a Gatsby workshop" doc #8847

shannonbux opened this issue Oct 5, 2018 · 8 comments · Fixed by #11812
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 Oct 5, 2018

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

Open a pull request

@shannonbux shannonbux 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 5, 2018
@thatfiredev
Copy link
Contributor

Mind if I take this one?

@Deborah-Digges
Copy link

If nobody's picked this up yet, I can start working on it :)

@amberleyromo
Copy link
Contributor

@rosariopfernandes @Deborah-Digges would love for one of you to pick this up -- please comment back here, and I'll assign the "claimed" label.

@Deborah-Digges
Copy link

Awesome! I can pick this one up @amberleyromo

@amberleyromo
Copy link
Contributor

Ok, thanks @Deborah-Digges! I'll mark it claimed.

@rosariopfernandes, would love to have you contribute on another issue. I'll be opening up some more docs issues soon, but take a look at all the open issues! #8719

@amberleyromo
Copy link
Contributor

Hi @Deborah-Digges -- still working on this?

@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Feb 11, 2019
@gatsbot
Copy link

gatsbot bot commented Feb 11, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

@liltechnomancer
Copy link

I am working on hosting a meetup in Phoenix here shortly. If no one is working on this I could try and get it made!

DSchau pushed a commit that referenced this issue Feb 19, 2019
## Description

As per [rfc/29](gatsbyjs/rfcs#29), this PR introduces a major change to the Gatsby docs: a new `/contributing` section. I did a big find and replace to update all links, and there are also redirects for pages that moved.

This is a pretty large PR, and I welcome any and all feedback on the new structure and content. My only request is that we try to resolve any feedback quickly so that community PRs aren't working on outdated stuff.

Here's a screenshot of the new Contributing landing page:

![contributing landing page](https://user-images.githubusercontent.com/1045233/52890806-938f8a00-313b-11e9-8645-c4991fc95fa3.png)

## Related Issues

Fixes #11803, Fixes #8847 

## Outstanding questions
- Do we need to make any additional changes to CODEOWNERS?
- I included a link to `/contributing` in the docs sidebar to ease the transition. Should the link use some kind of icon to distinguish that it takes the user away from the docs?
- Should we add a new icon to the mobile nav (I didn't make any mobile changes in this PR)?
- Any changes to the sidebar, specifically around accordions?

## Subsequent related issues/stubs

- Gatsby Governance Model: #11805
- Triaging GitHub Issues: #11810
pragmaticpat pushed a commit to pragmaticpat/gatsby that referenced this issue Apr 28, 2022
## Description

As per [rfc/29](gatsbyjs/rfcs#29), this PR introduces a major change to the Gatsby docs: a new `/contributing` section. I did a big find and replace to update all links, and there are also redirects for pages that moved.

This is a pretty large PR, and I welcome any and all feedback on the new structure and content. My only request is that we try to resolve any feedback quickly so that community PRs aren't working on outdated stuff.

Here's a screenshot of the new Contributing landing page:

![contributing landing page](https://user-images.githubusercontent.com/1045233/52890806-938f8a00-313b-11e9-8645-c4991fc95fa3.png)

## Related Issues

Fixes gatsbyjs#11803, Fixes gatsbyjs#8847

## Outstanding questions
- Do we need to make any additional changes to CODEOWNERS?
- I included a link to `/contributing` in the docs sidebar to ease the transition. Should the link use some kind of icon to distinguish that it takes the user away from the docs?
- Should we add a new icon to the mobile nav (I didn't make any mobile changes in this PR)?
- Any changes to the sidebar, specifically around accordions?

## Subsequent related issues/stubs

- Gatsby Governance Model: gatsbyjs#11805
- Triaging GitHub Issues: gatsbyjs#11810
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging a pull request may close this issue.

6 participants