Deploy on Vercel
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Review the existing GitHub Pages deployment and the documentation build entry point, then compare the required Vercel setup with the current hosting workflow. Done means the documentation builds and deploys successfully on Vercel and the published site is accessible as intended.
Written by the indexing model from the issue text.
Description
I think Github Pages doesn't work well in China. Is it possible to deploy our document in vercel instead? They provide a much better cdn for accessing in China.
- Dominant language
- Svelte
- Stars
- 23
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Flow-Launcher/docs
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Flow-Launcher/docs#99 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Flow-Launcher/docs#87 · 13 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
Flow-Launcher/docs#79 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Flow-Launcher/docs#49 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Flow-Launcher/docs#45 · 1 reaction ·
All issues in Flow-Launcher/docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·