@kajabi-ui/styles 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/README.md +179 -4
- package/dist/tokens/core.json +1143 -0
- package/dist/tokens/semantic.json +812 -0
- package/package.json +4 -3
package/README.md
CHANGED
|
@@ -1,7 +1,182 @@
|
|
|
1
|
-
# Styles
|
|
1
|
+
# Kajabi Design System Tokens and Styles (@kajabi-ui/styles)
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A comprehensive design tokens package that provides standardized design primitives for Kajabi's design system. This package (@kajabi-ui/styles) serves as the foundation for consistent UI development across all Kajabi products.
|
|
4
4
|
|
|
5
|
-
## Building
|
|
6
5
|
|
|
7
|
-
|
|
6
|
+
## Purpose
|
|
7
|
+
|
|
8
|
+
This repository houses Kajabi's design system tokens, which serve as the single source of truth for colors, typography, spacing, and other design primitives used across Kajabi's products. These tokens ensure design consistency, streamline development, and create a unified visual experience.
|
|
9
|
+
|
|
10
|
+
Key features:
|
|
11
|
+
- Centralized design tokens management
|
|
12
|
+
- Platform-agnostic implementation
|
|
13
|
+
- Compatible with multiple formats (CSS, SCSS, JSON)
|
|
14
|
+
- Built with [Style Dictionary](https://amzn.github.io/style-dictionary) and [Tokens Studio](https://tokens.studio/)
|
|
15
|
+
- Easy integration with CDN options
|
|
16
|
+
|
|
17
|
+
## Installation
|
|
18
|
+
|
|
19
|
+
### NPM Package
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
npm install @kajabi-ui/styles
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
or
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
yarn add @kajabi-ui/styles
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
### Usage in Projects
|
|
32
|
+
|
|
33
|
+
#### CSS Import
|
|
34
|
+
|
|
35
|
+
```css
|
|
36
|
+
@use '~@kajabi-ui/styles/pine/pine.css';
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
#### SCSS Import
|
|
40
|
+
|
|
41
|
+
```scss
|
|
42
|
+
@use '~@kajabi-ui/styles/pine/pine.scss';
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
#### JavaScript Import
|
|
46
|
+
|
|
47
|
+
```javascript
|
|
48
|
+
import '@kajabi-ui/styles/pine/pine.css';
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### CDN Usage with jsDelivr
|
|
52
|
+
|
|
53
|
+
You can also use jsDelivr to include our design tokens directly in your HTML without installing the package:
|
|
54
|
+
|
|
55
|
+
```html
|
|
56
|
+
<!-- Global CSS -->
|
|
57
|
+
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@kajabi-ui/styles/dist/pine/pine.css">
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
The CDN option is ideal for:
|
|
61
|
+
- Quick prototyping
|
|
62
|
+
- Projects that don't use a build system
|
|
63
|
+
- Third-party integrations with Kajabi
|
|
64
|
+
|
|
65
|
+
### Specific Component Usage
|
|
66
|
+
|
|
67
|
+
For more granular imports of specific components:
|
|
68
|
+
|
|
69
|
+
```css
|
|
70
|
+
/* Import only chip tokens */
|
|
71
|
+
@use '@kajabi-ui/styles/pine/components/pds-chip/pds-chip.tokens.scss';
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
## Available Token Categories
|
|
75
|
+
|
|
76
|
+
- Colors and themes
|
|
77
|
+
- Typography (font families, sizes, weights)
|
|
78
|
+
- Spacing and layout
|
|
79
|
+
- Border properties (width, radius)
|
|
80
|
+
- Shadows and elevation
|
|
81
|
+
- Z-index
|
|
82
|
+
- Motion and animations
|
|
83
|
+
- Component-specific tokens (button, chip, etc.)
|
|
84
|
+
|
|
85
|
+
## Project Structure
|
|
86
|
+
|
|
87
|
+
```
|
|
88
|
+
ds-tokens/
|
|
89
|
+
├── packages/
|
|
90
|
+
│ └── styles/ # Main package (@kajabi-ui/styles)
|
|
91
|
+
│ ├── src/
|
|
92
|
+
│ │ ├── tokens/ # Source token files (JSON format)
|
|
93
|
+
│ │ └── lib/ # Build and transformation scripts
|
|
94
|
+
└── .github/ # GitHub workflows and configuration
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
## Development with Nx
|
|
98
|
+
|
|
99
|
+
This project is built with [Nx](https://nx.dev/), a smart, extensible build framework. Nx helps manage monorepos and provides efficient build tools for multiple packages.
|
|
100
|
+
|
|
101
|
+
### Using Nx Commands
|
|
102
|
+
|
|
103
|
+
#### Building the Project
|
|
104
|
+
|
|
105
|
+
```bash
|
|
106
|
+
# Build the styles package
|
|
107
|
+
npx nx run @kajabi-ui/styles:build
|
|
108
|
+
|
|
109
|
+
# Or using the shorter syntax
|
|
110
|
+
npx nx build @kajabi-ui/styles
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
#### Running Other Scripts
|
|
114
|
+
|
|
115
|
+
```bash
|
|
116
|
+
# Generate tokens
|
|
117
|
+
npx nx run @kajabi-ui/styles:generate
|
|
118
|
+
|
|
119
|
+
# Run linting
|
|
120
|
+
npx nx run @kajabi-ui/styles:lint
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
#### Nx Targets
|
|
124
|
+
|
|
125
|
+
To see all available targets for the styles package:
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
npx nx show project @kajabi-ui/styles
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
|
|
132
|
+
### Using Token Studio
|
|
133
|
+
|
|
134
|
+
This project uses [Tokens Studio](https://tokens.studio/) (formerly Figma Tokens) to manage design tokens. Token Studio provides a bridge between design and development by allowing designers to maintain tokens in Figma that can be exported and used in the development workflow.
|
|
135
|
+
|
|
136
|
+
#### Getting Started with Token Studio:
|
|
137
|
+
|
|
138
|
+
1. **For Designers**:
|
|
139
|
+
- Install the [Tokens Studio for Figma](https://www.figma.com/community/plugin/843461159747178978/tokens-studio-for-figma) plugin
|
|
140
|
+
- Connect to our shared token repository
|
|
141
|
+
- Make changes through the Token Studio interface
|
|
142
|
+
|
|
143
|
+
2. **For Developers**:
|
|
144
|
+
- Token changes are synchronized with our repository through the build process
|
|
145
|
+
- Token files are stored in the `src/tokens/` directory
|
|
146
|
+
- Review and implement token changes using the standard contribution workflow
|
|
147
|
+
|
|
148
|
+
### Contribution Workflow
|
|
149
|
+
|
|
150
|
+
1. Create a feature branch
|
|
151
|
+
```bash
|
|
152
|
+
git checkout -b feature/your-feature-name
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
2. Make your changes to the token files in `src/tokens/`
|
|
156
|
+
|
|
157
|
+
3. Run the token generation script
|
|
158
|
+
```bash
|
|
159
|
+
npm run generate
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
4. Verify changes work as expected
|
|
163
|
+
|
|
164
|
+
5. Commit your changes with a descriptive message
|
|
165
|
+
```bash
|
|
166
|
+
git commit -m "Add new color tokens for marketing pages"
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
6. Push your changes and create a pull request
|
|
170
|
+
```bash
|
|
171
|
+
git push origin feature/your-feature-name
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
7. Request a review from the design systems team
|
|
175
|
+
|
|
176
|
+
## Release Process
|
|
177
|
+
|
|
178
|
+
The package is published to NPM with a structure that makes tokens accessible without the `dist/` prefix in import paths, ensuring a clean and intuitive developer experience.
|
|
179
|
+
|
|
180
|
+
---
|
|
181
|
+
|
|
182
|
+
© 2025 Kajabi, LLC. All rights reserved.
|