Jekyll is a wonderful program. The more I use it, the more I like it. It’s customizable, automatically parses markdown, and uses a template system that makes it very easy to create a consistent style. Its only flaw is that it depends on rubygems.
Jekyll does get a little getting used to, however. In this article, I’ll go over the basics:
- Creating a site
- Customizing a site
- Creating content
Note that I assume some basic familiarity with Git and the commandline, which will be covered in another post.
Creating a site
Congratulations! Your site is now live (at http://localhost:4000 by default).
Customizing your site
“Your awesome title” is a pretty terribly name for a site.
Go ahead and edit it in
There’s lots of other juicy config to change in there,
quick rundown here.
Other things to edit
Jekyll uses minima
by default; find where it is with
bundle show minima.
- Page layouts:
- Headers and footers:
- 404 page:
Jekyll expects a certain format from its templates. I’ve made an script that will handle the metadata automatically.
The content itself can be in one of three formats:
- Plain text
The source of my site is also available as an example.
- If, like me, you got a permissions error -
then you probably installed with a package manager. Unfortunately, you’ll have to reinstall gem; I’m not aware of any way around this. Since installing on a system-wide basis requires root permissions, /var/lib/ruby is only read/writable for root.
- If you want to edit where gems are stored, you’ll have to edit
the rubygem script itself. Find the ruby library (in my case,