About Radiant Podcast podcast tags and site structure

Hello Sean.
Searching the mailing list I understand that the Radiant Podcast has
been generated by radius tags and served by radiant itself.
Wouldn’t you mind to share some details about the tags used, the
page/sub-page architecture, etc.? For example how has been generated
the podcast.xml page?
I’d like to setup a podcast web site based on radiant …
Many thanks in advance.
Luigi

Luigi,

I’ve written an audio player extension1 for radiant, which you might
find useful. It allows you to upload mp3 files, without requiring any
other asset management extensions (e.g. page_attachments or
paperclipped). It also provides radius tags for embedding a flash mp3
player.

There is a good reference on the wiki about creating an RSS feed from
Radiant content:

http://wiki.radiantcms.org/Simple_RSS_Feeds

It would be quite straightforward to adapt this to use the appropriate
xml tags for a podcast.xml. Instead of iterating through children of a
page, you would iterate through a collection of mp3s.

Cheers,
Drew

Luigi,

My apologies for the late reply. Here’s how it works. First, I created
a root listing page (/podcast) for the podcast as an Archive page with
this structure:

–body–
<r:children:each limit=“15” order=“desc”>

| | ">Download (MP4)

Notes and Links

Subscribe to the podcast

–head-- (this part renders in the section of the layout)

That forms the basis of the “show notes” pages. In order to support
this and the XML feed, each child page of /podcast is constructed with
these parts (in no particular order):

  • size (length in bytes of the episode)
  • body (the description of the episode, usually short)
  • url (an absolute URL to the episode)
  • type (the MIME content type of the episode)
  • notes (notes to put in the “show notes” page)
  • duration (how long the episode is in HH:MM:SS)

Now, I use S3 to host the podcast episodes, so I put in this information
manually. If you were using page_attachments or some other media
manager extension, you might be able to have it fill some of these in
for you.

The last part is to create the podcast feed. As you may know podcast
feeds are just RSS 2.0 feeds with a few extra tags added. Here’s the
source of /podcast.xml:

<?xml version="1.0" encoding="UTF-8"?>


Radiant CMS Podcast http://radiantcms.org/podcast Publishing for Small Teams Radiant CMS Radiant CMS [email protected] Interviews with Radiant users and discussion about the progression of the Radiant project. Interviews with Radiant users and discussion about the progression of the Radiant project. no 7200 en-us " length="" type="" /> http://radiantcms.org

The main thing to notice is how the parts of each episode page are
pulled into the proper place in the feed.

Hope this helps!

Cheers,

Sean

Thanks to you guys. The radiant community rocks!

Nate T. wrote:

Mohit, you think you can get this into the Reboot docs? This is awesome! I
was just about to ask the list about this.

Hi Nate,

A bit tied up, but I’ve done the next best thing - linked a new page in
the documentation to Sean’s message in the Mailing List Archive so that
it’s easy to find. Will migrate the content and extension when I get a
bit more time.

http://wiki.radiantcms.org/Producing_a_Podcast

Cheers,
Mohit.
1/6/2009 | 11:38 PM.

Mohit, you think you can get this into the Reboot docs? This is awesome!
I
was just about to ask the list about this.

~Nate

On Tue, Jan 6, 2009 at 9:38 AM, Mohit S. [email protected] wrote:

documentation to Sean’s message in the Mailing List Archive so that it’s
easy to find. Will migrate the content and extension when I get a bit more
time.

http://wiki.radiantcms.org/Producing_a_Podcast

You are the man. I have one more thing to get out of the way and I’ll
start
helping you out with that. Documentation is still a bit weak for Radiant
and
I want to help that not be the case.

Cheers,

Nate

Nate T. wrote:

You are the man. I have one more thing to get out of the way and I’ll
start helping you out with that. Documentation is still a bit weak for
Radiant and I want to help that not be the case.
That would be great - I’m not actually doing that much documentation
actually, but it’s coming through thanks to all the contributors!

Cheers,
Mohit.
1/7/2009 | 12:37 AM.