Created
February 5, 2024 12:15
-
-
Save ChakshuGautam/ac1e76f55cb3ef47fea7daf4c33b0ae7 to your computer and use it in GitHub Desktop.
Docs on GitHub Pages vs Vercel (for BharatSahAIyak)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Context | |
1. There is a Vercel that we already maintain. | |
2. There is also a doc template that is one click deployment to vercel. | |
3. We generally deploy markdown files only on vercel. | |
## GitHub Pages - Pros || Vercel Cons | |
1. Easier for a new devloper. They would know GH Pages before vercel. | |
2. No other tool. | |
## GitHub Page - Cons || Vercel Pros | |
1. Add custom domains is a easier on Vercel. | |
2. Static files only. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GitHub Pages is ideal for simple, static sites directly connected to your GitHub repository. It's free and integrates well with your existing GitHub workflow but is somewhat limited in terms of server-side functionalities and dynamic content.
Vercel offers more advanced deployment options, automatic SSL, easy custom domain setup, serverless functions for dynamic content, and is also free for basic use. It's particularly powerful with Next.js projects but works well with other static site generators too.
In the end it depends on the user preference . I prefer vercel because it is easy to maintain and you will get a preview link for each PR and you can directly comment on the view