i'm a learning by doing kind of guy, used to have a project website in html for my studio project, started with an editor software, then started to copy and paste code snippets, then installed a .php CMS system and went try and error on it untill wikiloops worked (wikiloops is my very first php/SQL project ever). I'm a socialworker by education, so im a do it yourself guy when it comes to coding. Theres lots of footage online, and since the member system and forum / comment aspects where left over from the CMS, all I had to do is code the musical side of things and the special search engine. I have had some help coding by chrisB and a lot of help with the french interface from lutz (translation), but the main development and coding job is my part. Its difficult to do team coding, for documenting every move takes more time then the changes itself sometimes, so I kind of kept it a one man thing - that allows me to do messy code in some parts that would be hard to understand for pro-coder I guess ;) I have to do a general workaround to be able to teamwork this thing in the future, for there are some pretty nifty features I have in mind for the future for wich i will definetly require outside help.
I do like the kinda crude, AJAX-free style of wikiloops, its a pretty quick loading site that way compatible with older computers, not too fancy to look at, but working quite stable for quite some time... I always try to keep in mind there is people on this planet that might not be able to buy top class gear, so keeping things simple was always my aim. thx for your interest :)