Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE : Migrate CSS Styles to Tailwind CSS #133

Open
3 tasks done
prajwaln07 opened this issue Oct 9, 2024 · 1 comment · May be fixed by #149
Open
3 tasks done

FEATURE : Migrate CSS Styles to Tailwind CSS #133

prajwaln07 opened this issue Oct 9, 2024 · 1 comment · May be fixed by #149
Assignees
Labels

Comments

@prajwaln07
Copy link
Contributor

Feature Request: Convert Existing CSS to Tailwind CSS

Is your feature request related to a problem? Please describe.
Currently, the project uses standard CSS for styling, which can lead to inconsistency and make it more challenging to maintain. I'm always frustrated when I need to adjust styles across multiple files or components, as it takes more time and effort to ensure uniformity. Additionally, it increases the overall file size, making the project less optimized.

Describe the solution you'd like
I propose migrating the existing CSS styles to Tailwind CSS, a utility-first CSS framework. By using Tailwind CSS, we can:

  • Enhance the maintainability and readability of the codebase by utilizing utility classes directly in the JSX/TSX files.
  • Reduce the size of the final CSS output through Tailwind’s built-in purging mechanism, which removes unused styles.
  • Achieve faster styling iterations and a more consistent look and feel across the application.

Checklist

  • I am contributing under GSSoC-ext
  • I am contributing under Hacktoberfest
  • I follow the contribution guidelines
@prajwaln07
Copy link
Contributor Author

@divyansh-2005 please share your thoughts on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant