Thanks
I was sure for a moment that you'd used images for the headings; the Montez font is loading much faster than most fonts do under an @font-face rule. Limited character set, I suppose?
Glad you like it - I didn't want to miss out on the SEO opportunities... and yes, its limited (file size only 76kb).
It looks nice with the pagination you have now. I just wonder how the design will hold out with real content—I can imagine it working well with, let's call it "curated content", but a little less well with more random article lengths. I guess that translates as "good magazine/bad blog" in the common tongue. I'm guessing that you're testing several different page types there on one HTML page, and that the breaks in the background panels indicate the separation of the various page types.
The content will not be as text heavy - in fact I only intend to include limited textual content and heavier on graphics. And yes, you're right in that I'm trying out several html tags in one page to test page architecture and css. In reality, there won't be a fraction of the quantity.
Just a little question: do you anticipate maintaining the "print page" layouts for longer articles to make multicolumn work? Again, that makes content curation more important, so the site would be a lot more "hands on" than most designs. (At least until the new CSS methods get wider acceptance and implementation).
The print.css styling sheet will split out the multicolumns (which I'm pretty proud of) into single columns - as will the mobile.css file. In fact, the print.css file will cut out most of the spurious content (such as header, footer etc.). My only reservation here is that FF doesn't react well to print formats.....
The only real qualm I have is with the depth of the header. I haven't gone through looking for @media rules, though, and I'm using a rather large screen, so it may be just fine as it is. If it looks like more than a splash page on netbooks and mobile devices, you're golden.
Good point. The background image was designed to suit the minimum 1024 all the way up to 1920, but the key dandelion and night stars appear strongly in the 1024 resolution. The height is more of a concern and I've crushed the design so the grass line is half way up the screen at 768. This means that the first h1 title sits just above the base of the fold with at least two lines of text. I can crush it down a bit more but I'm keen to keep the overall feel.
Oh - and mobile devices comes next. I have a nice low-load php device detection script using user-agents. This works better than @media rules IMHO and is easier to change content as well as css.
Looks good but when I click Menu on my iPad it redirects to a page that doesn't exist - I can't see the source but I think convention is to redirect to the # symbol.
Yes, it goes to index.html.
As I said, the links (or inks as I actually put in my post) aren't active yet, but yes, I take your point on the hash symbol (#nogo).
I just want to get the pagination right first, then split off headers and footers into includes before duplicating the pages.
Nice to know Chrome works on iPad - thanks - also good example of 1024 resolution!
