Enhancement: Replacement from Normal CSS to Talwind CSS

## Description
The project currently uses traditional CSS stylesheets for UI styling. To improve consistency, maintainability, and development speed, we propose migrating the existing styling approach to **Tailwind CSS**, a utility-first CSS framework.

## Current State
- Styles are written using standard CSS files.
- UI styles are spread across multiple CSS files.
- Reusability and consistency require manual enforcement.

## Proposed Change
- Replace existing CSS styles with **Tailwind CSS utility classes**.
- Gradually refactor components to use Tailwind instead of custom CSS.
- Remove unused or redundant CSS after migration.

## Why This Change Is Beneficial
- Faster UI development with utility-first styling
- Improved design consistency across components
- Reduced CSS bloat and unused styles
- Easier onboarding for contributors familiar with Tailwind
- Better scalability as the project grows

## Expected Outcome
- The application UI remains visually consistent with the current design
- Styling is fully handled via Tailwind CSS utilities
- Improved maintainability and contributor experience

## Additional Context
This change is primarily a **refactor/enhancement** and does not introduce new features.
It can be tackled incrementally and is suitable for contributors with basic Tailwind knowledge.