- The things that you need to know about JavaScript before diving into the rabit hole. I publish articles on Dev.to on the topics regularly. I will add the links here as soon as I publish them.
+ +
| [`Blog`](https://dev.to/fahimfba/learn-javascript-printing-your-first-message-2m04) | N/A |
+| **Day 2** - (19-04-2023) | Comments in JavaScript | 
| [`Blog`](https://dev.to/fahimfba/mastering-javascript-unraveling-the-art-of-effective-commenting-for-better-code-collaboration-46b) | N/A |
+
+
+Each topic/guide has its own separate Markdown file with detailed explanation which contanins text, screenshot, screen recording, GIF, etc.
-
-
-### Step 3 :
-
-Scroll down to the "*Features*" section. Under "Issues", click on "*Set up templates*".
-
-
-
-### Step 4 :
-
-Click on the *Add template* drop-down menu, and select the type of template you'd like to create
-- Bug report - This template is used to convey the detailed information about the bug to the developers.
-- Feature request - It is a document where developers make requests for a product in development.
-- Custom template - This template is completely user controlled and can be customized according to needs.
-
-
-
-### Step 5 :
-
-You can click on *Preview and edit* to view and edit the template.
-
-
-
-### Step 6 :
-
-Click on the pencil icon to edit the template and type in the fields to edit their contents.
-
-
-
-### Step 7 :
-
-Enter the information under "Optional additional information" to automatically set a default issue title, assign the issue to users with read access to the repository, or apply labels to your issue template. In a YAML format, you can also include these details in the issue template along with the title, labels, or assignees.
-
-
-
-### Step 8 :
-
-Click on *Propose changes* in the top right corner of the page once you're done altering and previewing your template.
-
-
-
-### Step 9 :
-
-Write a commit message summarizing the changes you made.
-
-
-
-### Step 10 :
-
-Choose whether to establish a new branch and launch a pull request or to commit your template directly to the default branch underneath the commit message boxes.
-
-
-
-### Step 11 :
-
-Click on *Commit changes*. The template will be accessible for contributors to use when they open new issues in the repository once these modifications are merged into the default branch.
-
-
diff --git a/pages/How-to/guide/adding-pr-template.md b/pages/How-to/guide/adding-pr-template.md
deleted file mode 100644
index b78b6ac..0000000
--- a/pages/How-to/guide/adding-pr-template.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Create a PR Template
-
-Creating a PR template makes it easy to clarify what the proposed changes will do and receive actionable feedback from your team. Having a custom template facilitates clear communication between all team members and ensures that everyone is on the same page.
-
-You can create a `PULL_REQUEST_TEMPLATE/ subdirectory` in any of the supported folders to contain multiple pull request templates, and use the template query parameter to specify the template that will fill the pull request body.
-
-### Steps to successfully create a PR Template :
-#### There are two steps ways in which you can create a PR Template:
-1. To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`:
-
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
- 
-
- 
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
-### Step 3
-
-Click on `Create a new release` 
-
-### Step 4
-
-Click on `Choose a tag` to choose a tag and `target:` to choose the branch you are targetting. 
-
-
-### Step 5
-
-Add a title and a description about the tag.
-
-### Step 6
-
-You can choose if it's a pre-release(non-production ready) 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-3. Scroll till the end of the page and under Danger Zone, click Delete this repository.
- 
-
-4. Read the warnings.
-
-5. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
- 
-
-6. Click I understand the consequences, delete this repository
-
-That's it. You have sucessfully Delete a github reository 🎉
diff --git a/pages/How-to/guide/fork-repo.md b/pages/How-to/guide/fork-repo.md
deleted file mode 100644
index 4b132db..0000000
--- a/pages/How-to/guide/fork-repo.md
+++ /dev/null
@@ -1,25 +0,0 @@
-## How to fork a repository
-
-First log into your github account and after finding the repo you want to copy or contribute to, do the following steps.
-
-### Step 1:
-- On the top right side of the project repository you can see the fork section.Click on the fork section.
-
-
-
-### Step 2:
-After clicking the Fork section, you will be seeing the following page.
-
-
-
-### Step 3:
-- By default the repository name is same as their parent name.
-- You can change the name of repository, if you want to customize it.
-
-### Step 4:
-- Click on the create fork(green) button to fork the repository.
-
-- Now you made the copy of repo in your own GitHub section. All the repo files and even the commit history is preserved in your GitHub.
-
-
-
diff --git a/pages/How-to/guide/github-pages.md b/pages/How-to/guide/github-pages.md
deleted file mode 100644
index 4769e34..0000000
--- a/pages/How-to/guide/github-pages.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# How github pages work?
-GitHub Pages is a static site hosting service that **takes HTML, CSS, and JavaScript files straight from a repository on GitHub, optionally runs the files through a build process, and publishes a website.**
-
-## Step by step process to publish a website using Github pages:
-
-### Step 1
-
-You should have a repository, if you don't go on [this](create-repo.md) page to know how to create a repository.
-
-### Step 2
-
-Now if your repository have an *"index.html"* file, then github understands what you want to do.
-
-### Step 3
-
-Go to repository in Github and click on settings.
-
-
-
-### Step 4
-
-Click on the *pages* option on the sidebar menu.
-
-
-
-### Step 5
-
-Select the *main* branch in dropdown menu for branch.
-
-
-
-and hit *Save*.
-Your Github pages source is saved.
-
-You can check the process happening in actions tab.
-
-
-
-and when the action gets completed.
-
-
-
-### Step 6
-
-Go back to *settings > pages* and click on *Visit site* to see the deployment.
-
-
-
-#### That's it. You have successfully deployed your website using github pages 🎉
diff --git a/pages/How-to/guide/linking-issue-with-pr.md b/pages/How-to/guide/linking-issue-with-pr.md
deleted file mode 100644
index fe733ae..0000000
--- a/pages/How-to/guide/linking-issue-with-pr.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# How to Link and Issue no with a PR ❓
-### Things to keep in 🧠
-> You can link up to **ten issues** to each pull request.
-
-> The issue and pull request must be in the **same repository**.
-
-## Linking an issue with a PR 🔗
-1. Open the PR in which you want to link the issue. ( Note: If you are a contributor you can only link an issue to your PR. Only maintainers can do with any PR.)
-2. In the *right sidebar*, in the "**Development**" section click ⚙️.
-
-
-
-
-
-
-
-
-## Observations 🔍
--> Issue is linked to the pull request shows as **Open** 🟢.
-
--> **Successfully merging this pull request may close this issue.** ✔️
-
--> Issue number shows in the pull request commit with `#[issue-number]`.
-
-
-
-## Results ✅
-
--> Now Merging the pull request will **automatically close the linked issue.** *(Requires a refresh sometime to reflect changes)*
-
-
-
-## Important Notes 🚨
-
--> Linking an issue can also be done while creating pull request by tag the issue number [#17](https://github.com/Pradumnasaraf/open-source-with-pradumna/issues/17).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 
- 
- 
- 
- 
- 
- 
- 
-
-
-
-
-
-
-
-
-
- 
- 
- 
- 
The things that you need to know about JavaScript before diving into the rabit hole. I publish articles on Dev.to on the topics regularly. I will add the links here as soon as I publish them.
- - | [`Blog`](https://dev.to/fahimfba/learn-javascript-printing-your-first-message-2m04) | N/A |
-| **Day 2** - (19-04-2023) | | [`Blog`](https://dev.to/fahimfba/mastering-javascript-unraveling-the-art-of-effective-commenting-for-better-code-collaboration-46b) | N/A |
\ No newline at end of file