<commit_before>- content_for :page_title, "Hound"
- content_for :body_class, "home home-index"
- content_for :header_class, "home-header"

%section.intro
  .section-content
    .inner-wrapper
      .hero
        %h1
          Your code, always in style.
        %h2
          Hound comments on style violations in GitHub pull requests, allowing
          you and your team to better review and maintain a clean codebase.

        .cta
          = render "application/auth_button"

    .supported-languages
      %h4 Currently style checking

      .inner-wrapper
        %ul.languages
          %li.language
            .language-logo
              = image_tag "languages/ruby.svg"
            %h5 Ruby
          %li.language
            .language-logo
              = image_tag "languages/coffeescript.svg"
            %h5 CoffeeScript
          %li.language
            .language-logo
              = image_tag "languages/javascript.svg"
            %h5 JavaScript
          %li.language
            .language-logo
              = image_tag "languages/sass.svg"
            %h5 Scss
          %li.language
            .language-logo
              = image_tag "languages/go.svg"
            %h5 Go
          %li.language
            .language-logo
              = image_tag "languages/haml.svg"
            %h5 Haml
          %li.language
            .language-logo
              = image_tag "languages/python.svg"
            %h5 Python

%section.importance
  .section-content
    .section-title
      %h3
        Why does style matter?

    .inner-wrapper
      %article
        %figure.media-object
          .icon
            %i.fa.fa-bolt
        .media-body
          %h4 Convention
          %p
            Defining and sticking with a style guide helps reduce the amount of
            decisions that developers needs to make when writing code, helping to
            keep their focus on logic, not semantics and formatting.<commit_msg>Order language logos alphabetically, remove Python<commit_after>- content_for :page_title, "Hound"
- content_for :body_class, "home home-index"
- content_for :header_class, "home-header"

%section.intro
  .section-content
    .inner-wrapper
      .hero
        %h1
          Your code, always in style.
        %h2
          Hound comments on style violations in GitHub pull requests, allowing
          you and your team to better review and maintain a clean codebase.

        .cta
          = render "application/auth_button"

    .supported-languages
      %h4 Currently style checking

      .inner-wrapper
        %ul.languages
          %li.language
            .language-logo
              = image_tag "languages/coffeescript.svg"
            %h5 CoffeeScript
          %li.language
            .language-logo
              = image_tag "languages/go.svg"
            %h5 Go
          %li.language
            .language-logo
              = image_tag "languages/haml.svg"
            %h5 Haml
          %li.language
            .language-logo
              = image_tag "languages/javascript.svg"
            %h5 JavaScript
          %li.language
            .language-logo
              = image_tag "languages/ruby.svg"
            %h5 Ruby
          %li.language
            .language-logo
              = image_tag "languages/sass.svg"
            %h5 Scss

%section.importance
  .section-content
    .section-title
      %h3
        Why does style matter?

    .inner-wrapper
      %article
        %figure.media-object
          .icon
            %i.fa.fa-bolt
        .media-body
          %h4 Convention
          %p
            Defining and sticking with a style guide helps reduce the amount of
            decisions that developers needs to make when writing code, helping to
            keep their focus on logic, not semantics and formatting.
{'fraction_non_alphanumeric': 0.07174770039421813, 'fraction_numerical': 0.006044678055190539, 'mean_word_length': 1.4908376963350785, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, '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': '6686024', 'n_tokens_mistral': 1041, 'n_tokens_neox': 1015, 'n_words': 288}