javascriptecuador / javascriptecuador/web
Migrar de TailwindCSS a CSS puro
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Al principio del desarrollo del sitio se planteó usar TailwindCSS por la "velocidad de prototipado", pero la mayoría de los estilos del sitio se están construyendo con CSS puro, por esta razón y otras mencionadas en #41 se ha decidido usar CSS puro en vez de TailwindCSS.
Para lo cual se va a ir migrando los componentes que están con TailwindCSS. Además se plantea usar módulos de CSS y un linter para usar la convención BEM
Cualquier inquietud puedes comentarla aquí o escribir en el chat de la comunidad en Telegram
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, components, or tests are named. Start by locating the components that still use TailwindCSS and review the decision in issue #41; the migration is complete when those components use pure CSS with CSS modules and the agreed BEM linting convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript, tailwindcss
- Domain
- frontend, tooling, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100