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

Assess the Feasibility of Migrating to Tailwind #118

Open
Vinyl-Davyl opened this issue Nov 30, 2024 · 5 comments
Open

Assess the Feasibility of Migrating to Tailwind #118

Vinyl-Davyl opened this issue Nov 30, 2024 · 5 comments

Comments

@Vinyl-Davyl
Copy link
Collaborator

Feature Request 🛍️

Create a roadmap for transitioning from Ant-UI to Tailwind CSS. Highlight key steps (e.g., component mapping, theme building, phasing out Ant-UI).

Use Case

The goal of this feature is to improve the flexibility, customizability, and maintainability of the Template Playground's styling framework. Ant-UI provides pre-styled components with limited customization options, while Tailwind CSS offers a more modular and flexible approach. Transitioning to Tailwind CSS would allow us to build custom themes, improve the consistency of UI design, and better accommodate future feature requirements.

Possible Solution

  1. Component Mapping

    • Audit existing components built with Ant-UI.
    • Map them to equivalent Tailwind implementations, identifying gaps.
  2. Theme Building

    • Design and implement a base Tailwind CSS theme to replicate the current look and feel.
    • Create utilities for consistent styling across components.
  3. Incremental Migration

    • Begin migrating non-critical UI components to Tailwind CSS.
    • Gradually replace Ant-UI components while ensuring no disruption to the app’s functionality.
  4. Testing and Validation

    • Test each migrated component for visual and functional consistency.
    • Regularly validate the app’s performance during the transition.
  5. Documentation

    • Maintain detailed documentation for the migration process, including new component designs and Tailwind CSS best practices.
@meetoza30
Copy link

@Vinyl-Davyl is this issue solved? I would like to try if this isnt solved yet.

@DianaLease
Copy link
Member

@Vinyl-Davyl is this issue solved? I would like to try if this isnt solved yet.

I believe @nitro56565 is looking into this currently. @nitro56565, is there anything @meetoza30 could help with?

@nitro56565
Copy link
Contributor

Hey @meetoza30,

Thanks for your interest in helping out with this! Right now, the issue is still on hold since we’re not entirely sure about all the challenges this migration might bring.

If you’re keen to dig into it and contribute, I’d recommend checking out the doc I shared on Discord in the Technology WG channel. Watching a few past WG calls could also give you a better idea of how we’re thinking about the design.

@Vinyl-Davyl
Copy link
Collaborator Author

Yeah Hey @meetoza30 this issue is still on hold. No conclusion has been made yet, but it's one we are looking into.

@Vinyl-Davyl
Copy link
Collaborator Author

@Vinyl-Davyl is this issue solved? I would like to try if this isnt solved yet.

I believe @nitro56565 is looking into this currently. @nitro56565, is there anything @meetoza30 could help with?

Yeah

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

No branches or pull requests

4 participants