Content migration - fill out "Static Folder" stub

[amberleyromo]

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

• Read the Style Guide and follow it in order for your PR to be accepted. Pay special attention to the templates.
  • Style Guide: https://www.gatsbyjs.org/docs/gatsby-style-guide/
  • Docs Templates: https://www.gatsbyjs.org/docs/templates/
  • Example of a similar article: https://www.gatsbyjs.org/docs/working-with-images/

Draft the doc

• Add to the Static Folder stub article
• Use the following reference material as a primary starting point to draft the new doc:
  • Using the static folder.
  • When to use the static folder
• Make sure you rewrite and adjust the content-- Add introductory language, etc. Make it a cohesive doc (not just copy/paste). Follow the format listed in these resources:
  • Docs Templates: https://www.gatsbyjs.org/docs/templates/
  • Example of a guide to imitate: https://www.gatsbyjs.org/docs/deploying-to-s3-cloudfront
• Add a sentence to the Adding images fonts and files page, linking over to the new "static folder" doc page. (That way the content is linked, but not duplicated)
• Find the stub in the docs sidebar, and remove the asterisk next to the title, (which will indicate that the doc is no longer a stub).

Open a pull request

• Open a pull request with your work, including the words "closes Content migration - fill out "Static Folder" stub #9222" in the pull request description.

[thatfiredev]

@amberleyromo I'd gladly take this one :)

[amberleyromo]

@rosariopfernandes great! thanks so much! Marking as claimed