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

Refactor: Replace Hardcoded Hex Colors with Custom Tailwind Color Templates #18

Open
6 of 10 tasks
VinuB-Dev opened this issue Jan 13, 2025 · 0 comments
Open
6 of 10 tasks
Assignees
Labels

Comments

@VinuB-Dev
Copy link

Issue Description

The current codebase contains hardcoded hex color values (e.g., #D0D5DD, #74777B, #4541C6, #F5F5FF) in the class names instead of using Tailwind CSS color classes or custom color templates. This reduces code consistency and increases maintenance effort.

Expected Behavior

All colors should use Tailwind CSS color classes or project-specific custom color templates to ensure:

  • Ease of updating the color palette in the future.
  • Improved readability and adherence to Tailwind CSS conventions.

Current Behavior

The code includes hardcoded hex color values such as #D0D5DD, #74777B, #4541C6, and #F5F5FF instead of Tailwind CSS color utilities or custom templates.

Screenshots

Screenshot 2025-01-13 at 6 18 12 PM

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Inspect the codebase for components where colors are hardcoded as hex values.
  2. Review the provided snippet to see an example of the issue.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

Tailwind CSS offers a robust color palette that supports most design needs. Additionally, custom color templates can be defined in the Tailwind CSS configuration file (tailwind.config.js) for colors not available in the default palette. This would align the code with project standards and reduce the risk of inconsistencies.

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants