epicmaxco/vuestic-admin

Mix of tailwind and bem

Open

#1,017 建立於 2024年1月24日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Vue (10,951 star) (1,801 fork)user submission
d1: super easygood first issuerefactoringv1: minor

描述

Right now we have some components that use bem, while majority of the application uses tailwind

I searched by "__" and this seems to be the list. Feel free to check other components.

We want to only use tailwind for vuestic-admin. So for all of these we need to replace bem implementation with tailwind classes (simplest way might be to use GPT to help with that).

image

貢獻者指南

技術棧
vuetailwindcss
領域
frontend
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of VueBasic knowledge of Tailwind CSS
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
First, search for components using BEM class names (indicated by ' ' or ' ') in the repository, likely under src/components. Use the list provided in the issue as a starting point. For each component, identify the current BEM classes and replace them with equivalent Tailwind utility classes. You can refer to existing Tailwind styled components in the codebase for consistency. Using an AI tool like GPT can help generate Tailwind class combinations. After changes, ensure the component renders correctly and matches the original layout.