Glossary Component / Tool Tips #1087
Labels
issue level II: main
issue tracking level I issues; often will be tracking cross-fuctional teams tasks
p-feature: glossary tool tip
priority: low
role: design
anything related to design
role: development
anything related to code
role: UX content writing
size: 3pt
Can be done in 13-18 hours
Milestone
Action Items
Overview
There was a glossary issue (link) a year or so ago to create a glossary of terms and definitions for the website to make it easier for users to understand difficult legal language. Now we are discussing how to create tool tips to implement this glossary. This is a step after the glossary is done/discussions should be had in tandem with the glossary development.
This issues should be tackled between design, content, and dev.
We will need:
Resources/Instructions
Link to glossary issues & docs
Figma space link here
The text was updated successfully, but these errors were encountered: