-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
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! |
Found the final two paragraphs ("why" and the closing paragraph) in Figma: Locations: Shifted final line in all three locations. Updated SOT on Google Docs Hello @SamHyler the issue is ready for review. |
Hey @cjankowski23! Thanks again for taking this issue.
|
Progress: The line has now been shifted into its own closing line separate from the "Why" page. Estimated Time to Completion (ETC): 1 week Blockers: |
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! |
Hey @cjankowski23! Thanks again for taking this issue.
|
1 similar comment
Hey @cjankowski23! Thanks again for taking this issue.
|
Hey @cjankowski23! Thanks again for taking this issue.
|
4 similar comments
Hey @cjankowski23! Thanks again for taking this issue.
|
Hey @cjankowski23! Thanks again for taking this issue.
|
Hey @cjankowski23! Thanks again for taking this issue.
|
Hey @cjankowski23! Thanks again for taking this issue.
|
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
Resources/Notes
No response
The text was updated successfully, but these errors were encountered: