From 75fb0b57f7ee15e7fc9f2779a92a3c9a3659722d Mon Sep 17 00:00:00 2001 From: Shinwoo PARK Date: Fri, 10 May 2024 23:38:43 +0900 Subject: [PATCH] Update README.md --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 11ccf91..ec65f9b 100644 --- a/README.md +++ b/README.md @@ -6,11 +6,10 @@ My goal is to create **fully typesafe**, **highly customizable** component with ## Rules of PSW-UI Development -* Only use **React** or **Svelte**, **TailwindCSS**, **tailwind-merge**, **clsx**, **class-variance-authority** for runtime dependency. In development environment, there's no need to restrict it, right? -* **Simplicity** over **Versatility**. Since it has small dependency and easy to edit, user can always easily add or patch their own code to the component. +* Only use **React** or **Svelte**, **TailwindCSS**, **tailwind-merge**, **clsx**, **class-variance-authority** for runtime dependency. +* **Simplicity** over **Versatility**. Make it easy to edit, so user can easily add or patch their own code to the component. * **Hate script.** If you can do that with CSS, just do that with CSS. Why use JS? -* **Love transitions.** Actually _Implementing In-Out Transition_ is much more difficult thing to do in react, especially with DOM manipulation. It really should be in the plan. -* **Stick with defaults.** Just let others do their customization. And, well, TailwindCSS's default theme is pretty cool. +* **Stick with the defaults.** Just let others do their customization. And, well, TailwindCSS's default theme is pretty cool. * **Keep component isolated.** Leave them alone. Don't make one dependent to others. ## Milestones