]> git.ipfire.org Git - ipfire.org.git/blame - src/scss/bootstrap-4.0.0-alpha.6/docs/getting-started/build-tools.md
Introduce autotools
[ipfire.org.git] / src / scss / bootstrap-4.0.0-alpha.6 / docs / getting-started / build-tools.md
CommitLineData
91e44d91
S
1---
2layout: docs
3title: Build tools
4description: Details on how to use Bootstrap's included build tools to compile source code, run tests, and more.
5group: getting-started
6---
7
8Bootstrap uses [Grunt](http://gruntjs.com) for its CSS and JavaScript build system and Jekyll for the written documentation. Our Gruntfile includes convenient methods for working with the framework, including compiling code, running tests, and more.
9
10## Contents
11
12* Will be replaced with the ToC, excluding the "Contents" header
13{:toc}
14
15## Tooling setup
16
17To use our Gruntfile and run our documentation locally, you'll need a copy of Bootstrap's source files, Node, and Grunt. Follow these steps and you should be ready to rock:
18
191. [Download and install Node](https://nodejs.org/download/), which we use to manage our dependencies.
202. Install the Grunt command line tools, `grunt-cli`, with `npm install -g grunt-cli`.
213. Navigate to the root `/bootstrap` directory and run `npm install` to install our local dependencies listed in [package.json](https://github.com/twbs/bootstrap/blob/master/package.json).
224. [Install Ruby][install-ruby], install [Bundler][gembundler] with `gem install bundler`, and finally run `bundle install`. This will install all Ruby dependencies, such as Jekyll and plugins.
23 - **Windows users:** Read [this unofficial guide](http://jekyll-windows.juthilo.com/) to get Jekyll up and running without problems.
24
25When completed, you'll be able to run the various Grunt commands provided from the command line.
26
27[install-ruby]: https://www.ruby-lang.org/en/documentation/installation/
28[gembundler]: https://bundler.io/
29
30## Using Grunt
31
32Our Gruntfile includes the following commands and tasks:
33
34| Task | Description |
35| --- | --- |
36| `grunt` | Run `grunt` to run tests locally and compile the CSS and JavaScript into `/dist`. **Uses [Sass](http://sass-lang.com/), [Autoprefixer][autoprefixer], and [UglifyJS](http://lisperator.net/uglifyjs/).** |
37| `grunt dist` | `grunt dist` creates the `/dist` directory with compiled files. **Uses [Sass](http://sass-lang.com/), [Autoprefixer][autoprefixer], and [UglifyJS](http://lisperator.net/uglifyjs/).** |
38| `grunt test` | Runs [scss-lint](https://github.com/brigade/scss-lint), [ESLint](http://eslint.org/) and [QUnit](https://qunitjs.com/) tests headlessly in [PhantomJS](http://phantomjs.org/) (used for CI). |
39| `grunt docs` | Builds and tests CSS, JavaScript, and other assets which are used when running the documentation locally via `jekyll serve`. |
40| `grunt watch` | This is a convenience method for watching just Sass files and automatically building them whenever you save. |
41
42## Autoprefixer
43
44Bootstrap uses [Autoprefixer][autoprefixer] (included in our Gruntfile and build process) to automatically add vendor prefixes to some CSS properties at build time. Doing so saves us time and code by allowing us to write key parts of our CSS a single time while eliminating the need for vendor mixins like those found in v3.
45
46We maintain the list of browsers supported through Autoprefixer in a separate file within our GitHub repository. See [`/grunt/postcss.js`](https://github.com/twbs/bootstrap/blob/master/grunt/postcss.js) for details.
47
48## Local documentation
49
50Running our documentation locally requires the use of Jekyll, a decently flexible static site generator that provides us: basic includes, Markdown-based files, templates, and more. Here's how to get it started:
51
521. Run through the [tooling setup](#tooling-setup) above to install Jekyll (the site builder) and other Ruby dependencies with `bundle install`.
532. From the root `/bootstrap` directory, run `bundle exec jekyll serve` in the command line.
543. Open <http://localhost:9001> in your browser, and voilĂ .
55
56Learn more about using Jekyll by reading its [documentation](https://jekyllrb.com/docs/home/).
57
58## Troubleshooting
59
60Should you encounter problems with installing dependencies or running Grunt commands, uninstall all previous dependency versions (global and local). Then, rerun `npm install`.
61
62[autoprefixer]: https://github.com/postcss/autoprefixer