[docs][workflows] Deploying to other hosting services

[jamstack-elise]

Part of the Top 25 Learning Workflows initiative. See #13708 for the meta issue that this issue falls under.

User story

As a new Gatsby user, I want to know other hosting services that can deploy Gatsby that is not listed here.

Evaluation

Search	Discover	Complete	Linked	Tone	Style	Overall
😐	😞	n/a	😐	n/a	n/a	😐

Steps taken to implement

1. Searchability

Google

• Google search keywords: "deploy gatsby"
  results:
  1st page: no relevant links. A reference to keyword "deploy gatsby to digitalocean" found in related search.
  3rd page: Drupal
• Google search keywords: "deploy gatsby digitalocean"
  results: 1st page: Gatsby GitHub Issue, Google snippet video tutorials: (1) (2) (3)
• Google search keywords: "deploy gatsby to other hosting services"
  results: 1st page: DeployHQ

Bing

• Bing seach keywords: "deploy gatsby"
  results: 1st page: DeployHQ

2. Discoverability
From a "deploy gatsby" search on Google, the first result was Gatsby's documentation. I could not find links relating to "Other hosting domains."

3. Completeness - n/a
By 2, document discovery is null. Completeness is ∅.

4. Linkedness
As a new Gatsby user, perhaps Adding a Path Prefix, Multi-Core Builds, Asset Prefix could help. In addition, I'd do some discovery on the links found on: "The Gatsby blog also has posts on both deployment and hosting." Cross fingers! 🤞🤞

5. Tone and accessibility - n/a
By 2, document discovery is null. Tone & accessibility is ∅.

6. Style - n/a
By 2, document discovery is null. Style is ∅.

Recommendations

• I agree that an explicit "other options" page is helpful to determine other hosting domain platforms found on the Top 25 Workflows spreadsheet.
• Ask Gatsby's developer community through an open form what other hosting platforms they are curious about (E.g. GoDaddy, Dreamhost, Bluehost, DigitalOcean, et al).
• Use form data to
  1. determine other hosting services documentation to generate.
  2. determine what keywords can be used to find already existing tutorials.

[github-actions]

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!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

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

[github-actions]

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.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

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

[rationalthinker1]

It is marked as done but where is the instructions to deploy this manually? I have it on digitalocean.

[AishaBlake]

Opening this back up! We weren't quite ready to tackle this work before gatsbot closed it automatically but this is still a priority. If folks in the community would like to work on it, we welcome contributions.

In addition to the initial assessment, I'd like to revisit the quality of existing documentation. We have a lot of options listed and I want to make sure they're still accurate, useful, discoverable, etc. I also wonder if we need to provide any more background information around what's happening when you host a project.

It is marked as done but where is the instructions to deploy this manually? I have it on digitalocean.

@rationalthinker1 do you mean that you want to see documentation around how to host a Gatsby site on DigitalOcean?

[rationalthinker1]

@rationalthinker1 do you mean that you want to see documentation around how to host a Gatsby site on DigitalOcean?

Hey Aisha, I'm sorry. That's what I meant. I want to host gatsby on digital ocean.

[AishaBlake]

Taking another look at this issue, it looks like some things have improved. I'd also like to note that, though the initial line item in the umbrella issue is "Deploying to other hosting services" that's not actually a search I'd assume people are using. It's more likely people are looking for either a specific service or a more general page on "deploying a Gatsby site" which I think we have pretty well covered.

This issue has uncovered a desire for docs on deploying with DigitalOcean. We have a lot of services covered, so I'm going to close this in favor of a new issue specifically calling for a DigitalOcean guide. Some notes on where I think we're at with this:

• Searching "deploy Gatsby" now turns up links to our Deploying and Hosting page first. Most results on the first page of both Google and Bing are either gastbyjs.org or .com
• We now have docs on deploying to 18 different services.
• The docs seem to generally follow the style guide but they've been added over quite a long time and their formatting isn't as consistent as I would like. This might be confusing for users trying to decide where to deploy their Gatsby sites. I'll write up a specific issue for this as well.

Thank you both for your input! I really appreciate your interest and effort in making the Gatsby docs even better.