UI/UX CoP Audit #553

juliagab56 · 2024-02-20T18:33:49Z

Overview

We want to audit the UI/UX CoP drive, wiki and github project boards to make sure all of our resources are accessible and navigation is clear and efficient.

Action Items

Resources/Instructions

Notes to add on individual guides during audit

    - Volunteers with over 3 weeks of inactivity are unassigned from their "guides" issue
    - Unassigned guide is moved back to prioritized backlog

Meeting Dates

March 01,2024
March 06, 2024
March 14, 2024
March 29, 2024
April 04, 2024
April 04, 2024
April 05, 2024 Guides Team Meeting
April 18, 2024

The text was updated successfully, but these errors were encountered:

Aparna1Gopal · 2024-03-02T04:25:45Z

Notes: Meeting: March 01,2024

Mapped out this issue. Identified all the clean-up activity required
Above instructions regarding "guides" were updated on the UI/UX Templates and Guides project board here

Aparna1Gopal · 2024-03-07T03:35:12Z

Notes: Meeting: March 06,2024

Mapped out a plan of action to clean-up the guides and templates board

Step 1

For guides that have not been worked on for 6+ months, the following steps are followed: Volunteers are unassigned and the following note is made on the guide:
- Volunteers with over 3 weeks of inactivity are unassigned from their "guides" issue
- Unassigned guide is moved back to prioritized backlog

Step 2

If there has been some progress on the guides in the last 6 months, then the following steps are followed: (based on feedback during all-Leads meeting on March 06,2024)
- Click +Saved replies - (at) person for an update - add labels (to update! & 2 weeks label) - and of there is no update in two weeks, follow Step 1

juliagab56 · 2024-03-12T20:21:08Z

Added another checklist item: audit Figma files.

Change Log and Proposals:

Figma allows for multiple projects within an account. We can separate our files into separate projects for better organization and navigation.
Public vs Private:
a. One project will contain all public files we share with our CoP, where they can view and edit. (workshops, exercises, icebreakers...)
b. The other project will contain all private files leadership will use to prepare workshops, house the CoP design system, work on any in-house project for the CoP (onboarding project...)
Opened a new project called "UI/UX CoP Management" for all private files
Renamed "HfLA CoP: Design" to "UI/UX Community of Practice" for all public, volunteer facing files (names can be improved).
Improved naming system:
- UI/UX CoP Management
  - All internal files for co-leads
    - NAME OF PROJECT (UI/UX CoP Internal)
- UI/UX Community of Practice
  - All shared files for volunteers
    - NAME OF PROJECT (UI/UX CoP)
      - [DATE] Name of Project
Added iconography for better, faster recognition
Changed "UI/UX CoP Design System" name to "Design System (UI/UX CoP Internal)" and moved it to "UI/UX CoP Management"
Structured meeting scopes so we can better organize assets:
- Workshops: Structured sessions that include a combination of teaching, demonstration, and guided practice. Designed to teach specific skills or tools with a clear learning goal.
- Challenges or Exercises: Sessions that are more focused, with the aim of applying knowledge or skills in a specific context. They can be collaborative or competitive.
- Ice Breakers or Games: Casual sessions designed to facilitate networking, foster kinship and familiarity within the community, and personal connections among volunteers.
FigJam files have border constraints. How do we scale?
- Run activities on FigJam and store files in a Figma design file since we can duplicate many more pages?
Moved "Design Critique" activity/asset to FigJam (UI/UX CoP) and deleted original file. Added a link to the Figjam board on the issue 539.
Created a "Challenges & Exercises (UI/UX CoP) Figma file.

Aparna1Gopal · 2024-03-30T04:26:46Z

Notes: Meeting: March 29,2024

Use each meeting to:
- Formulate guidelines/policies on how to carry-out a particular task. Such that there is a standardised procedure when the work is being distributed/assigned and the co-leads are working async.
- Review work conducted async. Work through any doubts/questions/corrections/feedback.
- Plan out async work for next week/next meeting
- Assign work for next week/next meeting
Distributed the tasks on the Audit Github Project Boards - Templates and Guides Board
Julia G did a walkthrough of the Figma file ideas/steps
- Need to create a Cover Page/Instruction page/Landing Page for the Private and Public Figma files (especially Naming conventions, iconography, how to use the pages etc.)
Next week
- Review async progress from this week
- Review remaining issues under Audit Github Project Boards - Templates & Guides
- Review tasks from the Figma Files + create guidelines for work + distribute tasks

Aparna1Gopal · 2024-04-04T15:34:48Z

Notes: Meeting: April 04, 2024

Aparna G completed assigned tasks under 'Action Items - Template and Guides.' Guides have been reviewed as per Instructions and moved to prioritized Backlog accordingly.

juliagab56 · 2024-04-04T23:00:59Z

Notes: April 04, 2024

Completed assigned tasks under 'Action Items - Template and Guides.' Guides have been reviewed as per Instructions and moved to other columns accordingly.
Where can we note questions for Bonnie?
- Guide Tracker project board
How can we communicate through this issue (Aparna & Julia)?
Check if info is documented Who are the HackforLA Stakeholders? #2
Ask Bonnie is this is an active issue Research Starter Kit #121 or what are the next steps.
When volunteers open and close issues by accident they automatically go into "in progress," even if they weren't there to begin with.
Bonnie to invite Julia G to Guides team meeting (Friday at 7:30am PST)
- Gather Qs for guides team

juliagab56 · 2024-04-05T20:05:11Z

Notes: April 05, 2024 Guides Team Meeting

Teaching volunteers how to use Github will have the biggest impact when it comes to keeping the projects boards and issues updated and tidy.
- To be discussed with co-leads if we should hold the github training sooner, in April 24 instead of May 15.
All guide issues to go into one repo, and have a label for each CoP
- the intership team, is working on issue templates for the guides
- we need to make guides that match the templates and viceversa
Add 'good first issue' to any guides that are simple and yet to be worked on, put labels so we know what's going on in each guide and that vounteers can easily navigate the board.
- use the saved replies

Aparna1Gopal · 2024-04-19T03:25:11Z

Notes: Meeting: April 18, 2024

Reviewed details from UI/UX CoP Audit #553 (comment)
Action items expanded under 'Audit Github Project Boards' to include links to all the Project Boards to help with tracking the boards
Plan of action for next meeting finalized
- Co-work on the action items under Audit Github Project Boards
- Add 'good first issue' to the appropriate guides
- Review UI/UX Design, Research & Writing Project Boards

Aparna1Gopal · 2024-04-26T02:49:59Z

Notes: Meeting: April 25, 2024

Use 'good first issue' label to sort out the guides in the backlog for new volunteers
'Good first issue' label used for guides that have good & simplified documentation. The history of the issue should be simplified and easy to grasp by the co-leads. In order for it to be understandable and easy to grasp by new members
Working on labelling the backlog:
- Julia working on - UI/UX CoP Co-Leads Guidelines (Leadership Checklist doc) #280 to Create a Guide: Research Participant Recruitment #45
- Aparna working on - Guide: How To Choose a Survey Platform for Your Surveys/User Testing #182 to Create a Guide: Color Theory in UX/UI Design #47
Aparna: Have completed reviewing the Backlog Guides and labelling with the 'good first issue.' Had to move Guide: Figma for developers (written by their friends at UI/UX) #27 & Guide: Effective Practices for communicating with Product Managers #14 to Ice-box due to the complexity of the issue.

Aparna1Gopal · 2024-05-10T02:19:16Z

Notes: Meeting: May 09, 2024

Collect best practices and processes through May & June. Focus on best practices in Google drive arrangement & Wiki IA.
Applying brand assets. Example: Cover on Google drive, Logo on Google drive, Meetup events.
Julia G & Aparna G come back in July. Will workshop on the audit (of Wiki & Google drive).
A public/open source folder/assets that could be accessed (example: how to conduct ethical research and publish it on a publishing site like ISSU - keeping it open source) - Drive better engagement to the CoP. Make resources more accessible.
Make a list of open issues that UX'ers joining the CoP can work on right away (example: publications on open source platforms - converting pdf to uploading on ISSUE etc.). Following the model of developers working on open tickets on teams.
To meet in last week of May to clean-up open role Project Boards.

Aparna1Gopal · 2024-06-27T02:08:13Z

Due to migration to new GitHub Project Board, the Audit Github Project Boards section is complete

Process of migration & notes from meetings

pogwon · 2024-09-04T22:27:38Z

After some initial organization of the Wiki page and an audit, here are some suggested changes:

Delete the following pages and consolidate into one "Guest Speakers" page with their respective sections:
- Speaker Instructions
- Home - Guest Speakers
- In-House Speakers
- Past Speakers
- Potential Speakers
Delete FAQ page and create a section for it on the Home Page
Delete the following pages and consolidate into one "Resources" page with their respective sections:
- External UXR Tools
- Home - Member Info
- Home - Resources
- Home - UI/UX CoP Branding Kit
- How to Conduct a Peer Review
- Research Frameworks
- Resource Repository (Could potentially be its own page since it is quite lengthy)
Delete the following pages and consolidate into one "UI/UX Guides" page with their respective sections:
- UI/UX Finished Guides and Templates
- How to Conduct a Peer Review
- Setup Interviews on Hack for LA Zoom accounts (include a duplicate of this section under "Guest Speakers" page)
Need to include a link to our project board on our Home Page as well as on the "Volunteer with Us" Page

juliagab56 added documentation Improvements or additions to documentation role: CoP Lead - Design complexity: medium size: 2pts Can be done in 7-12 hours labels Feb 20, 2024

juliagab56 self-assigned this Feb 20, 2024

juliagab56 changed the title ~~Google drive + Wiki content and IA audt~~ Google drive + Wiki content and IA audit Feb 20, 2024

juliagab56 changed the title ~~Google drive + Wiki content and IA audit~~ UI/UX CoP Audit Mar 2, 2024

Aparna1Gopal self-assigned this Mar 2, 2024

Aparna1Gopal mentioned this issue Mar 2, 2024

UI/UX Cop Lead / Org Agenda #187

Open

2 tasks

ExperimentsInHonesty mentioned this issue Mar 7, 2024

CoP leads Agenda hackforla/communities-of-practice#9

Open

This was referenced Apr 4, 2024

Who are the HackforLA Stakeholders? #2

Closed

Research Starter Kit #121

Open

Figure out what title to use for HfLA open role #161

Open

Guide: Effective practices for user testing #29

Open

Aparna1Gopal added the UI/UX CoP Leads Issues allocated to the 'CoP Leads' Project Board label Jun 21, 2024

Aparna1Gopal assigned pogwon Jul 3, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

UI/UX CoP Audit #553

UI/UX CoP Audit #553

juliagab56 commented Feb 20, 2024 •

edited by pogwon

Loading

Aparna1Gopal commented Mar 2, 2024 •

edited

Loading

Aparna1Gopal commented Mar 7, 2024 •

edited

Loading

juliagab56 commented Mar 12, 2024 •

edited

Loading

Aparna1Gopal commented Mar 30, 2024

Aparna1Gopal commented Apr 4, 2024

juliagab56 commented Apr 4, 2024 •

edited

Loading

juliagab56 commented Apr 5, 2024

Aparna1Gopal commented Apr 19, 2024

Aparna1Gopal commented Apr 26, 2024 •

edited

Loading

Aparna1Gopal commented May 10, 2024 •

edited by juliagab56

Loading

Aparna1Gopal commented Jun 27, 2024 •

edited

Loading

pogwon commented Sep 4, 2024 •

edited

Loading

UI/UX CoP Audit #553

UI/UX CoP Audit #553

Comments

juliagab56 commented Feb 20, 2024 • edited by pogwon Loading

Overview

Action Items

Resources/Instructions

Notes to add on individual guides during audit

Meeting Dates

Aparna1Gopal commented Mar 2, 2024 • edited Loading

Notes: Meeting: March 01,2024

Aparna1Gopal commented Mar 7, 2024 • edited Loading

Notes: Meeting: March 06,2024

juliagab56 commented Mar 12, 2024 • edited Loading

Aparna1Gopal commented Mar 30, 2024

Notes: Meeting: March 29,2024

Aparna1Gopal commented Apr 4, 2024

Notes: Meeting: April 04, 2024

juliagab56 commented Apr 4, 2024 • edited Loading

Notes: April 04, 2024

juliagab56 commented Apr 5, 2024

Notes: April 05, 2024 Guides Team Meeting

Aparna1Gopal commented Apr 19, 2024

Notes: Meeting: April 18, 2024

Aparna1Gopal commented Apr 26, 2024 • edited Loading

Notes: Meeting: April 25, 2024

Aparna1Gopal commented May 10, 2024 • edited by juliagab56 Loading

Notes: Meeting: May 09, 2024

Aparna1Gopal commented Jun 27, 2024 • edited Loading

pogwon commented Sep 4, 2024 • edited Loading

juliagab56 commented Feb 20, 2024 •

edited by pogwon

Loading

Aparna1Gopal commented Mar 2, 2024 •

edited

Loading

Aparna1Gopal commented Mar 7, 2024 •

edited

Loading

juliagab56 commented Mar 12, 2024 •

edited

Loading

juliagab56 commented Apr 4, 2024 •

edited

Loading

Aparna1Gopal commented Apr 26, 2024 •

edited

Loading

Aparna1Gopal commented May 10, 2024 •

edited by juliagab56

Loading

Aparna1Gopal commented Jun 27, 2024 •

edited

Loading

pogwon commented Sep 4, 2024 •

edited

Loading