Maintain button label convention

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem context

• How can we maintain the GitLab UX style in a scalable way with a growing number of contributors (both GitLab team members and community)?
• Style guides (UX and code) and merge request reviews are helpful, but they rely on humans. Can we automate the problem away?
• Can we easily localize GitLab (translate to other languages) for non-English markets in the future?

Tackle smallest problem

• The scope of the issue is to design and implement a system to ensure that GitLab button labels always follow the sentence case convention (and not title case):
• Add merge request and not Add Merge Request
• https://docs.gitlab.com/ce/development/ux_guide/copy.html
• https://material.google.com/style/writing.html#writing-capitalization-punctuation

Suggestions

• Refactor code so that all user-facing text in GitLab is in a small number of places. This allows the UX team to easily make updates by themselves.
• Frontend tests: Consider a Selenium test that takes the compiled HTML, finds all the button labels, and then asserts that they all follow the conventions. If there is an offfending button, the build fails.