Page to Show Latest Technology Made at NASA

[DonaldReddy]

Title of Issue and Pull Request must be Same

Issue number

fixes: #157

Video/Screenshots (mandatory)

techport.mp4

Checklist:

• I have mentioned the issue number in my Pull Request.
• I have commented my code, particularly in hard-to-understand areas
• I have gone through the contributing.md file before contributing

Additional context:

I have created a page to show the latest projects happening at NASA, first, it shows the latest updated projects in the past week.
Users can click on load more to fetch projects, each click goes back a week.

I added Pagination to divide the projects into pages, each page shows 10 projects.

Users can search for projects by using a sticky search bar.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
cosmo-xplore	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 26, 2024 10:48am

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9250661	Triggered	Generic High Entropy Secret	0d524fe	src/components/DefaultDisplay/DefaultDisplay.jsx	View secret
9250661	Triggered	Generic High Entropy Secret	306b779	src/components/MarsRover/MarsRover.jsx	View secret
9250661	Triggered	Generic High Entropy Secret	306b779	src/pages/NasaProjects/NasaProjects.jsx	View secret
9250661	Triggered	Generic High Entropy Secret	79b0008	src/pages/NasaProjects/NasaProjects.jsx	View secret
9250661	Triggered	Generic High Entropy Secret	0d524fe	src/components/MarsRover/MarsRover.jsx	View secret
9250661	Triggered	Generic High Entropy Secret	27310b8	src/components/Apod/Apod.jsx	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}

[DonaldReddy]

@PranavBarthwal @surajvast1 please review this PR