The main Gatsby site at gatsbyjs.org

Run locally with:

• yarn install
• gatsby develop

See the full contributing instructions at https://www.gatsbyjs.org/contributing/how-to-contribute/

To work with environment variables create a file in the root of www called .env.development.

The .env.development file is ignored by git. Your token should never be committed.

To develop on the starter library, you'll need to supply a GitHub personal access token.

1. Create a personal access token in your GitHub Developer settings.
2. In the new token's settings, grant that token the "public_repo" scope.
3. Add the GitHub token to the .env.development file:

GITHUB_API_TOKEN=YOUR_TOKEN_HERE

Note: For gatsby build to be able to run you also need a .env.production file with the same contents

Guess.js is disabled by default and can be enabled by setting ANALYTICS_SERVICE_ACCOUNT and ANALYTICS_SERVICE_ACCOUNT_KEY env variables. These variables need to have access to the gatsbyjs.org analytics.

If you have access to the keys, add them like so:

ANALYTICS_SERVICE_ACCOUNT="service account@email.com"
ANALYTICS_SERVICE_ACCOUNT_KEY="PEM KEY VALUE"

Localizations are currently a work-in-progress and are thus disabled by default. They can be enabled by setting the LOCALES env variable to the locales you want to build:

LOCALES="es ja id pt-BR zh-Hans"

The list of possible locales can be found at i18n.json.

The default locale, English, is always on. There is currently no UI to link to the localizations, so you'll have to type in the name of the file you want to go to using the language code (e.g. /es/tutorial/part-one).

If you are not working on a starter or site showcase, it might be beneficial to use a placeholder image instead of actual screenshots. It will skip downloading screenshots and generating responsive images for all screenshots and replace them with a placeholder image.

Add the following env variable to your .env.development file to enable placeholder behaviour:

GATSBY_SCREENSHOT_PLACEHOLDER=true

For more information checkout gatsby-transformer-screenshot docs.

Since #18027, we are using theme-ui (via gatsby-plugin-theme-ui) to handle theming, CSS authoring, and to provide a dark color mode.

• Please use the sx prop and theme values to style elements and components wherever possible. The prop is "enabled" by adding theme-ui's JSX pragma.
• It is still okay to directly import tokens, e.g. mediaQueries or colors directly from www/src/gatsby-plugin-theme-ui if it helps your specific use case — for example when global CSS is required, when passing theme values to other libraries or plugins, when authoring complex responsive styles, etc.
• It is also perfectly fine to follow the theme-ui approach for responsive styles!
• If you need to add fields to the theme, you can do so in (the work-in-progress) www/src/gatsby-plugin-theme-ui. As things settle down, we will eventually migrate changed and added role-based tokens to https://www.npmjs.com/package/gatsby-design-tokens.
• Please keep the dark mode in mind when editing existing or adding new components.
• Please bear with us while we adjust https://www.gatsbyjs.org/guidelines/design-tokens/ to document the theme-ui values next to the raw token values.