@marigold/theme-rui 0.3.0 → 0.3.1

package/dist/global.css

@@ -0,0 +1,8 @@
+@layer base {
+  body {
+    font-optical-sizing: auto;
+    font-style: normal;
+
+    @apply supports-[font-variation-settings:normal]:font-sans-variable text-foreground bg-background font-sans;
+  }
+}

package/dist/mixins.css

@@ -0,0 +1,44 @@
+/*
+  File: tailwind-components.css
+
+  Description
+  -----------
+  This file defines custom Tailwind CSS component classes by bundling commonly used utility classes
+  with the @apply directive. The goal is to reduce duplication, enhance maintainability, and ensure
+  a consistent styling pattern across various components.
+
+  Usage
+  -----
+  Import this file into your main stylesheet or reference it in your Tailwind CSS configuration.
+
+  Best Practices
+  --------------
+  - Encapsulate frequently used utility combinations into custom classes for better reusability.
+  - Update the definitions here to maintain consistency in our design system across all components.
+  - Keep custom classes focused on specific styling concerns to preserve clarity.
+*/
+@layer utilities {
+  .mixin-ring-focus-visible {
+    @apply focus-visible:border-ring focus-visible:ring-ring/50 outline-none focus-visible:ring-[3px];
+  }
+
+  .mixin-ring-has-focus-visible {
+    @apply has-focus-visible:border-border has-focus-visible:ring-ring/50 has-focus-visible:ring-[3px];
+  }
+
+  .mixin-ring-focus-visible-checkbox {
+    @apply group-focus-visible/checkbox:ring-ring/50 group-focus-visible/checkbox:ring-[3px];
+  }
+
+  .mixin-ring-focus-visible-borderless {
+    @apply focus-visible:ring-ring/50 outline-none focus-visible:ring-[3px];
+  }
+
+  .mixin-ring-focus-within {
+    @apply focus-within:border-ring focus-within:ring-ring/50 outline-none focus-within:ring-[3px];
+  }
+
+  .mixin-disabled {
+    @apply disabled:bg-disabled disabled:text-disabled-foreground disabled:cursor-not-allowed disabled:border-none disabled:shadow-none;
+  }
+}

package/dist/theme.css

@@ -1,4 +1,6 @@
-/* 
+@import './mixins.css';
+
+/*
     TODO: how to do normalization so we doesn't break everything?
     TODO: omit "background" in the naming convention? (https://ui.shadcn.com/docs/theming#convention)
     TODO: create component styles files and compile to CSS classes?
@@ -154,5 +156,3 @@
     }
   }
 }
-
-@import './mixins.css';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@marigold/theme-rui",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Marigold RUI Theme",
   "license": "MIT",
   "keywords": [
@@ -56,6 +56,6 @@
     "@marigold/theme-plugins": "1.0.1"
   },
   "scripts": {
-    "build": "NODE_ENV=production tsup && postcss -o dist/styles.css src/styles.css && cp src/theme.css dist/theme.css"
+    "build": "NODE_ENV=production tsup && postcss -o dist/styles.css src/styles.css && cp src/theme.css src/global.css src/mixins.css dist/"
   }
 }