Gridless is meant to be a starting point, which should be edited, tweaked and overwritten to suit each project's design requirements, rather than being blindly used as a black box of non-touchiness.

PHILOSOPHY

Some of the core principles of Gridless:

DBY (Don't Bore Yourself) approach

Gridless takes the boring parts of making websites and webapps out. It comes packed with everything you're tired of doing in every new project: CSS normalization, beautiful typography, a well-organized folder structure, IE bugfixes and other nice tricks.

Progressive responsiveness

Gridless uses mobile firstresponsive web design to adapt itself to the device's width. This means it'll work anywhere: old feature phones, newer smartphones, tablets, notebooks and bigger desktops. IE6/7/8 don't support media queries, so we use Respond.js to polyfill that.

Agnostic starting point

Gridless is extremely simple and straightforward. It doesn't come with any predefined grid systems or non-semantic classes. Gridless is meant to be a starting point, which should be edited, tweaked and overwritten to suit each project's design requirements.

MAIN FEATURES

Responsive (responds to the user's device screen width with the correct content and CSS)

CURRENT STATUS

Gridless is under active development. Its current version is 2.0.

FAQ

WHY THE NAME GRIDLESS?

Because Gridless is ...well, gridless. It doesn't come with any grid systems.

In my opinion, grid systems are a great idea, but not in the way they're being used today — with lots of presentational classes like span-x or grid_y in the markup. These classes only describe the presentation of the content, nothing else. Markup should be semantic; it is meant to describe the structure of the content.