05:19 <eroc> Hello. Can anyone help me set the feed_url so it gets correctly picked up by the call to atom_feed? Here's my code of feed.haml. It gets routes to feed.xml

05:19 <eroc> = xml_sitemap items: @items.reject{ |i| exclude_from_sitemap(i) }¬

05:20 <eroc> The "exclude_from_sitemap" method just weeds out css, js, etc.

05:21 <eroc> I know I'm supposed to set feed_url on the feed item, but I'm having trouble figuring out what that item is and how to set properties on it.

05:21 <eroc> In case it's not abundantly obvious, I'm new to nanoc.

05:21 <bobthecow> feed_url and stuff go in the frontmatter of your feed item file.

05:21 <bobthecow> i.e. the yaml section at the top.

05:22 <bobthecow> um.

05:22 <bobthecow> the thing you pasted is how you do a sitemap, not a feed :)

05:24 <bobthecow> this is a feed:

05:24 <bobthecow> https://gist.github.com/bobthecow/a81d8f5ab89b41011bb3

05:24 <eroc> Whoops, my bad. Here was the code:

05:24 <eroc> = atom_feed title: 'Agile Commerce Blog', limit: 10

05:25 <bobthecow> i believe title, author_name and author_uri are the only things you need to include in your feed's metadata.

05:25 <eroc> I think in my tired state, I might have been editing the wrong file. Here goes with the front matter.

05:26 <bobthecow> you can pass things in to the atom_feed helper, or you can set them in the frontmatter. i prefer the frontmatter, personally, because it means my file is cleaner :)

05:27 <eroc> I checked the source and passing in the feed_url isn't supported. It's the one property (that I noticed) that couldn't be passed in.

05:27 <eroc> Adding it to the front matter worked like a charm. Thanks.

05:27 <bobthecow> ahh. interesting.

05:27 <bobthecow> most of 'em can be passed in. that's probably an oversight.

05:27 <bobthecow> but generally, nanoc prefers frontmatter anyway.

05:28 <eroc> I hadn't made the connection between the frontmatter and the @item object within the atom_feed method.

05:28 <bobthecow> because then it's a property of the feed item itself, not just a variable set in your template.

05:28 <eroc> Cool, I'll adjust my code to favor front matter.

05:28 <bobthecow> yeah, @item is always the thing currently being compiled.

05:28 <eroc> Thanks again.

05:29 <bobthecow> no problem.

05:33 <eroc> One more totally random question. When I throw front matter in a markdown file for a blog article, it screws with the syntax highlighting in my code editor (Vim). When I add "created_at", it looks like the start of some underlined text. It's not a big deal, but an annoyance. For my articles, I've been breaking out the front matter into a separate yaml file, but that's sort of a pain also. Any pro tips on how to address this?

05:35 <bobthecow> nah. i just put up with it :(

05:35 <bobthecow> https://gist.github.com/bobthecow/20e652201bd805b4ccbb

05:35 <bobthecow> try that?

05:36 <bobthecow> at least the syntax highlighter i use only has problems when i have multiple underscores in the same line.

05:36 <bobthecow> it deals with `foo: bar_baz` just fine.

10:35 <ddfreyne> bobthecow: Idea for quick data sources:

10:35 <ddfreyne> bobthecow: in Rules: source :items, :from => :filesystem, :path => 'content/**/*', :strip => /^content\//

10:36 <ddfreyne> It makes the answer to the question "where does my data come from" more explicit

12:32 <cDlm> didn't read before, but +1 to that last idea

16:57 <bobthecow> ddfreyne: https://waffle.io

16:57 <bobthecow> trello but with github issues as the data store.

16:57 <bobthecow> i really dig it.

16:57 <bobthecow> See https://waffle.io/waffleio/waffle.io

16:59 <bobthecow> ddfreyne: i don't know that i like mixing data sources in with rules.

16:59 <bobthecow> i might come around, but to me rules is "here's how to compile my site"

16:59 <bobthecow> data sources seems a lot more config-y

17:39 <ddfreyne> bobthecow: I'm thinking of Rules more as a general Makefile

17:40 <ddfreyne> you specify the source data in there as well, in a way.