@gov-design-system-ce/fonts 0.0.1 → 0.0.2
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/package.json +1 -1
- package/readme.md +8 -83
package/package.json
CHANGED
package/readme.md
CHANGED
|
@@ -1,86 +1,11 @@
|
|
|
1
|
-
|
|
1
|
+
# Gov Design System Fonts
|
|
2
|
+
This package includes Gov Design System CE Fonts.
|
|
2
3
|
|
|
3
|
-
|
|
4
|
+
## Usage
|
|
5
|
+
For usage instructions, please see [documentation](https://designsystem.gov.cz/).
|
|
4
6
|
|
|
5
|
-
|
|
7
|
+
## Copyright
|
|
8
|
+
Copyright(c) 2020 - 2023 Ministerstvo vnitra České republiky
|
|
6
9
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
# Stencil
|
|
11
|
-
|
|
12
|
-
Stencil is a compiler for building fast web apps using Web Components.
|
|
13
|
-
|
|
14
|
-
Stencil combines the best concepts of the most popular frontend frameworks into a compile-time rather than run-time
|
|
15
|
-
tool. Stencil takes TypeScript, JSX, a tiny virtual DOM layer, efficient one-way data binding, an asynchronous rendering
|
|
16
|
-
pipeline (similar to React Fiber), and lazy-loading out of the box, and generates 100% standards-based Web Components
|
|
17
|
-
that run in any browser supporting the Custom Elements v1 spec.
|
|
18
|
-
|
|
19
|
-
Stencil components are just Web Components, so they work in any major framework or with no framework at all.
|
|
20
|
-
|
|
21
|
-
## Getting Started
|
|
22
|
-
|
|
23
|
-
To start building a new web component using Stencil, clone this repo to a new directory:
|
|
24
|
-
|
|
25
|
-
```bash
|
|
26
|
-
git clone https://github.com/ionic-team/stencil-component-starter.git my-component
|
|
27
|
-
cd my-component
|
|
28
|
-
git remote rm origin
|
|
29
|
-
```
|
|
30
|
-
|
|
31
|
-
and run:
|
|
32
|
-
|
|
33
|
-
```bash
|
|
34
|
-
npm install
|
|
35
|
-
npm start
|
|
36
|
-
```
|
|
37
|
-
|
|
38
|
-
To build the component for production, run:
|
|
39
|
-
|
|
40
|
-
```bash
|
|
41
|
-
npm run build
|
|
42
|
-
```
|
|
43
|
-
|
|
44
|
-
To run the unit tests for the components, run:
|
|
45
|
-
|
|
46
|
-
```bash
|
|
47
|
-
npm test
|
|
48
|
-
```
|
|
49
|
-
|
|
50
|
-
Need help? Check out our docs [here](https://stenciljs.com/docs/my-first-component).
|
|
51
|
-
|
|
52
|
-
## Naming Components
|
|
53
|
-
|
|
54
|
-
When creating new component tags, we recommend _not_ using `stencil` in the component name (ex: `<stencil-datepicker>`).
|
|
55
|
-
This is because the generated component has little to nothing to do with Stencil; it's just a web component!
|
|
56
|
-
|
|
57
|
-
Instead, use a prefix that fits your company or any name for a group of related components. For example, all of the
|
|
58
|
-
Ionic generated web components use the prefix `ion`.
|
|
59
|
-
|
|
60
|
-
## Using this component
|
|
61
|
-
|
|
62
|
-
There are three strategies we recommend for using web components built with Stencil.
|
|
63
|
-
|
|
64
|
-
The first step for all three of these strategies is
|
|
65
|
-
to [publish to NPM](https://docs.npmjs.com/getting-started/publishing-npm-packages).
|
|
66
|
-
|
|
67
|
-
### Script tag
|
|
68
|
-
|
|
69
|
-
- Put a script tag similar to
|
|
70
|
-
this `<script type='module' src='https://unpkg.com/my-component@0.0.1/dist/my-component.esm.js'></script>` in the head
|
|
71
|
-
of your index.html
|
|
72
|
-
- Then you can use the element anywhere in your template, JSX, html etc
|
|
73
|
-
|
|
74
|
-
### Node Modules
|
|
75
|
-
|
|
76
|
-
- Run `npm install my-component --save`
|
|
77
|
-
- Put a script tag similar to
|
|
78
|
-
this `<script type='module' src='node_modules/my-component/dist/my-component.esm.js'></script>` in the head of your
|
|
79
|
-
index.html
|
|
80
|
-
- Then you can use the element anywhere in your template, JSX, html etc
|
|
81
|
-
|
|
82
|
-
### In a stencil-starter app
|
|
83
|
-
|
|
84
|
-
- Run `npm install my-component --save`
|
|
85
|
-
- Add an import to the npm packages `import my-component;`
|
|
86
|
-
- Then you can use the element anywhere in your template, JSX, html etc
|
|
10
|
+
## Keywords
|
|
11
|
+
none
|