Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run VS Code Spell Checker on hamburger-nav.html #7386

Closed
7 of 9 tasks
Tracked by #5248 ...
k-cardon opened this issue Sep 4, 2024 · 6 comments
Closed
7 of 9 tasks
Tracked by #5248 ...

Run VS Code Spell Checker on hamburger-nav.html #7386

k-cardon opened this issue Sep 4, 2024 · 6 comments
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Comments

@k-cardon
Copy link
Member

k-cardon commented Sep 4, 2024

Overview

We need to audit HfLA codebase files for spelling errors using the Code Spell Checker extension in VS Code in order to ensure site quality. Results will be categorized as misspellings or false positives in the HfLA spelling audit spreadsheet1 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 extension2
  • Do not change any configuration settings or make any spell corrections
  • Open the file '_includes/hamburger-nav.html' and note any Code Spell Checker errors
  • Locate the file in column A ("File") of the "Page Audit" sheet. In the column labeled "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 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

Resources/Instructions

Footnotes

  1. HfLA spelling audit spreadsheet - Results

  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. The extension can also be installed via the VS Code Marketplace website here.

@k-cardon k-cardon added Feature: Administrative Administrative chores etc. role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.5pt Can be done in 3 hours or less labels Sep 4, 2024
@k-cardon k-cardon self-assigned this Sep 4, 2024
@HackforLABot
Copy link
Contributor

Hi @k-cardon, we notice that you are assigned to an issue that you authored. Please remember to add the Draft label to this issue while you are working on it.

@k-cardon k-cardon added the Draft Issue is still in the process of being created label Sep 4, 2024
@k-cardon
Copy link
Member Author

k-cardon commented Sep 4, 2024

I created this set of issues at @roslynwythe 's suggestion so that I could have a small issue to work on :)

@k-cardon
Copy link
Member Author

Provide Update

  1. Progress: waiting for approval
  2. Blockers: currently assigned to the issue-making issue for this one
  3. Availability: evenings, weekends this week
  4. ETA: end of week

@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on Draft Issue is still in the process of being created labels Sep 13, 2024
@ExperimentsInHonesty
Copy link
Member

@k-cardon this issue has been approved and I have moved it to the in progress column.

@k-cardon
Copy link
Member Author

No spell check errors found

@k-cardon k-cardon added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Sep 17, 2024
@LRenDO
Copy link
Member

LRenDO commented Sep 18, 2024

Hi @k-cardon! Great job with this issue! It looks like there are no errors on this page on my end too! You also did a great job with moving the issue to the right column and adding the correct label. Thanks for contributing to this epic!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Development

No branches or pull requests

5 participants