First, really great to see such a theme come to life! Moving it to Github would make it a lot easier to collaborate on it, should you be interested in some help.

The default layout should be fluid and with support of media queries. 1140px fluid is fine for starters, I think.

Comments

pyotrpro’s picture

pyotrpro commented

look at this - good framework for good html5 theme with media queries ;) http://lessframework.com/

alexweber’s picture

alexweber commented

awesome link, thanks!

brewthis’s picture

brewthis commented

The Less Framework isn't what Zentropy should be copying, in my opinion. I would suggest adding empty media queries for users to get started (http://www.stuffandnonsense.co.uk/blog/about/hardboiled_css3_media_queries) and making sure the standard design is using fluid widths.

Here's an approach I prefer to for example the Less-way: http://cssgrid.net

alexweber’s picture

alexweber commented
Version: 7.x-0.0-beta1 » 7.x-0.x-dev
Assigned: Unassigned » alexweber
Status: Active » Postponed

This is being considered and scheduled to be incorporated probably in version 2

tombigel’s picture

tombigel commented

Alex,
There are some different approaches to using media queries.

The approach of grid1140 if top to bottom - you use the media queries to identify smaller and smaller screens.

There is another approach (I see it as a much more solid approach) that uses media queries from the bottom up. Meaning, for small screens and weak machines and for IE < 7 you use a very simplified no-floats no-decoration CSS, and as you go up in screen size and in browser capabilities you add more and more advanced CSS.

This approach is explained in this slideshare slide show: http://www.slideshare.net/arborwebsolutions/beyond-responsive-web-design

I haven't tried to use this concept just yet, but this is what I had in mind when I thought of writing a new theme.

alexweber’s picture

alexweber commented

Thanks tombigel I'll look into it! :)

alexweber’s picture

alexweber commented
Status: Postponed » Closed (works as designed)

This issue has been dead forever, cleaning up issue queue for work on 2.0 release.