GitLab Pages allows you to create a statically generated website from your project that is automatically built using GitLab CI and hosted on our infrastructure.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
Pages is not strategically our most important Release feature, but it's a popular feature and one that people really enjoy engaging with as part of the GitLab experience; it's truly one of our most "personal" features in the Release stage. We do not plan to provide a market-leading solution for static web page hosting, but we do want to offer one that is capable for most basic needs, in particular for hosting static content and documentation that is a part of your software release.
Automatic certificate renewal (gitlab-ce#28996) is our most popular issue and one that can be quite irritating to manually manage. We're excited to address this next in order to make using Pages easier and require less ongoing maintenance.
This category is currently at the "Complete" maturity level, and our next maturity target is Lovable (see our definitions of maturity levels). Key deliverables to achieve this are:
Automatic certificate renewal (gitlab-ce#28996) is highly popular in almost every category here, and would make adoption of GitLab Pages much more attractive.
The most popular customer issue is gitlab-ce#28996, which makes setting up and renewing certificates automatic for your Pages site. This is an ongoing hassle once you set up your Pages site since renewals in particular are frequent and manual. Solving this problem will make Pages even more automatic and easy to use.
Aligned with what CS is seeing, gitlab-ce#28996 (certificate renewal) is our top customer issue.
Additionally, our TAM team has identified gitlab-ce#29963 (GitLab Pages without DNS wildcard) as important for their customers.
Similar to many other categories in the vision here at the moment, internal customers have frequently raised gitlab-ce#28996 (certificate renewal) as the biggest irritation in working with pages.
Our own docs team is considering moving to a different hosting provider; details on reasons why can be found at gitlab-docs#313. The main difficulty with using Pages at www-gitlab-com / GitLab documentation scale is:
From a vision standpoint, adding Review Apps for Pages (gitlab-ce#26621) is interesting because it allows for more sophisticated development flows involving testing, where at the moment the only environment that GitLab understands is production. This would level up our ability for Pages to be a more mission-critical part of projects and groups.