@quieto/ui 0.0.0-stage → 0.1.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Dillon Schultz
+
+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

@@ -1,3 +1,143 @@
-# Temporary Holding Version
+# @quieto/ui
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Web components for the Quieto Design System, built with [Lit](https://lit.dev) and styled entirely
+by [`@quieto/design-tokens`](https://www.npmjs.com/package/@quieto/design-tokens). They work in any
+framework, or none.
+
+```bash
+npm install @quieto/ui
+```
+
+## Set up
+
+Load the design tokens **once**, at the top of your app, then register the components:
+
+```js
+import '@quieto/design-tokens/css';
+import '@quieto/ui';
+```
+
+```html
+<qds-button variant="primary">Save</qds-button>
+```
+
+Without the token stylesheet the components still render, from fallback values built into each
+one, but nothing follows your theme and dark mode does nothing. `@quieto/design-tokens` is
+installed with this package, so there is nothing else to add.
+
+Importing `@quieto/ui` registers every element. To register only what you use, import components
+one at a time instead:
+
+```js
+import '@quieto/ui/qds-button.js';
+import '@quieto/ui/qds-text-field.js';
+```
+
+## Components
+
+| Element | What it is |
+| --- | --- |
+| `qds-accordion`, `qds-accordion-item` | Collapsible sections. Optionally `exclusive`, so only one is open. |
+| `qds-button` | A button: four variants, three sizes, a loading state. Submits forms. |
+| `qds-card` | A container with media, header, body, and footer regions. |
+| `qds-checkbox` | A checkbox, including the indeterminate state. |
+| `qds-chip` | A compact status or category label. Removable, or `selectable` as a filter chip. |
+| `qds-input` | A bare single-line text input, named by its `label` attribute. |
+| `qds-modal` | A modal dialog, built on the native `<dialog>`. |
+| `qds-progress-bar` | Determinate or indeterminate progress. |
+| `qds-radio-group`, `qds-radio` | A set of options of which one is chosen. |
+| `qds-stack` | Lays its children out with gaps from the spacing scale. |
+| `qds-tabs`, `qds-tab`, `qds-tab-panel` | Tabs, each showing one panel. |
+| `qds-text-field` | A complete text field: visible label, input, hint, and error message. |
+| `qds-toggle` | An on/off switch, for settings that apply immediately. |
+
+Every property, attribute, slot, event, CSS part, and CSS custom property is documented in
+`custom-elements.json`, a
+[Custom Elements Manifest](https://github.com/webcomponents/custom-elements-manifest) that ships
+in this package. Editors and tools that read the format use it for autocomplete.
+
+## Forms
+
+The form controls — `qds-checkbox`, `qds-radio-group`, `qds-toggle`, `qds-input`,
+`qds-text-field`, and a `qds-button` with `type="submit"` or `"reset"` — take part in a surrounding
+`<form>` like native controls do, even though their inputs are inside shadow DOM:
+
+- they submit their value under their `name`
+- `required`, and the input types' own rules such as `type="email"`, block submission
+- `form.reset()` restores the value the markup declared
+- a `<fieldset disabled>` disables them
+
+```html
+<form>
+  <qds-text-field label="Email" name="email" type="email" required></qds-text-field>
+  <qds-checkbox name="updates" value="yes">Send me updates</qds-checkbox>
+  <qds-button type="submit">Sign up</qds-button>
+</form>
+```
+
+## Events
+
+Components fire events prefixed with `qds-`, such as `qds-change` and `qds-close`. They bubble
+and cross shadow boundaries, so a listener anywhere above the component hears them. `qds-change`
+and `qds-input` fire only for what the user does, not for values your own code sets.
+
+```js
+document.querySelector('qds-toggle').addEventListener('qds-change', (event) => {
+  console.log(event.detail.checked);
+});
+```
+
+## Restyling
+
+Each component reads its styles from its own component tokens, the
+`--qds-component-{name}-*` variables in `@quieto/design-tokens`. Overriding one of those variables is
+the supported way to restyle a component, and it applies wherever you set it:
+
+```css
+qds-button.brand {
+  --qds-component-button-primary-color-background-rest: var(--qds-color-purple-600);
+  --qds-component-button-border-radius: var(--qds-border-radius-full);
+}
+```
+
+For anything the tokens do not cover, components expose CSS parts:
+`qds-button::part(button) { … }`.
+
+## Accessibility
+
+Each component follows the matching ARIA pattern: keyboard support, focus management, and the
+right roles and states. A few things are still up to you:
+
+- **Name the controls that have no visible label.** `qds-input` and `qds-progress-bar` take a
+  `label` attribute, and an icon-only `qds-button` takes `label` too.
+- **Group filter chips.** Wrap a set of `selectable` chips in an element with `role="group"` and an
+  `aria-label`, so they are announced together.
+- **Choose heading levels.** Set `heading-level` on `qds-accordion-item` to fit the outline of your
+  page.
+
+## Server rendering
+
+The components can be server-rendered with
+[`@lit-labs/ssr`](https://www.npmjs.com/package/@lit-labs/ssr) into declarative shadow DOM, so they
+appear styled before any JavaScript runs. Load
+`@lit-labs/ssr-client/lit-element-hydrate-support.js` before `@quieto/ui` on the client, or every
+component renders twice.
+
+## Compatibility
+
+- **Browsers:** current versions of Chrome, Edge, Firefox, and Safari. Form participation relies
+  on form-associated custom elements: Safari 16.4 and later, Firefox 98 and later.
+- **Modules:** ES modules, unbundled, with bare imports of `lit`. Use a bundler, or an import map.
+- **TypeScript:** types are included, and `HTMLElementTagNameMap` knows every element, so
+  `document.querySelector('qds-modal')` is typed.
+
+## Versioning
+
+This package is pre-1.0, so **component APIs can change in any minor release.** On `0.x`, npm's
+caret range does not cross a minor version: `^0.1.0` installs `0.1.x` but never `0.2.0`. The
+[changelog](https://github.com/dillonschultz93/qds/blob/main/packages/ui/CHANGELOG.md) lists every
+breaking change.
+
+## License
+
+MIT