I am hoping to be able to do a Standards compliant Geeklog, and went searching through the archives. I saw a post by Gwen back last fall. It was followed up by comments by SaltLakeJohn -
Was just wondering what the status was of their CSS attempts for layout of Geeklog - something I really want to do! Have either of you read Eric Meyer on CSS: Mastering the Language of Web Design or do you visit Jeffrey Zeldman's site regularly? Great resources for working out your CSS woes.
If you've got any tiger tidbits for me, or if you've got a working 100% CSS Geeklog, I'd love to see your theme/stylesheet. Thanks in advance!
Would love to see what you did - - if you've still got the files, and I've GOT to think you didn't trash them The doc on theme variables seems to be really helpful. I hate to say it, but I have a very limited target audience, so I don't think the problems with Safari, etc. are going to be too much trouble.
Have you seen the CSS Zen Garden??
Check it out- there are some really awesome examples of how you can change the personality of a page with a stylesheet.Well, I'm no guru, but I do have a fair amount of patience. If you do nested divs, can't you do a decent 3-column layout?
I'm game to give it the ol' college try! I'll post results, if I get anything done before I take off for the summer.
I have done three coloumn layout for www.geeklook.com with CSS only and then decided to preserve table for coloumn layout at least. I think CSS importance is not in layout but in context-based formating. At geeklook.com the text is formatted differently on homepage and on article view. Different look for left or right blocks is also done with CSS only (Geeklog code offers the same opportunity through templates).
As to tables, it is relatively easy to clean them off the templates. Thankfully, there is also not muchHTML hard-wired into the code. But those <br> tags in the code drive me nuts... I haven't changed any of Geeklog core code on purpose (to make the theme forward compatible), but I hope in future versions Geeklog will produce "logical" output rather than "visual" output. I mean, the outpot should be <h2>Title</h2> rather than <td class="Title">... etc.