@proveanything/smartlinks 2.0.17 → 2.0.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/docs/API_SUMMARY.md +1 -1
- package/dist/docs/theme-tokens.md +12 -7
- package/docs/API_SUMMARY.md +1 -1
- package/docs/theme-tokens.md +12 -7
- package/package.json +1 -1
package/dist/docs/API_SUMMARY.md
CHANGED
|
@@ -1,12 +1,17 @@
|
|
|
1
1
|
# SmartLinks Theme Tokens — host theming contract
|
|
2
2
|
|
|
3
|
-
Status: **v1
|
|
4
|
-
>
|
|
5
|
-
>
|
|
6
|
-
>
|
|
7
|
-
>
|
|
8
|
-
>
|
|
9
|
-
>
|
|
3
|
+
Status: **v1 — live. This is the theming contract to build against.**
|
|
4
|
+
> ✅ **Adopt this.** The R5 host (Hub/Portal) sets the `--sl-*` tokens on your mount root and sends
|
|
5
|
+
> `smartlinks:root-state` for live viewer-preference changes; the SDK preset (`theme.css`), the iframe
|
|
6
|
+
> bootstrap (`theme-boot.js`) and the Hub theme engine all speak this contract. Bind your app to these
|
|
7
|
+
> tokens (via `theme.css`) and it is themed by every host, forever, with no per-app theme code.
|
|
8
|
+
>
|
|
9
|
+
> **It degrades gracefully, so adoption is safe.** `theme.css` ships sensible fallback values for every
|
|
10
|
+
> token, so on a host that hasn't enabled token theming yet the app simply renders with neutral
|
|
11
|
+
> defaults rather than breaking. The legacy path (`useSmartLinksTheme()` + shadcn `--primary`/`--background`
|
|
12
|
+
> via the `?theme=` payload, see [`theme.system.md`](./theme.system.md)) still works during the
|
|
13
|
+
> transition, and [step 17] shows how to bridge shadcn variables to these tokens so both paths stay live.
|
|
14
|
+
> New work should bind to the tokens here.
|
|
10
15
|
|
|
11
16
|
Applies to: `@proveanything/smartlinks` ^2.0 (R5), container + widget embeds
|
|
12
17
|
Companion to: [`css-baseline.md`](./css-baseline.md) (mechanics, live) — this doc is **brand** (colour, shape, type)
|
package/docs/API_SUMMARY.md
CHANGED
package/docs/theme-tokens.md
CHANGED
|
@@ -1,12 +1,17 @@
|
|
|
1
1
|
# SmartLinks Theme Tokens — host theming contract
|
|
2
2
|
|
|
3
|
-
Status: **v1
|
|
4
|
-
>
|
|
5
|
-
>
|
|
6
|
-
>
|
|
7
|
-
>
|
|
8
|
-
>
|
|
9
|
-
>
|
|
3
|
+
Status: **v1 — live. This is the theming contract to build against.**
|
|
4
|
+
> ✅ **Adopt this.** The R5 host (Hub/Portal) sets the `--sl-*` tokens on your mount root and sends
|
|
5
|
+
> `smartlinks:root-state` for live viewer-preference changes; the SDK preset (`theme.css`), the iframe
|
|
6
|
+
> bootstrap (`theme-boot.js`) and the Hub theme engine all speak this contract. Bind your app to these
|
|
7
|
+
> tokens (via `theme.css`) and it is themed by every host, forever, with no per-app theme code.
|
|
8
|
+
>
|
|
9
|
+
> **It degrades gracefully, so adoption is safe.** `theme.css` ships sensible fallback values for every
|
|
10
|
+
> token, so on a host that hasn't enabled token theming yet the app simply renders with neutral
|
|
11
|
+
> defaults rather than breaking. The legacy path (`useSmartLinksTheme()` + shadcn `--primary`/`--background`
|
|
12
|
+
> via the `?theme=` payload, see [`theme.system.md`](./theme.system.md)) still works during the
|
|
13
|
+
> transition, and [step 17] shows how to bridge shadcn variables to these tokens so both paths stay live.
|
|
14
|
+
> New work should bind to the tokens here.
|
|
10
15
|
|
|
11
16
|
Applies to: `@proveanything/smartlinks` ^2.0 (R5), container + widget embeds
|
|
12
17
|
Companion to: [`css-baseline.md`](./css-baseline.md) (mechanics, live) — this doc is **brand** (colour, shape, type)
|