website Epic: Create template, spreadsheet and list of issues for spellcheck audit

Dependency

[x] #5739
[x] #5738
[x] #5736
[x] #5737
[x] #5735
[x] #5311
[x] #5514
[x] #5515
[x] #5516
[x] #5518
[x] #5519
[x] #5595
[x] #5596
[x] #5600
[x] #5598
[x] #5524
[x] #5525
[x] #5526
[x] #5527
[x] #5528
[x] #5529
[x] #5520
[x] #5530
[x] #5531
[x] #5532
[x] #5533
[x] #5517
[x] #5527
[x] #5604
[x] #5594
[x] #5603
[x] #5602
[x] #5599
[x] #5597
[x] #5981
[x] #5982
[x] #5983
[x] #5984
[x] #5985
[x] #5986
[x] #5987
[x] #5988
[x] #5989
[x] #5990
[x] #5991
[x] #5992
[x] #5993
[x] #5994
[x] #5995
[x] #5996
[x] #5997
[x] #5998
[x] #6086
[x] #6087
[x] #6088
[x] #6089
[x] #6090
[x] #6091
[x] #6092
[x] #6093
[x] #6094
[x] #6095
[x] #6096
[x] #6097
[x] #6487
[x] #6488
[x] #6489
[x] #6490
[x] #6491
[x] #6492
[x] #6493
[x] #6494
[x] #6495
[x] #6496
[x] #6497
[x] #6498
[x] #6569
[x] #6570
[x] #6571
[x] #6572
[x] #6573
[x] #6574
[x] #6575
[x] #6576
[x] #6577
[x] #6578
[x] #6585
[x] #6590
[x] #6591
[x] #6592
[x] #6593
[x] #6594
[x] #6758
[x] #6757
[x] #7142
[x] #7143
[x] #7144
[x] #7145
[x] #7146
[x] #7147
[x] #7148
[x] #7149
[ ] #7448
[ ] #7449
[ ] #7450
[ ] #7451
[ ] #7452
[ ] #7453
[ ] #7454
[ ] #7455
[x] #7456
[x] #7386
[ ] #7391 Note: some spellcheck issues are not listed above - see the Issue Making Level 1 issues below

Dependencies/ Issue Making Level 1 issues

[x] #6499
[x] #6541
[x] #6679
[x] #6871
[x] #7165
[x] #7166
[x] #7167
[ ] #7587
[ ] #7168

Overview

We need to create issues to audit all appropriate codebase files for Code Spell Checker results. The HfLA spelling audit spreadsheet[^1] will be used to track spell check audit issues, record false positives and misspellings, and track resulting issues for resolving errors.

Action Items

[x] Create HfLA spelling audit spreadsheet[^1]
- [x] List files we wish to spell check in Page Audit sheet
- [x] List excluded files/paths in Excluded Paths sheet
[x] Create an issue template for spell checking (Small) - see https://github.com/hackforla/website/issues/5248#issuecomment-1685247438
[x] Create GitHub issue template - #5540
[x] sample issue #5311
- Dev will install cSpell and will check the specified page
- Errors will be recorded and categorized as misspellings or false positives
[ ] Create Issue Making Level 1 issues to create issues and list above

Resources/Instructions

This issue is part of #4349 [^1]:HfLA spelling audit spreadsheet

Aug 17 '23 23:08 roslynwythe

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

Aug 17 '23 23:08 github-actions[bot]

hello @roslynwythe , i am interested to contribute to Hack for LA's website....can u please let me know how can i ...

Aug 18 '23 19:08 Gourav2609

Hi @Gourav2609 you will have to become a member of Hack for LA, but you don't have to live in LA. See https://www.hackforla.org/join

Aug 20 '23 10:08 roslynwythe

Draft Audit Issue Template

Title: Run VSCode Spell Checker on [INSERT FILE PATH]

### Overview
We need to audit HfLA codebase files for spelling errors using the VSCode Code Spell Checker extension in order to ensure site quality.  Results will be categorized as misspellings, false positives in the HfLA spelling audit spreadsheet[^1] and will be resolved in later issues.  

### Action Items
- [ ] You must use VS Code as your local text editor and install the `Code Spell Checker` VS Code extension[^2]  
- [ ] Do not change any configuration settings or make any spell corrections
- [ ] Open the file '[INSERT FILE PATH]'and note any Code Spell Checker errors
- [ ] Locate the file in column A ("File") of the "Page Audit" sheet.  In the column labelled "Result Summary", select the appropriate option:  `No errors` or `At least one error`.  
- [ ] If at least one error was reported, copy/paste each cSpell message into a separate row in the `Results` sheet
- [ ] In each new row, select the appropriate value: `misspelling` or `false positive` from the "Result type" column.  A false positive is a term that is not a misspelling, but it is not recognized by the spell checker because it is a technical term, abbreviation, acronym, URL or proper noun (name of a person, place or organization).  
- [ ] Move this issue to the Questions/In Review column and apply the label 'ready for dev lead`

### Merge Team
- [ ] After this issue is closed, release the dependency on this issue in #5248
- [ ] After the last dependency has been released, close that issue. 

### Resources/Instructions
- This issue is part of #5248
[^1]: [HfLA spelling audit spreadsheet - Results](https://docs.google.com/spreadsheets/d/1c2C9zUF_LsLGrnJN_LAlPV4UObz-nYffJyOiB_M6oI0/edit#gid=69989048)
[^2]:The recommended installation method is to install Code Spell Checker directly from the VS Code text editor, and those instructions can be found [here](https://code.visualstudio.com/learn/get-started/extensions). The extension can also be installed via the VS Code Marketplace website [here](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker).

Aug 20 '23 10:08 roslynwythe

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Aug 24 '23 06:08 github-actions[bot]

@roslynwythe

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.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
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, September 26, 2023 at 12:06 AM PST.}

Sep 29 '23 07:09 github-actions[bot]

@roslynwythe