Fixed linter issues

markitosha · markitosha · commit 93b293c75860 · 2025-05-12T09:28:34.000+02:00
diff --git a/proposals/js-node-restructure.md b/proposals/js-node-restructure.md
@@ -1,10 +1,10 @@
-## 📘 JavaScript & Node.js Module Restructuring Plan Proposal
+# 📘 JavaScript & Node.js Module Restructuring Plan Proposal
 
-### 🎯 Goal
+## 🎯 Goal
 
 To restructure existing JavaScript and Node.js content into a new modular curriculum across three tracks: **Foundation**, **Frontend Specialism**, and **Backend Specialism**. The focus is on reuse, clarity, and separating concerns between frontend and backend education.
 
-This is schemas for current module structures. I will use the same **color-coding** for the parts of new modules, so it would be obvious where is this topic is coming from. You can also use the attached file to have interactive schemas in [draw.io ](https://app.diagrams.net/)
+This is schemas for current module structures. I will use the same **color-coding** for the parts of new modules, so it would be obvious where is this topic is coming from. You can also use the attached file to have interactive schemas in [draw.io](https://app.diagrams.net/)
 
 [Click to dowload hyf.drawio.zip](https://github.com/user-attachments/files/19875331/hyf.drawio.zip)
 
@@ -38,7 +38,7 @@ This is schemas for current module structures. I will use the same **color-codin
 **Source**: copy of JavaScript 1\
 **Purpose**: Establish fundamental JavaScript knowledge. Teaches only one way to solve problems, no advanced topics or multiple approaches.
 
-#### Topics:
+#### Topics for General JavaScript
 
 - **Week 1**: Intro JS, Types, Setup, Operators, console.log, Errors, Variables
 - **Week 2**: Conditions, Functions, Scope, For loop
@@ -47,7 +47,7 @@ This is schemas for current module structures. I will use the same **color-codin
 
 ![Image](https://github.com/user-attachments/assets/03dd07df-6bb7-48a4-9aeb-053744da16af)
 
-#### Final Week Homework Note:
+#### Final Week Homework Note
 
 Introduce small reusable logic/function tasks already in the final week (e.g., calculating prices, transforming arrays) and encourage saving the code — these will be reused in API or frontend in later modules.
 
@@ -57,7 +57,7 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 **Purpose**: Introduce shared concepts between frontend and backend. Creates a unified mental model before Introductions for specialisations and removes duplicates from modules (like API explanations).\
 **Note**: It, probably, will require some new material there (we didn’t have architecture before), but we can always just stick to the topics that was introduced before in old modules.
 
-#### Topics [not limited to]:
+#### Topics for Web Architecture 101 [not limited to]
 
 - Client vs Server
 - What is Backend?
@@ -74,15 +74,15 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 
 **Duration**: 1 week\
 **Purpose**: Provide a hands-on primer to backend development. Enables learners to build a basic working backend (simple CRUD server or even less).\
-**Reasoning**: Placing backend first in hands-on development allows learners to apply their JavaScript fundamentals while reinforcing their understanding of APIs introduced in Web Architecture 101. This progression is both natural and confidence-building: learners already know how to write logic, and now they can wrap it in endpoints (basically, another level of functions). Starting here also clarifies the API  before they consume it from the frontend side.
+**Reasoning**: Placing backend first in hands-on development allows learners to apply their JavaScript fundamentals while reinforcing their understanding of APIs introduced in Web Architecture 101. This progression is both natural and confidence-building: learners already know how to write logic, and now they can wrap it in endpoints (basically, another level of functions). Starting here also clarifies the API before they consume it from the frontend side.
 
-#### Topics:
+#### Topics for Introduction to Backend
 
 - Intro to Node.js
 - Simple web server
 - Using Postman to test endpoints
 - CRUD implementation (focus on code, not theory)
-- *Optional*: Basic DB interaction (since we have a module, but not necessary)
+- _Optional_: Basic DB interaction (since we have a module, but not necessary)
 - Optional: Introduce a simple one-click deployment path
 
 ![Image](https://github.com/user-attachments/assets/e7516502-8137-40d0-ba8c-3999a417c408)
@@ -92,17 +92,17 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 **Duration**: 1 week\
 **Purpose**: Demonstrate how JavaScript is used on the frontend, how to interact with DOM and how to interact with APIs from the browser.
 
-#### Topics:
+#### Topics for Introduction to Frontend
 
 - Browser environment (HTML vs CSS vs JS, script tag placement, debugging)
 - DOM manipulation basics
 - Event listeners (focus on usage, no callback explanation)
 - `fetch()` for calling APIs (usage only — promises explained later)
-- *Optional*: Introduce a simple one-click deployment path
+- _Optional_: Introduce a simple one-click deployment path
 
 ![Image](https://github.com/user-attachments/assets/aab89368-8620-4ede-a0ed-3ce5575435bc)
 
-### Open Questions:
+### Open Questions
 
 - **Deployment**: Should we provide guided deployment in Introduction modules? Just instructions, so they would be able to use them for Foundation Final Project.
 
@@ -117,7 +117,7 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 **Duration**: 4 weeks\
 **Purpose**: Deepen JavaScript knowledge with modern concepts and patterns used in both frontend and backend development. This module is part of both the Frontend and Backend Specialisation tracks. While topics are shared, examples and homeworks must be tailored per track.
 
-#### Topics:
+#### Topics for Advanced JavaScript
 
 - **Week 1**: Array functions, Arrow functions
 - **Week 2**: Callback functions, Asynchronicity, Scope
@@ -126,12 +126,12 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 
 ![Image](https://github.com/user-attachments/assets/2d61e291-0abd-42a6-9eca-43ee38bb4bfb)
 
-#### Track-specific differentiation:
+#### Track-specific differentiation
 
 - **Frontend Specialism**: Browser-based examples (e.g., DOM tasks, UI-based async data fetching)
 - **Backend Specialism**: Server-based examples (e.g., file handling, API response management)
 
-#### To do:
+#### To do for Advanced JavaScript
 
 - Rethink the final assignment structure and integration with broader project.
 
@@ -144,7 +144,7 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 **Duration**: 2 weeks\
 **Purpose**: Expand learners’ backend development capabilities using Node.js and Express. Builds on Introduction to Backend with more advanced tooling, patterns, and responsibilities.
 
-#### Topics:
+#### Topics for Node.js
 
 - **Week 1**:
   - Express (intro, routing, logging, debugging)
@@ -161,7 +161,7 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 
 - Can optionally have an additional week to include advanced backend topics that was proposed in previous dicussions
 
-#### To do:
+#### To do for Node.js
 
 - Rethink the final assignment structure and integration with broader project.
 
@@ -171,8 +171,8 @@ Introduce small reusable logic/function tasks already in the final week (e.g., c
 
 > Should we introduce js module/import/export concept in foundation or not?
 
-*Option 1*: It might be natural to introduce separate files in «Introduction to Backend», and then mention in «Introduction to Frontend» how it is solved there.
+_Option 1_: It might be natural to introduce separate files in «Introduction to Backend», and then mention in «Introduction to Frontend» how it is solved there.
 
-*Option 2*: Introduce idea of structuring files (and import/export) on «Web Architecture 101» session.
+_Option 2_: Introduce idea of structuring files (and import/export) on «Web Architecture 101» session.
 
-*Option 3*: Not to give this concept in Foundation, because it seems like it can be done in one file, and later they will have to have separate files in React / Node anyway.
+_Option 3_: Not to give this concept in Foundation, because it seems like it can be done in one file, and later they will have to have separate files in React / Node anyway.
