Initial Commit

Author: Utkarsh Mishra

.github/ISSUE_TEMPLATE/documentation_request.yml

@@ -0,0 +1,32 @@
+name: Feature request
+description: Suggest lesson, propose new data-structure and algorithms, discuss new ideas
+title: "[FEATURE] <description>"
+labels: ["⭐ goal: addition"]
+body:
+  - type: textarea
+    id: requesttype
+    attributes:
+      label: ⭐ Request Type
+      description: name of the lesson or section you wanted to add.
+    validations:
+      required: true
+  - type: textarea
+    id: location
+    attributes:
+      label: 💻 Location
+      description: |
+        Where you think your lesson should be placed(location) so that there will be ease in understanding for new comers.
+    validations:
+      required: true
+  - type: textarea
+    id: addtionalinfo
+    attributes:
+      label: ❌ Additional Info
+      description: |
+        If you have any additional information that you think will help the community.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        You can also join the Discord community [here](#)

.github/ISSUE_TEMPLATE/improvement_request.yml

@@ -0,0 +1,32 @@
+name: Feature request
+description: propose improvements, adding new code, or any new features
+title: "[FEATURE] <description>"
+labels: ["⭐ goal: addition"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: ⭐ Summary
+      description: A brief summary of what you'd like to see added or improved.
+    validations:
+      required: true
+  - type: textarea
+    id: location
+    attributes:
+      label: 💻 Location
+      description: |
+        Describe where or in which section/lesson you want to do improvements.
+    validations:
+      required: true
+  - type: textarea
+    id: additionalinfo
+    attributes:
+      label: ❌ Additional Info
+      description: |
+        Any additional information you'd like to provide.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        You can also join the Discord community [here](#)

.github/pull_request-template.md

@@ -0,0 +1,32 @@
+<!--
+(Thanks for sending a pull request!)
+-->
+
+<!-- Add the issue number that is fixed by this PR (In the form Fixes #123) -->
+
+Fixes #
+
+#### Short description of what this resolves:
+
+<!--- issue name --->
+
+#### What Changes proposed in this pull request:
+
+-
+-
+-
+
+#### Checklist
+
+<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->
+
+- [ ] Added description of change
+- [ ] Added file name matches [File name guidelines](https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/CONTRIBUTING.md#New-File-Name-guidelines)
+- [ ] Added code examples, test must pass
+- [ ] Added documentation so that the program is self-explanatory and educational.
+- [ ] Relevant documentation/comments is changed or added
+- [ ] PR title follows semantic [commit guidelines](https://github.com/Utkarsh1504/ds-algo/CONTRIBUTING.md#Commit-Guidelines)
+- [ ] Search previous suggestions before making a new one, as yours may be a duplicate.
+- [ ] I acknowledge that all my contributions will be made under the project's license.
+
+Notes: <!-- Please add a one-line description for developers or pull request viewers -->

.github/workflows/gatsby.yml

@@ -0,0 +1,24 @@
+name: Deploy Gatsby Site to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@master
+      - name: npm install, build, and csv
+        run: |
+          npm install
+          npm run build
+          npm run csv
+      - name: Deploy site to gh-pages branch
+        uses: crazy-max/ghaction-github-pages@v2
+        with:
+          target_branch: gh-pages
+          build_dir: public
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,8 @@
+# Project dependencies
+# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git
+node_modules
+.cache/
+# Build directory
+public/
+.DS_Store
+yarn-error.log

.prettierrc

@@ -0,0 +1 @@
+{}

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting a maintainer of the [project team members](https://github.com/orgs/dsa-java)
+or write a email to 'utkarshmishra73444@gmail.com'. All complaints will be reviewed and investigated and will result
+in a response that is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Contributing to DS-Algo
+
+First of all, thanks for taking the time to contribute! This project can only grow and live by your countless contributions. To keep this project maintainable, we have developed some guidelines for our contributors.
+
+Please note that by participating, you are expected to uphold the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Table of Content
+
+- [Terms](#terms)
+- [Lesson](#lesson)
+- [Requesting A Lesson](#requesting-a-lesson)
+- [Fixing Typos](#fixing-typos)
+- [Improving Lesson](#improving-lesson)
+- [Our Standards](#our-standards)
+- [Communication](#communication)
+
+---
+
+## Lesson
+
+The crux of this site is are the `lesson`. Provided are two examples. Each lesson needs a frontmattter path, order, and title. Generally you should make the path and the file name match for ease of finding it.
+
+- In `Lesson` directory there are various sections. You can start contributing from there.
+- Inside each of the sections `lesson` present in the form of markdown. If you wanted to add a new lesson make a new file with `.md` extension and add at the top it.
+
+```yml
+
+    ---
+    path: "/pathName"
+    title: "TitleName"
+    order: "<Number><CapitalLetter>"
+    section: "SectionName"
+    description: "Learn DS-Algo/C++"
+    ---
+```
+
+- Modify this according to your contribution and go ahead
+- For writing concepts, take a look at the other [lessons]('lesson/Learn-Programming-Language/operator.md') markdown and make sure it is written in a similar way.
+
+## Terms
+
+Here are some terms that we will use in this repo:
+
+- `path` needs a leading slash. This will be slug of the lesson
+- `title`- will be the title displayed on the `Table of Contents` and on the page itself
+- `order`- the order of which the item should appear in the table of contents. should in `<Number><Capital-letter>` format where the number corresponds to the section itself and the letter corresponds to the order of the lesson inside the section, e.g. 3B means under the section 3 and the order of the lesson will be B(second)
+- `section` - the title of the section that the article is in. Only the first lesson for each section will be used.
+- `description` - a one-to-three sentence summary of the lesson. used for the meta tag for social shares and SEO. if no description is given, the siteMetadata.description for the site is used.
+- `icon` the Font Awesome icon you want for the home page of the site
+
+## Requesting A Lesson
+
+for requesting a lesson simply raise a new issue in the `Issues` section.
+
+- Search for other issues already requesting the lesson.
+- If an issue doesn't exist, create an issue naming it `new lesson: <name-of-the-lesson>`
+- provide description as mentioned in issue template.
+- Please create separate issues for each icon
+
+## Fixing Typos
+
+for fixing typo just make a pull request with your fixes, naming it:
+
+- `fixed typo: <name-of-the-lesson>`
+- provide description as mentioned in pull request template.
+
+## Improving lesson
+
+for any improvement in the lesson raise a new issue in the <code>Issues</code> section, Naming it:
+
+- `improvement: <name-of-the-lesson>`
+- provide description as mentioned in issue template.
+- also one thing to keep in mind, if you wanted to do improvement in the lesson, It should be clear and easy to understand.
+
+## Our Standards
+
+Before you submit your PR, please ensure that they meet the following standard:
+
+- For writing the concept, take a look at the other [lessons]('lesson/Learn-Programming-Language/operator.md') markdown and make sure it is written in a similar way.
+- Content inside the lesson should not be copied or plagarized from any other resources, you need to write your own content using your understanding about the concept.
+- Code example should not copied from anywhere else, you should set example by your own.
+- for adding images and gifs related to the lesson, make sure it is copyright free and not used for commercial purpose. but in case you don't find any image or gif on internet, you can use the [draw.io](draw.io) to make your own images. Images and gif used should be kept in `lesson/images/` directory.
+
+## Communication
+
+We are running a communication channel. You can go here to talk, discuss, and more with the maintainers and other people, too. Here's the invitation: [discord](#)