Initial Steps in Migrating CSS to Tailwind for Footer Component

[prajwaln07]

🛠️ Fixes Issue

Closes #133

👨‍💻 Description

• This pull request addresses the ongoing migration of CSS styles to Tailwind CSS for the project.
• I have initiated the process by converting specific components, including the Footer component, to utilize Tailwind CSS classes instead of traditional CSS.
• This transition aims to enhance the maintainability and scalability of the project's styles, allowing for easier modifications and a more responsive design.

📄 Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (adds or updates related documentation)

📷 Screenshots/GIFs (if any)

Include screenshots or GIFs to demonstrate your changes

✅ Checklist

• I am a participant of GSSoC-ext.
• I have followed the contribution guidelines of this project.
• I have viewed deployment of my code.
• My changes generate no new warnings.
• I have added documentation to explain my changes.

🤝 GSSoC Participation

• This PR is submitted under the GSSoC program.
• I have taken prior approval for this feature/fix.

🛠️ Future Work

• Given the extensive nature of this migration, I plan to continue migrating remaining styles to Tailwind CSS in subsequent pull requests. This phased approach will help minimize conflicts and maintain project stability.

[netlify]

👷 Deploy request for finnews pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	71970ca

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
fin-news	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 12, 2024 11:12am
fin-news-backend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 12, 2024 11:12am

[prajwaln07]

@divyansh-2005

📝 Note on Conflicts

As I continue to migrate the CSS styles to Tailwind CSS, I anticipate that there may be potential conflicts with ongoing developments in the repository. To manage this, I plan to submit the migration in multiple stages, allowing for easier integration and resolution of conflicts.

I appreciate your understanding and am open to any suggestions on how to approach this transition smoothly.

[DiwareNamrata23]

@divyansh-2005 look on to it

[prajwaln07]

@DiwareNamrata23
hi @divyansh-2005 ,

Since the CSS to Tailwind CSS migration is quite extensive, I suggest proceeding in stages. This way, we can address potential conflicts and ensure a smoother transition. I’ll submit PRs for each component or section, review them incrementally, and resolve any issues as we go.

Let me know your thoughts!

Thanks! 😊