Gatsby: Documentation for adding Gatsby to an existing repo/project

[ewolfe]

Summary

It would be nice to add documentation for adding Gatsby to an existing repo/project. Even if it means creating a new project via gatsby new my-blazing-fast-site and manually plucking the contents over to your existing project -- Since it would make it clear there no better alternatives (like gatsby new .).

Motivation

Why are we doing this?

_To make clear the suggested process for adding Gatsby to an existing repo/project._

What use cases does it support?

_Use cases where people aren't starting from scratch._

What is the expected outcome?

_A short blurb added somewhere to the documentation._

[gatsbot[bot]]

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!

[ewolfe]

Bump (to remove the stale label) since there are 13 👍

[gatsbot[bot]]

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!

[reyanshmishra]

not stale

[emplums]

Would love these docs!

[lannonbr]

@gillkyle is currently working on doing this for sites built with Create-React-App here: https://github.com/gatsbyjs/gatsby/pull/14626

[gillkyle]

The PR for porting from Create React App is about ready to be merged (https://github.com/gatsbyjs/gatsby/pull/14626)

Are there particular frameworks or configurations that would be helpful to have guides written for? (@emplums, @reyanshmishra, et al.) It was mentioned in the conversation for the above-linked PR that having some stubs for additional guides would be beneficial.