# grunt-html-build
## Linking Scripts and Styles
When using grunt-html-build, you can generate a HTML page which replace debug scripts and style links by production ones.
Let's take an application directory like this :
* app
* module1.js
* module2.js
* libs
* lib1.js
* lib2.js
* css
* lib1.css
* lib2.css
* app.css
* main.js
* index.html
### index.html
```html
```
### Gruntfile.js
```javascript
grunt.initConfig({
htmlbuild: {
src: 'index.html',
dest: 'dist/',
options: {
scripts: {
libs: 'libs/*.js',
app: 'app/*.js',
main: 'main.js'
},
styles: {
libs: [
'css/lib1.css',
'css/lib2.css'
],
app: 'css/app.css'
}
}
}
});
```
### Result
After grunt build, created index.html will contains links to files specified in options.
```html
```
### Tag options
* __optional__: Specifies that the tag can be omited from configuration. If not specified and no configuration exists for this particular tag. The task will fail.
* __inline__: Specifies that the tag must render the content of files directly in the resulting HTML.
* __noprocess__: Specifies that the tag content must not be processed by grunt.js templating engine. Must be used with __inline__.
* __[attributes]__: Specifies attributes that will be added to the resultings tags.