ER: Generic good first issue template for developers

[JessicaLucindaCheng]

Emergent Requirement - Problem

• Since we write a lot of good first issues, it would be helpful to have a generic good first issue template for writing developer issues.
• This template would be used to write good first issues for role: front end and/or role: back end/devOps.

Issue you discovered this emergent requirement in

• Rollout Plan: Refactor code with img HTML tags to end without a slash #4362

Date discovered

2023-04-24 at Dev/PM meeting

Did you have to do something temporarily

• YES - I just write issues using the regular blank issue template
• NO

Who was involved

@JessicaLucindaCheng
@bonniewolfe

What happens if this is not addressed

We have to write good first issues using the blank issue template or blank issue form.

Resources

• Examples of good first issues:
  • img Tag Refactor: Citizen Engagement page #4449
  • Update labels: Issue Template: blank-issue-form-with-dependency #4491
  • Update Self-Invite Link for the Slack Icon in the Footer of the Website #4141

Recommended Action Items

• Make a new issue for a developer to work on creating a generic good first issue template
  • The new issue should include the labels: Issue Making: Level 2 and Complexity: See issue making label.
• Discuss with Merge Team if you need help writing the issue or have questions

Potential solutions [draft]

[ExperimentsInHonesty]

Here is a generic issue template that works for one-line changes to project Markdown files

### 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 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/gh-pages/CONTRIBUTING.md).

### Overview
[Replace WITH DESCRIPTION OF WE NEED TO DO X FOR Y REASON]

### Action Items
- [ ] Change the GitHub link for [Replace PROJECT TITLE] so it resolves to the correct url
    - **Line 54** under `_projects/[Replace PROJECT.MD file name]`

From:
```
[Replace ADD EXISTING LINE]
```
To:
```
[Replace ADD NEW LINE]
```
- [ ] Using Docker, check the page [Replace HAS X STATE]  in mobile, tablet, and desktop views as on the current website
- [ ] Ensure that [Replace X CHECK] from the [Replace PAGE NAME](https://www.hackforla.org/[Replace PAGE URL]) and [Replace with PROJECT NAME](https://www.hackforla.org/projects/[Replace PROJECT PAGE URL]) both resolve to the new address

### Resources/Instructions
- Directory to find the page in once you have it in your IDE: `_projects/[Replace PROJECT.MD file name]`
- [Projects page](https://www.hackforla.org/projects/)
- Project page URL: https://www.hackforla.org/projects/[Replace PROJECT PAGE URL]
- Click on the filename below to see the source file code:
[Replace with LINK TO THE PROJECT PAGE IN THE GITHUB REPO]

[JessicaLucindaCheng]

Issue Writing

• Progress: None
• Blockers: None
• Availability: TBD
• ETA: TBD

Notes from Dev/PM from 2023-06-05

• After the issue to create a generic good first issue template is completed, the following issues need to be made for slightly more specific templates:
  • A one line change for Markdown files in _project. See the template here: ER: Generic good first issue template for developers #4591 (comment)
  • Possibly other scenarios