Most pages in the GitLab documentation are written manually in Markdown. However, some pages are created by automated processes.
Two primary categories of automation exist in the GitLab documentation:
Automation helps with consistency and speed. But content that is automated in a non-standard way causes difficulty with:
Ideally, any automation should be done in a standard way, which helps alleviate some of the downsides.
Pages generated from structured dataSome functionality on the docs site uses structured data:
Other pages are generated by using non-standard processes. These pages often use solutions that are coded across multiple repositories.
Make an automation requestIf you want to automate a page on the docs site:
Because automation adds extra complexity and a support burden, we review it on a case-by-case basis.
Document the automationIf you do add automation, you must document:
.gitlab-ci.yml
updates and any pipeline requirements.Other GitLab team members should be able to easily find information about how to maintain the automation. You should announce the change widely, including, at a minimum:
#whats-happening-at-gitlab
.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4