Remove PR previews after merging
For large sites with a lot of PR's the PR deploy previews list gets very long. Even after a PR is merged in Github, it still sticks around in the Gatsby Cloud UI. Ideally, this PR preview would go away after a PR is merged or at least provide an option in the UI to manually remove that PR deploy preview.
Users should be able to deploy Express-middleware style functions to be deployed alongside their Gatsby site using file-system style routing.
Expose a Gatsby Cloud management API
Having the web UI as the sole interface for configuring a large number of sites is just painful. Headless Gatsby Cloud, no ?
Add environment variables from config file
Add the ability to set environment variables via a config file instead of the UI.
Password Protection for Hosted Sites
For a site on Gatsby Hosting, I would like to be able to add simple password protection for users to be able to access the site.
Support for Cypress (end-to-end tests)
Add support for running Cypress end-to-end tests against Gatsby Cloud builds. The traditional approach involves building a site and running tests via GitHub Actions, which doesn't take advantage of Gatsby Cloud.
For sites hosted on Gatsby Hosting, allow for locale(country)-based redirects in createRedirect.
Forms in Gatsby Cloud
Are there plans to have a Forms feature similar to Netlify Forms in Gatsby Cloud?
Page for content editors with simpler UI
Technical users sometimes want to give non-technical users a curated view into the key questions they care about, such as "when is the content I just edited going live?" and "is there an error on master?". However, they are reluctant to give access to Gatsby Cloud because the full interface can feel overwhelming for non-technical users (weird long numbers? build logs? branches? login with Github?). We could create a "content editor" role, or special route for content editors, that hides the complexity they don't need.