A grunt task to help integrate Semantic UI to your project
If you haven't used grunt before, be sure to check out the Getting Started guide, as it explains how to create a gruntfile as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:
npm install grunt-semantic-ui --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of Javascript:
grunt.loadNpmTasks('grunt-semantic-ui');
The grunt-semantic-ui task works by parsing a json encoded configuration file, where you declare which parts of semantic-ui you want to use. This configuration is read, and the generated css, js and asset files are copied to the provided destination. As a minimum, you must provide a configuration file, and a destination:
'semantic-ui': {
all: {
options: {
config: 'semantic-config.json',
dest: 'mycoolapp/public/'
}
}
}
The semantic config json file, is a simple json representation of the semantic source directory structure of the components you want to use.
For example, if you need to use Semantic's Global reset and site components, your semantic-config.json
would look like that:
{
"globals": [
"reset",
"site"
],
}
grunt-semantic-ui
uses Semantic's default
theme by default. You can use a different theme by adding a theme.config file in your project, and adding a theme
property in the task's options, that points to the theme file.
'semantic-ui': {
all: {
options: {
config: 'semantic-config.json',
dest: 'mycoolapp/public/',
theme: 'mycoolapp/my-semantic-theme.config'
}
}
}
Type: String
The path to the semantic configuration file, that is used to define what components are going to be compiled. Alternatively, you can provide the configuration object inline.
Type String
The path to the destination folder where the compiled files will be written. NOTE
the following three folders will be created, if they don't already exist: css
, scripts
, themes
Type String
The path to a semantic-ui theme configuration file.
- 2015-09-09 v0.1.5 Fixed a bug with the default theme.config path
- 2015-09-07 v0.1.4 Some bugfixes, cleaner output
- 2015-09-04 v0.1.0 First release