Update all text references of Dashboard to Cloud

.textlintrc

@@ -10,7 +10,7 @@
         // Cypress product
         ["^Cypress\.io", "Cypress"],
         ["Cypress' ", "Cypress's "],
-        ["Cypress dashboard", "Cypress Dashboard"],
+        ["Cypress cloud", "Cypress Cloud"],
 
         // Brands and Technologies
         ["ansi", "ANSI"],

CONTRIBUTING.md

@@ -254,10 +254,10 @@ To add a page, such as a new guide or API documentation:
 > has a different layout from the other guide pages, you would create a
 > component file within `/guides` matching the route name that you want to use.
 > For example, if I wanted to create a unique guide page without the sidebar
-> about using the Dashboard, I would create a file called
-> `/pages/guides/my-dashboard-guide.vue` and create a Vue component for the
-> specific layout I want to create. The page will then be accessible at the
-> route `/guides/my-dashboard-guide`.
+> about using Cypress Cloud, I would create a file called
+> `/pages/guides/my-cloud-guide.vue` and create a Vue component for the specific
+> layout I want to create. The page will then be accessible at the route
+> `/guides/my-cloud-guide`.
 
 #### A Worked Example
 

content/_data/plugins.json

@@ -129,7 +129,7 @@
         },
         {
           "name": "Knapsack Pro Cypress",
-          "description": "Dynamic tests split across parallel CI nodes with Knapsack Pro Queue Mode to get faster CI builds. Note - this is 3rd party implementation, different from the Cypress Dashboard parallelization.",
+          "description": "Dynamic tests split across parallel CI nodes with Knapsack Pro Queue Mode to get faster CI builds. Note - this is 3rd party implementation, different from Cypress Cloud parallelization.",
           "link": "https://github.com/KnapsackPro/knapsack-pro-cypress",
           "keywords": ["CI parallelisation", "continuous-integration"],
           "badge": "community"
@@ -939,7 +939,7 @@
         },
         {
           "name": "Cypress Image Snapshot",
-          "description": "Catch visual regressions and compare image diffs locally and in Cypress Dashboard.",
+          "description": "Catch visual regressions and compare image diffs locally and in Cypress Cloud.",
           "link": "https://github.com/palmerhq/cypress-image-snapshot",
           "keywords": ["image-diff", "snapshot"],
           "badge": "community"

content/_data/screencasts.json

@@ -111,7 +111,7 @@
       "youtubeId": "jO2ssfqhrSc"
     },
     {
-      "title": "GitHub integration with Cypress Dashboard of Cypress 3.4.1",
+      "title": "GitHub integration with Cypress Cloud of Cypress 3.4.1",
       "url": "https://www.youtube.com/watch?v=NGsGx3cbDcc&t=",
       "sourceName": "Youtube",
       "sourceUrl": "https://www.youtube.com/watch?v=NGsGx3cbDcc&t=",

content/_data/sidebar.json

@@ -216,8 +216,8 @@
           ]
         },
         {
-          "title": "Dashboard",
-          "slug": "dashboard",
+          "title": "Cypress Cloud",
+          "slug": "cloud",
           "children": [
             {
               "title": "Introduction",
@@ -1110,8 +1110,8 @@
               "slug": "general-questions-faq"
             },
             {
-              "title": "Dashboard",
-              "slug": "dashboard-faq"
+              "title": "Cypress Cloud",
+              "slug": "cloud-faq"
             },
             {
               "title": "Company",

content/_data/webinars.json

@@ -22,7 +22,7 @@
       "slides": "https://cypress.slides.com/cypress-io/codecov"
     },
     {
-      "title": "Introduction to the Cypress Dashboard",
+      "title": "Introduction to Cypress Cloud",
       "date": "November 18, 2020",
       "author": "Cypress with Cecelia Martinez",
       "youtubeId": "4JT5z0ng2E0",

content/api/commands/debug.md

@@ -92,7 +92,7 @@ the following:
 
 ## See also
 
-- [Dashboard](https://on.cypress.io/dashboard)
+- [Cypress Cloud](https://on.cypress.io/cloud)
 - [`.pause()`](/api/commands/pause)
 - [`cy.log()`](/api/commands/log)
 - [`cy.screenshot()`](/api/commands/screenshot)

content/api/commands/pause.md

@@ -127,7 +127,7 @@ will run only the next command and pause again.
 
 ## See also
 
-- [Dashboard](https://on.cypress.io/dashboard)
+- [Cypress Cloud](https://on.cypress.io/cloud)
 - [`cy.debug()`](/api/commands/debug)
 - [`cy.log()`](/api/commands/log)
 - [`cy.screenshot()`](/api/commands/screenshot)

content/api/commands/screenshot.md

@@ -248,8 +248,8 @@ off by setting `screenshotOnRunFailure` to `false` within your
 
 #### Screenshots in CI
 
-You can see screenshots taken during a CI run in the
-[Dashboard Service](https://on.cypress.io/dashboard) without any extra work.
+You can see screenshots taken during a CI run in
+[Cypress Cloud](https://on.cypress.io/cloud) without any extra work.
 
 Alternatively, to see screenshots in your Continuous Integration UI, most CI
 providers document a way to export the screenshots as artifacts and to make them
@@ -351,7 +351,7 @@ following:
 - [After Screenshot API](/api/plugins/after-screenshot-api)
 - [`cy.debug()`](/api/commands/debug)
 - [`Cypress.Screenshot`](/api/cypress-api/screenshot-api)
-- [Dashboard Service](/guides/dashboard/introduction)
+- [Cypress Cloud](/guides/cloud/introduction)
 - [`.pause()`](/api/commands/pause)
 - [Screenshots and Videos](/guides/guides/screenshots-and-videos)
 - [Visual Testing](/guides/tooling/visual-testing)

content/api/cypress-api/screenshot-api.md

@@ -181,6 +181,6 @@ Cypress.Screenshot.defaults({
 ## See also
 
 - [cy.screenshot()](/api/commands/screenshot)
-- [Dashboard Service](/guides/dashboard/introduction)
+- [Cypress Cloud](/guides/cloud/introduction)
 - [Screenshots and Videos](/guides/guides/screenshots-and-videos)
 - [Visual Testing](/guides/tooling/visual-testing)

content/api/plugins/after-screenshot-api.md

@@ -105,7 +105,7 @@ on('after:screenshot', (details) => {
 ## See also
 
 - [cy.screenshot()](/api/commands/screenshot)
-- [Dashboard Service](/guides/dashboard/introduction)
+- [Cypress Cloud](/guides/cloud/introduction)
 - [Plugins Guide](/guides/tooling/plugins-guide)
 - [Screenshots and Videos](/guides/guides/screenshots-and-videos)
 - [Visual Testing](/guides/tooling/visual-testing)

content/api/plugins/after-spec-api.md

@@ -98,8 +98,8 @@ module.exports = (on, config) => {
 ### Delete the recorded video if the spec passed
 
 You can delete the recorded video for a spec when certain conditions are met.
-This will skip the compression and uploading of the video when recording to the
-Dashboard.
+This will skip the compression and uploading of the video when recording to
+Cypress Cloud.
 
 The example below shows how to delete the recorded video for specs with no
 failing tests.
@@ -127,8 +127,8 @@ on('after:spec', (spec, results) => {
 ### Delete the recorded video if no tests retried
 
 You can delete the recorded video for a spec when certain conditions are met.
-This will skip the compression and uploading of the video when recording to the
-Dashboard.
+This will skip the compression and uploading of the video when recording to
+Cypress Cloud.
 
 The example below shows how to delete the recorded video for specs that had no
 retry attempts when using Cypress [test retries](/guides/guides/test-retries).

content/examples/examples/applications.md

@@ -102,7 +102,7 @@ activities, best practices and information sharing.
 - Combined coverage with Jest and Cypress via
   [Cypress code coverage plugin](https://github.com/cypress-io/code-coverage)
 - linters and pre-commit hooks: Eslint, Prettier, Js-beautify, Husky
-- recording test results on Cypress Dashboard
+- recording test results on Cypress Cloud
 
 ## More examples
 

content/examples/examples/workshop.md

@@ -31,7 +31,7 @@ a full list).
 - Using the Selector Playground
 - Testing XHR requests
 - Using data fixtures to mock data
-- Running tests on CI and recording to the Dashboard
+- Running tests on CI and recording to Cypress Cloud
 - Customizing your own reporters
 - Writing custom Cypress commands
 - Debugging in Cypress