Most of the syntax is stock, but the link syntax isn't stock at all. None of the links will work on a default install. Enabling WikiWords is pretty easy, but every page is going to have to be put through a translator anyway.
We need to look at this through a broader point of view, anyway. If you were making a new wiki about the tropes in media today, what would you do?
What would you call it?
What features are important?
Does it need to have attached forums? If so, what should be the scope of those forums?
How would you organize works and tropes?
Would Web 2.0 (beta) features like WYSIWYG editing be useful?
Is it important to keep the same format for legacy users?
Since we'll be moving to new software anyway, we might as well do an assessment of what features we need now. A little planning now will save us tons of time in the future. If you have technical expertise in wikis, scripting languages, or databases, and are willing to contribute some time, make a note of it in the thread. My current software stack is Mac OS/Apache/SQLite/Perl, but I'm adaptable. The person I convinced to host the project uses lighthttpd and PHP (and is currently developing his own wiki in PHP and Javascript). There's still a good chance we might go with PmWiki anyway, but it's still up in the air.
Anyway, lets keep it to technical concerns for now. I don't want to get too far off into community standards type things until we actually have a wiki to talk about these things on. Also: see http://www.wikimatrix.org/ for even-more-than-you-ever-wanted-to-know comparisons of wiki software.
-- ∇×V
We need to look at this through a broader point of view, anyway. If you were making a new wiki about the tropes in media today, what would you do?
What would you call it?
What features are important?
Does it need to have attached forums? If so, what should be the scope of those forums?
How would you organize works and tropes?
Would Web 2.0 (beta) features like WYSIWYG editing be useful?
Is it important to keep the same format for legacy users?
Since we'll be moving to new software anyway, we might as well do an assessment of what features we need now. A little planning now will save us tons of time in the future. If you have technical expertise in wikis, scripting languages, or databases, and are willing to contribute some time, make a note of it in the thread. My current software stack is Mac OS/Apache/SQLite/Perl, but I'm adaptable. The person I convinced to host the project uses lighthttpd and PHP (and is currently developing his own wiki in PHP and Javascript). There's still a good chance we might go with PmWiki anyway, but it's still up in the air.
Anyway, lets keep it to technical concerns for now. I don't want to get too far off into community standards type things until we actually have a wiki to talk about these things on. Also: see http://www.wikimatrix.org/ for even-more-than-you-ever-wanted-to-know comparisons of wiki software.
-- ∇×V