<commit_before><div class="intro">
  <p>
    The web is a responsive place, 
    from your lithe <span class="amp">&</span> lively development process 
    to your end-user's super-tablet-multi-magic-lap-phone. 
    You need grids that are powerful yet custom, 
    reliable yet responsive.
  </p>
  <p>
    Susy grids are fluid on the inside, 
    ready to respond at any moment, 
    but contained in the candy shell of your choice, 
    so they respond how and when and where you want them to.
  </p>
  <p>
    We don't design your site or dictate your markup,
    we just do the math and get out of your way.
  </p>
</div>
<section class="info">
  <div class="v1-0">
    <h2>
      <a href="https://rubygems.org/gems/susy">Version 1.0<i>.rc.0</i></a>
    </h2>
    <div class="highlight">
      <pre>gem install susy --pre</pre>
    </div>
    <ul>
      <li><a href="https://github.com/ericam/susy/blob/master/CHANGELOG.mkdn">What's changed</a></li>
      <li><a href="https://github.com/ericam/susy/blob/master/CHANGELOG.mkdn#upgrade">Upgrade</a></li>
    </ul>
  </div>
  <div class="v0-9">
    <h2>
      <a href="https://rubygems.org/gems/compass-susy-plugin">Version 0.9</a> (deprecated)
    </h2>
    <div class="highlight">
      <pre>gem install compass-susy-plugin</pre>
    </div>
    <ul>
      <li><a href="https://gist.github.com/1163918">Reference</a></li>
      <li><a href="https://gist.github.com/1163463">Tutorial</a></li>
    </ul>
  </div>
</section>
<section class="why">
  <h2>Why is 1.0 a release candidate?</h2>
  <p>
    Susy 1.0 is stable, tested, <span class="amp">&</span> feature complete;
    but our launch depends on unreleased Compass and Sass features.<commit_msg>update home page version<commit_after><div class="intro">
  <p>
    The web is a responsive place, 
    from your lithe <span class="amp">&</span> lively development process 
    to your end-user's super-tablet-multi-magic-lap-phone. 
    You need grids that are powerful yet custom, 
    reliable yet responsive.
  </p>
  <p>
    Susy grids are fluid on the inside, 
    ready to respond at any moment, 
    but contained in the candy shell of your choice, 
    so they respond how and when and where you want them to.
  </p>
  <p>
    We don't design your site or dictate your markup,
    we just do the math and get out of your way.
  </p>
</div>
<section class="info">
  <div class="v1-0">
    <h2>
      <a href="https://rubygems.org/gems/susy">Version 1.0<i>.rc.1</i></a>
    </h2>
    <div class="highlight">
      <pre>gem install susy --pre</pre>
    </div>
    <ul>
      <li><a href="https://github.com/ericam/susy/blob/master/CHANGELOG.mkdn">What's changed</a></li>
      <li><a href="https://github.com/ericam/susy/blob/master/CHANGELOG.mkdn#upgrade">Upgrade</a></li>
    </ul>
  </div>
  <div class="v0-9">
    <h2>
      <a href="https://rubygems.org/gems/compass-susy-plugin">Version 0.9</a> (deprecated)
    </h2>
    <div class="highlight">
      <pre>gem install compass-susy-plugin</pre>
    </div>
    <ul>
      <li><a href="https://gist.github.com/1163918">Reference</a></li>
      <li><a href="https://gist.github.com/1163463">Tutorial</a></li>
    </ul>
  </div>
</section>
<section class="why">
  <h2>Why is 1.0 a release candidate?</h2>
  <p>
    Susy 1.0 is stable, tested, <span class="amp">&</span> feature complete;
    but our launch depends on unreleased Compass and Sass features.
{'fraction_non_alphanumeric': 0.1662276851038923, 'fraction_numerical': 0.019315188762071993, 'mean_word_length': 2.901826484018265, 'pattern_counts': {'":': 0, '<': 123, '<?xml version=': 0, '>': 123, 'https://': 12, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6854875', 'n_tokens_mistral': 1289, 'n_tokens_neox': 1210, 'n_words': 334}