_src | ||
_config.yml | ||
.gitignore | ||
assets sheet.psd | ||
bower.json | ||
Gemfile | ||
Gemfile.lock | ||
Gruntfile.js | ||
package.json | ||
README.md |
kremalicious3
kremalicious.com based on Jekyll. Neat.
Requirements
You need to have the following tools installed on your development machine before moving on:
Get up and running
For various reasons the assets build process and Jekyll site generation is managed through Grunt instead of jekyll
or rake
.
Both, grunt server
and grunt build
, use grunt-jekyll to first generate the site into the generated
folder and the following Grunt tasks output into that folder.
The media
folder holding the source post images is excluded from Jekyll site generation and rsynced around from _src/_media
to generated/media
before site generation starts.
Image size generation for post teaser images and photos is done with jekyll-picture-tag, putting resized images into generated/media/gen
.
Install dependencies
Run the following command from the repository's root folder to install all dependencies.
npm install && bower install && bundle install
Development build
This generates the site and assets with some Jekyll development options and starts a local dev server combined with a livereloading watch task under http://localhost:1337
.
jekyll-picture-tag makes site generation very slow at the moment. During development, uncommenting some lines in that plugin's file speeds up regeneration dramatically. Seriously, from like 10 min. to 10 sec. Downside: no teaser images or photos in the development build.
grunt server
Production build
Runs almost the same tasks as grunt server
but cleans the build directory before running Jekyll with some production options and additionally optimizes all image assets.
grunt build