p-sw/pswui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Shinwoo PARK 2024-05-10 23:38:43 +09:00 committed by GitHub
parent d43b5567ad
commit 75fb0b57f7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -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