Comments for mojombo's jekyll  

Epic commit message.

awesome-tastic!

Try 0.11.0. You should be able to:

gem.files.exclude 'test/dest/**/*'

If a post has been created without any meta data at the top, it will fail here. Maybe self.data[“title”] should be set on initializing; being the slug if no meta data is provided.

I belive this works. I use it in ‘my blog’:http://github.com/bjartek/bjartek.github.com/blob/d74a3bd052627a77d0c772a100d14ef66cc967f4/_layouts/default.html

The first example was supposed to be:

categories:
 – foo
 – bar
 – xyzzy

YAML has built-in support for lists of values, so why not use it? Like:

categories: – foo – bar – xyzzy

OR

categories: [ foo, bar, xyzzy ]

Comma-separated lists can co-exist with this if we want to.

That’s the usage. Works pretty well for me. Although the .split call will utterly fail when you just specify

-
categories: 
-

Looks nice, is this a stable addition?

Usage?

---
categories: foo, bar, xyzzy
---

Still doesn’t seem to show up on my path… osx, gems 1.3.1. ??

shame

Nice. I’ve been treating ‘topics’ semantically like ‘tags’ and setting them as yaml front matter instead.

jekyll.gemspec needs to be updated too:

ncr:~/dev/jekyll$ gem build jekyll.gemspec 
WARNING:  no homepage specified
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - test/source/posts/2008-12-03-permalinked-post.textile

note: the “mojombo merged commit ‘8d08a2’” commit made breaking changes, for me. site.posts is empty in index.html (because read_posts isn’t always called before rendering pages). fixed that but now post.content is the untransformed source of the post, not markdownified / textilized. trying to make sure transform explicitly gets called, setting post.content, before index.html (and other such pages) are rendered …

updated history @ http://github.com/remi/jekyll/commit/1cadd8f5b08675821d5f85b7e4b7b1a74a604cc2 to reflect this

d’oh! in commit http://github.com/mojombo/jekyll/commit/6d8c73349e2e05529a3e4f7b27dd808070b7ab0e i decided that the post’s YAML front matter should get merged into the to_liquid instead of using post.data. I initially tried post.data, but merging into to_liquid seemed to be a much cleaner solution.

A WEBrick based alternative to this is now in master.

The commit has since been removed.

Wouldn’t it be better to specify the categories that a post should belong to in an array in the yaml header for the post? This would seem to be a much more flexible way to add a post to multiple categories (and easily change your mind later). The dir structure approach would seem to lead to arbitrarily deep dir structures. And would be much more labor intensive to change. Taking it to the logical extreme, if I have 100 categories, and I have a post that I want to show in all 100 cats, do I have to create a dir structure 100 levels deep? Or do I have 100 dirs and symlink the post file into each of those dirs? (Caveat : I have not tried to use this feature yet so I could be full of crap.)

Fantastic! I was looking for javascript-only libraries in case syntax highlighting would have complicated Jekyll. Looks like you found a great way to put this together.