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

Implement 3 Key terms #1356

Open
3 of 4 tasks
SamHyler opened this issue Apr 23, 2024 · 17 comments
Open
3 of 4 tasks

Implement 3 Key terms #1356

SamHyler opened this issue Apr 23, 2024 · 17 comments
Assignees
Labels
dependency The issue or reason why this issue is in the icebox feature: guidelines feature: Style Guide guidance on writing and visual components feature: UX improvements issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: high role: UX content writing size: 5pt Can be done in 19-30 hours Status: Update Requested

Comments

@SamHyler
Copy link
Member

SamHyler commented Apr 23, 2024

Dependency

#1629 #1630 #1631

Overview

Follow up on Content terminology research issue 999 #999 for 3 key terms.
Discuss strategy within Content before finishing this issue.

Three key terms need to be 1. added to the Content Guidelines and 2. implemented across the site.

Action Items

Resources/Notes

For extra context and project tracking - see related issue, now closed #598

This is the research slide deck the also contains info about the 3 key terms https://docs.google.com/presentation/d/1sJgFQiAtwdWQxRvjT3Kx-rBy2cbx7m-J_FKp2oHN39A/edit#slide=id.g2cecb737568_0_0

Workspace: https://www.figma.com/design/hYqRxmBVtJbDv9DJXV6nra/Expunge-Assist-Main-Figma?node-id=2-8v

UXR follow-up issue around Declaration #1647

@SamHyler SamHyler added priority: high draft Not yet ready to be worked on role: UX content writing size: 3pt Can be done in 13-18 hours feature: Style Guide guidance on writing and visual components feature: guidelines feature: UX improvements issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks ready for content lead labels Apr 23, 2024
@SamHyler SamHyler added this to the Stakeholder Review milestone Apr 23, 2024
Copy link

Hey @SamHyler! Thanks for taking this issue.

To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below!

Thanks again!

1 similar comment
Copy link

Hey @SamHyler! Thanks for taking this issue.

To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below!

Thanks again!

@SamHyler
Copy link
Member Author

Issue will be finished and ready to work on after about a week, depending on lead schedules and availability to meet and plan.

Hey @SamHyler! Thanks for taking this issue.

To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below!

Thanks again!

Copy link

github-actions bot commented May 2, 2024

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

Copy link

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

3 similar comments
Copy link

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

Copy link

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

Copy link

github-actions bot commented Jun 8, 2024

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

@SamHyler
Copy link
Member Author

SamHyler commented Jun 9, 2024

Moving implementation to 2.0 as we don't have clear terms for 2 of the 3. Needs follow up discussion and work

@SamHyler SamHyler added size: 5pt Can be done in 19-30 hours and removed size: 3pt Can be done in 13-18 hours labels Oct 6, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@hackforla hackforla deleted a comment from github-actions bot Oct 7, 2024
@SamHyler
Copy link
Member Author

SamHyler commented Oct 7, 2024

I will be completing this in the next sprint here. First steps: discuss terms that need clarification in Content and make decision on term 3. Currently discussing how to implement across site with Design. Figma page is opened and ready for work.

Copy link

Hey @SamHyler! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

@SamHyler SamHyler removed the draft Not yet ready to be worked on label Oct 24, 2024
@SamHyler
Copy link
Member Author

Key terms: Declaration (will update to be legally correct as a first step, needs follow up discussion with UXR and follow up research around accessibility), Expungement (will update across CGs and website), and people with criminal records (will discuss within Content how to create continuity, simplicity, and accessibility).

@SamHyler
Copy link
Member Author

Terms have been added (started) to the Content Guidelines (CGs). Will finalize after clarifications

@SamHyler SamHyler added dependency The issue or reason why this issue is in the icebox and removed Status: Update Requested labels Oct 24, 2024
Copy link

github-actions bot commented Nov 2, 2024

Hey @SamHyler! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

@SamHyler
Copy link
Member Author

SamHyler commented Nov 7, 2024

SOT is audited and ready, @TechWriterMelissa and I are changing 2 terms site wide as the next step, and the whole content team is discussing the third team. Ready for follow-up on accessibility of declaration with UXR, will create an issue.

Content will be defining terms on the website (i.e. potentially a tool tip explaining what a declaration is and possible alternative terms). However, the term can still potentially pose an accessibility problem.

@SamHyler
Copy link
Member Author

Follow-up around declaration in #1647 handed over 15/11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency The issue or reason why this issue is in the icebox feature: guidelines feature: Style Guide guidance on writing and visual components feature: UX improvements issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: high role: UX content writing size: 5pt Can be done in 19-30 hours Status: Update Requested
Projects
Status: In Progress (active)
Development

No branches or pull requests

2 participants