What is GitLab Pages?
Who uses GitLab Pages?
GitLab Pages Integrations
Why developers like GitLab Pages?
Here are some stack decisions, common use cases and reviews by companies and developers who chose GitLab Pages in their tech stack.
I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.
GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.
It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.
We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.
While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.
We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.
GitLab Pages offers us a great way of internal documentation-presentation (javadoc, jsdoc, etc.) and and acts as a static document repository for things like our checkstyle-configuration, which makes it a flexible and powerful part of the GitLab infrastructure.
While there are obviously other options like a normal directory on the servers or a fully-fledged website that uses the gitlab-api to display this data, we decided to use Gitlab Pages as we can deploy to the page as a part of our gitlab ci pipeline.