search

postcss / postcss.org

Official website for PostCSS
https://postcss.org
MIT License
80 stars 49 forks source link

Use postcss-cssnext in the boilerplate? #53

Closed jeddy3 closed 8 years ago

jeddy3 commented 8 years ago

This is a quick follow-on to @MoOx's comment in the boilerplate issue and the stylelint PR.

Are you be willing to accept a PR that replaces the current individual postcss plugins, of postcss-custom-media and postcss-custom-properties, with the postcss-cssnext plugin pack? I'll then be able to use its nesting feature as a replacement for @MoOx's use of indentation that I had to nuke in https://github.com/jeddy3/postcss.com/commit/592fe836fd6fa04f042b5fa064f6a07d5daa7787#diff-8a4b7dda92b463014bdba201b85229b6R24.

I figured it would be better to include postcss-cssnext, rather than request the addition of just postcss-nesting, as postcss-cssnext seems to be—like stylelint—featured in the early design mock-ups.

There are a few rules—function-calc-no-unspaced-operator, media-feature-range-operator-space-after, selector-pseudo-element-colon-notation etc—within stylelint-config-standard that are geared towards the features of postcss-cssnext, and so I think they will be an excellent fit for each other.

What do you think?

mxstbr commented 8 years ago

Yes, I'd love that! I haven't done anything with the config yet, but we should really showcase what PostCSS is capable of with this website! Please submit a PR!

MoOx commented 8 years ago

Should do the same in the default boilerplate for cssnext and stylelint.

jeddy3 commented 8 years ago

Should do the same in the default boilerplate for cssnext and stylelint.

Sounds like a plan :)

marcustisater commented 8 years ago

Yup, I agree as well. Great pointers @jeddy3