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

Declaration Generator/LG: Shift line down to closing paragraph #1503

Open
4 of 5 tasks
SamHyler opened this issue Aug 16, 2024 · 7 comments
Open
4 of 5 tasks

Declaration Generator/LG: Shift line down to closing paragraph #1503

SamHyler opened this issue Aug 16, 2024 · 7 comments
Assignees
Labels
feature: letter generator issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: high role: UX content writing size: 1pt can be done in 6 hours or less Status: Update Requested

Comments

@SamHyler
Copy link
Member

SamHyler commented Aug 16, 2024

Title

Shift the final line down to the closing paragraph

Overview

High priority quick fix issue from Bonnie's feedback (#1461).
The final line in the final paragraph ("Why") before the closing in the LG/Declaration generator needs to be moved to the closing paragraph.

Action Items

  • Check off these boxes as they are done and document progress and updates in the comments below
  • Find the final two paragraphs ("why" and the closing paragraph) in Figma
  • Move the final line that is pre-written by EA/the generator in the "Why" paragraph to the closing paragraph. The line says "Thank you for considering my case."
  • Update final copy in all 3 spaces: Mobile, Desktop, and the Content SOT on Google Docs
  • Tag the Content leads on this issue by adding the label ready for content lead and pinging on slack

Resources/Notes

No response

@SamHyler SamHyler added priority: high role: UX content writing size: 1pt can be done in 6 hours or less feature: letter generator issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks ready for content lead labels Aug 16, 2024
@SamHyler SamHyler added this to the Stakeholder Review 2.0 milestone Aug 16, 2024
@cjankowski23 cjankowski23 self-assigned this Sep 25, 2024
Copy link

Hey @cjankowski23! Thanks for taking this issue.

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

Thanks again!

@cjankowski23
Copy link
Member

cjankowski23 commented Sep 26, 2024

Found the final two paragraphs ("why" and the closing paragraph) in Figma:

Locations:
Advice Page + Input Field
Master Pages: Desktop
Master Pages: Mobile

Shifted final line in all three locations.

Updated SOT on Google Docs
Expunge Assist SOT

Hello @SamHyler the issue is ready for review.

Copy link

github-actions bot commented Oct 5, 2024

Hey @cjankowski23! 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!

@cjankowski23
Copy link
Member

Progress:
Noticed when checking the Figma files sometimes the "Thank you for your consideration" statement was at the beginning of the why paragraphs, other times at the end of the why section. I audited the live form and messaged @SamHyler for clarification.

The line has now been shifted into its own closing line separate from the "Why" page.

Estimated Time to Completion (ETC): 1 week

Blockers:
Messaged @anitadesigns and @jyehllow on slack to check spacing is visually correct on the master draft for mobile and desktop before handing off to Dev.

@anitadesigns
Copy link
Member

I reviewed 2 frames (1 desktop and its mobile correspondent) and have questions for 2 other frames that I left on Figma! If those two frames add copy changes, I can review the padding once it is confirmed!

Copy link

Hey @cjankowski23! 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!

1 similar comment
Copy link

github-actions bot commented Nov 3, 2024

Hey @cjankowski23! 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: letter generator issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: high role: UX content writing size: 1pt can be done in 6 hours or less Status: Update Requested
Projects
Status: In Progress (active)
Development

No branches or pull requests

3 participants