Update feature-homepage-launch branch on November 21, 2024

.github/ISSUE_TEMPLATE/add-github-handle.md

@@ -2,16 +2,17 @@
 name: github-handle in project file
 about: For adding github-handle to member data in a project file
 title: Add github-handle for [INSERT NAME] in [INSERT PROJECT FILE]
-labels: 'good first issue, P-Feature: Project Info and Page, ready for dev lead, role:
-  back end/devOps, role: front end, size: 0.25pt'
+labels: 'Complexity: Small, feature: spelling, good first issue, P-Feature: Project
+  Info and Page, ready for merge team, role: back end/devOps, role: front end, size:
+  0.5pt, size: 0.25pt'
 assignees: ''
 
 ---
 
 ### Prerequisite
 1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started Page](https://www.hackforla.org/getting-started).
 2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).
-   
+
 ### Overview
 We need to create a single variable `github-handle` to hold the github handle for each member of the leadership team. Eventually `github-handle` will replace the `github` and `picture` variables, reducing redundancy in the project file.
 
@@ -24,7 +25,7 @@ We need to create a single variable `github-handle` to hold the github handle fo
 with
 ```
 - name: [INSERT MEMBER NAME]
-  github-handle: 
+  github-handle:
 ```
 - [ ] Do not use a tab to indent `github-handle`. YAML doesn't allow tabs; it requires spaces.
 - [ ] Using docker, confirm that the appearance of the project webpage is unchanged at all screen sizes. The project webpage URL can be found below under Resources.
@@ -33,9 +34,9 @@ with
 - [ ] Release the dependency for this issue in #5441. If all the dependencies have been completed, close that issue.
 
 ### Resources/Instructions
-https://github.com/hackforla/website/wiki/project.md-file-template  
-https://jekyllrb.com/  
-For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/[INSERT-PATH-TO-PROJECT-FILE]  
+https://github.com/hackforla/website/wiki/project.md-file-template
+https://jekyllrb.com/
+For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/_projects/[INSERT_PROJECT_FILE]?plain=1
 Project Webpage: https://www.hackforla.org/projects/[INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION]
 
 - This issue is part of #5441.

.github/ISSUE_TEMPLATE/communities-of-practice-information-updates.yml

@@ -1,9 +1,7 @@
 name: Communities of Practice information updates
 description: CoP leads use this issue to make changes to Leadership members and contact info
-title: 'Communities of Practice information updates: [INSERT NAME OF Community of
-  Practice]'
+title: 'Communities of Practice information updates: [INSERT NAME OF Community of Practice]'
 labels: ['role: product', 'P-Feature: Communities of Practice', 'time sensitive', 'Complexity: Missing', 'size: missing']
-
 body:
   - type: markdown
     attributes:
@@ -20,9 +18,24 @@ body:
   - type: markdown
     attributes:
       value: "Change Description: NO"
-  - type: markdown
+  - type: dropdown
+    attributes:
+      label: "Change Leadership Type"
+      options:
+        - "YES"
+        - "NO"
+      description: "If YES on Change Leadership Type, choose the Leadership Type; if NO, leave the field with the NA value:"
+    validations:
+      required: true
+  - type: dropdown
     attributes:
-      value: "Change Leadership Type: NO"
+      label: "Leadership Type"
+      options:
+        - "N/A"
+        - "Mentor Led"
+        - "Community Led"
+      default: 0
+      description: "Select the type of leadership if applicable."
   - type: markdown
     attributes:
       value: "Change Slack Link: NO"
@@ -58,11 +71,10 @@ body:
         Title:
         GitHub Handle:
         Slack Member ID:
-  - type: markdown
-    attributes:
-      value: "### Resources"
   - type: markdown
     attributes:
       value: |
-        folder where files are in the repo: https://github.com/hackforla/website/tree/gh-pages/_data/internal/communities
-        where you can see the live page: https://www.hackforla.org/communities-of-practice
+        ### Resources
+        * Folder where files are in the repo: https://github.com/hackforla/website/tree/gh-pages/_data/internal/communities
+        * Where you can see the live page: https://www.hackforla.org/communities-of-practice
+        * If you need to update your meeting times, names, dates, or frequency, please see the [VRMS User Guide](https://github.com/hackforla/VRMS/wiki/User-Guide). The HackforLA.org website gets the meeting times from the updates made to each Community of Practice's meeting data in vrms.io

.github/ISSUE_TEMPLATE/correct-misspelling-on-website-page.md

@@ -0,0 +1,31 @@
+---
+name: Correct misspelling on Website Page
+about: Describe this issue template's purpose here.
+title: Correct misspelling in [REPLACE WITH NAME OF PAGE] page
+labels: 'Feature Missing, feature: spelling, good first issue, role: back end/devOps,
+  role: front end, size: 0.25pt, time sensitive'
+assignees: ''
+
+---
+
+### Prerequisite
+1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started).
+2. Please make sure you have read our **[Hack for LA Contributing Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)** before you claim/start working on an issue.
+
+### Overview
+Our website needs to be free of misspellings so that our reputation for quality is maintained.  In this issue a misspelling in the [REPLACE WITH WHERE]  on the [REPLACE WITH NAME OF PAGE] page will be corrected.  
+
+### Action Items
+- [ ] For the file `[REPLACE WITH DIRECTORY & NAME OF FILE (e.g., /pages/communities-of-practice.html)]`, correct the spelling from "[REPLACE WITH MISSPELLED WORD]" to "[REPLACE WITH CORRECT SPELLED WORD]", so
+   ```
+   [REPLACE WITH CURRENT CODE]
+   ```
+   becomes
+   ```
+   [REPLACE WITH FUTURE CODE - WHAT IT WILL LOOK LIKE AFTER ITS FIXED]
+   ```
+- [ ] Use Docker to test changes locally, in both desktop and mobile views
+
+### Resources
+Website page with issue: [REPLACE WITH URL OF PAGE ON WEBSITE]
+File on GitHub: https://github.com/hackforla/website/blob/gh-pages/REPLACE WITH DIRECTORY & NAME OF FILE (e.g., /pages/communities-of-practice.html)]

.github/ISSUE_TEMPLATE/img-tag-refactor-on-website.md

@@ -11,7 +11,7 @@ assignees: ''
 
 ### Prerequisite
 1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session.
-2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).
+2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).
 
 ### Overview
 We want to change an img HTML tag ending with a slash (<img.../>) to an img tag without an ending slash (<img...>) so that the codebase is consistent with how we use img HTML tags.

.github/ISSUE_TEMPLATE/post-an-open-role.md

@@ -0,0 +1,12 @@
+---
+name: Post an open role
+about: Recruit volunteers for specific open roles template
+title: 'HfLA Website: Open Role for: [Replace with NAME OF ROLE]'
+labels: 'Complexity: Small, role missing'
+assignees: ''
+
+---
+
+![image](https://user-images.githubusercontent.com/37763229/162992303-b0fae60e-1886-45ce-93c1-d1a27a909327.png)
+
+[INSERT DRAFT FROM THE Recruit volunteers for team open roles issue]

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

@@ -26,7 +26,7 @@ As a new designer on the HfLA website UX team, fill in the following fields as y
 - [ ] 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.
+ - [ ] 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).
@@ -63,7 +63,7 @@ Progress through issues with increasing complexity in the following order:
 - 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
+- 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
 
 ### Resources/Instructions
 - [GitHub Project Board - Hack for LA ](https://github.com/hackforla/website/projects/7)

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

@@ -24,7 +24,6 @@ As a new developer on the HfLA website team, fill in the following fields as you
 - [ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
   - [ ] 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)
 - [ ] 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 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
 - [ ] 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 (gear in right side panel)
 - [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
@@ -34,8 +33,8 @@ As a new developer on the HfLA website team, fill in the following fields as you
   - [ ] (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)
+- [ ] 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.7 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
@@ -83,7 +82,7 @@ Progress through issues in the [prioritized backlog](https://github.com/hackforl
 ### 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 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.
+- 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

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

@@ -36,6 +36,7 @@ body:
         - "LA TDM Calculator"
         - "Lucky Parking"
         - "Open Community Survey"
+        - "Tech Work Experience"
         - "VRMS"
         - "Write for All"
         - "Youth Justice Nav"
@@ -93,6 +94,7 @@ body:
         - "shared-housing-project.md"
         - "spare.md"
         - "tdm-calculator.md"
+        - "tech-work-experience.md"
         - "undebate.md"
         - "vrms.md"
         - "website.md"
@@ -217,6 +219,20 @@ body:
     id: github-link
     attributes:
       label: GitHub Link
+
+  - type: dropdown
+    id: additional-github-repos-yes-no
+    attributes:
+      label: "Do you have any additional (other than your primary) GitHub repositories that your volunteers make issues or PRs against?"
+      options:
+        - "YES"
+        - "NO"
+    validations:
+      required: true
+  - type: textarea
+    id: additional-github-repos
+    attributes:
+      label: "If yes, list the repo URLs here"
 
   - type: dropdown
     id: update-slack-link-yes-no

.github/ISSUE_TEMPLATE/project-profile-leader-updates---add.md

@@ -0,0 +1,44 @@
+---
+name: Project Profile leader updates - Add
+about: This template is for website team only to ADD a single volunteer
+title: 'Update Project Profile: [Project Name] Add [Name of Volunteer]'
+labels: 'good first issue, P-Feature: Project Info and Page, role: back end/devOps,
+  role: front end, size: 0.25pt, time sensitive'
+assignees: ''
+
+---
+
+### Prerequisites
+1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started](https://www.hackforla.org/getting-started) page and attend an onboarding session.
+2. You have already read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).
+
+### Overview
+We need to keep project information up to date so that visitors to the website can find accurate information.
+
+### Action Items
+- [ ] In your IDE, open the `_projects/[Insert filename].md` file.
+- [ ] Observe the existing syntax of the front matter block [^1] in the file.
+- [ ] Find the `leadership` variable and add the following profile. 
+```
+  - name: [Insert leadership member's name]
+    github-handle: [Insert GitHub handle]
+    role: [Insert role]
+    links:
+      slack: https://hackforla.slack.com/team/[Insert Slack member ID]
+      github: https://github.com/[Insert GitHub handle]
+    picture: https://avatars.githubusercontent.com/[Insert GitHub handle]
+```
+- [ ] Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request:
+  - [ ] [Insert name of project] page [^2]
+- [ ] Once your pull request is merged, go to the initiating ER [^3]
+  - [ ] Check off this issue under the _Dependency_ section
+  - [ ] If all the issues in the _Dependency_ section are checked off, move initiating ER [^3] to **Questions / In Review** column and uncheck the **Dependency label**.
+    - <details>
+        <summary>Click here to see how to uncheck the <b>Dependency label</b></summary>
+        <img src="https://github.com/hackforla/website/assets/31293603/6f53f4d4-7d2c-45f8-8534-9936fc9adee8" width="300px">
+      </details>
+
+### Resources/Instructions
+[^1]: [Info about the front matter block](https://jekyllrb.com/docs/front-matter/)
+[^2]: Project detailed info page URL: [Insert project specific page URL here]
+[^3]: initiating ER:  #[Insert ER number]