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

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.

(Large) Requires effort in validation through replication or research. Typically, more than a paragraph, less than a page.

(Very Large) Solution may not be straightforward or known. Significant investigation or expert knowledge required. Typically revising up to a full page, or sections of multiple pages.

For documentation-labeled items, use when content is added or updated for a new or changed feature, including MRs where the technical writer reviews a developer's work. Generally used with `feature` label.

For documentation-labeled items, use for content changes that resolve identified issues, including inaccurate or unclear content, typos, style problems, outdated screenshots, or bad URLs.

For documentation-labeled items, use for content changes not related to newly introduced features, fixes, or non-content structural items.

For documentation-labeled items, use when changes don't affect visitor readable, rendered content. Includes metadata, markdown code (incl. tiers or admonitions), and redirects.