Merge pull request #12 from ReCoded-Org/m2-content-expansion

Module 2 content expansion

Author: Shrreya

README.md

@@ -18,7 +18,7 @@ This serves as a content monorepo for all the readings of the backend bootcamp c
 |       | README.md
 |   └───...                         // and so on
 |
-└───module2-database-technologies
+└───module2-databases
 |   └───assets                      // common assets folder for module
 │   └───r1-introduction-to-databases
 |       | README.md                 // reading content goes here

module1-introduction-to-backend/README.md

@@ -1,6 +1,6 @@
 # Module 1: Introduction to Backend
 
-Last Revised: 05/10/2021
+Last Revised: 14/10/2021
 
 ## Summary
 Writing backend code requires an intimate understanding of REST and the request-response lifecycle. Students learn how to build and run a local server with API endpoints
@@ -13,7 +13,7 @@ validations and return a response.
 
 1.1 [Beginners guide to Node.js and NPM [R]](../module1-introduction-to-backend/r1.1-beginners-guide-nodejs-npm/README.md)
 
-1.2 [Getting ready with Node.js [L]](../module1-introduction-to-backend/r1.2-getting-ready-with-nodejs/README.md)
+1.2 [Getting started with Node.js [L]](../module1-introduction-to-backend/r1.2-getting-started-with-nodejs/README.md)
 
 2 [HTTP and REST [R]](../module1-introduction-to-backend/r2-http-and-rest/README.md)
 
@@ -37,4 +37,4 @@ validations and return a response.
 
 5.1 [API Documentation using Swagger [L]](../module1-introduction-to-backend/r5.1-api-documentation-swagger/README.md)
 
-6 [Outro](../module1-introduction-to-backend/r6-outro/README.md)
+6 [Summary [R]](../module1-introduction-to-backend/r6-summary/README.md)

module1-introduction-to-backend/assets/README.md

@@ -1,7 +1,7 @@
 # Introduction to Backend
 Welcome to your first lesson of the Backend Web Development Bootcamp! The objectives of this lesson are:
 1. To understand the roles of frontend developer vs backend developer vs fullstack developer
-2. To get familar with the basics of backend web architecture
+2. To get familiar with the basics of backend web architecture
 
 Here we go!
 

module1-introduction-to-backend/r1-introduction-to-backend/README.md

@@ -53,6 +53,7 @@ Node.js is written with C, C++ and JavaScript and uses libuv underhood to handle
 
 <img src="https://drive.google.com/uc?export=view&id=18ys74BkK9tzQ6u8avgVw9seweoXY6GnA" width="60%">
 
+
 ### NPM and Packages in Node.js
 One of the major factors of Node's success is npm - its popular package manager, which allows JavaScript developers to share useful packages quickly and easily. NPM – or "Node Package Manager" – is the default package manager for JavaScript's runtime Node.js. NPM consists of two main parts:
 - a CLI (command-line interface) tool for publishing and downloading packages, and
@@ -95,7 +96,7 @@ Also, as asynchronous programming is the core of Node.js it is important to unde
 If you're interested to dive deeper into understanding Node.js, [here](https://nodejs.dev/learn/introduction-to-nodejs) is a learning path that you can follow.
 
 ## Why are we teaching Node.js in this bootcamp?
-From the previous lesson or previous experience, you might already be familar with other server-side languages like Python, PHP, Ruby or Java. So why did we choose to teach Node.js?
+From the previous lesson or previous experience, you might already be familiar with other server-side languages like Python, PHP, Ruby or Java. So why did we choose to teach Node.js?
 
 1. **Popularity**: Node.js has been consistently growing in popularity since it's introduction. As per the [Stackoverflow developer survey of 2021](https://insights.stackoverflow.com/survey/2021), JavaScript is the most popular language for 9 years in a row and Node.js has moved up to be the 6th most popular technology. Many companies that we have got in touch with have expressed interest in hiring more Node.js developers.
 2. **Modern tech stack choice**: With the web being focussed more towards real-time user interaction, and serving web apps over websites, Node.js with its features is becoming the go-to choice for many tech companies.
@@ -110,6 +111,7 @@ Now that you have enough context on Node.js, let's prepare our coding environmen
 - https://medium.com/jspoint/introduction-to-node-js-a-beginners-guide-to-node-js-and-npm-eca9c408f9fe
 - https://en.wikipedia.org/wiki/Node.js
 - https://www.simplilearn.com/tutorials/nodejs-tutorial/what-is-nodejs
+- https://www.simform.com/blog/what-is-node-js/#section2
 - https://www.freecodecamp.org/news/what-is-npm-a-node-package-manager-tutorial-for-beginners/
 - https://nodejs.dev/learn/introduction-to-nodejs
 - https://medium.com/jspoint/how-javascript-works-in-browser-and-node-ab7d0d09ac2f

module1-introduction-to-backend/r1.1-beginners-guide-nodejs-npm/README.md

@@ -0,0 +1,3 @@
+# Getting started with Node.js
+
+[Assignment repo link](https://github.com/ReCoded-Org/curriculum-backend-getting-started-nodejs)

module1-introduction-to-backend/r1.2-getting-started-with-nodejs/README.md

@@ -67,7 +67,7 @@ HTTPS uses an encryption protocol called [Transport Layer Security (TLS)](https:
 1. **Private key**: This key is controlled by the owner of a website and it's kept, as you might have guessed, private. This key lives on a web server and is used to decrypt information encrypted by the public key.
 2. **Public key**: This key is available to everyone who wants to interact with the server in a way that's secure. Information that's encrypted by the public key can only be decrypted by the private key.
 
-HTTPS prevents websites from having their information broadcast in a way that's easily viewed by anyone snooping on the network. When information is sent over regular HTTP, the information is broken into packets of data that can be easily “sniffed” using some software tools. This makes communication over an unsecure medium, such as public WiFi in a cafe, highly vulnerable to interception. In fact, all communications that occur over HTTP occur in plain text, making them highly accessible to anyone with the correct tools, and vulnerable to on-path attacks.
+HTTPS prevents websites from having their information broadcast in a way that's easily viewed by anyone snooping on the network. When information is sent over regular HTTP, the information is broken into packets of data that can be easily "sniffed" using some software tools. This makes communication over an unsecure medium, such as public WiFi in a cafe, highly vulnerable to interception. In fact, all communications that occur over HTTP occur in plain text, making them highly accessible to anyone with the correct tools, and vulnerable to on-path attacks.
 
 With HTTPS, traffic is encrypted such that even if the packets are sniffed or otherwise intercepted, they will come across as nonsensical characters.
 

module1-introduction-to-backend/r2-http-and-rest/README.md

@@ -1,3 +1,3 @@
 # Testing APIs with Postman
 
-Assignment repo link to be inserted
+[Assignment repo link](https://github.com/ReCoded-Org/curriculum-backend-api-postman)

module1-introduction-to-backend/r2.2-testing-apis-with-postman/README.md

@@ -1,3 +1,3 @@
 # Express.js Meme Website
 
-Assignment repo link to be inserted
+[Assignment repo link](https://github.com/ReCoded-Org/curriculum-backend-expressjs-meme-website)

module1-introduction-to-backend/r3.1-expressjs-meme-website/README.md

@@ -1,3 +1,3 @@
 # Express.js Meme API
 
-Assignment repo link to be inserted
+[Assignment repo link](https://github.com/ReCoded-Org/curriculum-backend-expressjs-meme-api)