epicmaxco/vuestic-admin

Mix of tailwind and bem

Open

#1,017 opened on Jan 24, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Vue (1,801 forks)user submission
d1: super easygood first issuerefactoringv1: minor

Repository metrics

Stars
 (10,951 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Contributor guide

Research direction
Review the identified components listed in the issue and replace BEM classes with equivalent Tailwind utility classes. Use the existing Tailwind configuration and patterns from the rest of the codebase for consistency.
Tech stack
vuetailwindcss
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Tailwind CSSBEM methodology
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65