This Repo is meant to be Open source, I'm looking for an experienced OS contributor/maintainer to help me license these repo.

Please add a blurb with the licence that you add and why you picked it.

Add course content for "Debugger tools".

Overview

This module is intended to cover the basics of the debugger tools in the browser. How to view the page's sources, how to navigate the DOM and observe changes made to styles, the Javascript console and its ability to interact with the DOM, observing HTTP requests on the network tab, and how applications and websites store session data in the browser.

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

All content must be added to the debugger folder.

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

Please update the links in the table of contents in the main README.md file as part of your PR.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- debugger
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets 
 |    |-- exercises
 |    |     |--> Topic specific exercises (if any) 

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to include references to the original source will be removed or declined.

Improve diagrams on client-server topic

Overview

Better, prettier and more descriptive diagrams are needed for the client-server topics.

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- 1_clientServer
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to include references to the original source will be removed or declined.

Add course content for the topic "Understanding the browser"

Overview

This module is intended to cover the basics of how the browser works. The nomenclature of the URL, how the browser makes and handles requests, and how content is interpreted and presented to the end-user. A visual representation of the lifecycle (from entering the URL to rendering the content) of a browser request would be great!

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

All content must be added to the browser folder.

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

Please update the links in the table of contents in the main README.md file as part of your PR.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- browser
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets 
 |    |-- exercises
 |    |     |--> Topic specific exercises (if any) 

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to provide references to the original source will be removed or declined.

Add course content for Basic HTTP.

Overview

This module is intended to cover the basics of HTTP. It's intended to cover the different types of requests, status codes and an overview of the anatomy of an HTTP request and response. What differentiates HTTP from HTTPS and why do we care about HTTPS.

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

All content must be added to the http folder.

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

Please update the links in the table of contents in the main README.md file as part of your PR.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- http
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets 
 |    |-- exercises
 |    |     |--> Topic specific exercises (if any) 

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to include references to the original source will be removed or declined.

Add course content for The DOM.

Overview

This module is intended to cover the basics of the document object model (DOM), why the dom is needed, how nodes are organized in the DOM and introductory content for the building blocks of web pages (HTML, CSS and Javascript).

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

All content must be added to the dom folder.

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

Please update the links in the table of contents in the main README.md file as part of your PR.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- dom
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets 
 |    |-- exercises
 |    |     |--> Topic specific exercises (if any) 

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to provide references to the original source will be removed or declined.

Add course content for the Client-Server Model.

Overview

This module is intended to cover the basics of the client-server model. How clients and servers share information. The flow of information using requests and responses and the role of web apps (and mobile apps) within the model.

Guidelines

Partial contributions are welcome! You are not expected to cover or provide all the content for this topic, all types of contributions are encouraged!

You are encouraged to take credit for your contribution, drop your name in the list of contributors for each topic (found in the topic's readme.md file)

All content must be added to the clientServer folder.

When submitting your PR, if possible, provide a rough estimate of how long it will take to consume the content.

File structure

When creating course content, please use the following file structure.

 Introduction-to-the-web
 |-- assets
 |    |--> Module's common images and files
 |-- clientServer
 |    |-- readme.md -> topic content
 |    |-- assets
 |    |     |--> Topic specific assets 
 |    |-- exercises
 |    |     |--> Topic specific exercises (if any) 

On contributing content and Plagiarism

Please be mindful with the content you include. If you quote or use content created by someone else, always give credit to the original author and make sure that you have their permission to share their content.

Contributions that copy commercial courses, or that fail to provide references to the original source will be removed or declined.