Nanoc is a static site generator much like jekyll or octopress, but with a more minimalistic approach. These generators are not necessarily the most suitable choice for a podcast website, but it’s possible and you might save up on webspace and traffic when you use GitHub or Neocities.
Creating the podcast feed is basically like writing a normal Atom feed for the blog, since podcast feeds ARE indeed feeds with an enclosure tag in which the URL to the audio or video file is placed. This guide does not include the itunes tags. I might add it one day. Follow the instructions and use the documentation for the Helper Blogging. Tag your podcast episodes as kind:article.
The media files are placed in content/mp3 and content/opus, which is where the links in the feeds will point to later.
I invented the fields mp3 and opus, since these are the file formats I want to use. The values are the filenames. The header of a new episode/post would look like
title: 001 - Podcast Episode Title
created_at: 2015-03-14 09:00:00 +0000
This has to be filled manually everytime, so make sure you have the exact filename, as some podcast clients won’t allow correction of the URL.
The next step is to write different feeds for the formats. For that, I’m using the new field format, which will be interpreted by the Helper class later on. For example, I called my normal feed blogfeed and the podcast feeds mp3feed and opusfeed. Create the file blogfeed.erb in the content folder and fill it with the following:
<%= atom_feed :title => 'repats podcast blog', :author_name => 'repat',
:author_uri => 'http://repat.de', :limit => 10, :format => 'blog' %>
The mp3feed.erb and opusfeed.erb are filled accordingly:
<%= atom_feed :title => 'repats podcast mp3', :author_name => 'repat',
:author_uri => 'http://repat.de', :limit => 10, :format => 'mp3' %>
<%= atom_feed :title => 'repats podcast opus', :author_name => 'repat',
:author_uri => 'http://repat.de', :limit => 10, :format => 'opus' %>
The next step is to use the Blogging locally in your nanoc installation. To do that you need to copy it from the gems folder into your lib folder. For me, that was
$ cp /var/lib/gems/1.9.1/gems/nanoc-3.7.5/lib/nanoc/helpers/blogging.rb lib/
It should be included like this in the lib/default.rb
Add the following attribute to the AtomFeedBuilder class
If you don’t trust yourself to always remember the files you might want to add this exception to the validate_feed_item function
raise Nanoc::Errors::GenericTrivial.new('Cannot build Atom feed: no format(mp3,opus,blog) in params, item or site config')
After the # Add link comment is a good place to insert the enclosure tag. File.size() will only work if the files are there and the exact same name. This code could probably be written a bit more safely, but I’m not a ruby developer and since I will have an mp3 file and and opus file in every post it’s not a problem this way.
# Add podcast enclosure
if format == 'mp3'
xml.link(href:"http://yourpodcast.com/mp3/" + a[:mp3],length:File.size("content/mp3/" + a[:mp3]), type:"audio/mpeg", rel:"enclosure")
elsif format == 'opus'
xml.link(href:"http://yourpodcast.com/opus/" + a[:opus],length:File.size("content/opus/" + a[:opus]), type:"audio/mpeg", rel:"enclosure")
To interpret the mp3 and opus attribute from earlier in the actual post, the last step is to add this line to the atom_feed function:
builder.format = params[:format]
You might need to install builder to let this run
$ sudo gem install builder
The only thing left to do is to edit the Rules file:
compile '/blogfeed' do
compile '/mp3feed' do
compile '/opusfeed' do
route '/blogfeed' do
route '/mp3feed' do
route '/opusfeed' do
You can find the blogging.rb and the Rules file on GitHub.