Feature test squash merge

.github/ISSUE_TEMPLATE/alt-text-audit---design.md

@@ -2,7 +2,8 @@
 name: Alt Text Audit - Design
 about: WCAG Audit
 title: Review alt text for WCAG compliance on [insert page name here] page
-labels: 'Feature: Accessibility, role: design, Size: Small'
+labels: 'Feature: Accessibility, Feature: Onboarding/Contributing.md, prework, Ready
+  for Milestone, role: design, Size: Small, size: 1pt'
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/credits-file-template--edit-content-field-and-remove-type-field.md

@@ -31,11 +31,13 @@ For the file `_data/internal/credits/[INSERT FILE NAME HERE].yml`, do the follow
   ```
   content-type: image
   ```
-
 - [ ] Remove line [ADD LINE NUMBER WHICH HAS TYPE] for the type field
   ```
   type: [INSERT THE CURRENT TEXT ON THE FILE HERE]
   ```
+- [ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #2775 by
+  - [ ] Checking off the dependency for this issue
+  - [ ] If all dependencies are checked off, please move issue #2775 to the New Issue Approval column and remove the Dependency label
 
 ### Resources/Instructions
 - This issue is tracked in the epic #2775.

.github/ISSUE_TEMPLATE/pre-work-template---design.md

@@ -23,7 +23,7 @@ As a new designer on the HfLA website UX team, fill in the following fields as y
 - [ ] Add this issue to Projects: Project Board (gear in right side panel)
 - [ ] Confirm that team lead has given you login credentials for the team Miro and Figma accounts
 - [ ] Attend weekly team meetings: 
-   - [ ] UX weekly team meeting, Thursdays 5pm PST
+   - [ ] UX weekly team meeting, Wednesday 2:30 pm PST
    - [ ] All team meeting (UX, Development, Product), Sunday 10am PST
 - [ ] Review [Design_Short Term Goals, Plan, and Tasks](https://docs.google.com/document/d/1FxwgdnWBbbQ8Pi3tspnukZTWwXtqnRXfNkNhVMEloY0/edit)
 - [ ] Review the [Start Here](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8561%3A72465) and [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) pages in Figma

.github/ISSUE_TEMPLATE/pre-work-template--dev.md

@@ -16,9 +16,10 @@ As a new developer on the HfLA website team, fill in the following fields as you
 
 ### Action Items
 - [ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
-- [ ] Share your Gmail address and GitHub handle with the team lead so you can be added to the Google Drive and the website-write team
-- [ ] (Once added to the Drive) Add yourself to the [team roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0) 
-- [ ] Confirm with the team lead that they have added you to the zoom meeting calendar invites and GitHub repository
+- [ ] Share your Gmail address with the team lead so you can be added to the Google Drive
+- [ ] Also, confirm with the team lead that they have added you to the Zoom meeting calendar invites
+- [ ] (Once added to the Drive) Add yourself to the [team roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0)
+- [ ] After you have finished adding yourself to the roster, let a team lead know you have added yourself to the roster and would like to be added to the `website-write` and `website` teams on GitHub
 - [ ] Once added to the website-write team:
   - [ ] Self Assign this issue (gear in right side panel)
   - [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label
@@ -32,8 +33,8 @@ As a new developer on the HfLA website team, fill in the following fields as you
 - [ ] Complete steps 1.1 - 1.6 in [Part 1: Setting up the development environment within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-1-setting-up-the-development-environment)
   - [ ] OPTIONAL: If you run into any issues, use [4.1 How do I ask for help within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#41-what-do-i-do-if-i-need-help) as a visual example to get a hold of our [HfLA website leadership team](https://github.com/hackforla/website/projects/7#card-69730135). That way we can help you resolve any set up issues immediately.
 - [ ] Read section 2.1 - 2.4 in [Part 2: How the Website team works with GitHub issues within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-2-how-the-website-team-works-with-github-issues)
+  - [ ] Follow the steps in section [2.3 Where can I find GitHub issues to work on?](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#23-where-can-i-find-github-issues-to-work-on) to assign yourself your first issue under the Project Board's Prioritized Backlog column and use [2.7 Working on a Issue within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#27-working-on-an-issue) to start working on your issue
   - [ ] Read [2.6 What to do when you need to stop mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue)
-  - [ ] Use the information from part 2 to assign yourself your first issue under the Project Board's Prioritized Backlog column and use [2.7 Working on a Issue within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#27-working-on-an-issue) to start working on your issue
 - [ ] Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
    - [ ] Estimate: Copy the below and put it in the "good first issue" that you picked.
  Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment.
@@ -59,16 +60,19 @@ As a new developer on the HfLA website team, fill in the following fields as you
    - [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
 - [ ] Read and understand how we progress through issues. Then, you can check this off.
 Progress through issues with increasing complexity in the following order:
-  - Good first issue
-  - Good second issue
-  - Small 
-  - Medium 
-  - Large
+  - Good first issue (one per person)
+  - Good second issue (one per person)
+  - Small (one per person, with some exceptions, see below)
+  - Medium (you can work on more than one medium issue, but only one at a time)
+  - Large (you can work on more than one large issue, but only one at a time)
     - The reasons for this progression are:
       - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
       - We are trying to teach you the team methodology through the issues themselves.
       - It ensures you understand what we expect and the quality of contributions.
-- [ ] Go familiarize yourself with the [Hack for LA Design System page in Figma](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)  (where you can see components and their classes)
+    - You can work on back-to-back small issues if it meets the following criteria:
+      - You are learning something new and need to work on an issue of a lesser complexity
+      - Special request by a lead or pm
+- [ ] Go familiarize yourself with the [Hack for LA Design System page in Figma](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)  (where you can see components and their SCSS classes)
 - [ ] Once all tasks are completed, close this issue.  This issue will remain open until you get through your first progress report.  Once you have done that, we are confident you know how to keep the momentum going on your issue and keep your team informed.
 
 ### What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

.github/ISSUE_TEMPLATE/project-profile-card-review-and-update.md

@@ -17,7 +17,7 @@ _insert url of their card here before sending - their cards can be found in this
 ### Action Items
 
 - [ ] [INSERT TEAM NAME HERE] Team Leadership
-   - [ ] Please check off everything that is ok the way that it is, and if not, please provide the updated information in the comments below:
+   - [ ] Please check off everything that is ok the way that it is, and if not, please provide the updated information in a new comment below:
       - [ ] title
       - [ ] description
       - [ ] image
@@ -36,7 +36,7 @@ _insert url of their card here before sending - their cards can be found in this
       - [ ] partner
       - [ ] tools
       - [ ] status
- - [ ] Open an issue on VRMS to update the meeting times and provide the link to the new issue in the comment below
+ - [ ] If you need updates to your meeting times, open an issue on VRMS to update the meeting times and provide the link to the new issue in a new comment below
 
 ### Resources
 [VRMS Add/edit team meeting time template issue](https://github.com/hackforla/VRMS/issues/new?assignees=&labels=1+week+change+request&template=add-edit-team-meeting-time.md&title=Meeting+time+change+request+for+%5BProject+Name%5D)

.github/ISSUE_TEMPLATE/wiki--research-plan-review----replace-with-name-of-page-.md

@@ -0,0 +1,63 @@
+---
+name: 'Wiki: Research Plan Review:  [REPLACE WITH NAME OF PAGE]'
+about: Research Plan Review
+title: 'Wiki: Research Plan Review:  [REPLACE WITH NAME OF PAGE]'
+labels: 'Feature: Wiki, role: user research, size: 0.5pt'
+assignees: sacamp
+
+---
+
+### Overview
+We need to make all the research pages in the wiki uniform so that we can determine what is missing and what next steps are
+
+### Action Items
+- [ ] Review [REPLACE WITH NAME OF PAGE] of the wiki to make sure it has the correct format
+- [ ] Add any titles that are missing
+- [ ] Move content into the correct categories
+- [ ] Order the items the same way that they exist in the format template below
+- [ ] Take Inventory of Assets
+   - [ ] Name of Research
+   - [ ] Research Date: 
+   - [ ] Current Status
+   - [ ] Outstanding task items
+   - [ ] Research Plan (including Audience Identification documentation)
+   - [ ] Scripts
+   - [ ] Interview recordings & Transcripts
+   - [ ] Synthesis (Miro or Figjam)
+   - [ ] Presentation of Findings	
+   - [ ] Action Items Spreadsheet
+- [ ] Check to see if there are more assets or assets (in the folder) from related research that are needed on this page, and add them
+- [ ] Evaluate all the research assets and summarize the status of the research under  "Current Status"
+- [ ] List out next steps under "Outstanding Task Items"
+
+
+### Resources/Instructions
+[Research Wiki page](https://github.com/hackforla/website/wiki/UI-UX-Researcher)
+[Direct link to page]
+[Spreadsheet](https://docs.google.com/spreadsheets/d/1ZdUOlFx0DrM6jUfjcIwGw42Fpgba_pQVlaKPL-DBy38/edit#gid=0)
+[Folder for the research]
+
+#### Format for wiki page
+```
+# [Name of Research]
+
+## Research Date: 
+
+## Current Status
+
+## Outstanding task items
+
+## Assets
+
+### Research Plan (including Audience Identification documentation)
+
+### Scripts
+
+### Interview recordings & Transcripts
+
+### Synthesis (Miro or Figjam)
+
+### Presentation of Findings	
+
+### Action Items Spreadsheet
+```

.github/workflows/pr-instructions.yml

@@ -5,6 +5,7 @@ on:
     branches:
       - 'gh-pages'
       - 'feature-homepage-launch'
+      - 'feature-tech-dropdown'
 
 jobs:
   Add-Pull-Request-Instructions:

.github/workflows/pull-request-trigger.yml

@@ -5,6 +5,7 @@ on:
     branches:
       - 'gh-pages'
       - 'feature-homepage-launch'
+      - 'feature-tech-dropdown'
 
 jobs:
   Hello-World:

.github/workflows/set-pr-labels.yaml

@@ -6,6 +6,7 @@ on:
     branches:
       - 'gh-pages'
       - 'feature-homepage-launch'
+      - 'feature-tech-dropdown'
 
 jobs:
   generate-labels-artifact: