Parameterizing words for better language consistency and i18n

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

• Close this issue

• Text copy inconsistency is a problem in GitLab, for example: https://gitlab.com/gitlab-org/gitlab-ce/issues/31850.
• As we continue to build more features, and build more complexity, copyediting becomes increasingly important in order to communicate ideas and UX flows in product. Tracking consistency is difficult.
• Simple words such as New, Create, Open are often not carefully used or not used consistently.
• The problem is exacerbated as we do i18n.
• Is there an opportunity to do more parameterizing in the app to get consistency?
• Are there any design / app framework best practices or tools/libraries that we could use?
• This would make the app more consistent and more scalable in terms of language, which plays a significant aspect in UX design, especially where given our complexity, we often have to explain flows with words.

Example

• Parameterize Pipeline (and it's grammatical variants). So every time we refer to it, we use the same parameter.
• Parameterize the states of a Pipeline, i.e. passed, failed, running, skipped.
• Parameterize Merge as an action word.
• So when you create the label "Merge when pipeline passes", you would just be stringing together some parameters (and you would have to pick the right grammar forms).