This page documents the DRI and scope of responsibility for GitLab's "content websites".
This area has traditionally been referred to as "the handbook", but over time has grown in scope to include multiple sites, projects, repos, and types of content.
Therefore, we are using the term "content websites" here to avoid ambiguity and properly frame discussions around this scope of responsibility.
There are currently two "content websites" under this scope of responsibility:
about.gitlab.comis primarily backed by the
gitlab-com/www-gitlab-comproject and repo.
about.gitlab.comis also backed by the
gitlab-com/marketing/digital-experience/buyer-experienceproject and repo, such as small-business and enterprise. The plan is to migrate more content from the
gitlab-com/www-gitlab-comproject to the
docs.gitlab.comproduct documentation site.
about.gitlab.comand the Internal Handbook.
about.gitlab.com, nor the "Internal Handbook" at
internal-handbook.gitlab.io. This DRI, once established, will be ultimately responsible for all aspects of these content websites, including:
gitlab-com/marketing/digital-experience/buyer-experienceproject and repo, as well as other content. The exact areas are still not fully defined, and this should also be clarified as part of the definition of DRIs.
There is currently information describing differing support policies for the content websites in various places, and some of this info may be inconsistent or outdated. For example, the "Handbook On-Call" page, or the Handbook Support page.
All of this information should be cleaned up and consolidated when a final DRI is assigned. In the meantime, this is the process to obtain support:
#handbook-escalationchannel. See the existing "Handbook On-Call - When to escalate an issue" section for what types of issues are appropriate to be asked in this channel.
Content Websites Support (about.gitlab.com or internal-handbook.gitlab.io)issue template.
#handbookchannel for the public
about.gitlab.comsite, or in the
#internal-handbookfor the Internal Handbook.