Moving changes from main to deployment (#70)

* Add lazy loading attribute for image HTML elements

* This commit fixes #39 (#41)

* Contact Page updated ; Color scheme modifed

* Unused images removed ; Navbar navigation improved

* Made changes myself

---------

Co-authored-by: Aditya Raute <[email protected]>
Co-authored-by: Aditya Raute <[email protected]>

* Implemented a responsive grid gallery that gets images from a json file (#56)

* Implemented a responsive grid gallery that gets images from a json file

* added image gallery to activities page

* Update PULL_REQUEST_TEMPLATE.MD

* Delete PULL_REQUEST_TEMPLATE.md

* Fixed typos

* Change navbar and body text color to white (#60)

* Change navbar and body text color to white

* Change underline from #ccc to #fff

* Prettier workflow merging (#62)

* Create main.yml

* Sample commit

* Update and rename main.yml to .github/workflows/main.yml

* Update and rename main.yml to prettify.yml

* Update prettify.yml

* Update the git command

* Prettified Code!

---------

Co-authored-by: adityaraute <[email protected]>

* Prettified Code!

* CSS: fix font color on contacts page  (#66)

* CSS: fix font color on contacts page.

* CSS: Change font color to white on active list item.

* Create SECURITY.md

* Footer Fixed by changing CSS (#71)

* height changed for footer

* chnages some css to make contact page look better

* To achieve that, I have restrucuture the html to add body inside a div with class mainbody

* Updated Favicon (#73)

* Uniformity restored in bug report issue template (#76)

* feat: add Prettier (#72)

* feat(project): add initial package.json file

* chore(package): update package.json config

- Remove unnecessary fields (version, main, keywords, author, license)
- Add `sideEffects` field set to false to enable better bundling optimizations.
- Specify package as an ES module by setting the `type` field to "module".
- Mark the package as private to prevent accidental publication.

* feat(npm-config): enforce installation of exact version dependencies

Add `.npmrc` file with `save-exact` set to `true` to enforce that the exact versions of dependencies are saved in package.json

* chore(dependencies): add `prettier` and `prettier-plugin-packagejson` as dev. dependencies

* feat(project): add Prettier config file

* chore: add .gitignore and .prettierignore files

Add .gitignore and .prettierignore files to prevent 'node_modules' and 'package-lock.json' from being tracked by git and formatted by Prettier.

* feat(package-scripts): add linting and formatting npm scripts

Added new `lint` and `fix` scripts in the package.json, allowing for code linting and auto-fixing issues using Prettier.

It also includes `concurrently` as a dev. dependency enabling running multiple npm scripts in parallel.

* style: add formatting changes made by Prettier

* chore(dependencies): add husky and lint-staged for pre-commit hooks

This commit adds two new development dependencies to the project: `husky` and `lint-staged`. Husky is used to configure Git hooks, and lint-staged allows running linters on staged files in Git

* chore(husky): add 'prepare' script for husky install

This commit ensures that Husky's git hooks are installed after running `npm install`.

* feat(husky): add pre-commit hook

* feat(lint-staged): add code formatting on commit

Added `.lintstagedrc.js` with a default export setting up Prettier to run against all matched files. The `--ignore-unknown` flag allows Prettier to skip files it does not recognize.

* ci(github-actions): add `node` setup in prettify workflow

This commit updates the code formatting's workflow. The 'Checkout' action is upgraded from v3 to v4. Additionally, this update introduces the setup-node action, specifying the `lts` version of Node.js, followed by `npm ci` to install dependencies based on the lock file.

* feat(environment): specify lts version of node in package.json

This commit introduces a `.nvmrc` file with the version `20.10.0`, and updates the `package.json` to include both `engines` and `volta` fields that enforce the use of the long-term support (LTS) of Node.js.

* ci(workflow): add names to new CI steps

* chore(dependencies): update `prettier-plugin-packagejson` to 2.4.9

* Added checkbox for issue template (#79)

* Added would you like to work on this issue

* Added would you like to work on this issue

* Update .github/ISSUE_TEMPLATE/feature_request.md

Co-authored-by: Aditya Raute <[email protected]>

---------

Co-authored-by: Aditya Raute <[email protected]>

* Change logo on all pages

change logo to favicon

* Added links to the logo (#86)

* Added would you like to work on this issue

* Added would you like to work on this issue

* Update .github/ISSUE_TEMPLATE/feature_request.md

Co-authored-by: Aditya Raute <[email protected]>

* Update index.html

* Update gallery.html

* Update contact.html

* Update gallery.html

* Update activities.html

* full url to reletive path

---------

Co-authored-by: Aditya Raute <[email protected]>

* Delete gallery.html

Unnecessary and unused file

* Convert all Issue Templates to Issue Forms #81 (#89)

* Convert all Issue Templates to Issue Forms #81

* Convert all Issue Templates to Issue Forms #81

* Convert all Issue Templates to Issue Forms #81

* Convert all Issue Templates to Issue Forms #81

* Convert all Issue Templates to Issue Forms #81

* Add media queries for contact page (#90)

* fixes issue #78

change logo to favicon

* Fixes the issue-#84

Add media query for mobile screen

* Fixes the issue-#84

Changed the contact CSS page. removed
unwanted code.

---------

Co-authored-by: Agriya Khetarpal <[email protected]>
Co-authored-by: Ashutosh Kapoor <[email protected]>
Co-authored-by: Chilufya <[email protected]>
Co-authored-by: BulumkoJele <[email protected]>
Co-authored-by: adityaraute <[email protected]>
Co-authored-by: Suyog Kurlekar <[email protected]>
Co-authored-by: Nishar Miya <[email protected]>
Co-authored-by: SaiPreethamReddyy <[email protected]>
Co-authored-by: S A G A R <[email protected]>
Co-authored-by: Bryan Mendoza <[email protected]>
Co-authored-by: Adam Basha <[email protected]>
Co-authored-by: VJKUMAR <[email protected]>
Co-authored-by: Latish 705 <[email protected]>

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,54 @@
+name: 🐞 Bug
+description: File a bug/issue
+title: "[BUG]: <title>"
+labels: [Bug, Needs Triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: A concise description of what you're experiencing.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1. In this environment...
+      2. With this config...
+      3. Run '...'
+      4. See error...
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+      
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false
+- type: dropdown
+  id: browsers
+  attributes:
+    label: What browsers are you seeing the problem on?
+    multiple: true
+    options:
+      - Firefox
+      - Chrome
+      - Safari
+      - Microsoft Edge

.github/ISSUE_TEMPLATE/feature_report.yml

@@ -0,0 +1,55 @@
+name: 💡 General Feature Request
+description: Have a new idea/feature for rbjks? Let us know...
+title: "[FEATURE]: <description>"
+labels: ["enhancement"]
+body:
+  - type: checkboxes
+    id: duplicates
+    attributes:
+      label: Is this a unique feature?
+      description: Increase the chances of your issue being accepted by making sure it has not been raised before.
+      options:
+        - label: I have checked "open" AND "closed" issues and this is not a duplicate
+          required: true
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem/unavailable functionality? Please describe.
+      description: A clear and concise description of what the problem is (for example "I'm always frustrated when [...]").
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Proposed Solution
+      description: A clear description of the enhancement you propose. Please include relevant information and resources (for example another project's implementation of this feature).
+    validations:
+      required: true
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Please add screenshots of the before and/or after the proposed changes.
+    validations:
+      required: false
+  - type: dropdown
+    id: assignee
+    attributes:
+      label: Do you want to work on this issue?
+      multiple: false
+      options:
+        - "No"
+        - "Yes"
+      default: 0
+    validations:
+      required: false
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: If "yes" to above, please explain how you would technically implement this
+      description: For example reference any existing code
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        You can also join our Discord community [here]

.github/PULL_REQUEST_TEMPLATE.MD

@@ -1,13 +1,37 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Motivation and Context
+
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
 Fixes #
 
-Changes proposed 
+## Description
+
+<!--- Describe your changes in detail -->
+
+## How Has This Been Tested?
+
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+## Types of Changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 
--
--
--
+## Checklist:
 
-Test Methodology and Results
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
 
--
--
--
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.

.github/workflows/prettify.yml

@@ -0,0 +1,34 @@
+name: Prettier Action
+
+on: push
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: ${{ github.head_ref }}
+          # Make sure the value of GITHUB_TOKEN will not be persisted in repo's config
+          persist-credentials: false
+
+      - name: Commit URL
+        run: git remote set-url origin https://github-actions:${{github.token}}@github.com/rbjks/rbjks.github.io.git
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: lts/*
+          cache: npm
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Prettify Code
+        uses: creyD/[email protected]
+        with:
+          dry: false
+          github_token: ${{ secrets.PERSONAL_GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1 @@
+node_modules

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx lint-staged

.lintstagedrc.js

@@ -0,0 +1,3 @@
+export default {
+  '*': 'prettier --ignore-unknown --write',
+};

.npmrc

@@ -0,0 +1 @@
+save-exact=true

.nvmrc

@@ -0,0 +1 @@
+20.10.0

.prettierignore

@@ -0,0 +1,2 @@
+node_modules
+package-lock.json

.prettierrc.js

@@ -0,0 +1,7 @@
+// @ts-check
+
+/** @type {import("prettier").Config} */
+export default {
+  singleQuote: true,
+  plugins: ['prettier-plugin-packagejson'],
+};

CONTRIBUTING.md

@@ -1,51 +1,46 @@
 # Contributing Guidelines
 
-First of all thanks for spending your time to contribute or showing interest to contribute to this project :smiley: 
+First of all thanks for spending your time to contribute or showing interest to contribute to this project :smiley:
 
 This documentation contains a set of `Guidelines` and `Steps` to help you during the contribution process.
 
-
-
 # 🔑 Guidelines for contributing :
 
 Here are some set of guidelines to follow while contributing to `rbjks.github.io` :
 
 1. Welcome to this repository, if you are here as an open-source program participant/contributor.
 2. Participants/contributors have to **comment** on issues they would like to work on, and mentors or the maintainers will assign you.
 3. Issues will be assigned on a **first-come, first-serve basis.**
-4. Participants/contributors can also **open their issues**, but it needs to be verified and labelled by a mentor. We respect all your contributions, whether it is an Issue or a Pull Request.
-5. Please check if the issue you want to is already listed, If its **already listed** chat in the comments to figure out whether someone is working on it or not, If issue is not listed then you can raise an issue, make sure you get it **assigned** to you before you start working on that project.A
+4. Participants/contributors can also **open their issues**. We respect all your contributions, whether it is an Issue or a Pull Request.
+5. Please check if the issue you want to is already listed, If its **already listed**, chat in the comments to figure out whether someone is working on it or not. If issue is not listed then you can raise an issue, make sure you get it **assigned** to you before you start working on that project.
 6. Please don't pick up an issue already assigned to someone else. Work on the issues after it gets **assigned to you**.
 7. Create your file in an appropriate folder with appropriate name and extension.
 8. Pull requests will be merged after appropriate reviews.
 9. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.
 
-
-
-
 # ▶️ Steps for contributing :
+
 ## Fork this repository
+
 <img align="right" width="300"  alt="image" src="https://user-images.githubusercontent.com/110724849/230174676-887cfddf-0c2d-4811-9aa1-0758af091c6b.png">
 
 <br>
 Fork this repository by clicking on the fork button on the top of this page.
 This will create a copy of this repository in your account.
 
-
 ## Clone This Repository
 
 <img  align="right" width="200" src="https://user-images.githubusercontent.com/110724849/230175272-c713e91d-f5bf-4cc3-8e37-b36f5d6881fb.png">
 
-Now clone the forked repository to your machine. 
+Now clone the forked repository to your machine.
 Go to your GitHub account, open the forked repository, click on the code button and then click the copy to clipboard icon.
 
-
 Open a terminal and run the following git command:
+
 ```
 git clone https://github.com/<Your-Github-username>/rbjks.github.io.git
 ```
 
-
 ## Create a branch
 
 Change to the repository directory on your computer (if you are not already there):
@@ -67,23 +62,29 @@ git checkout -b add-new-feature
 ```
 
 ## Make necessary changes and commit those changes
+
 If you go to the project directory and execute the command `git status`, you'll see there are changes.
 
 Add those changes to the branch you just created using the git add command:
 
 ```
 git add .
 ```
+
 Now commit those changes using the git commit command:
 
 ```
 git commit -m "Your commit message"
 ```
+
 ## Push changes to GitHub
+
 Push the changes to the forked repository using:
+
 ```
 git push origin <Your-branch-name>
 ```
+
 Navigate to the original fork of this repository on your profile and click on the branch you had committed to.
 Then click on Contribute to create a Pull Request i.e create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)
 
@@ -92,6 +93,7 @@ Then click on Contribute to create a Pull Request i.e create a PR on Github. (Do
 ## Are you a beginner in using Github?
 
 You can refer to the following articles on the basics of Git and Github and also contact me, in case you are stuck:
+
 - [Forking a Repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo)
 - [Cloning a Repo](https://help.github.com/en/desktop/contributing-to-projects/creating-an-issue-or-pull-request)
 - [How to create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github)