Jekyll is a simple, blog-aware, static site generator. It takes a template directory containing raw text files in various formats, runs it through a converter (like Markdown) and our Liquid renderer, and spits out a complete, ready-to-publish static website suitable for serving with your favorite web server.
If you already have a full Ruby development environment with all headers and RubyGems installed, you can create a new Jekyll site by doing the following:
# Install Jekyll and Bundler gems through RubyGems ~ $ gem install jekyll bundler # Create a new Jekyll site at ./myblog ~ $ jekyll new myblog # Change into your new directory ~ $ cd myblog # Build the site on the preview server ~/myblog $ bundle exec jekyll serve # Now browse to http://localhost:4000
Building a Jekyll site with the default theme is just the first step. The real magic happens when you start creating blog posts, using the front matter to control templates and layouts, and taking advantage of all the awesome configuration options Jekyll makes available.
The Jekyll gem makes a
jekyll executable available to you in your Terminal window. You can use this command in a number of ways:
$ jekyll build # => The current folder will be generated into ./_site $ jekyll build --destination <destination> # => The current folder will be generated into <destination> $ jekyll build --source <source> --destination <destination> # => The <source> folder will be generated into <destination> $ jekyll build --watch # => The current folder will be generated into ./_site, # watched for changes, and regenerated automatically.
Jekyll is, at its core, a text transformation engine. The concept behind the system is this: you give it text written in your favorite markup language, be that Markdown, Textile, or just plain HTML, and it churns that through a layout or a series of layout files. Throughout that process you can tweak how you want the site URLs to look, what data gets displayed in the layout, and more. This is all done through editing text files; the static web site is the final product.
A basic Jekyll site usually looks something like this:
. ├── _config.yml ├── _data | └── members.yml ├── _drafts | ├── begin-with-the-crazy-ideas.md | └── on-simplicity-in-technology.md ├── _includes | ├── footer.html | └── header.html ├── _layouts | ├── default.html | └── post.html ├── _posts | ├── 2007-10-29-why-every-programmer-should-play-nethack.md | └── 2009-04-26-barcamp-boston-4-roundup.md ├── _sass | ├── _base.scss | └── _layout.scss ├── _site ├── .jekyll-metadata └── index.html # can also be an 'index.md' with valid YAML Frontmatter
The front matter is where Jekyll starts to get really cool. Any file that contains a YAML front matter block will be processed by Jekyll as a special file. The front matter must be the first thing in the file and must take the form of valid YAML set between triple-dashed lines. Here is a basic example:
--- layout: post title: Blogging Like a Hacker ---
Between these triple-dashed lines, you can set predefined variables (see below for a reference) or even create custom ones of your own. These variables will then be available to you to access using Liquid tags both further down in the file and also in any layouts or includes that the page or post in question relies on.
Where you put HTML or Markdown files for pages depends on how you want the pages to work. There are two main ways of creating pages:
Both methods work fine (and can be used in conjunction with each other), with the only real difference being the resulting URLs. By default, pages retain the same folder structure in
_site as they do in the source directory.
|ID||The column of your product backlog item|
|Link (optional)||A URL of the product backlog item in your tracking software (if you have one)|
|Title||The summary or title or name of the product backlog item|
|State||To know which PBIs are done or in progress.|
|Type||So you can have the opportunity to filter on a specific PBI type.|
|Effort||If your Scrum team is pointing your stories, you can add the estimation value here. In another post, I will explain how to compare the effort versus the actual cycle time.|
|Cycle time||We will calculate the cycle time in this column. For work in progress, this column will be blank.|
|Age||For work in progress, we want to see their current age so you can track them. It will be blank for completed PBIs.|