thatcoolguy

Not that bad?

How is "monitoring email, filtering content, or even blocking access to sites" not bad?

CISPA would allow the government, companies and ISPs to have potential access to your private information, all in the name of "Cybersecurity". Please tell me how that isn't bad.

I don't know a lot, but Zepto seems to be focused on (mobile) Webkit.

GitHub repo?

Options:

- Emacs

- Vi

- Other

Is that another joke about how cool vim and emacs are and how other editors suck? Again, seriously?

I don't like it too much. It's still based on designing for desktop first.

I prefer the ones that use a mobile first approach, which is more future-proof and is supported on more devices.

Also, another thing to consider is fluid-width vs fixed-width. Fluid width layouts are harder, but much more future proof. The mobile device landscape changes fast, and there are lots of sizes to design for. A fluid-width website would be much better in this case.

Some of these are Gridless[1], HTML5 Boilerplate[2] and 320 and Up[3].

[1]: http://thatcoolguy.github.com/gridless-boilerplate/

[2]: http://html5boilerplate.com/

[3]: http://stuffandnonsense.co.uk/projects/320andup/

I totally agree.

Grid systems are great, but not in the way they're being used today - with lots presentational of classes and ids in the markup.

Are we going back to the days of tables for layout? Look, classes like span-x, grid-y, append-x describe only the presentation of the content. I thought HTML was meant to describe structure, not layout.

Grid systems are destroying the semantic web.

EDIT:

Other classes-littered systems aren't any better (OOCSS, I'm looking at you).

You're right, Gridless is not really the best name for this boilerplate, but I'm not good in choosing names :(

The problem with grid systems is that they include classnames and ids which should be unique to each project. You can still use grids, but please don't use span-x classes, customize the classnames and ids to suit to your project. And doing that isn't impossible or extremely hard, there are a lot of tools out there for that: Sass/Compass, LESS, Blueprint's compress.rb script etc.

1. Respond.js is not in the footer, it is inside the <head> tag. See here: https://github.com/thatcoolguy/gridless-boilerplate/blob/mas... 2. HTML5's syntax is not very strict, but I prefer closing void elements because I think it improves readability. 3. I chose not to add any responsive image style by default because of IE problems and Windows' rendering. I'm thinking of adding that soon.

Thanks :) I really think responsive web design and one web is the future of web design. There are some situations where a specific mobile website will be needed, but in the (near) future these will be very rare IMHO. If you have any cool ideas let me know with a pull request or something.

Thank you! It's still a work in progress and I'll be adding more information on it gradually.

I don't really see the need for a Compass version right now, but you can try to port it anytime. It'll be easy, since Gridless doesn't have any pre-made grid systems or classes.