Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Oct 15, 2015

  • Added a reference to scss-lint on syntax.
  • Fixed a typo. (And probably introduced many others).
  • Specified how to use spaces in HTML and CSS.
  • Fixed a typo about using integers or decimals.
  • Non-decorative images are always content.
  • One should never embed images or anything in HTML. There are more drawbacks than benefits on it.

  - Added a reference to scss-lint on syntax.
  - Fixed a typo. (And probably introduced many others).
  - Specified how to use spaces in HTML and CSS.
  - Fixed a typo about using integers or decimals.
  - Non-decorative images are always content.
  - One should never embed images or anything in HTML. There are more drawbacks than benefits on it.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spicymagpie Depending on platform, https://github.com/sasstools/sass-lint is usually a better choice since it supports Sass & SCSS syntax and leverages LibSass which is signifcantly much faster accordingly.

Accordingly, it's often seen as a better choice, but there's nothing wrong with naming both—with it likely being the first one listed instead of this one or a Ruby Sass - LibSass distinction.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @lozandier, thanks for the suggestion! Frankly, I don't even know if this PR is still valid for what has been done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant