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

Design operations: Audit Figma file #1295

Closed
14 of 17 tasks
gabydisarli opened this issue Nov 7, 2023 · 8 comments
Closed
14 of 17 tasks

Design operations: Audit Figma file #1295

gabydisarli opened this issue Nov 7, 2023 · 8 comments
Assignees
Labels
carryover Carryover from a previous sprint design

Comments

@gabydisarli
Copy link
Contributor

gabydisarli commented Nov 7, 2023

Issue description

Audit the Figma file and document inconsistencies between the file and what's in production.

Acceptance criteria

  • Create a document for the audit so we can track the work and make sure all updates get made. This document should result in a list of updates needing to be made.
  • Create any follow on tickets breaking up the update work into manageable chunks ie. the request form, domain management, info site, etc.

Additional context

The Figma file is out of date and doesn't always match what's in production. This leads to doubled efforts when designers have to make updates to a screen that hasn't been kept up to date in Figma. The Figma should have parity with what's in production so devs and designers know that the Figma is correct and can be trusted.

Links to other issues

@kristinacyin
Copy link
Contributor

We need to move the Figma files from Truss to CISA workplace, so it might make sense to audit + update the Figma files as we move them

@h-m-f-t h-m-f-t removed the later Not MVP label Mar 11, 2024
@gabydisarli gabydisarli changed the title Design operations: Audit Figma file & come up with governance plan Design operations: Audit Figma file Mar 12, 2024
@gabydisarli
Copy link
Contributor Author

Discussion notes

@rileyorr
Copy link

The audit is in progress in the form of a spreadsheet in Google Drive but hasn't yet been shared out to the design team.

@Katherine-Osos Katherine-Osos added the carryover Carryover from a previous sprint label Mar 25, 2024
@rileyorr
Copy link

Finished the audit this morning! I will schedule time to review the audit with Katherine, Gaby, and Kristina. I'd like their feedback and perspective on some of my findings and open questions prior to creating tickets.

@rileyorr
Copy link

rileyorr commented Apr 1, 2024

I've finished writing all the tickets and linking them to the spreadsheet! Not sure who the appropriate reviewer should be for this work but I'm ready for it to be reviewed and approved as needed.

cc @Katherine-Osos @gabydisarli

@gabydisarli
Copy link
Contributor Author

@rileyorr Everything looks great! Can you link all the tickets created as a result of this work to this ticket under the "Links to other issues" section. That way it's easy to see them all at a glance.

@h-m-f-t
Copy link
Member

h-m-f-t commented Apr 2, 2024

@gabydisarli I just did that! Looks great. cc: @rileyorr

@rileyorr
Copy link

rileyorr commented Apr 2, 2024

@h-m-f-t thank you for linking those tickets! @gabydisarli let me know when I'm good to close this ticket

@AnnaGingle AnnaGingle mentioned this issue Oct 18, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carryover Carryover from a previous sprint design
Projects
Archived in project
Development

No branches or pull requests

6 participants