This is a React Typescript components library which supports React and Next applications produced by Oak National Academy.
This library is suitable for use in an app using React 18 and Next.js 13.5+
You can install it using npm i @oaknational/oak-components or any other package manager that supports the NPM registry.
👉 You'll need two environment variables to enable icons NEXT_PUBLIC_OAK_ASSETS_HOST and NEXT_PUBLIC_OAK_ASSETS_PATH. Values for these can be obtained from the .env config from OWA or from a fellow engineer.
For components to be styled correctly they will need access to a theme, some global styles and the Lexend font.
If you're using the Next.js App router your root layout should look something like:
// layout.js
import { OakThemeProvider, oakDefaultTheme, OakGlobalStyle } from "@oaknational/oak-components";
import { Lexend } from "next/font/google";
const lexend = Lexend({ subsets: ['latin'] });
export default function RootLayout({ children }) {
return (
<html lang="en">
<OakGlobalStyle />
<body className={lexend.className}>
<OakThemeProvider theme={oakDefaultTheme}>{children}</OakThemeProvider>
</body>
</html>
);
}To enable SSR of styles and avoid a flicker of unstyled content you'll need to configure your Next.js app to support styled-components
If you're using TypeScript you might want to add @types/styled-components to your development dependencies (npm i -D @types/styled-components). This will ensure that all components are properly type hinted in your IDE.
- Copy the example env config
cp .env.example .env - Ask a colleague for the values to populate
.env - run
nvm use - run
npm install - To view the storybook run
npm run storybook
We use conventional commits and semantic versioning. Releases are managed by Semantic Release and are automatically published to NPM on every merge to main.
Changes should go through a pull-request to main and require approval by at least 1 reviewer. You should seek reviews from a QA/designer/PM when necessary.
The release process is driven by the commit messages, following the Conventional Commits standard. The @semantic-release/commit-analyzer plugin will determine the type of release (major, minor, or patch) based on the commit message.
Here’s a summary of the commit types that trigger a release:
- Patch release (x.x.x): Commits that start with
fix:or contain other conventional keywords indicating bug fixes. - Minor release (x.x.0): Commits that start with
feat:indicate a new feature but not a breaking change. - Major release (x.0.0): Commits that contain
BREAKING CHANGE:in their description, which indicates a breaking change that requires a major version bump.
Commit messages that begin with chore, refactor or docs, etc. will not trigger the release process.
Sometimes it isn't enough to develop entirely inside Storybook and it might be necessary to try local changes inside a target app. You can do this with yalc
- Install yalc
npm i yalc -g - Run
npm run publish:localto add the package to yalc's local registry. - Inside the target app run
yalc add @oaknational/oak-components— this will install the package from the local registry like it would from NPM- 🚨 if you're an Oak engineer developing in OWA there is a convenience script and you should use
npm run use-local-componentsinstead as it will perform some additional work to remove any existing installation of the package.
- 🚨 if you're an Oak engineer developing in OWA there is a convenience script and you should use
- Now when you start your target app you should have access to the locally packaged version of the library
- To uninstall the local package you can run
yalc remove @oaknational/oak-componentsinside the target app- 🚨 if you're an Oak engineer developing in OWA there is a convenience script and you should use
npm run remove-local-componentsinstead as it will automatically re-install the library from NPM.
- 🚨 if you're an Oak engineer developing in OWA there is a convenience script and you should use
We're trying to follow the tenets of "Atomic design". Brad Frost's book is a great resource if you're just starting out building your first component for this library. It's also a great reference if you're in doubt as to where a component belongs (it can be a little fuzzy at times!).
Components are organised into a three tier hierarchical structure applying the following rules:
- Can import other atoms
- Imports from molecules and organisms are forbidden!
- Generic
- Unstyled
- Avoid embedded logic and state
- No sub-components
(eg.
Box)
- Imports from atoms components and other molecules
- Imports from organisms are forbidden!
- Generic
- Styled
- Avoid embedded logic and state
- No sub-components
(eg.
IconButton)
-
Imports from atoms, molecules and occasionally organisms
-
Combines multiple molecules together
-
Applicable to a limited range of contexts which might occur in multiple apps
-
Styled
-
May contain embedded logic or state
-
May be split into sub-components (eg.
SchoolInputForm)NB. these rules are a work in progress. Modifications may be required as the library builds.
Please see our security.txt file.
We don't currently accept external contributions to the code base, but this is under review and we hope to find an approach the works for us and the community.
As with all web projects we are dependent on open source libraries maintained by others. While it is not practical to acknowledge them all, we would nevertheless like to express our gratitude for the contributions and efforts of the OSS community. Our dependency list can be found in our package.json file.
Unless stated otherwise, the codebase is released under the MIT License. This covers both the codebase and any sample code in the documentation. Where any Oak National Academy trademarks or logos are included, these are not released under the MIT License, and should be used in line with Oak National Academy brand guidelines.
Any documentation included is © Oak National Academy and available under the terms of the Open Government Licence v3.0, except where otherwise stated.