Fix lint issues

Not ready yet: any links starting `/` need to be rewritten

Author: rvedotrc

legacy/javascript/homework-projects/README.md

@@ -4,10 +4,8 @@
 
 During the JS2 and JS3 modules, you will be working on a project instead of the usual weekly homework assignments (which you can still do, as optional practice). Each week, you will be required to add new features to your project. By the end of JS3, you will have built an actual app using your newly gained knowledge and coding skills!
 
-
 ![diagram](assets/project-flow.png)
 
-
 ## WHY
 
 We're doing this for four main reasons:
@@ -17,7 +15,6 @@ We're doing this for four main reasons:
 - You will build a solid project for your portfolio that you can showcase on your CV and in future tech interviews!
 - You will gain experience presenting your project and code in a 'mini-tech interview' at the end of JS3.
 
-
 ## PROJECT IDEAS
 
 [Currency Converter](projects/currency-converter/currency-converter.md)
@@ -29,32 +26,22 @@ We're doing this for four main reasons:
 > [!NOTE]
 > New projects are welcome to be added by mentors. Just follow a similar structure to the existing ones, and submit it as a PR for review by staff and other mentors.
 
-
-
 ## HOW
 
 The projects will either be worked on individually, in a pair or as a group. You may also be set up to peer review another's project. This is up to the staff and mentors running the module.
 
-
-
 First, you will pick a project idea from above. Each week, you will have specific tasks that you have to deliver. Those tasks are provided in your chosen project description. The tasks are designed to help you practice the main learning points throughout the JS2 and JS3 modules.
 
-
-
 You will work in your project repository for JS2 and JS3 (not the central homework repository!), and you will submit the weekly task in the usual way by creating a Pull Request.
 
 During JS2 and JS3, refer to the relevant [homework submission guide](guides/weekly-submission-guide.md).
 
 The main difference is that you will be on a different repository and that you will merge the PR after implementing the review-based improvements, while all the technical steps are the same as always.
 
-
-
 ## DEPLOYMENT
 
 So you can demo your project easily both at the end of the project, but also to future employers, it is a requirement that you deploy the project. You can use the [HackYourFuture project template](https://github.com/HackYourFuture-CPH/hyf-project-template) as a starting point, or an otherwise agreed upon process by the staff and mentors.
 
-
-
 ## CONCLUSION
 
 When you wrap up your project in JS3 week3, you will get a chance to present your project either as a video recording or on a demo day. If your team is hosting a demo day, then check out [this guide](guides/demo-day-presentation.md) for how to prepare for the presentation.

legacy/javascript/homework-projects/guides/weekly-submission-guide.md

@@ -12,11 +12,6 @@
 - [ ] stay patient. Slack, Google and ChatGPT are your best friends now.
 - [ ] make the changes as per PR review in the appropriate branch, push the changes to the appropriate branch and merge the PR.
 
- <br/>
-
-<hr>
-<hr>
-
 ## Before you start the project
 
 - Create a public project repository in your GitHub account (choose the option to add README.md).
@@ -25,70 +20,48 @@
 ## Before you start your homework
 
 1. You are probably opening your project repo on the last weeks branch - make sure that any changes you have there are either committed and pushed, or stashed, or discarded - whatever you prefer. The point is to be mindful that:
-   <br/> - you are most probably starting on a branch you last worked with, that is how VS Code works,
-   <br/> - and there might be changes that you have not handled last time.
-   <br/> - if you are about to start a new homework, you need to go to `main` first.
 
-<br/>
+   - you are most probably starting on a branch you last worked with, that is how VS Code works,
+   - and there might be changes that you have not handled last time.
+   - if you are about to start a new homework, you need to go to `main` first.
 
 2. Checkout to `main` and pull the latest changes from it. If you skip this step, you will get in trouble sooner or later.
 
-<br/>
-
 3. Checkout to your new homework branch, following the branch naming convention of `module-week/yourname`.
    See [allowed branch name prefixes](#allowed-branch-name-prefixes).
 
-<br/>
 ❗ Always firstly checkout to the new homework branch from an updated `main`. Always.
 
-<br/>
-
 ### Allowed branch name prefixes
 
-|                   |                   |                   |     |     |
-| ----------------- | ----------------- | ----------------- | --- | --- |
-| javascript2-week1 | javascript2-week2 | javascript2-week3 |     |
-| javascript3-week1 | javascript3-week2 | javascript3-week3 |     |
+|                   |                   |                   |
+| ----------------- | ----------------- | ----------------- |
+| javascript2-week1 | javascript2-week2 | javascript2-week3 |
+| javascript3-week1 | javascript3-week2 | javascript3-week3 |
 
 ### Examples
 
-> ❌ javascript3/maria <br/>
-> ❌ javascript2-week1-homework <br/>
-> ❌ javascript3-week2 <br/>
-> ✅ javascript3-week3/maria
-
-<br/>
+- ❌ javascript3/maria
+- ❌ javascript2-week1-homework
+- ❌ javascript3-week2
+- ✅ javascript3-week3/maria
 
 ## Completing and submitting your homework
 
 1. Implement your homework. Be mindful of structuring and naming. Make sure you complete all the tasks listed for that week in your project description.
 
-<br/>
-
 2. Verify that your branch name is right. Commit and push your homework to the repository. If the branch name is not right, you can commit and checkout to a new, correct branch from the current branch - you will carry all the commits with you. Then you can push.
 
-<br/>
-
 3. Go to your project repository and create a Pull Request from your weekly homework branch to `main`.
 
-<br/>
-
 4. Post the link to the PR to your class channel and celebrate with your classmates! 🎉 💃🏽 🕺🏾 🥳
 
-<br/>
-
 ## After submitting your homework
 
 1. Follow the PR to see the review and interact with the reviewer as well as make the suggested changes.
 
-<br/>
-
 2. When you have made changes to the code since the homework submission and review, push the changes and merge the PR.
 
-<br/>
-
 3. Update your local `main` with the merged changes in the remote `main`.
 
-<br/>
-
 4. Take a moment to celebrate your progress and be proud of your learning!

legacy/javascript/homework-projects/projects/currency-converter/currency-converter.md

@@ -1,7 +1,7 @@
-![](https://media.giphy.com/media/LdOyjZ7io5Msw/giphy.gif)
-
 # CURRENCY CONVERTER
 
+![showering in money](https://media.giphy.com/media/LdOyjZ7io5Msw/giphy.gif)
+
 You started working in a new cool fintech startup, and your first task is to build a simple currency converter app.
 It is expected that your app will have at least these features and functionality:
 
@@ -54,20 +54,16 @@ Then, after an update (the bonus task) it could look something like this:
 }
 ```
 
----
-
 ### `JS2 week2` - Array functions, Arrow function
 
 Start with creating an array of currency rate objects. Even a small one is perfectly enough, but go as big as you want!
 Continue with the format of the object you used last week or improve it and refactor!
 
 - [ ] List: Traverse through your array of the currency rate objects, and display them in a grid of items containing all the relevant details.
-- [ ] Implement a function to find a specific currency rate, searching by the currency `from` or `to`. <br/>
+- [ ] Implement a function to find a specific currency rate, searching by the currency `from` or `to`.
       Basically, it is just a search function! With a twist, though, because you have both the `from` and the `to` fields.
       As a user, I want to find a specific rate, but I am too lazy to scan through all the rates with my eyes, I want to be able to type in and search!
 
----
-
 ### `JS2 week3` - Callback function, Asynchronicity, Scope
 
 - [ ] Implement a timeout to show an announcement when the market open or/and close. The market opens at 9AM and closes at 5PM local time.
@@ -76,35 +72,24 @@ Continue with the format of the object you used last week or improve it and refa
       a. Implement a watcher to periodically check a specific currency conversion and alert the user when the value reaches a speicfic point. Let's say the user is interested in converting USD to Danish kroner but the rate today is very bad, 1 USD is 5 DKK. We wan to alert the user when 1 USD is 7 DKK so the user can convert with maximum gain
       b. Watch currency updates and show a banner with the hotest currency exchange rate. I.e., currency conversion reaching the double value.
 
----
-
 ### `JS3 week1` - Json, Apis, Fetch
 
 - [ ] Follow the [API creation guide](/homework-projects/guides/making-your-API-guide.md) to make your own API that you will use from now on.
 - [ ] Refactor your code so that you use the currency rates dynamically from your API instead of the static array of objects.
 - [ ] Implement functionality to search for a specific currency.
 - [ ] Ensure all the functionality is working smoothly after refactoring.
 
----
-
 ### `JS3 week2` - Promises, Async/Await
 
 - [ ] You used promise chaining last week - now rewrite the fetch in the "async await" approach.
 - [ ] Testing. Implement a test to ensure that the application will work as expected after the refactoring.
 
----
-
 ### `JS3 week3` - Classes, Revision and Presentation of projects
 
 - [ ] Rest, revise JS fundamentals, finish, and brush up your project, prepare to present and explain it.
 - [ ] Make improvements to the style or functionality or add additional functionality.
 - [ ] Prepare to showcase your project to external people, talk through your code and explain what you have implemented.
 
----
-
-<br/>
-<br/>
-
 ## Project completion checklist ✅
 
 - [ ] I can insert a new currency rate

legacy/javascript/homework-projects/projects/memory-game/memory-game.md

@@ -2,7 +2,8 @@
 
 ![Agent J from "Men In Black": "Hey, don't even worry about it", while flashing the neuralyzer](https://media.giphy.com/media/374pcIBVEGb6g/giphy.gif)
 
-You joined an online game platform startup and your task is to build one of the small classic games. <br/>
+You joined an online game platform startup and your task is to build one of the small classic games.
+
 You will build a Memory Game, where a user needs to flip all the cards in a game in pairs until they find all the matching pairs. You aspire to make the game smooth and pleasant, so the user is compelled to spend more time playing it.
 
 > [!NOTE]

legacy/javascript/homework-projects/projects/movie-app/movie-app.md

@@ -1,4 +1,3 @@
-
 # MOVIE APP
 
 ![Garfield, slouched in a chair and changing the TV channel](https://media.giphy.com/media/KZe02gpoAj4yVjxKQt/giphy.gif)

legacy/javascript/homework-projects/projects/quiz-app/quiz-app.md

@@ -1,4 +1,3 @@
-
 # QUIZ APP
 
 ![Dexter from "Dexter's Laboratory" filling in some answers on a piece of paper](https://media.giphy.com/media/y1JYvLe9fFfpK/giphy.gif)
@@ -39,7 +38,6 @@ const quizQuestion = {
 };
 ```
 
-
 ### `JS2 week2` - Array functions, Arrow function
 
 Start with creating an array of quiz question objects. Even a small one is perfectly enough, but go as big as you want!
@@ -51,8 +49,6 @@ Continue with the format of the question object you used last week or improve it
 
 - [ ] build a function to filter the questions by searching the content of the question.
 
-
-
 ### `JS2 week3` - Callback function, Asynchronicity, Scope
 
 - [ ] add inputs for 2 player names and a button to start a quiz. When the quiz starts, player names are displayed with their collected points (0 to begin with).
@@ -65,7 +61,6 @@ b. add number inputs for the player points and use the browser's arrow buttons o
 
 - [ ] optional bonus: play a sound and end the quiz game when one of the players has reached 10 points.
 
-
 ### `JS3 week1` - Json, Apis, Fetch
 
 - [ ] follow the [API creation guide](/homework-projects/guides/making-your-API-guide.md) to make your own API that you will use from now on.
@@ -76,8 +71,6 @@ b. add number inputs for the player points and use the browser's arrow buttons o
 
 - [ ] add alphabetical sorting of the questions and random sorting of the questions and let the user choose.
 
-
-
 ### `JS3 week2` - Promises, Async/Await
 
 - [ ] you used promise chaining last week - now rewrite the fetch in the "async await" approach.

legacy/javascript/homework-projects/projects/recipe-app/recipe-app.md

@@ -1,4 +1,3 @@
-
 # RECIPE APP
 
 ![Spongebob Squarepants, doing some cooking](https://media.giphy.com/media/N23cG6apipMmQ/giphy.gif)
@@ -40,8 +39,6 @@ const recipeObject = {
 - [ ] Implement a form to add a new recipe with a minimum of 5 ingredients.
 - [ ] Optional: implement functionality to add a new ingredient to a recipe.
 
-
-
 ### `JS2 week2` - Array functions, Arrow function
 
 Start with creating an array of recipe objects. Even a small one is perfectly enough, but go as big as you want!
@@ -52,39 +49,31 @@ Continue with the format of the recipe object you used last week or improve it a
 - find a recipe by a provided search word to check in the recipe title.
 - sort the recipe array by the amount of ingredients needed.
 
-
-
 ### `JS2 week3` - Callback function, Asynchronicity, Scope
 
 - [ ] Implement a cooking timer where the time is user-picked via an input or hard-coded. The timer should alert and/or ring once the time is up.
 - [ ] Implement a timer for how much time you have spent on the page.
 
-
 ### `JS3 week1` - Json, Apis, Fetch
 
 - [ ] Follow the [API creation guide](/homework-projects/guides/making-your-API-guide.md) to make your own API that you will use from now on.
 - [ ] Refactor your code so that you ditch the static array of objects and instead fetch the recipes data from your API.
 - [ ] Implement functionality to search for an ingredient, fetch and display the relevant ingredient prices for a recipe
 - [ ] Ensure all the functionality is working smoothly after refactoring.
 
----
-
 ### `JS3 week2` - Promises, Async/Await
 
 - [ ] You used promise chaining last week - now rewrite the fetch in the "async await" approach.
 - [ ] Use the fuunctions created in preivous week and build functionality to:
 - [ ] Find a recipe by a provided search word to check in the recipe title.
 - [ ] Sort the recipe array by the amount of ingredients needed.
 
-
 ### `JS3 week3` - Classes, Revision and Presentation of projects
 
 - [ ] Rest, revise JS fundamentals, finish, and brush up your project, prepare to present and explain it.
 - [ ] Make improvements to the style or functionality or add additional functionality.
 - [ ] Prepare to showcase your project to external people, talk through your code and explain what you have implemented.
 
-
-
 ## Project completion checklist ✅
 
 - [ ] I can see a page with a list of recipes displayed in a grid;