The layout of HR’s hafVAST Blog has changed yet one more time. Maybe this time the layout will stay the same for a couple of months or so…or maybe not! The site displays correctly on the IE7 and FF2.0 browsers but has not yet been tested with earlier versions of either browser. One of my design goals was to avoid the use of “hacks” to compensate for the way the different browsers implement the W3C xHTML and CSS specifications.
The new layout validates as xHTML 1.0 Strict…or at least it did last time I checked! If you are using an older browser that does not conform to the standards , the layout may appear to be broken. I hope it is still readable in those cases. If the display does not render properly on your screen, feel free to leave a comment telling me what browser and version you are using, along with the screen resolution.
Sweet! You are getting more and more and more of a designer’s eye, HarryB. I love this new look and I am glad to see that you have pulled your trademark look with the *bridges connecting communities* into your blog. Thanks for the link to me that you have had for a long time – it means *a lot* to me. Also, good for you with the Mambo Foundation link!
I cannot believe you strive for (and achieve) xHTML 1.0 Strict. That is such an accomplishment. You raise the bar and I am struggling with maintaining 1.0 transitional! I don’t pay enough attention and I get swept away with the silly stuff. 😉
That Web 1.5 button is incorrect. You are mashable! I have covered this with you already. It’s time, HarryB, to admit – you are indeed Web 2.0 and quit being such a Web 1.0 snob! 😉
Looks good in FF v 2.0.0.1 and IE 7. I think you are in good shape!
HAPPY NEW YEAR, HarryB!
Amy 🙂
All right, I am clean, again. Why do I let it slip out of control? How do you get to STRICT? Impressive.
Its not worth the time, effort and brain cells one burns to keep a site strict. But keeping a site “transitional ” is really a matter of paying attention to detail and most importantly, running the validator each timne you do an update so the errors do not accumulate.
Yes, you are right, good idea!