With the popularity of the JAM Stack, platforms like Vercel and Netlify have become the go-to way to deploy websites. My first experience had to be to deploy FrictionLog's website in Vercel.
While this is the first time using Vercel, I have deployed websites using Netlify, and I'm familiar with the flow. It was a great experience to deploy our website in Vercel, not only for development but also for previews of pull requests, all done automatically.
The goal of this exercise was to deploy our NextJS code to the web.
I have considerable experience in web development, including Angular and VueJS, but recently when I got into developing with React and NextJS, learning the JAM Stack. I do have prior experience of using Netlify to deploy a blog.
The home page is clear and easy to understand what the platform does, the features and value proposition.
I usually use Github Auth for development tools. The creation of my account was effortless.
Looking back, this is obvious, but at the moment, it took me some time to create the project since FrictionLog's code is in a Github organization, and I didn't have the Org Admin permission.
To deploy an organization repository, you must be an organization owner. I believe Vercel should be capable of checking this and provide guidance to the user.
Once sorting our the permissions issue, the project setup and deployment did take just a few minutes and was a great experience.
This feature that generates deployments of soon-to-be merged code is excellent. No extra configuration was needed.
The short answer is not right away; deployments stay around for some time after the code merge completes, and the branch has is removed. Eventually, the platform automatically deletes them, but there is no way to trigger that action manually.
The Vercel CLI automatically recognizes the project using the GitHub URL and links it.