@royaloperahouse/chord 0.2.6-a → 0.3.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,68 +1,91 @@
1
- # Royal Opera House - chord
1
+ # Royal Opera House - Front End Design System
2
2
 
3
- Welcome to the Royal Opera House library components `@royaloperahouse/chord`.
3
+ Welcome to the Royal Opera House Front End Design System, `@roh-frontend/design-system`.
4
4
 
5
5
  This package is a library of UI components intended to be used in the ROH website.
6
6
 
7
+ It uses React, TypeScript, TSDX and Storybook.
7
8
 
8
- ## Install
9
+ ## Commands
10
+
11
+ The required package dependencies need to be insalled using `yarn`. Once ready you can issue the following:
12
+
13
+ To run Lint on the package use:
14
+
15
+ ```bash
16
+ yarn lint # you can also use the --fix option to perform automatic fixes
17
+ ```
18
+
19
+ To run the unit tests (using Jest) use:
20
+
21
+ ```bash
22
+ yarn test # you can also use the -u option to update snapshots if needed
23
+ ```
24
+
25
+ To run the unit tests (using Jest) and store them for display in storybook use:
26
+
27
+ ```bash
28
+ yarn test-storybook # you can also use the -u option to update snapshots if needed
29
+ ```
30
+
31
+ To run storybook use:
9
32
 
10
33
  ```bash
11
- npm i --save @royaloperahouse/chord
34
+ yarn storybook
12
35
  ```
36
+
37
+ To build a static version of storybook use:
38
+
13
39
  ```bash
14
- yarn add @royaloperahouse/chord
40
+ yarn build-storybook
15
41
  ```
16
42
 
17
- ## Usage
43
+ This will create a static copy in `./storybook-static`, and there is an index.html page inside the core directory. This allows the site to be previewed directly in the git repository via serving pages (it needs to be configured for that branch).
18
44
 
19
- ```javascript
20
- import {
21
- Footer, GlobalStyles, ThemeProvider, ThemeType,
22
- } from '@royaloperahouse/chord';
45
+ To build the package use:
23
46
 
47
+ ```bash
48
+ yarn build
24
49
  ```
25
- ## Sample
26
-
27
- ```javascript
28
-
29
- import {
30
- Footer, GlobalStyles, ThemeProvider, ThemeType,
31
- } from '@royaloperahouse/chord';
32
-
33
-
34
- const App = ({ children }: InnerProps): React.ReactElement => (
35
- <ErrorBoundary>
36
- <ThemeProvider theme={ThemeType.Core}>
37
- <GlobalStyles />
38
- <Wrapper>
39
- <Header />
40
- <GlobalStyle />
41
- <HealthBanner />
42
- <ErrorBoundary>
43
- <Content>
44
- {children}
45
- </Content>
46
- </ErrorBoundary>
47
- <LiveChat />
48
- </Wrapper>
49
- <Footer data={footerData} />
50
- </ThemeProvider>
51
- </ErrorBoundary>
52
- );
53
50
 
51
+ To release a new version.
52
+ Release will be publishe in npm (NPM_TOKEN will be required)
53
+ Storybook will be pushed to bitbucket. *** Push will be done Ensure you don't have things pendint to push
54
+
55
+ ```bash
56
+ NPM_ROH_TOKEN={NPM_TOKEN} RELEASE_VERSION={RELEASE_VERSION} yarn publish-release
54
57
  ```
55
58
 
56
- ## Components
57
59
 
58
- Editorial, Footer, GlobalStyles, Grid, GridItem, Heading, Icon, Navigation, PeopleListing, PrimaryButton, PromoWithTitle, SecondaryButton, SectionSplitter, SectionTitle, Sponsorship, TertiaryButton, TextOnly, ThemeProvider, TypeTags
60
+ MORE INFO TO FOLLOW - PARTICULARLY FOR THE CI SETUP AND HOW PACKAGES ARE PUSHED.
61
+
62
+ # Recommended Use of Package
63
+
64
+ `TODO`
65
+
66
+ # Processes to follow prior to commits
67
+
68
+ Before a commit is made you need to do the following:
69
+
70
+ - Make sure that you are in your own work branch (properly named, including the JIRA ticket number and a short description)
71
+ - `yarn lint` - ensure that you are not introducing errors
72
+ - `yarn test` - ensure that tests are running as expected
73
+ - `yarn test-storybook` - Save the test results to for the static site
74
+ - `yarn build-storybook` - Update the static site
75
+ - Commit your changes in your branch locally
59
76
 
77
+ Next, if you are ready to merge into the main development branch then:
60
78
 
61
- ## Types
79
+ - _*ensure that you pull the latest changes from that branch into your new branch, resolving any merge conflicts that may arise*_
80
+ - Commit any merge changes locally
81
+ - Push your branch changes to the origin repo
82
+ - Raise a Pull Request to merge back into the main development branch, AND ensure that the required reviewers are assigned.
83
+ - The reviewers may raise issues, and once resolved, they will be responsible for performing the merge.
62
84
 
63
- ThemeType
85
+ ### Example
64
86
 
87
+ TODO
65
88
 
66
- ## Documentation
89
+ ### Bundle analysis
67
90
 
68
- See Storybook as a reference
91
+ Calculates the real cost of your library using [size-limit](https://github.com/ai/size-limit) with `yarn size` and visulize it with `yarn analyze`.
@@ -96,8 +96,8 @@ var commonColors = {
96
96
  var fontFamilies = {
97
97
  adobeGaramondPro: 'adobe-garamond-pro',
98
98
  adobeGaramondProItalics: 'adobe-garamond-pro-italics',
99
- gothamSSmMedium: 'Gotham SSm Medium',
100
- gothamSSm: 'Gotham SSm',
99
+ gothamSSmMedium: 'Gotham SSm B',
100
+ gothamSSm: 'Gotham SSm A',
101
101
  sabonNextLTProRegular: 'Sabon Next LT Pro Regular',
102
102
  sabonNextLTProRegularItalics: 'Sabon Next LT Pro Regular Italics'
103
103
  };