Updated home.css

[1754riya]

Related Issue

@dhairyagothi, please merge PR.

[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
write issue no. here

Email id used to regsiter for VSoc'24

[email protected]

Description

[Please include a brief description of the changes or features added]

Type of PR

• Bug fix
• Feature enhancement
• Documentation update
• Security enhancement
• Other (specify): _______________

check in issue by entering [X] in boxes

Screenshots / Videos (if applicable)

[Attach any relevant screenshots or videos demonstrating the changes]

Checklist

• I have performed a self-review of my code.
• I have read and followed the Contribution Guidelines.
• I have tested the changes thoroughly before submitting this pull request.
• I have provided relevant issue numbers, screenshots, and videos after making the changes.
• I have commented my code, particularly in hard-to-understand areas.
• I have followed the code style guidelines of this project.
• I have checked for any existing open issues that my pull request may address.
• I have ensured that my changes do not break any existing functionality.
• Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
• I have read the resources for guidance listed below.
• I have followed security best practices in my code changes.

check in issue by entering [X] in boxes

Additional Context

[Include any additional information or context that might be helpful for reviewers.]

Contribution Guidelines

Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:

Issue Creation

1. Limit on Issues:
   • Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

2. Basic Contributions:

   • This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
   • For these tasks, issues will be assigned the Easy label.

3. Acknowledging Hard Work:

   • If a contributor puts in significant effort on a task, the issue will be upgraded to Medium. This is our way of recognizing and appreciating extra effort.

4. Feature Additions and Component Work:

   • Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
   • The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

• Easy:
  • Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.
• Medium:
  • Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.
• Hard:
  • Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
50-days-50-web-project	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 13, 2024 0:38am

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13030270	Triggered	Generic High Entropy Secret	2a090bc	public/Word_dictionary/app.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[dhairyagothi]

good @1754riya merged

[github-actions]

🎉 Your pull request has been successfully merged! 🎉 Thank you for your valuable contribution to our project. Your efforts are greatly appreciated. Feel free to reach out if you have any more contributions or if there's anything else we can assist you with. Keep up the fantastic work! 🚀