@juwel-development/design-system 2.1.1 → 3.1.0

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.
Files changed (40) hide show
  1. package/README.md +31 -0
  2. package/dist/design-system.js +246 -170
  3. package/dist/index.css +1 -1
  4. package/dist/types/Arrangement/Cluster/Cluster.d.ts +50 -0
  5. package/dist/types/Arrangement/Stack/Stack.d.ts +46 -0
  6. package/dist/types/Display/Figure/Figure.d.ts +21 -4
  7. package/dist/types/Display/Rail/Rail.d.ts +6 -0
  8. package/dist/types/Display/Typography/H1/H1.d.ts +7 -1
  9. package/dist/types/Display/Typography/Note/Note.d.ts +35 -0
  10. package/dist/types/Interaction/Input/Input.d.ts +5 -0
  11. package/dist/types/Interaction/Link/Link.d.ts +4 -4
  12. package/dist/types/Interaction/TextArea/TextArea.d.ts +5 -0
  13. package/dist/types/Layout/Form/Form.d.ts +8 -4
  14. package/dist/types/Layout/Header/Header.d.ts +20 -1
  15. package/dist/types/Layout/Hero/Hero.d.ts +9 -7
  16. package/dist/types/Layout/Section/Section.d.ts +7 -0
  17. package/dist/types/Theme/Palette.d.ts +55 -6
  18. package/dist/types/index.d.ts +3 -0
  19. package/package.json +2 -6
  20. package/src/Arrangement/Cluster/Cluster.tsx +80 -0
  21. package/src/Arrangement/Stack/Stack.tsx +75 -0
  22. package/src/Display/Figure/Figure.tsx +48 -7
  23. package/src/Display/Rail/Rail.tsx +6 -0
  24. package/src/Display/Typography/H1/H1.tsx +17 -7
  25. package/src/Display/Typography/Note/Note.tsx +56 -0
  26. package/src/Interaction/Button/Button.tsx +4 -1
  27. package/src/Interaction/Input/Input.tsx +25 -6
  28. package/src/Interaction/Link/Link.tsx +9 -5
  29. package/src/Interaction/TextArea/TextArea.tsx +25 -6
  30. package/src/Layout/Form/Form.tsx +24 -8
  31. package/src/Layout/Header/Header.tsx +37 -4
  32. package/src/Layout/Hero/Hero.tsx +10 -6
  33. package/src/Layout/PageHead/PageHead.tsx +2 -0
  34. package/src/Layout/Section/Section.tsx +11 -0
  35. package/src/Theme/Palette.ts +63 -14
  36. package/src/Theme/renderTokens.ts +18 -1
  37. package/src/index.ts +3 -0
  38. package/src/tokens.css +20 -9
  39. package/src/tokens.dark.css +16 -5
  40. package/src/tokens.light.css +16 -5
package/README.md CHANGED
@@ -103,3 +103,34 @@ checks it again on pull requests.
103
103
  Merging to `main` runs semantic-release, which works out the version from those
104
104
  messages, writes `CHANGELOG.md`, tags the commit, publishes to npm and opens a GitHub
105
105
  release with the generated notes. No version number is set by hand.
106
+
107
+ ### Publishing a note
108
+
109
+ A commit body can carry a `NOTE:` footer, which puts a **consumer-facing note** into
110
+ `CHANGELOG.md` under its own `NOTE` heading. The version is unaffected - a `fix:` with a
111
+ note is still a patch - so a note never has to be dressed up as a breaking change to get
112
+ published:
113
+
114
+ ```
115
+ fix(section): give the section a positioning context
116
+
117
+ NOTE: An absolutely-positioned descendant of a `Section` that used to anchor to an outer
118
+ ancestor now anchors to the section instead - silently, with no error.
119
+ ```
120
+
121
+ Write one when a change alters how a consumer's existing code behaves **without** being a
122
+ breaking change: nothing they wrote stops compiling, but what it does is different. A note
123
+ is not a second subject line and not a place for implementation detail - it says what a
124
+ consumer has to know, in their terms. A commit carrying a note reaches the changelog
125
+ whatever its type prefix, so even a `chore:` can publish one.
126
+
127
+ One commit may carry several notes. Two rules keep them intact, both of them the commit
128
+ parser's: put a **blank line between notes**, or one of them is silently dropped, and keep
129
+ any `(#issue)` reference **off the last line of a wrapped note**, or the note is cut short
130
+ there and the reference is filed against the commit instead. Each note is published
131
+ prefixed with the commit's scope, so a commit whose notes span several components reads
132
+ better with no scope at all.
133
+
134
+ A real breaking change still uses `BREAKING CHANGE:`, and still forces a major. The two
135
+ keywords are not interchangeable, and the reason a third one cannot simply be added is in
136
+ the [architecture standard](./docs/agents/standards/architecture.md#release).