[Umbrella] Rename Zeit to Vercel

[muescha]

Note: please wait for classification of this issue from @gatsbyjs/learning before submitting PR

Description

Zeit is now renamed to Vercel.

Important renamings:

• ZEIT → Vercel
• ZEIT Now → Vercel
• ZEIT Smart CDN → Vercel Edge Network

References

• Vercel Banding Timeline
• Vercel Branding FAQ

Steps to reproduce

search repo for zeit: https://github.com/gatsbyjs/gatsby/search?q=zeit&unscoped_q=zeit

Note

some changes (for example GitHub repo are) available after 20. May 2020 -> see time line

Changes

All changes described in Timeline

Brand names:

• Zeit to Vercel
• Now to Vercel
• Zeit Now to Vercel
• Now CLI to Vercel CLI
• ZEIT to Vercel

Commands:

• now to vercel

Environment:

• NOW_* to VERCEL_*

Domains:

• zeit.co to vercel.com
• now.sh to vercel.app

GitHub:

• /zeit to /vercel (after 20. May 2020)

Places to change

Note: only searched for Zeit but not so much for Now, added some now places

Unclassified occurrence

• (@muescha in fix(docs): links in sidebar to vercel #24021 merged) www/src/data/sidebars/doc-links.yaml

  78 - title: Deploying to ZEIT Now
  79   link: /docs/deploying-to-zeit-now/
  80   breadcrumbTitle: ZEIT Now
  

• (@muescha in fix(docs): remove deploying-to-now.md #24016 merged) docs/docs/deploying-to-now.md
  -> remove duplicate file of docs/docs/deploying-to-vercel.md

• (@iamdarshshah in fix(docs) - changes( ZEIT to Vercel) in docs/starters.yml #24022 merged) docs/starters.yml

  5472 - Continuous deployment via Netlify or Zeit.
  5893 zeit
  5904 - Custom server to test Production Builds on your local network via zeit/serve
  

• (@darkmtr in fix(docs): changes(ZEIT to Vercel) in core-utils and recipes #24120 merged) /docs/recipes/deploying-your-site.md

  • in section: ### Directions
  • what: references to now

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/blog/100days/free-hosting/index.md

  34 and [ZEIT Now](/docs/deploying-to-zeit-now/).
  

• (@iamdarshshah in fix(docs): next.js github links (zeit to vercel) #24785 merged) docs/blog/2017-10-03-smartive-goes-gatsby/index.md

  48 [Next.js](https://github.com/zeit/next.js/), as seemingly everyone going for a
  

• (@iamdarshshah in fix(docs): next.js github links (zeit to vercel) #24785 merged) docs/blog/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md

  58 I’ll also mention [next.js](https://github.com/zeit/next.js) which is quite
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/blog/2019-01-01-publish-multiple-gatsby-sites/index.md

  464 Now is a tool created by ZEIT that makes
  466 If you haven’t used Now before, then go-ahead and [get started](https://zeit.co/now#features)
  

• (@muescha in fix(blog): publish multiple sites: change now to vercel #24877) docs/blog/2019-01-01-publish-multiple-gatsby-sites/index.md

  • in section: ### Vercel
  • what: references to now

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/blog/2019-01-25-blazing-fast-development-with-gatsby-and-sanity-io/index.md

  130 either [Now](https://zeit.co)
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/blog/2019-04-06-security-for-modern-web-frameworks/index.md

  113 They are not the only ones: Azure, Google, Amazon, Zeit.co,
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/blog/2019-11-14-announcing-gatsby-cloud/index.md

  101 like Heroku, Netlify, Zeit,
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/docs/building-a-contact-form.md

  159 This initial implementation listens for POST requests to `/contact`, and sends you an email with the submitted form data. You can deploy this server with services such as [Now](https://zeit.co/now).
  

• (@iamdarshshah in fix(docs) - [Now documentation] link (ZEIT to Vercel) #24024 merged) docs/docs/caching.md

  50 When deploying with Now, follow the instructions in the [Now documentation](https://zeit.co/guides/deploying-gatsby-with-now#bonus:-cache-your-gatsby-assets).
  

• (@iamdarshshah in fix(docs) - [Now documentation] link (ZEIT to Vercel) #24024 merged) docs/docs/deploying-to-vercel.md

  9 ## Step 1: Installing Now CLI
  14 npm install -g now
  31 - [Example Project](https://github.com/zeit/now/tree/master/examples/gatsby)
  

• docs/docs/deploying-to-vercel.md

  • (@stackrole-dev in Update deploying-to-vercel.md #24119 merged) what: still refer to now cli and to zeit github
  • https://gatsby-functions.now-examples.now.sh
  • (@iamdarshshah in fix: links zeit to vercel #24786 merged) [Example Project](https://github.com/zeit/now/tree/master/examples/gatsby)
  • note: github change is available after 20.may

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/docs/preparing-for-deployment.md

  49 - [ZEIT Now](/docs/deploying-to-zeit-now)
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/docs/recipes.md

  132 - [Deploying to ZEIT Now](/docs/recipes/deploying-your-site#deploying-to-zeit-now)
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/docs/glossary/continuous-deployment.md

  10 and [Zeit](https://zeit.co/)
  

• (@iamdarshshah in fix(docs): /docs/* links (ZEIT to Vercel) #24026 merged) docs/docs/recipes/deploying-your-site.md

  85 ## Deploying to ZEIT Now
  87 Use [Now CLI](https://zeit.co/download) to deploy your Gatsby application without leaving the command-line interface.
  91 - A [ZEIT Now](https://zeit.co/signup) account
  93 - [Now CLI](https://zeit.co/download) package installed
  106 - [Deploying to ZEIT Now](/docs/deploying-to-zeit-now/)
  

• (@iamdarshshah in fix: links zeit to vercel #24786 merged) examples/using-styled-jsx/README.md

  5 Demonstrates using [styled-jsx](https://github.com/zeit/styled-jsx) with the
  

• (@darkmtr in fix(docs): changes(ZEIT to Vercel) in core-utils and recipes #24120 merged) packages/gatsby-core-utils/README.md

  69 A utility that enhances `isCI` from 'ci-info` with support for ZEIT's Now and Heroku detection
  

• (@iamdarshshah in fix: links zeit to vercel #24786 merged) packages/gatsby-plugin-styled-jsx/README.md

  3 Provides drop-in support for [styled-jsx](https://github.com/zeit/styled-jsx).
  17 You can add styled-jsx [plugins](https://github.com/zeit/styled-jsx#css-preprocessing-via-plugins) with the `jsxPlugins` option
  30 [Configuration options for `styled-jsx`](https://github.com/zeit/styled-jsx#configuration-options) can also be specified:
  

• (@iamdarshshah in fix(www): update zeit to vercel links #24044 merged)starters/README-template.md

  96 [![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/gatsbyjs/gatsby-starter-<%= name %>)
  

Usage in comments

• packages/gatsby-core-utils/README.md

  90 // {CI_NAME: "ZEIT Now"}
  

• packages/gatsby-core-utils/src/ci.ts

  37 * Gets the name of the CI environment (e.g. "ZEIT Now", "Heroku", etc.)
  

Usage in string constants

• packages/gatsby-core-utils/src/ci.ts

  5 getEnvDetect({ key: `NOW_BUILDER_ANNOTATE`, name: `ZEIT Now` }),
  6 getEnvDetect({ key: `NOW_REGION`, name: `ZEIT Now v1` }),
  

  Note: i don't know how to solve this? maybe both (new and old) should be valid? NOW_REGION and VERCEL_REGION?

• packages/gatsby-core-utils/src/ci.ts

  getEnvDetect({ key: `VERCEL_URL`, name: `Vercel Now` }),
  getEnvDetect({ key: `NOW_BUILDER`, name: `Vercel Now` }),
  

  @jamoo added getEnvDetect in Detect vercel again after rebranding in gatsby-telemetry #25883 Detect vercel again after rebranding in gatsby-telemetry

• packages/gatsby-core-utils/src/ci.ts

  getEnvDetect({ key: `VERCEL_BUILDER`, name: `Vercel Now` }),
  

  @jamoo added getEnvDetect in Also detect VERCEL_BUILDER should Vercel one day use it as per the docs #25926

• packages/gatsby-core-utils/src/__tests__/ci.ts

  37 expect(getCIName()).toEqual(`ZEIT Now`)
  45 expect(getCIName()).toEqual(`ZEIT Now v1`)
  

[iamdarshshah]

@muescha Nice catch. Digging into it. Thanks

[muescha]

oh - that was a draft and should not commited, i updated it now...

[muescha]

please lets wait before doing some PR for a classification from gatsby team @gatsbyjs/learning for classification which change is needed and which change we skip

[iamdarshshah]

Sure, Thanks for the quick update.

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[muescha]

not stale

[muescha]

there are left only few places:

• https://gatsby-functions.now-examples.now.sh
• and in the gatsby-core-utils package

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[LekoArts]

Only left is gatsby-core-utils now

[muescha]

🌟 🚢