My boilerplate for creating new web projects with Gulp.js. Forked from Todd Motto's GulpOSS with some additions from Mark Goodyear and Big Bite Creative and various tutorials around the web.
- Lints and concatenates JS files.
- Compiles Sass files and automatically adds vendor prefixes.
- Exports both minified and expanded JS and CSS files with header info.
- Generates SVG sprites.
- Generates documentation.
- Cleans up file directories.
- Runs Jasmine unit tests and generates reports.
- Includes a
.travis.ymlfile for continuous integration with TravisCI.
In This Documentation
- Getting Started
- File Structure
- Working with the Source Files
- Options & Settings
- Continuous Integration
- License
Make sure these are installed first.
- In bash/terminal/command line,
cdinto your project directory. - Run
npm installto install required files. - When it's done installing, run one of the task runners to get going:
gulpmanually compiles files and runs unit tests.gulp watchautomatically compiles files, runs unit tests, and applies changes using LiveReload.gulp testcompiles files and runs unit tests.
Add your files to the appropriate src subdirectories. Gulp will process and and compile them into dist.
- Content in subdirectories under the
jsfolder will be concatenated. For example, files injs/detectswill compile intodetects.js. Files directly underjswill compile individually. - Files in the
imgdirectory will be copied as-is into thedist/imgdirectory. - SVG files placed in the
src/svgdirectory will be optimized and compiled into thedist/svgdirectory. SVG files placed in a subdirectory ofsrc/svgwill be compiled into a single SVG sprite named after the subdirectory.
gulp-boilerplate/
|—— dist/
| |—— css/
| | |—— myplugin.css
| | |—— myplugin.min.css
| |—— img/
| | |—— # image files
| |—— js/
| | |—— classList.js
| | |—— classList.min.js
| | |—— myplugin.js
| | |—— myplugin.min.js
| |—— svg/
| | |—— icons.svg
| |—— # static assets
|—— docs/
| |—— assets/
| |—— dist/
| |—— index.html
| |—— # other docs
|—— src/
| |—— docs/
| | |—— _templates/
| | | |—— _header.html
| | | |—— _footer.html
| | |—— assets/
| | | |—— # doc-specific assets
| | |—— index.html
| | |—— # other docs
| |—— img/
| | |—— # image files
| |—— js/
| | |—— classList.js
| | |—— myplugin.js
| |—— sass/
| | |—— _config.scss
| | |—— _mixins.scss
| | |—— components/
| | | |—— myplugin.scss
| |—— svg/
| | |—— # svgs
|—— test/
| |—— coverage/
| | |—— various files
| |—— results/
| | |—— unit-tests.html
| |—— spec/
| | |—— spec-myplugin.js
|—— .travis.yml
|—— gulfile.js
|—— index.html
|—— package.json
|—— README.md
|—— README-TEMPLATE.md
Sass files are located in src > sass. Gulp generates minified and unminified CSS files. It also includes autoprefixer, which adds vendor prefixes for you if required by the last two versions of a browser.
JavaScript files are located in the src > js directory.
Files placed directly in the js folder will compile directly to dist > js as both minified and unminified files. Files placed in subdirectories will also be concatenated into a single file. For example, files in js/detects will compile into detects.js. Files directly under js will compile individually.
Gulp Boilerplate is set up for unit testing with Jasmine. Add your tests to test/spec/spec-myplugin.js. Adjust filenames and references as needed.
Unit test results are printed in terminal, but you can also view them in a browser under test/results/unit-tests.html. Get a report of how much of your scripts is covered by testing under test/coverage.
SVG files placed in the src/svg directory will be optimized with SVGO and compiled into dist/svg as-is.
SVG files placed in subdirectories of src/svg will be ocmpiled into a single SVG sprite named after the parent directory. For example, files in src/svg/icons would compile into a single icons.svg file.
Add HTML or markdown (.md or .markdown) files to your docs folder in src.
The _templates directory in src contains the _header.html and _footer.html templates. These are automatically added to the beginning and end of each documentation page. You can also add your own templates to the _templates directory. Include template files in your docs by writing @@include('path-to-file') on its own line in your markup (or markdown).
Files placed in the assets directory will be moved over as-is to the docs directory. The boilerplate will also add a copy of your dist files so you can use them in your documentation.
Open up package.json to change the name, version, URL and other data about the project.
Inside gulpfile.js, banner.full is the expanded header, while banner.min is included with minified content.
Inside gulpfile.js you'll see a variable named paths. Adjust the paths to suit your workflow.
var paths = {
input: 'src/**/*',
output: 'dist/',
scripts: {
input: 'src/js/*',
output: 'dist/js/'
},
styles: {
input: 'src/sass/**/*.{scss,sass}',
output: 'dist/css/'
},
svgs: {
input: 'src/svg/**/*.svg',
output: 'dist/svg/'
},
static: 'src/static/**',
test: {
input: 'src/js/**/*.js',
karma: 'test/karma.conf.js',
spec: 'test/spec/**/*.js',
coverage: 'test/coverage/',
results: 'test/results/'
},
docs: {
input: 'src/docs/*.{html,md,markdown}',
output: 'docs/',
templates: 'src/docs/_templates/',
assets: 'src/docs/assets/**'
}
};This boilerplate includes a configuration file for Travis CI, a continuous integration service for GitHub.
If you sign-up and activate it for your repository, Travis CI will run your build and execute any processes to make sure everything is working as expected. This is particularly useful when working with a team or managing open source projects with multiple contributors.
The .travis.yml file is pre-configured for the boilerplate's build system. Even if you add files or update the Gulp tasks, you shouldn't need to change anything for it to work.
This boilerplate also works with Codeship.io.
After you have signed up and connected your repository you will be given options for configuring your tests. In the dropdown labeled Select your technology to prepopulate basic commands choose node.js. This will cause codeship to run npm install prior to running your tests.
Then in the Configure Test Pipelines box replace grunt test with gulp test. Save your settings and make
a commit to your repository. Codeship should then build and test your repository successfully.
In lieu of a formal style guide, take care to maintain the existing coding style. Please apply fixes to both the development and production code. Don't forget to update the version number, and when applicable, the documentation.
The code is available under the MIT License.