We have clients that will be editing a page in the CMS and wish to preview but occasionally the preview will break and we have no idea, it would be great to be notified when a preview stops working.

It'd be convenient when reading through a list of build logs to see for each build, which pages were effected. It'd be great too if for each page, you could see the list of builds that had effected it.

There is a chance that the *. gatsbyjs.io domain gets crawled and indexed by search engines, which may be unwanted behaviour, especially if a custom domain is configured.

As a project manager, I would like the Gatsby codebase and the source codebase (in this case, WordPress) to be in the same git repo so that maintenance and workflows are simpler and certain files can be easily shared. For example, when creating a new Gutenberg block in WP, if the two codebases were in the same repo, a WP developer could write the CSS for a block and Gatsby could pull it directly from the same directory when building.

Currently lighthouse reports are generated only for the home (/) page. It would be useful to have this configurable. Example use case: all of our regional gatsby sites have the'/' redirected to /xx/ page (replace xx with regional ID). Due to this, lighthouse reports are not generated in gatsby cloud.

When I configure multiple domains for one site, I should be able to select a primary domain. The other domains should redirect to the primary domain. This is not possible today because createRedirect only works with paths, not domains. I believe redirecting secondary domains to the primary domain is a more common use case than serving the same site from multiple domains.

NOW: When Preview Builds failed 10 times, Gatsby Cloud automatically turns off "Preview Builds" option in order to avoid failed builds loop. EXPECTED: When it turns off "Preview Builds", it can send an email or notification to some endpoints.

Add A/B testing by branches like Netlify

We use Sanity and webhooks to trigger builds whenever a document is published in Sanity. We also have a large number of editors, as well as scheduled processes syncing data from other places. This leads to a lot of builds/invocations that are unnecessary. It would be great if we could debounce builds (at least triggered by webhooks) to once every {n} minutes.

Having the web UI as the sole interface for configuring a large number of sites is just painful. Headless Gatsby Cloud, no ?