Skip to content

[Feature] - Switch to ShadCN and TailwindCSS #80

@Yugveer06

Description

@Yugveer06

What feature would you like to see?

Feature Request: Switch to ShadCN and TailwindCSS

Description

Currently, we build all components and styles from scratch. Switching to ShadCN for UI components and TailwindCSS for styling will improve accessibility, reusability, and maintainability.

Motivation

  • Accessibility: ShadCN provides accessible components out of the box, which can avoid issues like [Bug] - Language selector dropdown not working as expected in Safari #76.
  • Reusability: Ready-to-use, customizable components streamline development.
  • Maintainability: TailwindCSS reduces CSS bloat and simplifies style management.
  • Consistency: Ensures a unified look and feel across the app.

Benefits

  • Improved accessibility
  • Faster development
  • Cleaner, maintainable code
  • Better scalability

Implementation

  1. Add TailwindCSS.
  2. Migrate components to ShadCN.
  3. Incrementally refactor styles and components.

Additional Context

ShadCN and TailwindCSS align with modern best practices, enhancing our development process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    futureMight implement in the future

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy