This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
gulp-less-jade-skeleton with all
npm packages installed. Try it out:
gulp-less-jade-skeleton lists no main file and has no index.js, so it can't be directly required. If this is a mistake, please let us know. It may however contain internal files that you can require manually:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
# Gulp + Less + Jade skeleton
This is a skeleton to build static websties using Jade and Less, plus a live-reload webserver for faster development. It uses:
Extra things to make your website faster:
Please open a thread in https://github.com/OscarDCorbalan/gulp-less-jade-skeleton/issues
* `git clone https://github.com/OscarDCorbalan/gulp-less-jade-skeleton.git`
* [Node.js](http://nodejs.org): Just download v6 and install. Alternatively, if you're on OS X, you can do `brew install node` . * [Gulp](http://gulpjs.com): In a shell console type `npm install -g gulp`. * Gulp plugins and app dependencies: Open the repo directory in the console and type `npm install` or, shorter, `npm i`. * This will install any neded Node modules (cssmin, jade, less...)
Within the download you'll find the following directories and files:
Everything is run with Gulp.
Defined gulp tasks are:
gulpto run all default tasks only once
gulp serverto run all tasks AND start the webserver plus a watch task. This will automatically process changes, in real time, in your source files and make them available in the local web server, and will also automatically reload your browser.
http://localhostin your browser. This simple html files contains some hints if you don't know how to start.
src/dir is where you put your code and assets.
public/dir is fully auto-generated by Gulp. Your HTML files and everything else will be here.
Just copy into your server everything generated in the
public/ dir and you should be fine to go.
Make sure that your Jade templates generate an index.html or that your server is configured to serve any other file you want as default.
It's also possible to configure you server to automatically deploy the
/public folder from a branch of your Git fork, but it's out of the scope of this Readme.
Want to list yours? Just send me a message or submit a pull request.