You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before using source files you will need to create a `theme.config` by renaming `theme.config.example`, and a site folder by renaming `_site/` to `site/`
41
42
42
43
You can then import Semantic from your own LESS files:
44
+
43
45
```less
44
46
/* Import all components */
45
47
@import'src/semantic';
46
48
```
47
49
48
50
To import individual components you will have to create a scope for each import using `& {}`
51
+
49
52
```less
50
53
/* Import a specific component */
51
54
& { @import'src/definitions/elements/button'; }
@@ -61,7 +64,6 @@ filename | usage | Initial Name
61
64
**site/** | folder storing all your site's variables and css overrides for each UI component | _site/
62
65
**semantic.json** | stores folder paths for build tools and current installed version for updates. Only necessary when using build tools | semantic.json.example
63
66
64
-
65
67
### Workflow
66
68
67
69
You will only need to use Semantic's build tools while refining your UI. When designing pages, you can rely on the compiled css packages in `dist/`.
@@ -119,9 +121,9 @@ You may also specify your own custom LESS in `site/elements/button.overrides`. T
119
121
You can modify `theme.config` to use any prepackaged theme available in `src/themes/`.
120
122
121
123
For example you can modify `theme.config` to use a `github` button theme by changing
124
+
122
125
```less
123
126
@button: 'github';
124
127
```
125
128
126
129
View the [Customization Guide](http://learnsemantic.com/developing/customizing.html) to learn more
0 commit comments