Okay... so far I have the following coded for the website back-end as SQL functions, including test-case SQL scripts when appropriate:
Stuff I still need to finish as SQL functions:
Once that's all done, coding up the actual website will be relatively minor by comparison for the core structure, but that's the intent. Keep the PHP code unobtrusive for main page-content, allow easy styling of the website itself and integrating with other tools like forums and what-not.
I already have the core website-infrastructure code done on the PHP side. Mostly it should be sitting down with a couple nice artists I know that are going to be working with me on the website, and kit-bashing things together so we can show a few ideas to the rest of the convention staff; then fully flesh out whatever folks decide looks best.
And when this is all said and done? I'll be packaging up the raw scripts and minimal website code with all styling stripped out, and punt it up as an archive for others to use. I'm tired of hearing about folks struggling with making a website for their convention/get-together/whatever, and why have a dozen other folks re-invent the wheel? That, and I figure I'm using best-practices as I understand them, so I'd like to give others a chance to look over the code and hopefully warn me if I'm doing something that's causing a larger hole than it's covering up.