Orphaned patchs, half completed tasks and semiuseful documents which I continously forgot I actually had. Far too many graphics used in place of text, i.e. graphics consisting entirely of text written in a particular font and colour. Minimize dross content. The use of webmake allows me to meet pretty much all of my goals. I write them once and webmake converts them to html, some tricky perl looks around for related material and adds it to the webpage, e.g. patchfile links, source distribution tarball.
Documentation stays in sync, one central location for look and feel changes and maintainence is nil.
When web browsers move on and allow content to be seperated even more from layout that actually works right now, then I can track those changes without problems. Unfortunately the tools available to me cannot make the site beautiful, and they certainly cannot identify substandard content and remove or rewrite it for me, this is still a manual task, though I have future hopes. Why even have a website There are two overall design goals from the perspective of usage to make available potentially useful bits of information and code to others.