Matthias Kretschmann
d2e2832da4
|
||
|---|---|---|
| _src | ||
| .gitignore | ||
| Gemfile | ||
| Gruntfile.js | ||
| LICENSE | ||
| README.md | ||
| Rakefile | ||
| _config.yml | ||
| assets sheet.psd | ||
| bower.json | ||
| 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:
Content Creation
Some handy rake tasks creating the correct front matter for each content type:
| New Content | Command |
|---|---|
| Post | rake post -- Title |
| Photo | rake photo -- Title |
| Link | rake link -- Title |
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 _site folder and the following Grunt tasks output into that folder. The build task copies everything over into the _buildfolder.
The media folder holding the source post images is excluded from Jekyll site generation and rsynced around from _src/_media to _site/media before site generation starts.
Image size generation for post teaser images and photos is done with jekyll-picture-tag, putting resized images into _site/media/gen.
Install dependencies
Run the following command from the repository's root folder to install all dependencies.
npm 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 puts everything into the _build directory, versions all assets and optimizes all image assets.
grunt build
Licenses
Posts
All post content under _src/_posts is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Photos & images
All photos & image assets under _src/_media, _src/assets/img, and assets sheet.psd are plain ol' copyright.
Copyright (c) 2008–2014 Matthias Kretschmann
Don't care if you fork & play with it, but you're not allowed to publish anything from it as a whole without my written permission.
Everything else
The MIT License (MIT)
Copyright (c) 2008–2014 Matthias Kretschmann
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.