Labels

Issues, merge requests, and epics related to the docs archives https://gitlab.com/gitlab-org/gitlab-docs-archives

Issues describing a documentation backport to older GitLab versions

A Technical Writer has picked up this item from the docs or tw-team Slack channels, or from roulette, AND the item is outside of their assigned groups.

Apply this label only on issues/MRs that reply to a community comment in docs.gitlab.com

An idea or proposal for documentation content. For documentation site features, use https://gitlab.com/gitlab-com/gitlab-docs/issues

Docs feedback originating from a customer-created issue, survey comment, or the docs feedback form.

Related to docs linting (markdownlint, Vale) https://docs.gitlab.com/ee/development/documentation/testing.html#local-linters

Issues with missing documentation. Technical Writing team to follow up with Development team.

Issues and MRs that only require a documentation change, to differentiate from those coupled with a feature change

Documentation tasks that need to be reviewed by the Technical Writing team.

Issues, MRs, and Epics related to Docs Shell

Issues and Epics for the docs site (To Be Discussed)

Ongoing discussions and proposals related to the docs site (not ready for development yet)

Issues, MRs, Epics for docs.gitlab.com ready for development by engs and UXers

Issues and MRs (docs site): to be scheduled / prioritized

A follow-up issue/MR for additional documentation work from merged MRs. This can occur when more work is required after a technical writer review, or if a technical writer review didn’t occur.

(Trivial) Tiny change, such as fixing a single misspelling or grammatical mistake.

(Small) Simple change where problem is well understood, and little or no investigation is required. Typically a few words up to a couple sentences.

(Medium) Solution is well understood and relatively straightforward, small investigation effort may be required. Typically involving a few sentences.