EPIC - Create a glossary of terms

[SamHyler]

###Dependency
#478

Overview

Create a glossary of terminology and vocabulary. This issue primarily regards the Content glossary that will be used in, for example, tool tips and as modular copy across relevant parts of the site.

Linked issues address:
UXR and Content will collaborate to create the list of terms for the glossary, and discuss how to use it for different purposes.

Content needs an internal glossary for a future feature in the product. The terms should be written for the user of the website according to the style guide/Content Guidelines.

Research needs a glossary for the Wiki page and orientation of internal team members. The definitions can be written more broadly and developed.

Action Items

• Create draft of glossary based on user facing needs for the website ([Glossary ] Clarify terminology for product use #478). Incorporate the 3 key terms from Content Terminology Research #999
• Discuss between UXR and Content if changes are needed to adapt into a glossary for the Wiki
  • User Terminology Survey for Target Users #603
  • Revise and finalize
• Revise and finalize Content glossary
• Approve by Org. (Bonnie)
  • construct glossary in Wiki
  • Content contact with Dev to establish work going forward for potential tool tips
  • Close the issue

Resources/Instructions

Link Content Glossary for Bonnie's review here
Use this template to create the Glossary

Previous references:
Some research is found here.
Archived Content Glossary drafts

See slide 37 for a definition on Record Clearance https://portal.ct.gov/-/media/OPM/CJPPD/CjCjpac/CJPAC-Presentations-Folder/2019-Presentations/May-2019_-CouncilOfStateGov_PPT.pdf [note from Sylvia on 4/1/24: don't use information from sources outside of CA because it's not within scope and will cause confusion internally and externally]

[thomasdemoner]

Hi Sam, I changed the size label on this because we're using a new size system now, please let me know if it's correct. I'm also moving the issue out of waiting for approval and into the ice box. The priority is set to both low and medium, we should discuss this, but if you think this would be helpful for ongoing work in the project we can move it as you see fit.

[SamHyler]

Hi Sam, I changed the size label on this because we're using a new size system now, please let me know if it's correct. I'm also moving the issue out of waiting for approval and into the ice box. The priority is set to both low and medium, we should discuss this, but if you think this would be helpful for ongoing work in the project we can move it as you see fit.

Sounds good, Tom. Bonnie asked me to create it and put it in the waiting for approval box a while ago, but ice box sounds appropriate right now. The issue isn't fully fleshed out yet, but will be a next step after the Questions are further along. I think the size will actually be fairly large, we can change that when the issue is being worked on.

[thomasdemoner]

hey Sam! I think I see a couple of other issues that you have created that sound similar to this one and are also in the Icebox:

• https://github.com/hackforla/expunge-assist/projects/1#card-78052247
• https://github.com/hackforla/expunge-assist/projects/1#card-77965069

I just want to make sure they aren't duplicates and to see if either of them could be combined.

[SamHyler]

• https://github.com/hackforla/expunge-assist/projects/1#card-77965069

@thomasdemoner Thanks, Tom. I combined the two you listed, they are unrelated to the purpose of this issue. I had somewhat separate thoughts for the other two (updating guidelines vs copy in product) but they can be combined into a bigger issue for now.

[SamHyler]

This issue needs to be updated with all the relevant documents in the resource/instruction seciotn

[sylvia-nam]

Made comment on original issue to strikethrough irrelevant resource with justification

[SamHyler]

adding draft label as the issue needs revisions based on roadmapping