@ponti-studios/ui 0.1.2 → 0.4.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ponti Studios
+
+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,6 +1,6 @@
 # @ponti-studios/ui
 
-The canonical Ponti Studios UI package. It is published from this repository to GitHub Packages.
+The canonical Ponti Studios UI package. It is published from this repository to npm.
 
 ## Release
 
@@ -8,20 +8,20 @@ The canonical Ponti Studios UI package. It is published from this repository to
 2. Merge the change to `main`.
 3. Create and push a matching `ui-v<version>` tag, for example `ui-v0.1.0`.
 
-The `publish-ui` workflow validates that the tag and package version match, then publishes with the repository `GITHUB_TOKEN`. Do not publish from a workstation.
+The `publish-ui` workflow validates that the tag and package version match, then publishes with the repository’s npm publishing credentials. Do not publish from a workstation.
 
 ## Consumers
 
-Configure the GitHub Packages registry in the consumer repository:
+Configure the npm registry in the consumer repository:
 
 ```ini
-@pontistudios:registry=https://npm.pkg.github.com
+@ponti-studios:registry=https://registry.npmjs.org
 ```
 
-Private consumers need a token with `read:packages`, configured outside the committed project `.npmrc`:
+Consumers that need authentication should configure a token outside the committed project `.npmrc`:
 
 ```bash
-pnpm config set --location=user //npm.pkg.github.com/:_authToken "$NODE_AUTH_TOKEN"
+pnpm config set --location=user //registry.npmjs.org/:_authToken "$NODE_AUTH_TOKEN"
 ```
 
-GitHub Actions consumers should use their `GITHUB_TOKEN` after the package grants their repository Actions access. Non-GitHub build systems need the same read-only token in their user-level npm configuration or equivalent secret-backed registry integration.
+CI consumers should use a secret-backed npm token with read access.

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,17 @@
+# Third-party notices
+
+## Adobe Spectrum Tokens
+
+The light and dark color snapshots in `src/tokens/generated/*colors.generated.ts`
+are derived from Adobe Spectrum Tokens 14.15.0. Spectrum Tokens is distributed
+under the Apache License 2.0.
+
+Source: https://github.com/adobe/spectrum-tokens
+
+## Tailwind CSS
+
+The non-color foundations in `src/tokens/generated/foundations.generated.ts`
+and `src/tokens/generated/foundations.css` match the Tailwind CSS 4.3.3 default
+theme. Tailwind CSS is distributed under the MIT License.
+
+Source: https://github.com/tailwindlabs/tailwindcss