css-is-awesome 1.1.0

package/LICENSE-third-party

@@ -0,0 +1,88 @@
+Third-Party Licenses
+====================
+
+This project bundles or references third-party assets. Each entry below
+identifies the asset, where it lives in the repo, the upstream source,
+and the original license. css-is-awesome itself is MIT (see LICENSE).
+
+----------------------------------------------------------------------
+Lucide — default `core` icon pack
+----------------------------------------------------------------------
+
+Vendored at: public/icons/core/
+
+Upstream:    https://lucide.dev
+             https://github.com/lucide-icons/lucide
+             npm: lucide-static
+
+The Lucide project is dual-licensed. The bulk of the icon set is
+distributed under the ISC License. A subset of icons is derived from
+the Feather project and is distributed under the MIT License.
+
+Both notices, reproduced verbatim from `node_modules/lucide-static/LICENSE`,
+follow.
+
+ISC License
+-----------
+
+Copyright (c) for portions of Lucide are held by Cole Bemis 2013-2022
+as part of Feather (MIT). All other copyright (c) for Lucide are held
+by Lucide Contributors 2022.
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+MIT License (Feather-derived icons)
+-----------------------------------
+
+The following Lucide icons are derived from the Feather project and
+distributed under the MIT License:
+
+  airplay, alert-circle, alert-octagon, alert-triangle, aperture,
+  arrow-down-circle, arrow-down-left, arrow-down-right, arrow-down,
+  arrow-left-circle, arrow-left, arrow-right-circle, arrow-right,
+  arrow-up-circle, arrow-up-left, arrow-up-right, arrow-up, at-sign,
+  calendar, cast, check, chevron-down, chevron-left, chevron-right,
+  chevron-up, chevrons-down, chevrons-left, chevrons-right, chevrons-up,
+  circle, clipboard, clock, code, columns, command, compass,
+  corner-down-left, corner-down-right, corner-left-down, corner-left-up,
+  corner-right-down, corner-right-up, corner-up-left, corner-up-right,
+  crosshair, database, divide-circle, divide-square, dollar-sign,
+  download, external-link, feather, frown, hash, headphones,
+  help-circle, info, italic, key, layout, life-buoy, link-2, link,
+  loader, lock, log-in, log-out, maximize, meh, minimize, minimize-2,
+  minus-circle, minus-square, minus, monitor, moon, more-horizontal,
+  more-vertical, move, music, navigation-2, navigation, octagon,
+  pause-circle, percent, plus-circle, plus-square, plus, power, radio,
+  rss, search, server, share, shopping-bag, sidebar, smartphone, smile,
+  square, table-2, tablet, target, terminal, trash-2, trash, triangle,
+  tv, type, upload, x-circle, x-octagon, x-square, x, zoom-in, zoom-out
+
+Copyright (c) 2013-present Cole Bemis
+
+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/MIGRATION.md

@@ -0,0 +1,312 @@
+# Migration Guide
+
+Breaking changes between css-is-awesome versions, and how to migrate.
+
+## v0.8.1 — animations split + small renames
+
+Patch release with one real fix (animations CSS Modules bug) and two small
+renames. No structural changes.
+
+### What changed at a glance
+
+| Area | v0.8.0 | v0.8.1 |
+|---|---|---|
+| `_animations.scss` shape | Mixed mixins + top-level CSS rules in one file | **Split** — mixins in `_animations.scss`, rules + keyframes in `_animations-utilities.scss` |
+| `progress-track` / `progress-fill` mixin names | Without `-base` suffix | **`-base` suffix added** to signal "compose me" |
+| `badge-base` / `badge` location | In `_feedback.scss` | **Moved to `_data.scss`** (next to `card-base` / `table-base`) |
+
+### 1. CSS Modules consumers — animations split
+
+If you previously imported animations from a `.module.scss` and hit
+`Selector "*, *::before, *::after" is not pure`, that's now fixed:
+
+```scss
+// component.module.scss — works now in v0.8.1
+@use 'css-is-awesome/scss/animations' as anim;
+.my-spinner { @include anim.animate(spin, $iteration: infinite, $timing: linear); }
+```
+
+**But the keyframes need to be loaded globally once.** Easiest path: keep
+the `@use 'css-is-awesome/scss/main';` line in your global SCSS — it
+already loads both halves. Or load the new utilities file directly:
+
+```scss
+// globals.scss (loaded once at app root)
+@use 'css-is-awesome/scss/animations-utilities';
+```
+
+### 2. Rename `progress-track` → `progress-track-base`
+
+```scss
+// v0.8.0
+.my-track { @include cia.progress-track; }
+.my-fill  { @include cia.progress-fill; }
+
+// v0.8.1
+.my-track { @include cia.progress-track-base; }
+.my-fill  { @include cia.progress-fill-base; }
+
+// OR use the new composer:
+.my-progress { @include cia.progress; }
+```
+
+The new `cia.progress` composer reads `[data-slot="fill"]` markup — see the
+mixin docstring for the recipe.
+
+### 3. `badge-base` / `badge` moved to `_data.scss`
+
+If you had a path-specific import:
+
+```scss
+// v0.8.0
+@use 'css-is-awesome/scss/components/feedback' as f;
+.my-badge { @include f.badge-base; }
+
+// v0.8.1 — option A: use the cia barrel (recommended)
+@use 'css-is-awesome/api' as cia;
+.my-badge { @include cia.badge-base; }
+
+// v0.8.1 — option B: import from data
+@use 'css-is-awesome/scss/components/data' as d;
+.my-badge { @include d.badge-base; }
+```
+
+The cia barrel re-exports all components, so the recommended Option A
+unsubscribes you from future location changes.
+
+### New mixins (additive, no migration needed)
+
+- `cia.wizard-shell` — 3-row layout with shared horizontal rhythm (stepper + body + controls)
+- `cia.stepper`, `cia.stepper-circle`, `cia.stepper-connector` — status-driven progress indicator
+- `cia.progress` — composed router (track + fill via `[data-slot]`)
+- `cia.sidebar` — Every-Layout sidebar (fixed nav + flexible content, gracefully stacks)
+- `cia.toolbar` — cluster with auto-margin `[data-slot="trailing"]`
+
+Plus bare-tags additions for `<dialog>` and `<progress>` (opt-in via the
+existing `bare-tags` recipe).
+
+---
+
+## v0.8 — mixin-first reframe + theme system collapse
+
+**Status:** breaking, no aliases. v0.8 is the pre-v1.0 lock-in pass.
+
+### What changed at a glance
+
+| Area | v0.7 | v0.8 |
+|---|---|---|
+| Primary API | utility classes + mixins | **mixin-first** (consumer picks their own selectors) |
+| Themes | 14 files (`press-light` + `press-dark` × 7 families) | **9 single-file themes** using `light-dark()` |
+| Theme selectors | `[data-theme="press-light"]` / `[data-theme="press-dark"]` | `[data-theme="press"]` |
+| Responsive `:` utilities | `.cia-sm:flex`, `.cia-md:hidden` etc. | **killed** (saves 8 KB gz) |
+| Utility classes (Sass path) | always emitted | **opt-in** via `@use ... with ($utilities: true)` |
+| JavaScript in npm package | optional add-ons | **zero** — hard rule |
+| Mixin names | 12 names renamed to spec vocabulary | see rename table below |
+
+### 1. Rename `data-theme` attribute values
+
+```html
+<!-- v0.7 -->
+<html data-theme="press-light">
+<html data-theme="press-dark">
+
+<!-- v0.8 -->
+<html data-theme="press">  <!-- both modes inside one theme file -->
+```
+
+The single-file themes use `light-dark()` for color tokens; the browser
+auto-swaps based on the user's OS `prefers-color-scheme`.
+
+### 2. Rename mixin calls
+
+| v0.7 | v0.8 |
+|---|---|
+| `@include cia.bp(md) { … }` | `@include cia.media(md) { … }` |
+| `@include cia.bp-down(md) { … }` | `@include cia.media-down(md) { … }` |
+| `@include cia.bp-between(sm, lg)` | `@include cia.media-between(sm, lg)` |
+| `@include cia.cq(md) { … }` | `@include cia.contain(md) { … }` |
+| `@include cia.cq-down(md)` | `@include cia.contain-down(md)` |
+| `cia.color-raw(border-focus)` | `cia.color-static(border-focus)` |
+| `@include cia.inset(4)` | `@include cia.pad(4)` |
+| `@include cia.inset-x(4)` | `@include cia.pad-x(4)` |
+| `@include cia.inset-y(2)` | `@include cia.pad-y(2)` |
+| `@include cia.squish(2, 4)` | `@include cia.pad-asym(2, 4)` |
+| `@include cia.font-load('Inter', '/inter.woff2')` | `@include cia.font-face('Inter', '/inter.woff2')` |
+| `@include cia.font-load-local('Inter', '/inter.woff2')` | `@include cia.font-face-local('Inter', '/inter.woff2')` |
+| Layout `@include cia.container` | `@include cia.wrap` |
+
+No aliases. Use a regex search-replace on your codebase, or wait for a
+codemod (planned for the future `@cia/codemod` package, v1.x).
+
+### 3. Remove responsive `:` utility classes
+
+```html
+<!-- v0.7 -->
+<div class="cia-sm:flex cia-md:hidden">
+
+<!-- v0.8 -->
+<!-- Option A: opt back in to responsive utilities -->
+<!-- in your app.scss: -->
+<!--   @use 'css-is-awesome' as cia with ($responsive-spacing: true); -->
+
+<!-- Option B (recommended): use the mixin form -->
+<div class="my-thing">
+<!-- in your SCSS: -->
+<!--   .my-thing {
+        @include cia.media(md) { display: flex; }
+      } -->
+```
+
+The responsive utility generator was emitting ~85 lines of cartesian-product
+classes that most consumers never used. Killing them dropped `main.scss` from
+16.6 KB gz to 8.2 KB gz.
+
+### 4. Opt back in to utility classes (Sass consumers)
+
+```scss
+// v0.7 — all utilities always emitted
+@use 'css-is-awesome' as cia;
+
+// v0.8 — utilities opt-in
+@use 'css-is-awesome' as cia with (
+  $utilities: true,             // emit .cia-* utility classes
+  $responsive-spacing: true,    // emit .cia-sm-p-md, etc.
+);
+```
+
+**Pre-built CDN consumers are unaffected** — `dist/css-is-awesome.utilities.css`
+still ships every utility class. The opt-in governs the Sass compile path only.
+
+### 5. Move JS handlers out of cia-core dependencies
+
+If you were relying on a JS shim shipped in `dist/`, it's gone. The
+CopyButton JS handler now lives at `public/copy-button.mjs` (not in the
+npm package). Three migration options:
+
+1. **Copy-paste the recipe** from `/docs/recipes/copy-button`. ~700 bytes,
+   framework-free.
+2. **Write your own handler** following the documented contract
+   (delegated click, `data-copy-target`, `data-copied` state).
+3. **Wait for `@cia/copy-button`** add-on package (v1.x roadmap).
+
+### 6. Embrace mixin-first authoring
+
+The v0.8 reframe is more philosophical than mechanical: **cia ships the
+mixin; you ship the class name**. Pre-v0.8 docs led with class examples
+(`<button class="cia-btn-primary">`); v0.8 docs lead with mixin examples:
+
+```scss
+// v0.7 — class form was primary
+<button class="cia-btn-primary">Save</button>
+
+// v0.8 — mixin form is primary
+<button class="save-btn">Save</button>
+
+// in your SCSS:
+.save-btn { @include cia.btn(primary); }
+```
+
+You can still use the `.cia-*` classes if you opt them in — they're a
+convenience layer now, not the primary API.
+
+### Where to read more
+
+- [`CHANGELOG.md`](./CHANGELOG.md) — full breaking-change list with code-level detail
+- [`AGENTS.md`](./AGENTS.md) — authoring guide updated for v0.8
+- `/docs/install` on the docs site — the new mixin-first install path
+- `/docs/themes/pairing` — the new `<link media>` paired-brand trick
+
+---
+
+## v0.7 — theme names carry a `-light` / `-dark` suffix
+
+**Status:** breaking (alias-cushioned). Approved pre-1.0.
+
+### What changed
+
+Every built-in theme name now carries a mode suffix so consumers can read
+intent at a glance. The defaults shipped before v0.7 were inconsistent
+(some had a suffix, most did not). All six original themes are renamed
+and now ship paired light/dark modes.
+
+| v0.6 name      | v0.7 name           | Notes                                          |
+|----------------|---------------------|------------------------------------------------|
+| `sketchbook`   | `sketchbook-light`  | Default. Still wins via `:root:not([data-theme])`. |
+| `press`        | `press-light`       |                                                |
+| `graphite`     | `graphite-dark`     | Graphite was always dark.                      |
+| `glass`        | `glass-light`       |                                                |
+| `cupertino`    | `cupertino-light`   |                                                |
+| `terminal`     | `terminal-dark`     | New `terminal-light` companion shipped — daylight editor. |
+
+### Migration steps for consumers
+
+#### Tier 1 — drop-in CSS (HTML, no build step)
+
+If your markup looks like this:
+
+```html
+<html data-theme="sketchbook">
+```
+
+…then nothing breaks today. The unsuffixed v0.6 names continue to resolve
+through alias selectors in `public/theme.css` for the entire 0.7.x line.
+
+Before v0.8 ships, rename to the suffixed form:
+
+```html
+<html data-theme="sketchbook-light">
+```
+
+If you self-host one of the per-theme files, update the path:
+
+```html
+<!-- v0.6 -->
+<link rel="stylesheet" href="/themes/press/theme.css">
+
+<!-- v0.7+ -->
+<link rel="stylesheet" href="/themes/press-light/theme.css">
+```
+
+The five renamed folders under `public/themes/` follow the same suffix
+convention as the data-theme names.
+
+#### Tier 2 — React (docs theme picker / cookies)
+
+If your app reads or writes the `cia-theme` cookie directly:
+
+```js
+// v0.6
+document.cookie = "cia-theme=sketchbook; path=/";
+
+// v0.7+
+document.cookie = "cia-theme=sketchbook-light; path=/";
+```
+
+Both cookie values resolve to the same tokens through 0.7.x because the
+pre-hydration script accepts both lists. Update your writes to the new
+names so existing cookies migrate naturally.
+
+The `<ThemePicker>` and `<ThemeTile>` components shipped in v0.7 already
+emit the suffixed IDs.
+
+#### Tier 3 — SCSS / mixins
+
+No SCSS API changed — the rename only affects the `data-theme` attribute
+values and the per-theme folder names. The mixin layer (`cia.color`,
+`cia.btn`, etc.) is untouched.
+
+### Removal timeline
+
+- **v0.7.x** — both old and new names work. Aliases ship in
+  `public/theme.css`. `MIGRATION.md` and `CHANGELOG.md` document the
+  rename. `<ThemePicker>` defaults to the new names.
+- **v0.8.0** — alias selectors removed. `<html data-theme="sketchbook">`
+  no longer resolves; consumers must use `sketchbook-light`. Per-theme
+  folder paths under the old names (`public/themes/press/`, etc.) are
+  also gone.
+
+### Related work
+
+- US-2.14.1 — maintainer-side rename (this PR).
+- US-2.14.2 — consumer migration guide (this file).
+- US-2.14.3 — alias-removal follow-up scheduled for v0.8.