I hadn't thought of it that way, actually.
Let me explain currently how the server is set up, and how I'll try and add it to SVN: (directory names are not set exactly as this, but this is how it basically works)
I have no issue with /public_html and tree being added to SVN (please note the code is not at all great) but do not feel that either /forum_system or /svn_web_client should be added.
I am coming round to the idea of having the web source in the SVN, since it can be checked out to the main site without too much hassle (one svn co
from me!) but since it is PHP rather than static HTML it may be a little difficult to test without bringing out to a world-readable site.
I still like the idea of a rotating tagline (i.e. a different tagline each page or something), but having one randomly generated per page raises issues with search engines and their caching, so I was thinking of changing it on a daily basis, rather than per-page.
I also like the anagrams ("LAME RED EDITOR" seems almost ironic) but I think that perhaps the meaning might be lost a bit on new people and inductees to the Emerald Editor School of Thought.
I can see where your thoughts are going with the site, Nick, and I will put the source of the main site (if nothing else) into SVN/website tonight hopefully, so please feel free to play around with it to see what you want to do with it. I personally like the existing site, layout, etc. but know that not everyone likes it, so I really should stop wielding the executive power!
Nick, As the person who has had more input into the look 'n' feel of Emerald Editor than most, I'm sorry I didn't do your template justice. I just wanted to take its goodness, tweak it a little, liberally sprinkle emeralds, and add it online.
Perhaps making the emeralds smaller would balance the small green bullet points in your template, and the 'cute' factor in mine?
I'm not a graphic designer as you will all have seen!
I'm more a hobbyist programmer (sometimes) so I don't always manage to implement graphical things the way they need to do them the best justice. That also goes for HTML, I don't always use the best HTML for the job, as said before, but that's a picky/semantic thing.
The code was salvaged from another project, so the tab system etc. is almost shoddily built, and probably could be cleaned up. (If I'm completely honest, I guess the shoddy coding is one of the reasons I've been reluctant to add to the SVN, although I think I never really realised it before)
*sigh* I guess I'm just not quite the coder I thought I was... (I can dream, anyhow)