The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:

1. '*.js': ['eslint'] <- fail when eslint finds issues issues
2. '*.js': ['eslint --fix', 'git add'] <- automatically fix eslint issues, and add to commit
3. '*.js': ['prettier --list-different'] <- fail when prettier finds issues
4. `'*.js': ['prettier --write

"lint-staged": {
    "src/**/*.js": [
      "prettier --write --trailing-comma es5 --semi false --print-width 160",
      "git add"
    ],
    "*.scss": [
      "stylefmt",
      "stylelint --syntax scss",
      "git add"
    ]
  },

How I currently am using it, how am I messing it up?

Describe the bug
In your documentation, it clearly states:

You may add as many html pages as you’d like to the root level directory, they will automatically be copied and minified into the dist/ folder upon building your site.

So I don't know if this a bug report or a feature request:

I want users to be able to visit website.com/survey instead of survey.html so I've put a

Would it be possible to prevent outputting invalid CSS properties that would fail a CSS syntax validation plugin such as csstree/stylelint-validator?

An example of this would be when using a mixin:

const example = css`
  ${({ height }) => height ? `height: ${height};` : ''}
  width: 100%;
`;

which the processor might output

In the document, here is no available options. Should I use:

"scss/at-extend-no-missing-placeholder": true,

or

"scss/at-extend-no-missing-placeholder": "always",

?

More rules without options in document:

• at-extend-no-missing-placeholder
• [at-impo

Related wemake-services/wemake-django-template#1046

Similar to the properties-order properties-alphabetical-order should report warning which weren't fixed by autofix. It could happen in CSS-in-JS, if rule has interpolations. Then postcss-sorting will skip it to not break the users code.

Related to https://github.com/hudochenkov/stylelint-orde

• compile styles - use #22 + styles task
• copy necessary files from theme directories (remember about inheritance)
• copy necessary files from /lib/web
• build require.js config
• copy and minify(?) html templates
• build js-translation.json

CSS that uses prefers-reduced-motion media query:

html {
  scroll-behavior: smooth;
}

@media screen and (prefers-reduced-motion: reduce) {
  html {
    scroll-behavior: auto;
  }
}

.stylelintrc.js uses stylelint-a11y and its rules (including a11y/media-prefers-reduced-motion):

module.exports = {
  'extends': 'stylelint-config-standard',
  'plugins': [

Howdy, I'm trying to get to the bottom of why border:none is specifically disallowed:
https://github.com/bjankord/stylelint-config-sass-guidelines/blob/master/src/.stylelintrc.json#L21

I see that this is based on sass guidelines, but the Sass Guidelines never recommend border: 0 over border: none explicitly.

The Sass Guidelines are based on

stylelint and stylelint order should be listed as peerDependencies so the user can specify their versions.

This fixes the issue of the blank line in error messages and allows users to use stylelint v10 (as you have a yarn.lock file)

After starting prettier-stylelint --write it is expected, that lines, marked like disabled or ignored, wouldn't be changed. But they are changing.

P.S: To .stylelintrc was added

"extends": "./node_modules/prettier-stylelint/config.js"

Everything was done like in the tutorial

What version of stylelint, prettier and stylelint-prettier are you using?

    "stylelint": "10.0.1",
    "stylelint-con

To help new contributors get started.