@poodle64/ui 2026.9.9 → 2026.9.10
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.
|
@@ -473,7 +473,16 @@
|
|
|
473
473
|
{@render brand()}
|
|
474
474
|
{:else}
|
|
475
475
|
{#if brandMark}
|
|
476
|
-
|
|
476
|
+
<!--
|
|
477
|
+
The mark sits directly on the chrome, with no plate behind it. The
|
|
478
|
+
chrome is the app's to brand, so anything painted here from a page
|
|
479
|
+
token punches a page-coloured hole through the brand colour; and a
|
|
480
|
+
mark is chosen to suit the ground it sits on — every brand guideline
|
|
481
|
+
says so, usually as "the white mark on a dark ground" — so it needs
|
|
482
|
+
no separating. An app that wants a plate owns the whole lockup
|
|
483
|
+
through the `brand` snippet, which is what that is for.
|
|
484
|
+
-->
|
|
485
|
+
<span class="grid size-8 flex-none place-items-center">
|
|
477
486
|
{@render brandMark()}
|
|
478
487
|
</span>
|
|
479
488
|
{/if}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@poodle64/ui",
|
|
3
|
-
"version": "2026.9.
|
|
3
|
+
"version": "2026.9.10",
|
|
4
4
|
"description": "Household shared component layer: shadcn-svelte primitives (bits-ui) plus the composed page chrome every app builds its routes from, restyled by each app's @poodle64/design-tokens alias layer. One fix reaches every app.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# @poodle64/ui — situation → component map
|
|
2
2
|
|
|
3
3
|
<!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
|
|
4
|
-
Generated from `@poodle64/ui@2026.9.
|
|
4
|
+
Generated from `@poodle64/ui@2026.9.10`. 57 components, 15 situations.
|
|
5
5
|
|
|
6
6
|
**Read this before writing a `<div>`.** Find the SITUATION you are in below, then compose the component named for it — do not hand-build it from raw `Card` or utility classes. Import is `import { Name } from '<import path>'`. Props marked `?` are optional. This map is the retrieval step the [`frontend-design` skill] makes mandatory; the [CHI 2026 study] measured composing-from-a-registry at 95% design-system compliance against 71% for writing the CSS from a prose style guide.
|
|
7
7
|
|