This repository has been archived by the owner on Feb 7, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
site-content.txt
85 lines (48 loc) · 2.2 KB
/
site-content.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
###Name:
Kaizen
###Intro:
a Japanese term that means “continuous improvement.” Kaizen (KYE-zen) is an effort to do things faster and more efficiently. On the factory floor, workers in Japanese factories are encouraged to provide feedback and suggestions, often taking time at the end of their shifts to brainstorm ideas. To “kaizen” a problem means to dissect it and come up with solutions.
###Methodology:
- OOCSS
- BEM
###Tech:
- Sass
- Bourbon
---
###Why?
It's about simplicity - We've built a nimble framework to get you started without the stuff you don't need. It only takes a few minutes to setup and every line of code is carefully considered with performance in mind. Think of it as the pencil instead of the blank page.
###What?
It's a bare-bones framework, it's meant to be hacked, modified and twisted to fit within your project yet it provides you with an extremely organized framework to build upon with just the right amount of utility and components.
###HOW?
If you're already using Sass, you likely have Ruby installed. To use Kaizen simply install it:
```
gem install kaizen-cli
```
To learn how to use the Kaizen CLI run:
```
kzn --help
```
---
###SEIRI
(ORGANIZATION)
Keep just what is needed. Clearly distinguish between what is required and what should be optional.
###SEITON
(ORDERLINESS)
Have a place for everything and implement a system whereby everything is in its place. Organize in a way that ensures that necessary things are easily accessible.
###SEISO
(CLEANLINESS)
This can be viewed as systematic clearing where everything is continuesly improved, tested and maintained on a regular basis.
###SEIKETSU
(STANDARDISATION)
Establish methods that will ensure the effective continuation of steps 1 through 3.
---
###MOBILE-FIRST
With mobile first, most styles are inherited from the smaller breakpoint, this keeps code light and manageable.
###TYPOGRAPHY
Typography reset, some utilities like .text-center and easily configurable settings.
###UNSTYLED
There's no need to remove styles, simply add your brand colors to the Kaizen framework.
###PERFORMANCE
Optional components are disabled by default, with a base stylesheet of ~7kb.
###Footer
This project is maintained by Wixel