I think I have it now.

Maybe this could be done with xslt. Hmm….

Now on to the tags I was thinking maybe using |div class=”explanation”| any explanation |/div| would be a good way to be able to create a node from html, especially if you are using php to parse it. I used the actual code earlier and your comments parsed them out is where the / tags came from

Your idea of an opml file per post is an interesting one - while potentially increasing storage requirements (uless the blog itself is generated from the opml) it would certainly allow for an interesting remixbility as different people could use inclusion to generate an opml file of posts by many authors (on a side note I’d love to see the ability to include OPML from a sub-node of an OPML document instead of just the entire document). One thing I though of when looking at your OPML is that you ave 2 nodes marked with isComment=true and was curious why you chose that.

As far as your question goes, I’m not sure what you mean by “the use of / tags to select the nodes”. Do you mean using tags to organize posts in the OPML? If so, I think of what I’m doing in the template that way, at least insofar as a post can belong to multiple categories and thus appear under multiple nodes within the OPML. Or am I misinterpreting what you mean?

Maybe full blog exports would be overkill after all.

I suppose it depends on what the actual uses people make of OPML formatted feeds. Your solution gives a realy nice structured representation of the posts on the site, by category and title. This is great for spreading links around, like Dave is doing currently, and this may be the right model at the moment. If the need for full content feeds becomes clear, I don’t think it would be hard to add it, as you’ve already done the heavy-lifting.

I have an interest in posts being actively reused in user-driven and collaborative ways, so full OPML interests me, as does the fact that they are less ephemeral than RSS.

Thanks again.

I added a function to check for posts and suppress empty categories. Along the way I discovered a flaw in my handling of suppressing top-level display of child categories and added a function to handle that as well.

While doing both of those, I realized that my flat handling of category nesting means that categories 2+ levels deep will also be suppressed; I need to design some recursion into my nesting functions to work that out.

As far as your other comment goes, I’m still thinking about that. Currently I display links to every post, and generating the content for all of that would be a heavy load and a long process (in a template that already takes longer than I’d like). I’m thinking about adding some config options to the management dashboard for this purpose and am also thinking about making it a template tag instead of a standalone template - essentially wrapping the whole thing in a plug-in to make it a little less hack-y. Any feelings on that?

The updated files are in the previously noted locations….

I did this by only pulling results back for categories that appear in the post2cat table.

Also, how about having an option to publish post content, too?

Thanks for putting this together. Very cool indeed.