Component Proposal: Glossary

[debjudy]

Examples
https://design.va.gov/content-style-guide/word-list
https://www.fec.gov/help-candidates-and-committees/registering-political-party/

https://github.com/18F/glossary

https://www.usaspending.gov/

DESIGN ASSETS

• 10% - Collect and analyze examples; draft research insights and list of features for team/client feedback
• 20% - Draft user story & clarify the problem(s) / user needs
• 30% - Low-fi design review
• 40% - Get community feedback on initial, Hi-fi designs
• 50% - Hi-fi Sketch assets review
• 60% - Hi-fi Adobe XD assets review
• 80% - Sketch and XD assets review w/ Dan + merged into master working files
• 100% - PR approved by Dan

GUIDANCE

• 10% - Summarize insights from research (desk + interviews)
• 20% - Draft guidance review no. 1 (minimum 2 bullets each section)
• 40% - Get community feedback on draft guidance
• 50% - Draft guidance review no. 2 (accessibility focus)
• 60% - Draft guidance review no. 3 (w/ Dan)
• 80% - Add component to research report and slide deck
• 100% - PR approved by Dan

CODE

• 10% - Code review no. 1 (Federalist preview) - interaction design focus
• 20% - Code review no. 2 (Federalist preview) - visual design focus
• 40% - Get community feedback or conduct tests with users, round 1
• 60% - Code review no. 3 (Federalist preview) - accessibility focus
• 80% - Get community feedback or conduct tests with users, round 2
• 100% - PR approved by Dan

[smcharg-ohss]

Here's another example: https://revenuedata.doi.gov/

When I was at Interior, we had the book icon like the FEC site linked above has and found during user interviews that people didn't always understand what the icon meant. Many didn't associate the book with getting more information or help and some thought it was a bible, so we switched to the question mark icon. Many more participants associated the question mark with getting more information about a term.

We would definitely use a glossary component at the Office of Homeland Security Statistics.