├── .github └── ISSUE_TEMPLATE │ ├── blank-issue.md │ ├── create-agenda.md │ ├── custom.md │ ├── feature_request.md │ ├── guest-speaker-consent.md │ ├── guest_speaker_questions.md │ ├── start-a-new-make-a-guide-issue.md │ ├── template-for-UX-Experience-Profile.md │ ├── template-for-making-guides.md │ ├── template-for-pilot-testing.md │ ├── ui-ux_cop_workshops.md │ ├── update-content-for-readme-file.md │ └── update-team-roster.md ├── LICENSE └── README.md /.github/ISSUE_TEMPLATE/blank-issue.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Blank Issue 3 | about: Consistent formatting make Issues concise and easy to navigate 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less. 12 | 13 | ### Action Items 14 | REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented. 15 | 16 | REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task. 17 | 18 | ### Resources/Instructions 19 | REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here. 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/create-agenda.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Create Agenda 3 | about: Assign issue to all team members day after meetup in prep for next meetup 4 | title: '' 5 | labels: documentation, help wanted, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Gather all items team members want to propose for this weeks' agenda. 12 | 13 | ### Action Items 14 | Add comment to this issue with your proposed agenda item. if item warrants an issue of its own please start a new issue, by going to the issues tab above and clicking on the New Issues green button. 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/custom.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Custom issue template 3 | about: Describe this issue template's purpose here. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: 'Feature Suggestion: ' 5 | labels: documentation 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Please write a user story for this feature suggestion in the following format: As a ______, I want to do X for Y reason and replace this text with it. 12 | 13 | ### Action Items 14 | - [ ] Define your Feature Suggestion 15 | - [ ] What is the feature you are suggesting? 16 | - [ ] Is this feature urgent 17 | - [ ] if so why? 18 | - [ ] How long do you expect it take to implement this issue? 19 | - [ ] Who is needed to implement this feature (Could you implement it yourself?) 20 | - [ ] Design 21 | - [ ] Front End 22 | - [ ] Back End 23 | - [ ] Database 24 | - [ ] What problem does this feature solve? 25 | - [ ] What technologies are needed for this feature? 26 | 27 | ### Resources/Instructions 28 | If there is a website which has documentation that helps with this issue provide the link(s) here: 29 | 30 | 31 | **Additional context** 32 | Add any other context or screenshots about the feature request here. 33 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/guest-speaker-consent.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Guest Speaker Consent 3 | about: Use this template to create consent documents for UI/UX CoP guest speakers 4 | title: 'Guest Speaker [Replace YEAR]: Create Consent Docs for [Replace NAME OF GUEST SPEAKER]' 5 | labels: 'role: CoP Lead - content, size: 0.5pt, UI/UX CoP Leads' 6 | assignees: '' 7 | 8 | 9 | --- 10 | 11 | #### Instructions for creating this issue 12 | The person who creates this issue should use links in the section "Resources for creating this issue" (i.e., 1.01, 1.02, etc.) to customize this issue. 13 | - Use Find/Replace (Mac: ⌘+F or PC: Ctrl+F) to search for and replace the keyword strings (including text and the brackets) below with the appropriate values 14 | - Year 15 | - [ ] Find/Replace `[Replace YEAR]` with the year that the talk will take place (Four digit format, ex: "2024") 16 | - Guest Speaker Name 17 | - [ ] Find/Replace `[Replace NAME OF GUEST SPEAKER]` with the first name and last name initial. If there is more than one guest speaker representing a specific organization, use the name of the organization (e.g., "Maze") 18 | - Date of Talk 19 | - [ ] Find/Replace `[Replace MONTH DAY OF TALK]` with the month and day of the presentation (ex: "May 07") 20 | - Update the issue title 21 | - [ ] Copy the text below 22 | ``` 23 | Guest Speaker [Replace YEAR]: Create Consent Docs for [Replace NAME OF GUEST SPEAKER] 24 | ``` 25 | - [ ] Choose "Edit" in the title section 26 | - [ ] Paste the text you copied into the issue title 27 | - [ ] Choose "Save" 28 | - Customize the issue settings (located in right sidebar) 29 | - [ ] Under Assignees, assign a team member if it has been determined. Otherwise, leave it blank. 30 | - [ ] Under Labels, choose the gear icon and apply the label `feature: guest speaker` 31 | - [ ] Under Labels, choose the gear icon and apply the label `feature: board / google drive / tools` 32 | - [ ] Under Labels, choose the gear icon and apply the label `complexity: good first issue` 33 | - [ ] Under Projects, choose the gear icon and choose `CoP Management` 34 | - Evaluate Dependencies 35 | - [ ] Read the dependencies listed in this issue. 36 | - [ ] Delete the dependencies section if both items have already been completed. If they have not, do the following: 37 | - Leave dependencies section with at least one check box unchecked 38 | - Under Labels (in the issue settings), choose the gear icon and apply the label `dependency` 39 | - Ask the CoP co-lead to put this issue in the Ice Box on the project board 40 | - Remove this section 41 | - [ ] After all the checkboxes above are complete and the issue is read to be worked on, delete all text below the "Instructions for Creating this Issue" (top heading) and above "Overview" (heading below) -- i.e., the issue assignee will never see this part. 42 | 43 | ### Overview 44 | We need to create consent documents for guest speaker [Replace NAME OF GUEST SPEAKER] so that we can keep track of what information is approved to be shared by the guest speaker. 45 | 46 | During these tasks you will be asked to add links to the Resources/Instructions section, and that section is at the bottom of this issue (go view it now). 47 | 48 | ### Dependency 49 | - [ ] The guest speaker has been contacted informally by one of the UI/UX CoP co-leads. 50 | - [ ] The guest speaker has agreed to be a guest speaker for the UI/UX CoP on a specific date. 51 | - [ ] Guest Speaker Question Tracker #355 52 | 53 | ### Action Items 54 | #### Customize Resource Links 55 | - Customize Resource for the [Replace YEAR] Speaker Google Drive Folder 56 | - [ ] Go to the main Google Drive Folder for the UI/UX Speakers (Resources # 1.01) 57 | - [ ] Choose the folder for [Replace YEAR]. If one does not exist yet, follow the steps below. Strikethrough or delete the steps below if there is already a folder. 58 | - [ ] Copy the text below. 59 | ``` 60 | [Replace YEAR]: Guest Speakers 61 | ``` 62 | - [ ] Create a new folder (right click and select "New folder" or click "+ New" button). 63 | - [ ] Paste in the copied text and click "Create" 64 | - [ ] Right-click on the [Replace YEAR]: Guest Speakers folder. 65 | - [ ] Choose "Copy link". 66 | - [ ] Update Resource # 2.01 with the link you just copied. Paste it inside parentheses at the end of the line. 67 | - [ ] Choose "Update comment" in GitHub and make sure all the checkboxes above have been checked. 68 | - Customize Resource for This Speaker's Google Drive Folder 69 | - [ ] Open the folder of Resource # 2.01. 70 | - [ ] Copy the text below. 71 | ``` 72 | [Replace NAME OF GUEST SPEAKER] ([Replace MONTH DAY OF TALK]) 73 | ``` 74 | - [ ] Create a new folder (right click and select "New folder" or click the "+ New" button). 75 | - [ ] Paste in the copied text and click "Create" 76 | - [ ] Right-click on the folder that you just created. 77 | - [ ] Choose "Get Link" and "Done" 78 | - [ ] Update Resource # 2.02 with the link you just copied. Paste it inside parentheses at the end of the line. 79 | - [ ] Choose "Update comment" in GitHub and make sure all the checkboxes above have been checked. 80 | - Customize Resource for this Speaker's Informed Consent Google Form 81 | - [ ] Open the Informed Consent Form in Resources # 1.02. 82 | - [ ] Choose the 3 vertical dots at the top of the Google Form on the left of your profile. 83 | - [ ] Choose "Make a copy" 84 | - [ ] Copy the text below 85 | ``` 86 | [Replace YEAR]: [Replace NAME OF GUEST SPEAKER]: Presentation Recording Consent Form 87 | ``` 88 | - [ ] Paste the text you copied into the "Name" field to rename the form 89 | - [ ] In the "Folder" field, choose "SpeakerConsentForm", then choose the back arrow to "UI/UX Community of Practice" 90 | - [ ] Choose "Speakers" > folder for [Replace YEAR]: Guest Speakers > folder for [Replace NAME OF GUEST SPEAKER] 91 | - [ ] Choose "Select" 92 | - [ ] Choose "Make a copy" 93 | - [ ] Update Resource # 2.03 link by completing the following steps 94 | - [ ] Choose "Send" in the `[Replace YEAR]: [Replace NAME OF GUEST SPEAKER]: Presentation Recording Consent Form` you just created. 95 | - [ ] Choose the link icon 96 | - [ ] Check the box for "Shorten URL" 97 | - [ ] Choose "Copy" 98 | - [ ] Update Resource # 2.03 with the link you just copied. Place it into parentheses at the end of the line. 99 | - [ ] Choose "Update comment" in GitHub and make sure all the checkboxes above have been checked. 100 | - Customize Resource for this Speaker's Informed Consent Email 101 | - [ ] Open the Speaker Consent Email Template in Resources # 1.03. 102 | - [ ] Click "File" and select "Make a Copy" 103 | - [ ] Copy the text below. 104 | ``` 105 | [Replace YEAR]: [Replace NAME OF GUEST SPEAKER]: Speaker Consent Email 106 | ``` 107 | - [ ] Paste the text you copied into the "Name" field to rename the doc. 108 | - [ ] In the "folder" field, choose "SpeakerConsentForm", then choose the back arrow to "UI/UX Community of Practice" 109 | - [ ] Choose "Speakers" > folder for [Replace YEAR]: Guest Speakers > folder for [Replace NAME OF GUEST SPEAKER] 110 | - [ ] Choose "Select" 111 | - [ ] Choose "Make a copy" 112 | - [ ] Replace the highlighted text (including brackets) with the appropriate information 113 | - [ ] First name of guest speaker 114 | - [ ] Month and day of presentation 115 | - [ ] Link to Google Form (Resource # 2.03) 116 | - [ ] Copy the link for Resource # 2.03 117 | - [ ] Delete the text `[ADD LINK]` 118 | - [ ] Highlight to select the text `link` 119 | - [ ] Right-click and select "Insert link" 120 | - [ ] Paste link for Google Form 121 | - [ ] Click "Apply" 122 | - [ ] Select all text 123 | - [ ] Click the "Highlight color" icon 124 | - [ ] Select "None" 125 | - [ ] Click "File", select "Share", and select "Share with Others" 126 | - [ ] Click "Copy link" and "Done" 127 | - [ ] Update Resource # 2.04 with the link you just copied. Place it into parentheses at the end of the line. 128 | 129 | #### Send Consent Documents 130 | - [ ] Assign CoP co-lead to issue 131 | - [ ] Unassign yourself (if not a CoP co-lead) 132 | - [ ] CoP co-lead reviews the Resources gathered during the completion of this issue. 133 | - [ ] CoP co-lead gives Guest Speaker 'edit' access to Google Consent Form 134 | - [ ] Open the Informed Consent Form in Resources # 2.03. 135 | - [ ] Click the 3 vertical dots at the top of the Google Form 136 | - [ ] Choose "Share" 137 | - [ ] Add Guest Speaker email address in the search bar and press enter 138 | - [ ] Give Guest Speaker's email address "Editor" access from drop-down menu 139 | - [ ] Uncheck "Notify People" 140 | - [ ] Click "Send" 141 | - [ ] CoP co-lead logs into uiux HfLA Gmail account 142 | - [ ] CoP co-lead copies and pastes email text from Resource # 2.04 143 | - [ ] CoP co-lead sends email to guest speaker at least one week before presentation 144 | - [ ] CoP co-lead moves Consent Form & Consent Email from public [UI/UX Community of Practice](https://drive.google.com/drive/folders/1QsvLA40-HbDc7VnKvIxHlowcef0R-EzY?usp=share_link) google drive folder to secure [UI/UX CoP - PII](https://drive.google.com/drive/folders/1uH8gK3r_RPd5kjfaQ8j8ggGw9mawZ9IV?usp=share_link) google drive folder 145 | 146 | ### Resources/Instructions 147 | #### Resources for creating this issue 148 | - 1.01 [Google Drive Folder: Speakers](https://drive.google.com/drive/folders/1QsvLA40-HbDc7VnKvIxHlowcef0R-EzY?usp=drive_link) 149 | - 1.02 [Google Form: Consent for Presentation Recording](https://docs.google.com/forms/d/1Zd0l9ppkhYOHNFplvezI5JEF5Hq1AAvVRGGBzD7x3ec/edit) 150 | - 1.03 [Google Doc: Speaker Consent Email Template](https://docs.google.com/document/d/12kHYsC32q-nywq1B0HaXmHomYN9CYtx5LOBIarAWYR0/edit?usp=drive_link) 151 | 152 | #### Resources gathered during the completion of this issue 153 | - 2.01 [Google Drive Folder: [Replace YEAR]: Guest Speakers] 154 | - 2.02 [Google Drive Folder: [Replace NAME OF GUEST SPEAKER] [Replace MONTH DAY OF TALK]] 155 | - 2.03 [Google Form: [Replace YEAR]: [Replace NAME OF GUEST SPEAKER]: Presentation Recording Consent Form] 156 | - 2.04 [Google Doc: [Replace YEAR]: [Replace NAME OF GUEST SPEAKER] Consent Email] 157 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/guest_speaker_questions.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Guest Speaker Questions 3 | about: Create issue to collect questions for guest speakers ahead of time 4 | title: 'Generate Questions for [YYYY-MM-DD]: [NAME/COMPANY]' 5 | labels: 'role: CoP Lead - content, question, UI/UX CoP Leads' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to create a list of questions for our guest speaker [PERSON - ROLE, COMPANY] attending on [DATE]. 12 | 13 | ### Action Items 14 | - [ ] Send issue to UI/UX Slack channel and ask UI/UX people to write their questions in the comments. 15 | - [ ] Collate the questions into a list of unique questions (non-duplicated questions). 16 | - [ ] Send collated questions to the guest speakers within 2 weeks of their talk. 17 | - [ ] Send [consent form](https://github.com/hackforla/UI-UX/issues/new?assignees=&labels=role%3A+CoP+Lead+-+content%2C+size%3A+0.5pt&projects=&template=guest-speaker-consent.md&title=Guest+Speaker+%5BReplace+YEAR%5D%3A+Create+Consent+Docs+for+%5BReplace+NAME+OF+GUEST+SPEAKER%5D) to the guest speakers within 2 weeks of their talk. 18 | 19 | ### Resources/Instructions 20 |
21 | Meetup/Slack Announcement (edit this) 22 | 23 | :mega: Mark your Calendars! **[INSERT SPEAKER NAME][INSERT ROLE at COMPANY]** will be visiting the **UI/UX Community of Practice on [DATE] from [TIME]!** 24 | 25 | :speech_balloon: **Topic:** [INSERT TITLE OF TALK] 26 | 27 | :question: Please post your **questions** for [INSERT SPEAKER NAME] **here** [INSERT LINK TO GITHUB ISSUE] :arrow_backward: 28 | 29 | :bust_in_silhouette: **About:** [INSERT SPEAKER BIO] 30 | 31 | :wave: [INSERT SPEAKER NAME]'s LinkedIn [INSERT LINK] 32 | 33 | Thank you! 34 | [UI/UX CoP Co-Leads](https://github.com/hackforla/UI-UX/wiki/CoP-Leads) | [UI/UX Community of Practice](https://github.com/hackforla/UI-UX/wiki) 35 | 36 | 37 |
38 | 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/start-a-new-make-a-guide-issue.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Start a new Make a Guide Issue 3 | about: Use this template if you want to make a guide for a UX/UI item 4 | title: 'Create a Guide/Template: [name of item]' 5 | labels: 'documentation, Guide: Gather Examples' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to create a guide for [name of item] so that [purpose of the item] 12 | 13 | ### Action Items 14 | - [ ] Gather examples of how other Hack for LA projects or volunteers have done this (if applicable), adding each example as a link in the resources section below. It is really important to annotate as you go in this issue, so that if you have to stop working on the issue, its already up to date with your findings. 15 | - [ ] If the guidance you received from the teams that have done this practice was not sufficient, remove the "Guide: Gather Examples" label and add the "Guide: Research" label 16 | - [ ] Research existing information about [name of item] in [relevant resources, articles, etc.] 17 | - [ ] Once done, evaluate if the guide requires a template. If it does then 18 | - [ ] if yes, remove the "Guide: Research" label and add the "Guide: Draft Template" label 19 | - [ ] Create a draft template 20 | - [ ] Once done, remove the "Guide: Draft Template" label and add the "Guide: Draft Guide" label 21 | - [ ] if no, remove the "Guide: Research" label and add the "Guide: Draft Guide" label 22 | Create a draft guide, either in markdown format in this issue or a google doc in the [ux/ui google drive](https://drive.google.com/drive/u/1/folders/1os-4KyGnL0SXIeyfoDICOEpG5CO_1MaV) 23 | - [ ] Once done, remove the "Guide: Draft Guide" label and add the "Guide: Needs Peer Review" label 24 | - [ ] Review the guide with UX/UI community of practice 25 | - [ ] Once done, remove the "Guide: Needs Peer Review" label and add the "Guide: Leadership Review" label 26 | - [ ] Present to the Hack for LA leadership team for sign off 27 | - [ ] Once approved, remove the "Guide: Leadership Review" label and add the "Guide: ready publication" label 28 | 29 | ### Resources 30 | Update issue #15 with the name of item you are working on 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/template-for-UX-Experience-Profile.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: UX Experience Profile 3 | about: UI/UX Community of Practice members keep track of their experience at HfLA 4 | title: 'UI/UX Experience Profile: YOUR NAME' 5 | labels: 'experience profile, good first issue' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Fill in the following fields as you work on these items at Hack for LA. 12 | 13 | ### Onboarding Action Items 14 | - [ ] Join UI/UX Github (Should happen during onboarding) 15 | - [ ] Confirm that you have been added to Github and make membership public by looking yourself up in our [People Directory](https://github.com/orgs/hackforla/people) 16 | - [ ] Get added to Google Drive (Should happen during onboarding) 17 | - [ ] Confirm your access by [UI/UX CoP Google Drive Link](https://drive.google.com/drive/folders/1Bw4qy9rQtJ16ccYsRUIg5BlxBxlqnEIQ?usp=sharing) 18 | - [ ] Set up [2FA](https://www.hackforla.org/guide-pages/2FA.html) on Github (Should happen during onboarding) 19 | - [ ] Confirm 2FA Status by clicking here to go to [your GitHub account>settings>account security](https://github.com/settings/security) and look for the disabled *Enable* button 20 | - [ ] Read the guide [What is a Kanban Board by Atlassian](https://www.atlassian.com/agile/kanban/boards) 21 | - [ ] All Hack for LA teams use Figma for our collaborative design. New to Figma? Learn more: [Figma for Beginners videos 1-4](https://www.youtube.com/watch?v=dXQ7IHkTiMM&ab_channel=Figma) 22 | - [ ] All Hack for LA teams generally work in an Agile framework. Read more about Agile and how it relates to Kanban [HERE](https://www.atlassian.com/agile). 23 | - [ ] Check out the [open Design roles](https://github.com/orgs/hackforla/projects/67/views/4), [open Research roles](https://github.com/orgs/hackforla/projects/67/views/8), [open Content roles](https://github.com/orgs/hackforla/projects/67/views/9) we have available. 24 | - [ ] Additional viewing for designers, Jennie Yip, [Reimagining Atlassian Design System](https://www.youtube.com/watch?v=_pfyLVXTVSQ) 25 | 26 | ### UI/UX Community of Practice (UI/UX CoP) Action Items 27 | - [ ] Join our weekly UI/UX Community of Practice meetings (Wednesday, 6PM PT) - use this [Zoom Registration Link](https://us06web.zoom.us/meeting/register/tZ0ofu6rpjsoHdKRfGoRGKwcm44z7MqfMZX5) to join our weekly meetings. 28 | - [ ] You Email address should have an associated Zoom account in order to register 29 | - [ ] Add this Zoom weekly meeting to your preferred Calendar 30 | - [ ] Our upcoming meeting and [schedule can be found here](https://github.com/hackforla/UI-UX/wiki#upcoming-meetings-) 31 | - [ ] Join this [UI/UX Slack channel](https://hackforla.slack.com/archives/C017ESHSMNG) for all communication/announcements. Introduce yourself on our UI/UX Slack channel 32 | - [ ] Take a peek at our [UI/UX CoP Wiki](https://github.com/hackforla/UI-UX/wiki) - for UI/UX specific resources! 33 | - [ ] [Guides](https://github.com/orgs/hackforla/projects/58/views/4) are currently being upgraded. This step can be skipped 34 | 35 | ### Project Experience Action Items 36 | 37 | #### Design 38 | 39 | - [ ] Wireframes - low fidelity 40 | - [ ] Mockups - high fidelity 41 | - [ ] Paper Prototyping 42 | - [ ] Sketching 43 |
44 | 45 | - [ ] Figma prototyping 46 | - [ ] Figma components 47 | - [ ] Figma auto-layout 48 | - [ ] HTML/CSS 49 |
50 | 51 | - [ ] Design evaluation 52 | - [ ] Design System 53 | - [ ] Group design ideation 54 | - [ ] Responsive design 55 | - [ ] Logo design 56 | - [ ] Icons, vector graphics, and photos 57 | 58 | #### Research 59 | - [ ] Interview 60 | - [ ] Observation 61 | - [ ] Diary studies 62 | - [ ] Survey 63 | - [ ] Affinity mapping 64 | - [ ] Empathy mapping 65 |
66 | 67 | - [ ] Usability test 68 | - [ ] A/B or multivariate testing 69 | - [ ] Competitive analysis 70 | - [ ] Secondary research 71 | - [ ] Web analytics 72 | - [ ] Task analysis 73 | - [ ] Card sorting 74 | - [ ] Tree testing 75 |
76 | 77 | - [ ] User persona 78 | - [ ] Journey mapping 79 | - [ ] Participant recruiting/screening 80 | - [ ] Cognitive walkthrough 81 | - [ ] Expert review 82 | - [ ] Heuristic evaluation 83 | - [ ] Research presentation 84 | 85 | 86 | #### Content 87 | - [ ] UX Content Writing 88 | - [ ] Content testing 89 | - [ ] Data-driven Content Analysis 90 | - [ ] Content Auditing 91 | - [ ] Content guidelines - style, tone, style, tone, voice, grammar 92 |
93 | 94 | - [ ] Branding and messaging 95 | - [ ] Search engine optimization 96 | - [ ] Content Strategy Development 97 | - [ ] Content Modeling 98 | - [ ] Visual communication design 99 | - [ ] Copywriting (promotional or informational writing) 100 | - [ ] Technical Writing (support docs, training content) 101 | 102 | #### Design, Research, Content 103 | - [ ] Inclusivity and Accessibility standards 104 | - [ ] Information Architecture 105 | 106 | 107 | ### GitHub Practice Action Items 108 | - [ ] Assign yourself to this issue. In the right side menu, click 'Assignees.' [Select 'assign yourself'](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users) 109 | - [ ] Assign this issue to the [CoP: UI/UX: Project Board](https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project). In the right side menu, click 'Projects.' Select project 'CoP: UI/UX: Project Board' from the drop-down menu. Under 'Status' select 'In Progress (actively working) from the drop-down menu. 110 | - [ ] This was a good first issue. Once you have completed the steps and checked all relevant boxes, you can [close this issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue) 111 | 112 | ### Conclusion Action Items 113 | - [ ] Use this as your own personal skills' resume! Link this UX Experience Profile when you contact Project Leads to discuss [UI/UX open roles](https://github.com/orgs/hackforla/projects/67/views/1) 114 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/template-for-making-guides.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Template for Making Guides 3 | about: Use this template if you want to make a guide for a UX/UI item 4 | title: 'Create a Guide/Template: [name of item]' 5 | labels: 'documentation, Guide: Research' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to create a guide for [name of item] so that [purpose of the item] 12 | 13 | ### Action Items 14 | - [ ] Gather examples of how other Hack for LA projects or volunteers have done this (if applicable), adding each example as a link in the resources section below 15 | - [ ] Once done, remove the "Guide: Gather Examples" label and add the "Guide: Research" label 16 | - [ ] Research existing information about [name of item] in [relevant resources, articles, etc.] 17 | - [ ] Once done, remove the "Guide: Research" label and add the "Guide: Draft Guide" label 18 | - [ ] Create a draft guide, either in markdown format in this issue or a google doc in the [ux/ui google drive](https://drive.google.com/drive/u/1/folders/1os-4KyGnL0SXIeyfoDICOEpG5CO_1MaV) 19 | - [ ] Once done, remove the "Guide: Draft Guide" label and add the "Guide: Needs Peer Review" label 20 | - [ ] Review the guide with UX/UI community of practice 21 | - [ ] Once done, remove the "Guide: Needs Peer Review" label and add the "Guide: Leadership Review" label 22 | - [ ] Present to the Hack for LA leadership team for sign off 23 | - [ ] Once approved, remove the "Guide: Leadership Review" label and add the "Guide: ready publication" label 24 | 25 | ### Resources 26 | Update issue #15 with the name of item you are working on 27 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/template-for-pilot-testing.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Template for design/conducting a pilot 3 | about: Use this template if you want to pilot a UX/UI Guide 4 | title: 'Conduct a Pilot: [name]' 5 | labels: 'documentation, Pilot: Locate Guide' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to pilot the guide for [name of item] so that [purpose of the item] 12 | 13 | ### Action Items 14 | - [ ] Locate the guide and related documents in resources. Link the Guide to this issue. 15 | - [ ] Once done, remove the "Pilot: Locate Guide" label and add the "Pilot: Learn Guide" label 16 | - [ ] Read the guide and follow the guide's instruction step-by-step. Note down any comments, confusions, blockers you have during the process 17 | - [ ] Once done, remove the "Pilot: Learn Guide" label and add the "Pilot: Draft Feedback" label 18 | - [ ] Organize all the notes and synthesize them in actionable feedbacks to the guide. 19 | - [ ] Once done, remove the "Pilot: Drafting Feedback" label and add the "Pilot: Review Feedback" label 20 | - [ ] Review the feedbacks with UX/UI community of practice, and make suggested update 21 | - [ ] Once done, remove the "Pilot: Review Feedback" label and add the "Pilot: Followup Action" label 22 | - [ ] Followup on the actions taken based on your feedback 23 | 24 | ### Resources 25 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ui-ux_cop_workshops.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: UI/UX CoP Workshops 3 | about: Create issue to conduct workshops at the UI/UX Community of Practice 4 | title: 'UI/UX CoP: [YYYY-MM-DD]: [WORKSHOP NAME]' 5 | labels: 'role: CoP Lead - content, size: 1pt, feature: workshop, UI/UX CoP Leads' 6 | assignees: '' 7 | --- 8 | ## 👀 Overview 9 | ### Workshop Name 10 | 11 | 12 | ### Workshop Description 13 | 14 | 15 | ### Date and Time 16 | 17 | 18 | ### Target Audience 19 | 20 | 21 | ## 💻 Pre-Workshop Preparation 22 | ### Action Items 23 | 24 | 25 | ### Instructions 26 | 27 | 28 | ### Resources 29 | 30 | 31 | ### Agenda 32 | 33 | 34 | ### Facilitator(s) 35 | 36 | 37 | ## 💬 Communication 38 | ### Pre-Workshop Message 39 | 40 | 41 | 42 | 43 | ### Reminder Message (1 day before) 44 | 45 | 46 | 47 | 48 | ## 🔄 Post-Workshop Updates 49 | ### Feedback Summary 50 | 51 | 52 | ### Next Steps 53 | 54 | 55 | ## 📝 Notes 56 | 57 | 58 | 59 | 60 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-content-for-readme-file.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Content for ReadMe file 3 | about: Instructions for revising the README.md file inside this repository 4 | title: '' 5 | labels: documentation, good first issue, help wanted, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to have a working READme file to easily on-board new team members. 12 | 13 | ### Action Items 14 | - [ ] Add the following information as a comment to this issue: 15 | - [ ] Identify what information needs to be collected. 16 | - [ ] Identify who holds each piece of information. 17 | - [ ] Collect information. 18 | 19 | ### Resources/Instructions 20 | PUT LINK TO README.md FILE HERE 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-team-roster.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Team Roster 3 | about: Provides new team members a link to team roster to input their information 4 | title: '' 5 | labels: documentation, good first issue, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Rolling Roster of Team Participants. 12 | 13 | ### Action Items 14 | Add or update your personal info to the team roster. 15 | 16 | ### Resources/Instructions 17 | ADD URL TO TEAM ROSTER HERE 18 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Header for Forms-2](https://github.com/hackforla/UI-UX/assets/86335455/ad981b67-e6bf-4037-8638-e5b8e3182330) 2 | 3 | 4 | # Welcome to the UI/UX Community of Practice! 5 | 6 | We are excited to have you here. Our community is dedicated to fostering collaboration, learning, and growth in the field of UI/UX design. Please follow the steps below to get started and integrate smoothly into our community. 7 | 8 | ## :calendar: Meeting Schedule 9 | ### When We Meet 10 | - Wednesdays at 6:00PM Pacific Time (except for the first week of every month, and holidays) 11 | 12 | ### Upcoming Meetings 13 | 14 | ### June 2025 15 | - June 04 - Planning Week (no UI/UX CoP Meeting) 16 | - June 11 - No UI/UX CoP Meeting 17 | - June 18 - No UI/UX CoP Meeting 18 | - June 25 - Career Development: Job Boards!📝📈 19 | 20 | ### July 2025 21 | - Hack for LA taking a summer break in July! See you in August 🙌🌞🍹🏖️ 22 | - Join our [Hack for LA Member Summer Potluck Picnic!](https://www.meetup.com/hackforla/events/302274209/?utm_medium=referral&utm_campaign=share-btn_savedevents_share_modal&utm_source=link) 23 | 24 | 25 | ## :white_check_mark: Getting Started 26 | ### Step 1. Complete General Onboarding 27 | If you haven't attended Hack for LA onboarding, please read the [Guide for New Volunteers](https://www.hackforla.org/getting-started), and register for an upcoming session before joining the community of practice. 28 | 29 | ### Step 2. Join Communication Channels 30 | After you've finished your Hack for LA general onboarding join other UI/UX peeps in your community of practice. 31 | 1. Join the [ui-ux Slack channel](https://hackforla.slack.com/archives/C017ESHSMNG) 32 | 2. Introduce yourself. You can use the template below: 33 | ``` 34 | Hi My name is _____ and I am looking forward to joining the UI/UX community of practice. 35 | ``` 36 | 37 | ### Step 3. Familiarize Yourself with our Processes and Tools 38 | At Hack For LA and the UI/UX CoP we use specific tools and processes to contribute and keep track of progress. You don't need to be an expert in any of these to join but it helps to familiarize yourself with them before getting started. 39 | 1. Github 40 | - [Get Started Documentation](https://docs.github.com/en/get-started) 41 | 2. Kanban Board 42 | - [What is Kanban?](https://www.atlassian.com/agile/kanban) 43 | - [What is a Kanban board and how to use it](https://www.atlassian.com/agile/kanban) 44 | 3. Agile Framework 45 | - [What is Agile?](https://www.atlassian.com/agile). 46 | 4. Figma 47 | - [Figma for Beginners Youtube videos](https://www.youtube.com/watch?v=dXQ7IHkTiMM&ab_channel=Figma) 48 | 49 | ### Step 4. Join the CoP Meetings   50 | 1. Join our weekly UI/UX Community of Practice meeting Wednesday at 6PM PT via Zoom. Onboard to know more! [Onboarding schedule here](https://www.meetup.com/hackforla/) 51 | 2. Participate in discussions and activities during meetings. 52 | 53 | ### Step 5. Engage and Contribute 54 | 1. Review the current Open Roles and start contributing to projects or the CoP 55 | - [Design](https://github.com/orgs/hackforla/projects/67/views/4) 56 | - [Research](https://github.com/orgs/hackforla/projects/67/views/8) 57 | - [Content](https://github.com/orgs/hackforla/projects/67/views/9) 58 | 2. Get started on a [Guide](https://github.com/orgs/hackforla/projects/58/views/4) 59 | 3. Create your own [UX Experience Profile](https://github.com/hackforla/UI-UX/projects/5) to keep track of your progress. 60 | 61 | ## :books: Additional Resources 62 | The UI/UX Community of Practice is one of many. [See all of our Communities of Practice](https://github.com/hackforla/communities-of-practice/blob/main/README.md) 63 | 64 | ## :handshake: Support and Assistance 65 | We will be implementing a support ticketing system soon. In the meantime, if you have any questions or need help, please reach out in the [ui-ux Slack Channel](https://hackforla.slack.com/archives/C017ESHSMNG) or join us during our CoP meeting on Zoom. Onboard to know more! [Onboarding schedule here](https://www.meetup.com/hackforla/) 66 | 67 | 68 | ![Header for Forms-2](https://github.com/user-attachments/assets/c7913dae-7be0-4de6-9392-39f71d3143c3) 69 | --------------------------------------------------------------------------------