Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Content Guidelines] Standardize language #1018

Open
9 tasks
Tracked by #1286
SamHyler opened this issue Sep 18, 2023 · 1 comment
Open
9 tasks
Tracked by #1286

[Content Guidelines] Standardize language #1018

SamHyler opened this issue Sep 18, 2023 · 1 comment
Labels
feature: guidelines feature: Style Guide guidance on writing and visual components issue level I: request Smallest type of issue; Typically can be completed by one person priority: medium role: UX content writing size: 3pt Can be done in 13-18 hours

Comments

@SamHyler
Copy link
Member

SamHyler commented Sep 18, 2023

Overview

Currently, we are missing a few key areas of content terminology that should be defined and added to the Content Guidelines.
For example: how do we refer to the Letter Generator, as "our tool" or "the tool" or "your tool" or something else? Are there other types of language that can be improved and made standard so that our product uses a singular voice?

This should be done in conjunction with the Terminology research results, that is, when those results come in, this list can be expanded.

Action Items

  • Research best practices and current information
  • Look for areas where content can be standardized and make a list/chart with all terms used and where they are
  • Suggest which term is best to use
  • Discuss in Content
  • Iterate
  • Discuss in Content
  • When decision is made (check with Sam/Content lead and in Content meetings), update all areas of the language across the site and update the Content guidelines with a "use this not that" type section
  • Check in with Design about any changes
  • Hand over to Dev

Resources/Instructions

@SamHyler
Copy link
Member Author

3 key terms will be adjusted site wide. Leaving issue for future work to standardize across the site and in the Content Guidelines (CGs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: guidelines feature: Style Guide guidance on writing and visual components issue level I: request Smallest type of issue; Typically can be completed by one person priority: medium role: UX content writing size: 3pt Can be done in 13-18 hours
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

4 participants