Honesty first:

Yes, I do realize that this site’s design is unfortunetly broken in Mozilla and likely most non-IE browsers. At some point during coding the CSS for the layout, something—most likely a miniscule padding number or so—must have been used and thus what all viewers besides IE users see is a literal “cascading style sheet” as the html layers are all out of joint. I’m sorry and quite embarrased by this sate of affairs.

My bad

I feel horrible about this as only a geek can. You see, when I was starting this site it was mostly for—and still is—a testbed for me to fool around with web and server technologies like CSS, XML, MYSQL, PHP, PERL, Apache, etc. Mozilla hadn’t hit it’s first stable release candidate and I had been drive to frustration with Netscape andd Internet Explorer alike. Thus, the standard support I followed when plotting the fundamental design elemants of the site were lax, because the browser support for full markup standards compliance at that time was both buggy and half-hearted. Only a year and a half ago it was relatively hard to see how standards compliance could become anything other than a secondary design goal; useful for avoiding the likes of the ole’ lazy designer’s favourite table hacks but not as away to unify site architecture. Growing compliance to the W3C has changed alot of things since then.

The browser wars are, thankfully, now irrelavant as new browsers and backends are relying primarily on standards compliant practices to govern the web. Why? Likely, this is due to greater awareness of interdependence between technologies such as in the case of markup: to fully employ CSS you need to harmonize it with the HTML it styles, likewise the HTML must be formed while mindful of employing a subsequent CSS sheme. In other words, structure (HTML) and aesthetics(CSS) are linked bi-directionally. When error-checking and finessing design code, validating both HTML and CSS will ensure everything displays the way you want it too. This reliability is golden.

Full Circle

Obviously I find myself with HTML and CSS which is out of sync with the current state of standards compliance. In my defense, all I can say is that I never had the aid of the current Mozilla release when I setup this site.
Correcting my markup is going to be far harder than having started from scratch with a workflow focused on validating code. So, that’s just what I’m going to have to do: rebuild as much as possible from scratch. The only reverse-engineering that will be reasonable involves being able to tackle one markup set at a time: CSS first followed by HTML and XML and then overall tweaking. Atleast I can feel somewhat competant about having set up include templates to simply slot changes into the design as I make them.

This site is finally looking to be coming together nicely.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

Epsum factorial non deposit quid pro quo hic escorol. Olypian quarrels et gorilla congolium sic ad nauseum. Souvlaki ignitus carborundum e pluribus unum. Defacto lingo est igpay atinlay. Marquee selectus non provisio incongruous feline nolo contendre. Gratuitous octopus niacin, sodium glutimate. Quo