feat: replace "site" with "project" in UI copy and documentation (#7299)

* refactor: replace "site" with "project" in UI copy and documentation

* refactor: update terminology from "site" to "project" across CLI codebase

* revert some changes + use "project ID" instead of siteId in error messages

* chore: run prettier

* update tests

* update snapshots + fix another test

* fix: remove "project"

* update siteId argument to id + updating another log with project ID

* revert analytics change + revert comment

* refactor: rename "site" to "project" in test descriptions

* fix checks for create living test sites

Author: cmparsons

README.md

@@ -84,7 +84,7 @@ netlify [command] help
 
 ## Documentation
 
-To learn how to log in to Netlify and start deploying sites, visit the
+To learn how to log in to Netlify and start deploying projects, visit the
 [documentation on Netlify](https://docs.netlify.com/cli/get-started/).
 
 
@@ -121,4 +121,4 @@ MIT. See [LICENSE](LICENSE) for more details.
 [snyk-img]: https://snyk.io/test/npm/netlify-cli/badge.svg
 [snyk]: https://snyk.io/test/npm/netlify-cli
 [netlify-img]: https://api.netlify.com/api/v1/badges/d3807379-2dcf-4a43-9c00-e7e8d90ecf70/deploy-status
-[netlify]: https://app.netlify.com/sites/cli/deploys
+[netlify]: https://app.netlify.com/projects/cli/deploys

docs/commands/clone.md

@@ -2,18 +2,18 @@
 title: Netlify CLI clone command
 sidebar:
   label: clone
-description: Clone a remote repo and link it to an existing site on Netlify
+description: Clone a remote repo and link it to an existing project on Netlify
 ---
 
 # `clone`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Clone a remote repository and link it to an existing site on Netlify
-Use this command when the existing Netlify site is already configured to deploy from the existing repo.
+Clone a remote repository and link it to an existing project on Netlify
+Use this command when the existing Netlify project is already configured to deploy from the existing repo.
 
 If you specify a target directory, the repo will be cloned into that directory. By default, a directory will be created with the name of the repo.
 
-To specify a site, use --id or --name. By default, the Netlify site to link will be automatically detected if exactly one site found is found with a matching git URL. If we cannot find such a site, you will be interactively prompted to select one.
+To specify a project, use --id or --name. By default, the Netlify project to link will be automatically detected if exactly one project found is found with a matching git URL. If we cannot find such a project, you will be interactively prompted to select one.
 
 **Usage**
 
@@ -29,8 +29,8 @@ netlify clone
 **Flags**
 
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
-- `id` (*string*) - ID of existing Netlify site to link to
-- `name` (*string*) - Name of existing Netlify site to link to
+- `id` (*string*) - ID of existing Netlify project to link to
+- `name` (*string*) - Name of existing Netlify project to link to
 - `debug` (*boolean*) - Print debugging information
 - `auth` (*string*) - Netlify auth token - can be used to run this command without logging in
 
@@ -42,7 +42,7 @@ netlify clone https://github.com/vibecoder/next-unicorn.git
 netlify clone git@github.com:vibecoder/next-unicorn.git
 netlify clone vibecoder/next-unicorn ./next-unicorn-shh-secret
 netlify clone --id 123-123-123-123 vibecoder/next-unicorn
-netlify clone --name my-site-name vibecoder/next-unicorn
+netlify clone --name my-project-name vibecoder/next-unicorn
 ```
 
 

docs/commands/deploy.md

@@ -13,7 +13,7 @@ Deploys from the build settings found in the netlify.toml file, or settings from
 The following environment variables can be used to override configuration file lookups and prompts:
 
 - `NETLIFY_AUTH_TOKEN` - an access token to use when authenticating commands. Keep this value private.
-- `NETLIFY_SITE_ID` - override any linked site in the current working directory.
+- `NETLIFY_SITE_ID` - override any linked project in the current working directory.
 
 Lambda functions in the function folder can be in the following configurations for deployment:
 
@@ -91,22 +91,22 @@ netlify deploy
 - `functions` (*string*) - Specify a functions folder to deploy
 - `json` (*boolean*) - Output deployment data as JSON
 - `message` (*string*) - A short message to include in the deploy log
-- `no-build` (*boolean*) - Do not run build command before deploying. Only use this if you have no need for a build or your site has already been built.
-- `open` (*boolean*) - Open site after deploy
+- `no-build` (*boolean*) - Do not run build command before deploying. Only use this if you have no need for a build or your project has already been built.
+- `open` (*boolean*) - Open project after deploy
 - `prod-if-unlocked` (*boolean*) - Deploy to production if unlocked, create a draft otherwise
 - `debug` (*boolean*) - Print debugging information
 - `auth` (*string*) - Netlify auth token - can be used to run this command without logging in
 - `prod` (*boolean*) - Deploy to production
-- `site` (*string*) - A site name or ID to deploy to
+- `site` (*string*) - A project name or ID to deploy to
 - `skip-functions-cache` (*boolean*) - Ignore any functions created as part of a previous `build` or `deploy` commands, forcing them to be bundled again as part of the deployment
 - `timeout` (*string*) - Timeout to wait for deployment to finish
-- `trigger` (*boolean*) - Trigger a new build of your site on Netlify without uploading local files
+- `trigger` (*boolean*) - Trigger a new build of your project on Netlify without uploading local files
 
 **Examples**
 
 ```bash
 netlify deploy
-netlify deploy --site my-first-site
+netlify deploy --site my-first-project
 netlify deploy --no-build # Deploy without running a build first
 netlify deploy --prod
 netlify deploy --prod --open

docs/commands/env.md

@@ -2,13 +2,13 @@
 title: Netlify CLI env command
 sidebar:
   label: env
-description: Control environment variables for the current site
+description: Control environment variables for the current project
 ---
 
 # `env`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Control environment variables for the current site
+Control environment variables for the current project
 
 **Usage**
 
@@ -24,10 +24,10 @@ netlify env
 
 | Subcommand | description  |
 |:--------------------------- |:-----|
-| [`env:clone`](/commands/env#envclone) | Clone environment variables from one site to another  |
+| [`env:clone`](/commands/env#envclone) | Clone environment variables from one project to another  |
 | [`env:get`](/commands/env#envget) | Get resolved value of specified environment variable (includes netlify.toml)  |
 | [`env:import`](/commands/env#envimport) | Import and set environment variables from .env file  |
-| [`env:list`](/commands/env#envlist) | Lists resolved environment variables for site (includes netlify.toml)  |
+| [`env:list`](/commands/env#envlist) | Lists resolved environment variables for project (includes netlify.toml)  |
 | [`env:set`](/commands/env#envset) | Set value of environment variable  |
 | [`env:unset`](/commands/env#envunset) | Unset an environment variable which removes it from the UI  |
 
@@ -40,13 +40,13 @@ netlify env:get VAR_NAME
 netlify env:set VAR_NAME value
 netlify env:unset VAR_NAME
 netlify env:import fileName
-netlify env:clone --to <to-site-id>
+netlify env:clone --to <to-project-id>
 ```
 
 ---
 ## `env:clone`
 
-Clone environment variables from one site to another
+Clone environment variables from one project to another
 
 **Usage**
 
@@ -58,16 +58,16 @@ netlify env:clone
 
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
 - `force` (*boolean*) - Bypasses prompts & Force the command to run.
-- `from` (*string*) - Site ID (From)
-- `to` (*string*) - Site ID (To)
+- `from` (*string*) - Project ID (From)
+- `to` (*string*) - Project ID (To)
 - `debug` (*boolean*) - Print debugging information
 - `auth` (*string*) - Netlify auth token - can be used to run this command without logging in
 
 **Examples**
 
 ```bash
-netlify env:clone --to <to-site-id>
-netlify env:clone --to <to-site-id> --from <from-site-id>
+netlify env:clone --to <to-project-id>
+netlify env:clone --to <to-project-id> --from <from-project-id>
 ```
 
 ---
@@ -129,7 +129,7 @@ netlify env:import
 ---
 ## `env:list`
 
-Lists resolved environment variables for site (includes netlify.toml)
+Lists resolved environment variables for project (includes netlify.toml)
 
 **Usage**
 

docs/commands/functions.md

@@ -9,7 +9,7 @@ description: Run netlify dev locally
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
 Manage netlify functions
-The `functions` command will help you manage the functions in this site
+The `functions` command will help you manage the functions in this project
 
 **Usage**
 

docs/commands/init.md

@@ -2,13 +2,13 @@
 title: Netlify CLI init command
 sidebar:
   label: init
-description: Initialize a new site locally
+description: Initialize a new project locally
 ---
 
 # `init`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Configure continuous deployment for a new or existing site. To create a new site without continuous deployment, use `netlify sites:create`
+Configure continuous deployment for a new or existing project. To create a new project without continuous deployment, use `netlify sites:create`
 
 **Usage**
 
@@ -19,7 +19,7 @@ netlify init
 **Flags**
 
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
-- `force` (*boolean*) - Reinitialize CI hooks if the linked site is already configured to use CI
+- `force` (*boolean*) - Reinitialize CI hooks if the linked project is already configured to use CI
 - `git-remote-name` (*string*) - Name of Git remote to use. e.g. "origin"
 - `manual` (*boolean*) - Manually configure a git remote for CI
 - `debug` (*boolean*) - Print debugging information

docs/commands/link.md

@@ -2,13 +2,13 @@
 title: Netlify CLI link command
 sidebar:
   label: link
-description: Link an existing site to a local site directory
+description: Link an existing project to a local project directory
 ---
 
 # `link`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Link a local repo or project folder to an existing site on Netlify
+Link a local repo or project folder to an existing project on Netlify
 
 **Usage**
 
@@ -21,8 +21,8 @@ netlify link
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
 - `git-remote-name` (*string*) - Name of Git remote to use. e.g. "origin"
 - `git-remote-url` (*string*) - URL of the repository (or Github `owner/repo`) to link to
-- `id` (*string*) - ID of site to link to
-- `name` (*string*) - Name of site to link to
+- `id` (*string*) - ID of project to link to
+- `name` (*string*) - Name of project to link to
 - `debug` (*boolean*) - Print debugging information
 - `auth` (*string*) - Netlify auth token - can be used to run this command without logging in
 
@@ -31,7 +31,7 @@ netlify link
 ```bash
 netlify link
 netlify link --id 123-123-123-123
-netlify link --name my-site-name
+netlify link --name my-project-name
 netlify link --git-remote-url https://github.com/vibecoder/my-unicorn.git
 ```
 

docs/commands/logs.md

@@ -7,7 +7,7 @@ sidebar:
 # `logs`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Stream logs from your site
+Stream logs from your project
 
 **Usage**
 

docs/commands/open.md

@@ -7,7 +7,7 @@ sidebar:
 # `open`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Open settings for the site linked to the current folder
+Open settings for the project linked to the current folder
 
 **Usage**
 
@@ -17,16 +17,16 @@ netlify open
 
 **Flags**
 
-- `admin` (*boolean*) - Open Netlify site
+- `admin` (*boolean*) - Open Netlify project
 - `filter` (*string*) - For monorepos, specify the name of the application to run the command in
-- `site` (*boolean*) - Open site
+- `site` (*boolean*) - Open project
 - `debug` (*boolean*) - Print debugging information
 - `auth` (*string*) - Netlify auth token - can be used to run this command without logging in
 
 | Subcommand | description  |
 |:--------------------------- |:-----|
-| [`open:admin`](/commands/open#openadmin) | Opens current site admin UI in Netlify  |
-| [`open:site`](/commands/open#opensite) | Opens current site url in browser  |
+| [`open:admin`](/commands/open#openadmin) | Opens current project admin UI in Netlify  |
+| [`open:site`](/commands/open#opensite) | Opens current project url in browser  |
 
 
 **Examples**
@@ -41,7 +41,7 @@ netlify open:site
 ---
 ## `open:admin`
 
-Opens current site admin UI in Netlify
+Opens current project admin UI in Netlify
 
 **Usage**
 
@@ -64,7 +64,7 @@ netlify open:admin
 ---
 ## `open:site`
 
-Opens current site url in browser
+Opens current project url in browser
 
 **Usage**
 

docs/commands/serve.md

@@ -3,14 +3,14 @@ title: Netlify CLI serve command
 sidebar:
   label: serve
 description:
-  Build the site for production and serve locally. This does not watch the code for changes, so if you need to rebuild
-  your site then you must exit and run `serve` again.
+  Build the project for production and serve locally. This does not watch the code for changes, so if you need to rebuild
+  your project then you must exit and run `serve` again.
 ---
 
 # `serve`
 
 <!-- AUTO-GENERATED-CONTENT:START (GENERATE_COMMANDS_DOCS) -->
-Build the site for production and serve locally. This does not watch the code for changes, so if you need to rebuild your site then you must exit and run `serve` again.
+Build the project for production and serve locally. This does not watch the code for changes, so if you need to rebuild your project then you must exit and run `serve` again.
 
 **Usage**