I’m not really sure I want one. I actually like writing html
(with emacs psgml mode)
better than learning new markup languages. The big advantage of
the interface is that if you’re setting up a new site, links to
the pages
that aren’t written yet are in red, and when you click on them you
get put directly into edit mode for them. But all the stuff about
lists and links and blockquotes and sections, which I do effortlessly in html,
I have to learn a whole new bunch of funny punctuation to do in
wikimedia markup.
But the application is a good one for a WIKI. There are three
of us giving a concert in December, and there’s a lot of
information about the playlist and the rehearsal schedule and
where to download the music, and where are the recordings of the
rehearsals and the drafts of the program and the program notes that needs to be kept in a central place.
The last few concerts I’ve done that on an html page, but the
WIKI concept of easily linking in new pages and easily traversing
the tree of linked pages probably will make for better
readability. And of course, the other performers are more likely
by some very small amount to write on a WIKI than on an html
page.
So I’ll let you know how it works out. In combination with my
addmedia.py
program, it was pretty easy to put up PDF and MIDI files for a
piece that’s only partially transcribed so I wouldn’t want to put
it up at Serpent
Publications yet. It was more of a pain to put up the list of
performers as a list because I’d never written a mediawiki markup
list before, but maybe the second list will be easier.
LayMusic.org 