Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

UX/UI Wiki #136

Closed
3 of 5 tasks
Hanastevenson opened this issue Oct 4, 2021 · 6 comments
Closed
3 of 5 tasks

UX/UI Wiki #136

Hanastevenson opened this issue Oct 4, 2021 · 6 comments
Labels
B: Documentation ⏳ <6 hrs Size: 1 HfLA week or 1 traditional work day

Comments

@Hanastevenson
Copy link
Member

Hanastevenson commented Oct 4, 2021

Overview

We need to document what the UX/UI team have done to date so that new members can understand our rationale and our decision making.

Action Items

  • View Development documentation in the Wiki as reference
  • UX/UI lead to create document
  • Add content to document
  • Review with PM
  • Create new ticket for UX/UI team to review

Resources/Instructions

The Wiki

@Hanastevenson Hanastevenson added this to the 01 - Velocity milestone Oct 4, 2021
@Hanastevenson Hanastevenson added Role: UX/UI Team Lead ⏳ <6 hrs Size: 1 HfLA week or 1 traditional work day labels Oct 4, 2021
@Hanastevenson
Copy link
Member Author

Please provide an update:

  1. Progress: "What is the current status of this ticket? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue or 3) put up a request for assistance on the #design-systems slack channel.

@rcurtis2
Copy link
Member

  1. Progress: I'm in the process of researching methods and creating the guide. Recently met with form design lead, Danielle, to get a clear roadmap of what had previously been done prior to me becoming the UX lead
  2. Blockers: I'm currently researching how best to construct a wiki so it is concise and is clear to new members
  3. Availability: I should be able to dedicate about 2-3 hours to work on this issue.
  4. ETA: Anticipate this issue to be completed end of Nov 2021

@Hanastevenson
Copy link
Member Author

@rcurtis2 As discussed in our meeting:

Upcoming/to-do - 1/13/2022

  • Add links to sections
  • Pull rationale for work done
  • Read through my work and think about the tone of voice (can a new joiner understand it?)
  • Add Link to Figjam
  • How the setup of how the google drive is organized
  • Where to find different information
  • Think about what the first ticket should be (secondary task)

@Hanastevenson
Copy link
Member Author

Add images/screenshots to #262

@Hanastevenson
Copy link
Member Author

@kelenelee
Copy link
Contributor

being tracked in #395

@kelenelee kelenelee removed this from the Velocity milestone Apr 23, 2022
@kelenelee kelenelee added this to the Project revival milestone May 5, 2022
@kelenelee kelenelee mentioned this issue May 5, 2022
12 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
B: Documentation ⏳ <6 hrs Size: 1 HfLA week or 1 traditional work day
Projects
No open projects
Status: ✅ DONE ✅
Development

No branches or pull requests

5 participants