From 8f8198a6bf0534f01f22518538560f9addb0b63e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Lorber?= Date: Thu, 20 Jul 2023 12:26:00 +0200 Subject: [PATCH] Update website/docs/deployment.mdx Co-authored-by: Joshua Chen --- website/docs/deployment.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/deployment.mdx b/website/docs/deployment.mdx index 10e8446022d8..3db389e1653b 100644 --- a/website/docs/deployment.mdx +++ b/website/docs/deployment.mdx @@ -122,7 +122,7 @@ If you are unsure of which one to choose, ask the following questions: Do I need collaboration-friendly deployment workflows? -- 🟡 Self-hosted services can leverage continous deployment functionality like Netlify, but more heavy-lifting is involved. Usually, you would designate a specific person to manage the deployment, and the workflow wouldn't be very git-based as opposed to the other two options. +- 🟡 Self-hosted services can leverage continuous deployment functionality like Netlify, but more heavy-lifting is involved. Usually, you would designate a specific person to manage the deployment, and the workflow wouldn't be very git-based as opposed to the other two options. - 🟢 Netlify and Vercel have deploy previews for every pull request, which is useful for a team to review work before merging to production. You can also manage a team with different member access to the deployment. - 🟡 GitHub Pages cannot do deploy previews in a non-convoluted way. One repo can only be associated with one site deployment. On the other hand, you can control who has write access to the site's deployment.