crossref pages to static

howto/gitlab.md

@@ -538,12 +538,12 @@ store temporary information, caches and session information. They can
 also communicate with the [Gitaly](https://gitlab.com/gitlab-org/gitaly) server which handles all
 communication with the git repositories themselves.
 
-Finally, Git)Lab also features GitLab Pages and Continuous Integration
-("pages" and CI, neither of which we do not currently use). CI is
-handled by [GitLab runners](https://gitlab.com/gitlab-org/gitlab-runner/) which can be deployed by anyone and
-registered in the Rails app to pull CI jobs. [GitLab pages](https://gitlab.com/gitlab-org/gitlab-pages) is "a
-simple HTTP server written in Go, made to serve GitLab Pages with
-CNAMEs and SNI using HTTP/HTTP2".
+### Continuous integration
+
+GitLab also features Continuous Integration (CI). CI is handled by
+[GitLab runners](https://gitlab.com/gitlab-org/gitlab-runner/) which can be deployed by anyone and registered in
+the Rails app to pull CI jobs. This is documented in the [service/ci
+page](service/ci).
 
 ### Spam control
 
@@ -566,6 +566,15 @@ We have not looked a lot into GitLab scalability. Upstream has
 user sizes. We have not yet looked into this, and so far have just
 thrown hardware at GitLab when performance issues come up.
 
+### GitLab pages
+
+[GitLab pages](https://gitlab.com/gitlab-org/gitlab-pages) is "a simple HTTP server written in Go, made to
+serve GitLab Pages with CNAMEs and SNI using HTTP/HTTP2".
+
+GitLab pages is not currently in use in our setup, but could be used
+as an alternative to the [static mirroring system](howto/static-component). See the
+[discussion there](howto/static-component#alternatives-considered) for more information about that design.
+
 ## Issues
 
 [File][] or [search][] for issues in the [gitlab project][search].