@amsterdam/design-system-react 0.11.1 → 0.12.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.
package/README.md CHANGED
@@ -1,18 +1,70 @@
1
1
  <!-- @license CC0-1.0 -->
2
2
 
3
- # Component library for React apps
3
+ # Amsterdam Design System: React components
4
4
 
5
- The `@amsterdam/design-system-react` package contains React implementations of various components.
6
- You can use this package in React apps.
5
+ This package provides all React components from the [Amsterdam Design System](https://designsystem.amsterdam).
6
+ Use it to compose pages in your website or application.
7
7
 
8
- The design tokens and CSS used in these components are published in separate npm packages,
9
- so don’t forget to install and include `@amsterdam/design-system-tokens` and `@amsterdam/design-system-css` too.
8
+ ## Introduction
10
9
 
11
- ## Stability of the components
10
+ This package is the primary entry point for digital services that we build in-house.
11
+ We’ve adopted the architecture of [NL Design System](https://nldesignsystem.nl/).
12
12
 
13
- The React Library has not yet reached a 1.0.0 version.
14
- However, most of them are stable enough to be used in production.
15
- Components that have known issues, or for which we anticipate API changes, show a ‘beta’ badge on their page.
13
+ ## Installation
16
14
 
17
- Make sure you specify the exact version as dependency.
18
- You can then schedule an upgrade to the latest version when you have time to test for regressions.
15
+ The components reference our
16
+ [stylesheets](https://www.npmjs.com/package/@amsterdam/design-system-css),
17
+ [design tokens](https://www.npmjs.com/package/@amsterdam/design-system-tokens)
18
+ [assets](https://www.npmjs.com/package/@amsterdam/design-system-assets),
19
+ and [React icons](https://www.npmjs.com/package/@amsterdam/design-system-react-icons).
20
+ Install all packages.
21
+
22
+ ```sh
23
+ npm install @amsterdam/design-system-assets @amsterdam/design-system-css @amsterdam/design-system-react @amsterdam/design-system-react-icons @amsterdam/design-system-tokens
24
+ ```
25
+
26
+ The React components themselves are unstyled.
27
+ [Override the design tokens](https://github.com/Amsterdam/design-system/blob/main/proprietary/tokens/README.md) to use them with a different branding.
28
+
29
+ ## Usage
30
+
31
+ Import the stylesheets for the fonts, tokens, and components.
32
+ Then import and use the components in your JSX.
33
+
34
+ <!-- prettier-ignore -->
35
+ ```ts
36
+ import "@amsterdam/design-system-assets/font/index.css"
37
+ import "@amsterdam/design-system-css/dist/index.css"
38
+ import "@amsterdam/design-system-tokens/dist/index.css"
39
+ import { Paragraph } from "@amsterdam/design-system-react"
40
+
41
+ const App = () => (
42
+ <Paragraph>Hello, world!</Paragraph>
43
+ )
44
+
45
+ export default App
46
+ ```
47
+
48
+ ## Updating
49
+
50
+ We follow semantic versioning and publish a [change log](https://github.com/Amsterdam/design-system/blob/main/packages/react/CHANGELOG.md) to guide you through updates.
51
+ The React components are a public API of the design system.
52
+ TypeScript helps to detect changed or deleted components, props, or prop values.
53
+
54
+ ### Stability
55
+
56
+ Despite being on ‘major version zero’, most components are stable enough to be used in production.
57
+ Various of our public-facing websites and applications already do.
58
+
59
+ Make sure you specify the exact version as dependency and test for regressions when upgrading to the latest version.
60
+
61
+ We’re finalizing the design and modelling of foundational concepts like typography, spacing, and colour.
62
+ After that, and a final review of the API of all current components, we’ll release version 1.0 of the entire design system.
63
+ Then, we’ll consider publishing all components separately to allow for more granular updates.
64
+
65
+ Components for which we anticipate API changes show a ‘beta’ badge at the top of their page in the [Design System handbook](https://designsystem.amsterdam/).
66
+
67
+ ## Support
68
+
69
+ Contact us if you have a question, find an issue, or want to contribute.
70
+ Find ways to reach us on [designsystem.amsterdam](https://designsystem.amsterdam/?path=/docs/docs-introduction--docs#send-a-message).