"It's a horror for me, even trying to grasp any of the code, to learn from it."

Then don't try to learn it from pages that are reduced to the bare minimum :)

The google search pages aren't any better, and that is because they get called a gazillion times a day. No, you simply can not use name="search_query", you have to use name="q". In some cases that is still understandable for an outsider, in most cases it isn't. And it doesn't need to be, it needs to be as small and compatible as possible, period.

The CMS thingy I'm currently coding doesn't output any line breaks either, not even one, as view them as a waste of bandwidth. Though when I find a way to "beautify" the HTML automatically, I'll surely add such an option to the cookie preferences. But to serve a "pretty" page with 20% of the data just being indentation, the source of which 99% of the visitors never get to see...? Nahh. I'd rather be the bad guy than do that ^^

While my CSS is somewhat "normal" (#header instead of #h) some class names are short bordering on obfuscated, too. Instead of, say, "perm_admin" (to color stuff only the admin can see), I have "padm". Or "pown" for stuff only the owner can see. Just because those get repeated a lot on a page, so I try to find the shortest name that still means something to *me*. Stuff that has beveled borders and children has is of class ".c", which in my mind stands for "container" (which doesn't even make sense haha, but ultimately that doesn't matter, I use that way to often for that class to have a long name, so any letter would be fine with me really).

Sure, the CSS is commented, but the comments get stripped and each definition put on one line before it gets sent out :P Here too I will add an option to not compress it, but compressed output will always be the default.

But hey, my CSS is kinda hackish anyway, so you wouldn't wanna learn that from me of all people :) And prolly not from Google either ;)