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
User interface polish pass (v1) #8238
Comments
@ghernandez345 I've labeled this as an epic. Feel free to spin out new issues from this, just make sure to link them up under "Child issues" so we can track them together. |
@ghernandez345 The plan is to bring this into the next release cycle. Will you please work with @RachelElysia to get this spec'd and estimated this week so it can be included in planning on Friday? Thanks! |
@xpkoala Will you please add a link to the 2nd document of polish fixes that you showed me yesterday? You can just add the link to the issue description. @ghernandez345 Should we create a new document to compile both of these documents (and any future ones) into? |
@lukeheath I updated the ticket to include the second document. @mike-j-thomas and I have one more session scheduled for later this evening where we will be adding more items to that second document. |
@xpkoala Sounds good. Please give @ghernandez345 a heads up when you've updated the doc. |
@mike-j-thomas @noahtalerman Heads up that as of 4.24.0 all issues that came out of Mike's polish pass have been closed and released. 🙌 |
@noahtalerman Should we keep this epic open for any reason? If not, I'll close it out and remove it from the roadmap board. |
Nice one. Thanks all 🙌🏻 |
Hooray! @lukeheath I think we can close this epic. Can you please leave it on the release board? Every week Mo and I review which issues made it into the "Confirm and celebrate" column. |
@mike-j-thomas just curious, do you and @xpkoala plan on continuing to do a polish pass every release? |
@noahtalerman I believe that is the plan. We missed the 4.24.0 p/p, but it's my intention to continue doing them for future releases. |
Great to hear! |
Goal
@mike-j-thomas will start regularly going through the user interface for a "polish pass" so that we can continue to improve and tighten up the UI. He will produce a checklist of fixes we can address during the merge freeze as time allows.
Because this first pass is much larger than subsequent ones will be tackling this as a dedicated epic. Our goal is twofold:
How?
@ghernandez345 will be taking lead on working with @mike-j-thomas to implement these changes and improve the overall design <-> frontend workflow so that our UI and Figma assets more closely match.
Video:
https://www.loom.com/share/b55adb446fdd49c98ec231a4f30edc23
Checklist of fixes:
https://docs.google.com/document/d/1x9E6fSzVSYwuMy0TQoRQUA8eMhZO09y4LakjCRZSHjo/edit?usp=sharing
Second document of fixes:
https://docs.google.com/document/d/11eby1jkkHQSpH08eO-N7__FjlzWpSA9IpFuoFZpfb80/edit#
Child issues
Polish fixes
Feature changes/Larger tasks
The text was updated successfully, but these errors were encountered: