@kirby-test-org/designsystem
v7.3.0
Published
Kirby Design Test Library.
Downloads
3
Readme
Kirby Design System
About
Kirby Design System is a UX Component library implementing the Kirby Design Philosophy.
Kirby Components are built on top of Angular and can be used in Angular projects.
The Kirby Cookbook, containing samples, status of components etc. can be accessed from https://cookbook.kirby.design.
Table of Contents
Installation
Install through npm:
npm i @kirby-test-org/designsystem
Include KirbyModule
Import the KirbyModule
in your AppModule
:
import { KirbyModule } from '@kirby-test-org/designsystem';
...
@NgModule({
imports: [
...,
KirbyModule
],
...
})
export class AppModule {}
Sass
Include the Kirby global styles in your app, e.g., in src/styles.scss
:
@import '~@kirby-test-org/designsystem/scss/global-styles';
In each .scss
file where you need to access the Sass utility functions from Kirby (e.g. colors or fonts) you must import the scss utilities:
@import '~@kirby-test-org/designsystem/scss/utils';
Generic Print Styles (Optional)
Kirby also provides a generic print stylesheet. It includes the basics. You most likely have to add local print styles specific to your app as well.
Import it into your app, e.g., in src/styles.scss
or in your local print stylesheet if you have one:
@import '~@kirby-test-org/designsystem/scss/print';
Testing
To unit-test applications using Kirby's Components, we recommend importing one of the following modules:
- When using jasmine:
import { KirbyTestingModule } from '@kirby-test-org/designsystem/
testing-jasmine'
;
- When using jest:
import { KirbyTestingModule } from '@kirby-test-org/designsystem/
testing-jest'
;
Example:
import { KirbyTestingModule } from '@kirby-test-org/designsystem/testing-jasmine';
describe('AppComponent', () => {
beforeEach(async(() => {
TestBed.configureTestingModule({
imports: [KirbyTestingModule],
declarations: [AppComponent]
}).compileComponents();
}));
...
});
For unit test performance reasons it's highly recommended to utilize these modules, since they provide a template-less implementation of the Kirby Components, but still translude content through <ng-content></ng-content>
and provide @Input
-decorated properties and @Output
-decorated EventEmitter
s, without
having to reflow the DOM, execute component logic etc.
Icons
Kirby comes bundled with a default set of icons. Make sure the .svg
files used by Kirby are copied to your output folder by adding the following to build > options > assets
in angular.json
:
{
...
"build": {
"options": {
"assets": [
...,
{
"glob": "**/*.svg",
"input": "node_modules/@kirby-test-org/designsystem/icons/svg",
"output": "./assets/kirby/icons/svg"
},
{
"glob": "close.svg",
"input": "node_modules/@kirby-test-org/designsystem/icons/svg",
"output": "./svg"
},
...
],
}
}
}
Migration Guides
For details on migrating from earlier versions of Kirby see our Migration Guides.
Folder Structure
The folder structure of the repository is based on Nrwl's NX mono-repository project.
A basic walkthrough is outlined in the structure below:
@kirby-test-org/designsystem
├── apps # Contains source code for applications
| └── cookbook # - Cookbook application (showcase and examples)
├── dist # Contains output files when building artifacts (for distribution)
| ├── apps
| └── libs
├── libs # Contains source code for libraries
| └── designsystem # - Actual implementation of library (designsystem)
├── scripts # Scripts for building artifacts
└── tools # Contains various tools
├── generate-mocks # - CLI utility for generating mocks for `@kirby-test-org/designsystem/testing-jasmine`
| # and `@kirby-test-org/designsystem/testing-jest` entry points.
├── sass-to-ts # - CLI and Webpack plugin for extract global variables from SASS to TS
├── schematics # - Angular schematics
Scripts
Below is an overview of most widely used scripts, available for this project.
Use them in your terminal like: npm run <script>
:
| Command | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| start | Starts the development server, providing a means of running (and developing on the Cookbook) |
| lint | Lints the entire project (both TypeScript and SCSS source code) |
| lint:cookbook | Lints the Cookbook application (both TypeScript and SCSS source code) |
| lint:designsystem | Lints the Designsystem library (both TypeScript and SCSS source code) |
| dist:cookbook | Builds a distribution folder of the Cookbook application |
| dist:designsystem | Builds a distribution folder of the Designsystem library |
| transpile:tools | Transpiles tools, required to produce library distribution (this is done as a post-install
hook, but may have value if altering tool implementation) |
Polyfills
Some features of Kirby requires polyfills to ensure compability across all major browsers (e.g. the ResizeObserverService
used by the automagic sizing feature of the Kirby Card
component).
To enable the polyfill, you register a polyfill loader that checks whether the polyfill is needed or the feature is already supported by the browser (and can skip requesting the polyfill).
To use the sizing feature of Kirby Card across all major browsers, you must copy additional files from the Kirby package to your output folder.
Add the following to build > options > assets
in angular.json
:
{
...
"build": {
"options": {
"assets": [
...,
{
"glob": "**/*",
"input": "./node_modules/@kirby-test-org/designsystem/polyfills",
"output": "./kirby/polyfills"
},
...
],
}
}
}
Finally, add the following to index.html
:
<head>
...
<script src="kirby/polyfills/resize-observer-polyfill-loader.min.js"></script>
</head>
Please note: If you don't want the additional http request for the polyfill loader, you can copy the contents of node_modules/@kirby-test-org/designsystem/polyfills/resize-observer-polyfill-loader.js
into a script
tag in index.html
instead
Chart Components
The Kirby chart components use Highcharts. Note that this is a licensed product.
Contributing
If you wish to contribute new features, bug fixes or something third to the project have a look at the contribution guidelines.