When comparing GitLab Pages vs Surge, the Slant community recommends GitLab Pages for most people. In the question“What is the best static website hosting provider?” GitLab Pages is ranked 2nd while Surge is ranked 16th. The most important reason people chose GitLab Pages is:
Gitlab pages are quick and simple to setup, with [documentation](http://doc.gitlab.com/ee/pages/) that's short and fast to read through.
Ranked in these QuestionsQuestion Ranking
Pro Easy to setup
Gitlab pages are quick and simple to setup, with documentation that's short and fast to read through.
Pro Regular updates
GitLab is being constantly worked on and has a new release every month.
Pro Free private repositories
On gitlab.com you can have free private repositories.
Pro Open Source
Unlike BitBucket or GitHub, GitLab itself is Open Source. Even EE (which is needed for pages, but is free on Gitlab.com) is "source available".
Pro Free Tier
Most sites are free and include basic SSL. Pro options for those who need it cost $13/month.
Pro Six Keystrokes to publish site
Type surge and hit enter in your project directory to deploy.
Pro pushState support for single page apps
Great for front ends like React and Vue.
Pro Supports Jekyll and Grunt and other CIs
Pro Support on Slack
Live Chat Support.
Pro Automatic Clean URLS
/page resolves /page.html
Pro Automatic Gziping
Auto gzips and sends gziped files.
Pro Custom 404.html files
Catch-all 200.html files.
Pro ent (intelligently) about trailing slashes (“/”)
Pro Far-future expire headers
Con Does not support .pdf by default
Does not support .pdf. You have to be personally whitelisted.