I've installed YA Wirebird site, this time replacing my Blogger blogs.

This was an interesting exercise, since (1) I'm using it to build a static site, and (2) it's not a "root" installation - all the other installations are "forum.domain.name/{resource}..." where this is "www.domain.name/blog/subblog/..."

Now, it was already a hack in that I have four Blogger blogs with a Perl script that mashes them together in the /blog/ directory with topics added, so it's a hack emulating a hack.

What I ended up doing was gutting the template - putting in the Blogger one and constructing the URLs to the static pages in the template instead of using the Wirebird-generated ones (which point into the dynamic Wirebird install). It means the dynamic Wirebird is mostly unusable (it keeps throwing you out to the static pages), but then I have a little "publish" script that does a LWP::Simple get on the page and stores it to the static file. Not a permanent solution, but it'll do for now.

Replying goes into Wirebird itself, and is a little bit iffy. I currently have the reply form set up as your basic Wordpressish name/email/web (the latter of which gets thrown away right now), which upsets Wirebird a little bit - when you give it an email, it wants to register you, and I'm not letting it yet (because I didn't have incoming email set up). I'm not sure if I'll want that to be a valid mode of operation yet (apparently while comment spam is a problem, people forging others' email addresses isn't?)

I think eventually I'll end up with a Wirebird::Blog mode instead of making Wirebird::Forum do double duty.