Skip to content

ci: Add Random Quote Generator with tsParticles Background and FreeAPI Integration#294

Open
Raijin-cyber wants to merge 5 commits into
hiteshchoudhary:mainfrom
Raijin-cyber:main
Open

ci: Add Random Quote Generator with tsParticles Background and FreeAPI Integration#294
Raijin-cyber wants to merge 5 commits into
hiteshchoudhary:mainfrom
Raijin-cyber:main

Conversation

@Raijin-cyber

@Raijin-cyber Raijin-cyber commented Aug 8, 2025

Copy link
Copy Markdown

✨ Random Quote Generator – Pull Request

🔗 Live Website: Random Quote Generator


🛠 Tech Stack

  • Vite + React – For a fast, modern frontend setup

  • 🎨 Tailwind CSS – For effortless and responsive styling

  • 🌌 tsParticles – For interactive background animation

  • 🌐 FreeAPI – Fetching quotes using getQuoteById endpoint


🌟 Features

  • Responsive Design – Works seamlessly across all devices

  • 🧠 Animated Abstract Background – Adds a dynamic and modern visual experience

  • 🎯 Attractive CTA Button – Gradient styled “Get Inspired!” button to fetch quotes

  • 📜 Clean Typography – Quotes are displayed in a legible and aesthetic format

  • 🔄 Dynamic Quote Fetching – Utilizes async API calls with robust error handling


🖼️ Screenshots

image Screenshot_20250808-191502_Chrome

Desktop View | Button Highlight -- | --   |  

📦 Improvements Included

  • Refactored the getQuote function for better readability

  • Added .env handling to abstract API URLs

  • Clean separation of logic and styling


🙌 Why This PR Should Be Merged

This PR is a complete, polished, and deploy-ready component of the application.
It demonstrates strong fundamentals of React, API integration, environment variable handling, and modern UI design with Tailwind CSS + tsParticles.

I'm open to feedback and excited to contribute further improvements or features as needed!

@Raijin-cyber Raijin-cyber changed the title Add Random Quote Generator with tsParticles Background and FreeAPI Integration ci: Add Random Quote Generator with tsParticles Background and FreeAPI Integration Aug 10, 2025

@wajeshubham wajeshubham left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not update.gitkeep file

@Raijin-cyber

Copy link
Copy Markdown
Author

Do not update.gitkeep file

Hey! I realized I accidentally deleted .gitkeep before initializing Git. I’d like to restore it with its original commit history so it doesn’t show up as modified in the PR. Could you guide me on the cleanest way to do that? I want to make sure I follow your structure exactly. Thanks!

@wajeshubham

Copy link
Copy Markdown
Collaborator

If its a part of a commit which has other changes, then just undo the deletion and commit the changes thats fine.

@Raijin-cyber

Copy link
Copy Markdown
Author

If its a part of a commit which has other changes, then just undo the deletion and commit the changes thats fine.

That .gitkeep file is not a part of the commit.
Should I create a new PR and a completely new repo again?

@Raijin-cyber

Copy link
Copy Markdown
Author

Sorry for the trouble. I am a beginner in open-source contributions.

@Raijin-cyber

Raijin-cyber commented Dec 1, 2025

Copy link
Copy Markdown
Author

Do not update.gitkeep file

Thanks for the feedback! Just to clarify — I added files to this folder as part of the feature, so it’s no longer empty. I removed the .gitkeep file as the repo wasn't empty anymore. I also reviewed other people's contributions to this API HUB, and none of them seem to keep the .gitkeep file, I guess.

According to the last commit's message of main branch of APIHUB, I have included the following information for you: I followed exactly:
feat: restructure the examples folder to make it well structured
- add frontend developers contribution guide
- add empty folders with gitkeep in examples folder for frontend contribution

Let me know what works best!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants