Added 404 page

[Jagpreet153]

Related Issue

254

Description

I have added animation in 404 page

Type of PR

• [x] Feature enhancement

Screenshots / videos (if applicable)

Checklist:

• [x] I have performed a self-review of my code
• [x] I have read and followed the Contribution Guidelines.
• [x] I have tested the changes thoroughly before submitting this pull request.
• [x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
• [x] I have commented my code, particularly in hard-to-understand areas.

Additional context:

Kindly add relevant labels to this PR

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
kaam-do	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 20, 2024 11:55am

[github-actions[bot]]

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! 😊

[PatilHarshh]

conflicts

[Jagpreet153]

conflicts

Resolved conflicts

[PatilHarshh]

[gitguardian[bot]]

⚠️ 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.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [11775317](https://dashboard.gitguardian.com/workspace/557539/incidents/11775317) | Triggered | Generic High Entropy Secret | 9a22bf8da99c45e648436d4bcf89acd1774104f0 | client/dist/assets/index-1f76e8ca.js | [View secret](https://github.com/PatilHarshh/Kaam-Do/commit/9a22bf8da99c45e648436d4bcf89acd1774104f0#diff-9b549d38729ade3223a624c409cd3f5dcf6cd685d44ef5e3709dd73689aed465R21) |

🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.}

[Jagpreet153]

@PatilHarshh Kindly review it now