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

Add term glossary (content guide) for terms often used ambiguously. #47

Closed
adunkman opened this issue Jan 25, 2019 · 2 comments
Closed
Labels
needs: documentation This issue can be fixed by updating documentation, and does not require programming. needs: research The issue cannot be implemented without additional research. skill: content design / strategy Issues needing content

Comments

@adunkman
Copy link
Member

It would be nice to have things like “backup codes” vs. “security codes” (etc) covered in the style guide.

@adunkman adunkman added needs: documentation This issue can be fixed by updating documentation, and does not require programming. needs: research The issue cannot be implemented without additional research. labels Jan 25, 2019
@adunkman
Copy link
Member Author

Came across the Content Style Guide today.

@porta-antiporta
Copy link
Contributor

migrated LG-2636

Login.gov Design automation moved this from Backlog / ideas to Done Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: documentation This issue can be fixed by updating documentation, and does not require programming. needs: research The issue cannot be implemented without additional research. skill: content design / strategy Issues needing content
Projects
No open projects
Development

No branches or pull requests

3 participants