opui-css 2.4.0 → 3.0.0

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2024 Felix Bohlin
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2024 Felix Bohlin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -8,13 +8,6 @@ https://open-props-ui.netlify.app/
 
 Check out the [getting started guide](https://open-props-ui.netlify.app/guide/getting-started.html).
 
-## Development
-
-```
-pnpm i
-pnpm dev:css
-```
-
 ## Backstory
 
 Practically all established UI libraries need to take older browser versions into account. Some have only just dropped Internet Explorer. Some have barely discovered the power of CSS grid. Open Props UI starts from a blank slate and re-imagines how a component library could be built if you used the most modern features.
@@ -30,3 +23,26 @@ Yes and no. Right now that's true for most components. The point is to let the s
 - Follow accessibility guidelines
 - Serve as an inspiration
 - Be scalable
+
+## Development
+
+```bash
+# Install dependencies
+pnpm i
+
+# Build all themes (outputs to dist/)
+pnpm build
+
+# Build themes in watch mode (rebuilds on file changes)
+pnpm dev
+
+# Clean the dist folder
+pnpm clean
+```
+
+### Theme Building
+
+The build system automatically processes all themes in the `src/themes/` folder. For each theme folder (ex: `chad-zn`, `theme-one`), it:
+
+1. Bundles `theme.css` → `dist/{theme-name}.css`
+2. Bundles `theme+op.css` → `dist/{theme-name}+op.css`

package/dist/op.css

@@ -69,17 +69,4 @@
 	--font-lineheight-5: 2;
 }}
 @layer openprops{
-:where(:root) {
-	--oklch-red: 25;
-	--oklch-pink: 350;
-	--oklch-purple: 310;
-	--oklch-violet: 290;
-	--oklch-indigo: 270;
-	--oklch-blue: 240;
-	--oklch-cyan: 210;
-	--oklch-teal: 185;
-	--oklch-green: 145;
-	--oklch-lime: 125;
-	--oklch-yellow: 100;
-	--oklch-orange: 75;
-}}
+:where(:root){--oklch-red:25;--oklch-pink:350;--oklch-purple:310;--oklch-violet:290;--oklch-indigo:270;--oklch-blue:240;--oklch-cyan:210;--oklch-teal:185;--oklch-green:145;--oklch-lime:125;--oklch-yellow:100;--oklch-orange:75}}