The ability to include a Button in a Readme/html doc that starts a deployment flow in Gatsby Cloud for a given github repo

Just about everyone I talk to that uses Gatsby asks "what do you do for search?" and I tell them I use Algolia. It would be rad if Gatsby Cloud provided a search option, so that any site that is built by Gatsby Cloud can just 1-click enable search and use a drop-in component to have site search working on their site. Whether it's a white-label of Algolia, or indexed to something we host like ElasticSearch or something, it would be a huge value add for Gatsby Cloud users. WordPress (when used as a monolith even) doesn't have great search, so a lot of folks already offload search to Algolia or ElasticSearch (see: https://www.elasticpress.io/ ) I believe having search indexing as part of Gatsby Cloud would add value to a lot of our users, and could attract a lot of folks from markets like WordPress where search is already a struggle.

Gatsby Cloud currently supports GitHub and GitLab sign-in / authentication and access to repos (version control system), which enables functionality like: Automatic re-building of Gatsby site on push Automatic building of Deploy Previews on pull request This request exists to capture demand for adding BitBucket functionality which would work similarly to the existing version control systems currently available today in Gatsby Cloud.

It would be great to easily lock your whole page or parts of it behind a password just by setting it like Netlify does it: https://docs.netlify.com/visitor-access/role-based-access-control/ Great for clients, great for testing, great for things that want to avoid compliance for a specific period and still be accessible on the web.

Webhooks are used to trigger builds and preview inside Gatsby Cloud. The problem is, it's sometimes difficult to determine what content was sent in that webhook and why that build/preview might have failed. A UI option to log both the headers and body of that webhook request would make debugging build/preview issues on Gatsby Cloud much easier.

I want to stop a current build so that triggered builds after it are not queued up but build instantly.

Add A/B testing by branches like Netlify

For sites hosted on Gatsby Hosting, allow for locale(country)-based redirects in createRedirect.

Show a graph of changes in performance over time instead of only per PR. Similar to the functionality of Calibre ( https://calibreapp.com/ )

Build previews use hostnames like this: https://build-12345678-9abc-def0-1234-56789abcdef0.gtsb.io/ https://siteprefix-branchname.gtsb.io/ These would be better: https://build-12345678-9abc-def0-1234-56789abcdef0.siteprefix.gtsb.io/ https://branchname.siteprefix.gtsb.io/ The use case here is whitelisting OAuth domains. I can't safely whitelist all Gatsby build domains. With the prefix as the third-level domain, I could safely whitelist *. siteprefix.gtsb.io for authentication operations.