Merge branch 'main' of https://github.com/Ricy137/Custom-ui

.github/workflows/valist.yml

@@ -0,0 +1,34 @@
+name: Valist Deploy
+on:
+  push:
+    branches:
+      - main
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Setup Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: '16' 
+
+      - name: Build and export Next.js app
+        run: |
+          npm install
+          npm run build && npx next export
+
+      - name: Mark Timestamp
+        run: echo "TIMESTAMP=$(date +%Y%m%d%H%M)" >> $GITHUB_ENV
+
+      - name: Valist Publish
+        uses: valist-io/valist-github-action@v2
+        with:
+          private-key: ${{ secrets.VALIST_SIGNER }}
+          account: ricy
+          project: ricysdemohouse
+          release: ${{ env.TIMESTAMP }}
+          platform-web: out
+

README.md

@@ -4,11 +4,16 @@
 
 ## Why do I start the repo?
 
-React components libraries like MUI is a good option for fast development phase, but they're also large and hard to customize. So I developed custom-ui since a customized component library will provide the minizest size which is good for performance, it will also be much easier for me to customize these components as well as optimize them and it would be a good way to level up my skills as a frontend engineer.
+React components libraries like MUI, ANTD is a good option for fast development phase, but they're also large and hard to customize. So I developed custom-ui since a customized component library will provide the minizest size which is good for performance, it will also be much easier for me to customize these components as well as optimize them and it would be a good way to level up my skills as a frontend engineer.
 
 But work is stressful and in high speed. Fortunately, I managed to get some optimization time for a project and successfully replaced all the MUI components with self made components in that project, which recuded almost 20% of overall JavaScript bundle size (of course which also leads to better performance). I decided to make more advantages of these components and make them more reusable, so I started this repo.
 
 ## Conflicts and thoughts
 
 Next: I love Next, the server side rendering is a great way to improve performance, its optimiztion for images is great, turboPack... But of course, due to Next's SSR feature, I also met many conflicts.
-One of the conflicts I met is UnoCSS which is an alternative to TailWind. UnoCSS can not only provide better performance and flexsibility, but also released more potention of Atom CSS : https://antfu.me/posts/reimagine-atomic-css . However, while I'm having a good time with UnoCSS with React and Vite, I didn't find a good to use it seamlessly with Next :(
+
+One of the conflicts I met is UnoCSS which is an alternative to TailWind. UnoCSS can not only provide better performance and flexsibility, but also released more potention of Atom CSS : https://antfu.me/posts/reimagine-atomic-css . However, while I'm having a good time with UnoCSS with React and Vite, I didn't find a good to use it seamlessly with Next :( . Current UnoCSS CLI is used. 
+
+## Future plan
+- add PWA features
+- add documents and examples