[First Timers Only] Improve Responsiveness of Front Page Component Containers

[danielmarv]

🐥 First Timers Only – Good First Issue

This issue is reserved for new contributors to this repository or anyone who is new to open source in general.
We understand that making your first pull request (PR) can be overwhelming, and we're here to help!

The purpose of this issue—and others labeled with good first issue—is to guide you through your first open-source contribution.

---

👾 Issue Description

Improve Responsiveness of UI Components in ClyCites-Frontend/ClyCites

Some components on the ClyCites website are not fully responsive, especially on smaller screen sizes like mobile and tablets. This affects user experience on devices with limited screen width.

Please improve the responsiveness of the following components (or explore and identify more):

• Navigation bar
• Hero section
• Footer

Focus on using responsive Tailwind CSS classes and flex/grid layouts to ensure components adapt gracefully across breakpoints.

---

✅ Suggested Solution

• Identify the affected components under ClyCites-Frontend/ClyCites.
• Modify the relevant layout or style files to use responsive classes (sm:, md:, lg: etc.) where appropriate.
• Test the responsiveness using browser DevTools or tools like Responsively App.

---

📋 Step-by-Step Guide to Contribute

1. Comment below to claim this issue.

2. Wait for a maintainer to assign it to you.

3. Fork the repo, then clone your fork locally.

4. Create a new branch:

    git checkout -b issue-xxx-improve-responsive-ui
   

🛠️ Implement the Fix

• Inspect components with responsiveness issues.

• Use appropriate responsive CSS classes (Tailwind recommended).

• Test changes on multiple screen sizes.

• Commit your changes:

  git commit -s -m "fix: improve responsiveness for navbar and footer components"
  

• Ensure your commit is signed off with -s to comply with the Developer Certificate of Origin.

• Push your branch to your forked repository:

  git push origin issue-xxx-improve-responsive-ui
  

• Open a Pull Request (PR) to the main repository.

• Monitor GitHub Actions for checks. Ask for help if something fails.

• Address review feedback if any.

• Once approved, a maintainer will merge your PR.

• Celebrate your first contribution! 🎉

[lucasmquinteros]

Hi! I'm interested in working on this issue. I’d like to start with just one section first — maybe the footer or the navbar — to get familiar with the project and make sure I can contribute effectively.

Is that okay? Also, is there any deadline I should keep in mind?

Thanks!

[danielmarv]

@lucasmquinteros
it ok you can go throught the it incase you need any help feel free to post it here

[ade-tech]

Hello can I also contribute to this

[olivierndanyuzwe]

Assign me the issue

[lunar2903]

I will like to contribute to your project to gain experience in open source contributions, please let me know if we can work together