Create issue template for fixing misspelled words on website

[essencegoff]

trafficstars

Overview

We need to create an issue template for fixing misspelled words on website so that it easy to create new issues.

Action Items

• [x] Copy the content from the sample issue ^1 to a comment on this issue
• [x] Copy the comment to a new comment
• [x] Edit to make generic
• [ ] Test it on a misspelling from [^2]
• [ ] Publish issue template

Resources/Instructions

[^2]:HfLA-Website: spelling audit

[essencegoff]

Sample Misspelling Issue

Text from 6232

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.
2. Please make sure you have read our Hack for LA Contributing Guide 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 "alt text" of an image on the Community of Practice page will be corrected.

Action Items

• [x] For the file /pages/communities-of-practice.html, correct the spelling from "commmunity" to "community", so

   <img class="header-hero-image" src="/assets/images/communities-of-practice/comm-prac-header.svg" alt="commmunity of practice header" />
  

  becomes

   <img class="header-hero-image" src="/assets/images/communities-of-practice/comm-prac-header.svg" alt="community of practice header" />
  

• [x] Use Docker to test changes locally, in both desktop and mobile views

Resources

Website page with issue: https://www.hackforla.org/communities-of-practice File on GitHub: https://github.com/hackforla/website/blob/gh-pages/pages/communities-of-practice.html

[essencegoff]

Draft Misspelling Template

Title

Correct misspelling in [REPLACE WITH NAME OF PAGE] page

Body

### 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)]

[HackforLABot]

@essencegoff

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, October 29, 2024 at 12:04 AM PST.}

[essencegoff]

Added template to repo and added the link to the top of the issue.