-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Comments
@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? |
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. |
Yeah Hey @meetoza30 this issue is still on hold. No conclusion has been made yet, but it's one we are looking into. |
Yeah |
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
Component Mapping
Theme Building
Incremental Migration
Testing and Validation
Documentation
The text was updated successfully, but these errors were encountered: