A lot of activity today! I have gotten rss working with HTML::Mason by converting the included template.rss into a format Mason can read. Then all that needs to be done is in autohandler, do something like this:

<%args>
$rss => ”
</%args>

% if (!$rss) {
# print default autohandler html
% }
% else {
% $r->content_type(”application/rdf+xml”);
<& rss.mas &>
%
% }

Then call any of your Mason components that use that autohandlers and add
?rss=1 to the uri. For instance, http://www.jessestay.com/index.html?rss=1

You can get the Mason module by clicking rss.tar.gz. I’ll add in atom support when I get some time later. You can try it out by adding my rss to your rss reader by clicking on the link to the right!

For all Richmonders (VA) please check out http://www.knowrichmond.com. I’m looking for ideas and need all the help I can get to get content for the site. I’ll post the best ideas online once I have enough content.

I’ve decided I’m going to begin porting Jeens over to Catalyst, based on Simon Cozen’s Maypole module. Perl is going to need to move to more of an MVC framework for it to stay up with the competition so I may as well help it out.

I in some ways want to leave where Simon Cozens left off with Feuilleton (good luck to him in his religious studies btw - been there and it is quite an experience that all should try!). The goal here is to produce a very plugable application that others can easily add to and modify.

I read somewhere today that the fastest way to get contributors to an open source project is to make the project in small components, allowing others to have their own small “projects” that contribute to the larger project. One example included was Blosxom and it’s plugins.

My thought on Jeens is that it will be more than just a blog, wiki, and photoalbum seperated. By combining elements of all three one should be able to create a “super blog”. So, using wiki elements one might be able to add a link into their blog entry that goes to a pure wiki page, or perhaps just certain components of a page can be a wiki, the rest static or a blog. Or you could have a photoblog, blog, and wiki all in one! Each component must be scalable to add further components and encourage public contributions.