https://github.com/djeglin/ignition-scss

Tired of hard-boiled css grid frameworks? Why not roll your own as you go, but with none of the hassle?
https://github.com/djeglin/ignition-scss

Last synced: 18 days ago
JSON representation

Tired of hard-boiled css grid frameworks? Why not roll your own as you go, but with none of the hassle?

• Host: GitHub
• URL: https://github.com/djeglin/ignition-scss
• Owner: djeglin
• Created: 2013-07-22T15:41:24.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2017-05-25T11:03:19.000Z (over 7 years ago)
• Last Synced: 2024-08-01T00:41:01.098Z (3 months ago)
• Language: CSS
• Size: 311 KB
• Stars: 3
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.markdown

Awesome Lists containing this project

README

        
# Ignition

## An SCSS mixin library for rolling your own semantic grid as you go

Grid systems are great. No, really. They are. Its just that, well... They aren't. They're too rigid, they force you to do things a certain way, and they require ugly, non-semantic markup to work. On the other hand, though, the alternative is hand-coding all that CSS that makes a responsive site work, and that can take a lot of code and a lot of time. 

Ignition was made to remedy this situation. Its an SCSS toolkit for creating responsive websites. It contains no classnames, no required HTML formatting and no actual grid system of its own. Instead, the focus is on allowing users to create a flexible, responsive, grid system for their web project as they go, whilst minimising the amount of CSS they have to write themselves. 

How does it do that, you ask? Well, observe the following block of SCSS code, written using Ignition:

````

section {

  @include container;

  padding-top: 28px;

  > p {

    @include component;

  }

}

````

... and the CSS that this renders in to when the SCSS is processed:

````

section {

  overflow: hidden;

  position: relative;

  *zoom: 1;

  max-width: 85.375em;

  margin-left: auto;

  margin-right: auto;

  padding-top: 28px; 

}

section > p {

  float: left;

  direction: ltr;

  position: relative;

  box-sizing: border-box;

  width: 100%;

  padding: 10px; 

}

@media screen and (max-width: 480px) {

  section > p {

    width: 100%;

    left: auto;

    right: auto; 

  } 

}

````

You can see from this example the dramatic saving in terms of the amount of SCSS that you have to write to create a responsive layout. 3 rules in your SCSS to generate all that CSS. Obviously, the above is a *very* simple example, but you get the point. Complex responsive layouts can be created in a fraction of the time without the need for introducing presentational CSS class names into your markup.