B + squash merge into gh-pages

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

@@ -18,29 +18,57 @@ As a new designer on the HfLA website UX team, fill in the following fields as y
 - [ ] Add yourself to the #hfla-site-ux and #hfla-site Slack channels
 - [ ] Share your Gmail address with the team lead
 - [ ] (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 meeting invites and [added you to the GitHub team](https://github.com/orgs/hackforla/teams/website-write/members) and GitHub repo
+- [ ] Confirm with the design lead, that they have added you to the meeting invites and [added you to the GitHub team](https://github.com/orgs/hackforla/teams/website-write/members) and GitHub repo
 - [ ] Self Assign yourself to this issue (gear in right side panel)
 - [ ] 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, Wednesday 2:30 pm PST
    - [ ] All team meeting (UX, Development, Product), Sunday 10am PST
+ - [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Wednesdays and Sundays). In case, you are unable in any given week, you should reach out to the design lead. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the design lead know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
 - [ ] 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
 - [ ] Review the [prioritized Backlog to see what Design Issues](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+design%22#column-7198257) are available (this will not be the complete list, but will give you some talking points for your conversation with your lead).
-- [ ] Once you accept an issue, please add your "Availability for this week" in that new issue's comment section using the 4 statuses below.
-```
-Availability for this week:
+- [ ] Once you take an 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 text below and put it in the 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.
+    ```
+   Availability for this week:
+   My estimated ETA for completing this issue:
+    ```
+   - [ ] Time spent so far: Copy the question below into a new comment below and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
+    ```
+    How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
+    ```
+   - [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report.  If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue.  This update should be done every week for every issue.  The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
+    ```
+    Provide Update
+    1. Progress
+    2. Blockers
+    3. Availability
+    4. ETA
+    ```
+### Additional notes:
+- [ ] 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 (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)
+- [ ] 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?
+- First, you should post the question as a comment on your assigned issue, so it can be easily referred to in the next bullet points
+- Then, add the issue to the "Design Weekly Meeting Agenda" column of the Project Board so that it can be addressed in the next design meeting
+- You may also add the label "Status: Help Wanted" so other designers can see it and potentially help answer your question
+- Lastly, you can post your question in the hfla slack channel and link the issue you're working on, so other volunteers can see and respond
 
-1. Progress: "What is the current status of your project? 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?"
-Images: "Add any images that would better help convey your progress of the issue."
-```
 ### Resources/Instructions
 - [GitHub Project Board - Hack for LA ](https://github.com/hackforla/website/projects/7)
 - [GitHub Project Board Prioritized Backlog highlighted and sorted by Design](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+design%22#column-7198257)
+- [Design Weekly Meeting Agenda](https://github.com/hackforla/website/issues/2106)
 - [Figma - Hack for LA](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website)
 - [Miro](https://miro.com/app/board/o9J_l6zD0JA=/)
 - [Google Drive - Hack for LA website team](https://drive.google.com/drive/folders/1p76K0FgfiAWeIIEyoyJ_Iik8FVj8cBjT?usp=sharing)

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

@@ -2,33 +2,39 @@
 name: Pre-work Template - Developers
 about: New developer team members should start by making this issue for themselves
 title: 'Pre-work Checklist: Developer: [replace brackets with your name]'
-labels: 'Feature: Onboarding/Contributing.md, prework, Ready for Milestone, size:
-  1pt'
+labels: 'Feature: Onboarding/Contributing.md, prework, size: 1pt'
 assignees: ''
 
 ---
 
 ### Prerequisite
-We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events
+We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.
 
 ### Overview
 As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.
 
+### Special Notes
+1. It may take you a few weeks to finish this issue, because part of it is learning how to provide updates on issues that take more than a week to complete.    Please keep this issue open until you have been able to do all the steps.  
+2. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues.
+
 ### Action Items
+
 - [ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
-- [ ] Share your GitHub handle and 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
+- [ ] Share your GitHub handle and Gmail address with a merge team member or technical lead so you can be added to the Google Drive
+  - [ ] To find contact information for the merge team members and technical leads, please take a look at our [Meet the Team wiki page](https://github.com/hackforla/website/wiki/Meet-the-Team)
+- [ ] Also, confirm with a merge team member or a technical lead that they have added you to the Google Calendar invites for our Zoom meetings
 - [ ] (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
+- [ ] After you have finished adding yourself to the roster, let a merge team member or a technical 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
+  - [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
   - [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
 - [ ] Signup for a [Figma](https://Figma.com) account
 - [ ] Attend weekly team meetings:
   - [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
   - [ ] (Optional) Office Hours, Thursdays 7-8pm PST
   - [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
+- [ ] Note: There are no meetings on the 1st-7th of every month.
 - [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
 - [ ] 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.
@@ -37,16 +43,16 @@ As a new developer on the HfLA website team, fill in the following fields as you
   - [ ] 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)
 - [ ] 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.
+ 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. (Note: Please provide estimates on all the issues that you pick up, going forward.)
     ```
    Availability for this week:
    My estimated ETA for completing this issue:
     ```
-   - [ ] Time spent so far: Copy the question below into a new comment below and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
+   - [ ] Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
     ```
     How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
     ```
-   - [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report.  If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue.  This update should be done every week for every issue.  The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
+   - [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report.  If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. **This update should be done every week for every issue that you are assigned to**. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
     ```
     Provide Update
     1. Progress
@@ -72,14 +78,15 @@ Progress through issues with increasing complexity in the following order:
     - 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
+- [ ] Read the [Start Here - Developers](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8583%3A0) in Figma
 - [ ] 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?
-- First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points
-- Then, add the issue to the "Development team meeting discussion items" column of the Project Board so that it can be addressed in the next development meeting
-- You may also add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question
-- Lastly, you can post your question in the hfla slack channel and link the issue you're working on, so other volunteers can see and respond
+- First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
+- Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
+- Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
+- Lastly, you can add the issue to the "Development team meeting discussion items" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.
 
 ### Resources/Instructions
 - [Contributing.md - Hack for LA](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)

.github/ISSUE_TEMPLATE/project-md-file--removing-unused--alt-hero--field.md

@@ -24,6 +24,9 @@ Moreover, if the `image-hero` were to be used in an img HTML tag in the future,
 ```
 alt-hero: [INSERT CURRENT ALT-HERO TEXT HERE]
 ```
+- [ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #2722 by
+  - [ ] Checking off the dependency for this issue
+  - [ ] If all dependencies are checked off, please move issue #2722 to the New Issue Approval column and remove the Dependency label
 
 ### Resources/Instructions
 - This issue is part of epic #2722 

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

@@ -27,7 +27,7 @@ Insert url of your project card here before sending; your card(s) can be found i
          - [ ] Role
          - [ ] SLACK ID
       - [ ] links
-         - [ ] Github
+         - [ ] GitHub
          - [ ] Slack
          - [ ] Test Site
          - [ ] Demo Site

.github/workflows/issue-trigger.yml

@@ -1,7 +1,7 @@
 name: Issue Trigger
 on:
   issues:
-    types: [opened]
+    types: [opened, assigned]
 
 jobs:
   Add-Missing-Labels-To-Issues:
@@ -25,7 +25,37 @@ jobs:
         uses: actions/github-script@v4
         id: post-comment
         with:
-            script: |
-              const results = ${{ steps.check-labels.outputs.result }}
-              const script = require('./github-actions/trigger-issue/add-missing-labels-to-issues/post-labels-comment.js')
-              script({g: github, c:context}, results)
+          script: |
+            const results = ${{ steps.check-labels.outputs.result }}
+            const script = require('./github-actions/trigger-issue/add-missing-labels-to-issues/post-labels-comment.js')
+            script({g: github, c:context}, results)
+
+  #Asking for preliminary update when issue is assigned
+  Ask-For-Preliminary-update:
+    runs-on: ubuntu-latest
+    #Triggers when the issue is newly assigned
+    if: ${{ github.event_name == 'issues' && github.event.action == 'assigned'}}
+    steps:
+      - uses: actions/checkout@v2  
+
+      # Check if the issue has the required roles
+      - name: Check Labels Prelim
+        uses: actions/github-script@v4
+        id: check-labels-prelim
+        with:
+          script: |
+            const script = require('./github-actions/trigger-issue/add-preliminary-comment/check-label-preliminary-update.js')
+            const checklabels = script({g: github, c: context})
+            return checklabels
+
+
+      # Post the comment based on the result of the previous step
+      - name: Post assigning issue comment
+        id: assigned-comment
+        uses: actions/github-script@v4
+        with:
+          script: |
+            const results = ${{ steps.check-labels-prelim.outputs.result }}
+            const script = require('./github-actions/trigger-issue/add-preliminary-comment/preliminary-update-comment.js')
+            script({g: github, c:context},results)
+