@kroo-web/design-system 1.0.61 → 1.0.63

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,4 +1,4 @@
1
- # Kroo Design System
1
+ # Kroo Design System
2
2
 
3
3
  ## Usage
4
4
 
@@ -9,11 +9,15 @@ First, install the package with whatever flavour of package manager that you wou
9
9
  ```bash
10
10
  npm install @kroo-web/design-system -S
11
11
  ```
12
+
12
13
  or
14
+
13
15
  ```bash
14
16
  yarn add @kroo-web/design-system -S
15
17
  ```
18
+
16
19
  or
20
+
17
21
  ```bash
18
22
  pnpm add @kroo-web/design-system -S
19
23
  ```
@@ -25,15 +29,15 @@ Next, add the following the highest up in your application, usually in the `App.
25
29
  This adds the tokens used in the design system to the root of the application. (the css modules come prebundled in the build this step is only for the tokens and odd global styles included in the design system).
26
30
 
27
31
  ```jsx
28
- import '@kroo-web/design-system/dist/styles/global.css';
32
+ import "@kroo-web/design-system/dist/styles/global.css";
29
33
  // For using the icons package
30
- import 'react-material-symbols/rounded';
34
+ import "react-material-symbols/rounded";
31
35
  ```
32
36
 
33
37
  That's all folks! You can now use the components in the design system in your application.
34
38
 
35
39
  ```jsx
36
- import { TextField } from '@kroo-web/design-system';
40
+ import { TextField } from "@kroo-web/design-system";
37
41
  ```
38
42
 
39
43
  ## react-toastify
@@ -60,12 +64,23 @@ This will overwrite the package with the local version of the package.
60
64
  npm link @kroo-web/design-system
61
65
  ```
62
66
 
63
-
64
-
65
67
  ## Next Steps
66
68
 
67
- This sways more on the side of component library rather than a design system due to the lack of tokens and living documentation. However, next steps would be to create a seperate package called @kroo-web/tokens allowing us to version the tokens and use them in the design system.
69
+ This sways more on the side of component library rather than a design system due to the lack of tokens and living documentation. However, next steps would be to create a seperate package called @kroo-web/tokens allowing us to version the tokens and use them in the design system.
68
70
 
69
71
  We could also use Token Studio with Figma to enable the designers to have control over the tokens allowing them to change the design system and see the changes in the design system in real time.
70
72
 
73
+ ## Deployments of storybook
74
+
75
+ This app uses Terraform to manage the Amplify instance in AWS
76
+
77
+ To make a change, amend the `/infra/service/amplify.tf` file and then run the below:
78
+
79
+ ```bash
80
+ npm run terraform:plan
81
+ npm run terraform:apply
82
+ ```
83
+
84
+ ## Gotchas
71
85
 
86
+ You need to set the github token in the `main.tf` file