Add script to create new translation repositories (gatsbyjs#18893)

* add the create script

* description of env

* add reference to comment.

* edit README

* more information in README

* update create script

* add pulling logic

* add maintainers to organization

* add comment

* add discord link

* add more discord references

* Move script explanations to the README

* Update scripts/i18n/README.md

Co-Authored-By: Marcy Sutton <marcy@gatsbyjs.com>

* link to translation guide

* Update create.js

* remove style guide from list of scripts

scripts/i18n/.gitignore

@@ -0,0 +1,2 @@
+.env
+.cache

scripts/i18n/PROGRESS.template.md

@@ -0,0 +1,23 @@
+## For New Translators
+
+To translate a page:
+
+1. Check that no one else has claimed your page in the checklist and comments below.
+2. Comment below with the name of the page you would like to translate. **Please take only one page at a time**.
+3. Clone this repo, translate your page, and submit a pull request!
+
+Before contributing, please read the [translation guide](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/#contributing-to-a-translation) to understand the Gatsby translation process.
+
+Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
+
+## For Maintainers
+
+When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
+
+- [ ] Home Page (@gatsbybot) #1
+
+When PRs are merged, make sure to mark that page as completed!
+
+## Core Pages
+
+**These pages should be translated first.** These pages must be translated to be considered an official Gatsby localization.

scripts/i18n/README.md

@@ -0,0 +1,40 @@
+# Gatsby Internationalization Scripts
+
+These scripts are used to create and maintain new Gatsby translation repositories. They should be run by an admin of the GatsbyJS GitHub organization to start new translations and keep them up-to-date.
+
+## Environment
+
+These scripts require the following variables to be defined in the environment, e.g. through a `.env` file:
+
+- `GITHUB_ADMIN_AUTH_TOKEN` - a personal access token for a user with admin access to the gatsbyjs organization. This token must have the following write permissions: `admin:org`, `public_repo`
+- `GITHUB_BOT_AUTH_TOKEN` - a personal access token for [gatsbybot](https://github.com/gatsbybot) with `public_repo` permission.
+
+## `create`
+
+Usage:
+
+```
+yarn run create [issue #]
+```
+
+The `create` script sets up a new translation repository. It takes in the issue number of a [translation request issue](https://github.com/gatsbyjs/gatsby/issues/new?template=new_translation.md) that has a YAML code block:
+
+```yaml
+name: English # name of the language to be translated *in English*
+code: en # ISO-639 code or IETF language tag
+maintainers: # List of maintainers
+  - tesseralis
+  - marcysutton
+```
+
+The script will take this info and:
+
+- Create a new repo `gatsby-en`
+- Populate the repo with content from `gatsby-i18n-source`, containing all translateable content
+- Create an issue as gatsbybot showing the prioritized list of pages to translate
+- Assign all maintainers as CODEOWNERS and permissions
+- Invite all maintainers to the GatsbyJS GitHub organization
+
+## `sync` (TODO)
+
+The `sync` script updates contents of the translation repository based on new changes to the repo. It can be run manually or through a bot.