-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better install instructions #4
Comments
@ai Would you say it's ok for now as it is? |
Better. But best way will be just a diff — ”replace this to this” (sorry, that I only write bad things, I am Russian we always only talk only about bad things, you do great work, really fast development). |
No problem, since it's constructive. I just think it's hard to provide a diff, since PostCSS can be used in so many different ways and setups. And there is some chance people will prefer using the CLI for debugging instead of changing the build process, anyway, I guess. I re-edited the gulp-postcss example slightly to make it more clear what to change, though. |
Yeap, but we can provide diff for easy and popular cases and have API for other cases :) |
You current instructions is good. But we could do better :).
People will use your tool, then they have some problem in existed build tool. So, they already use some tool: grunt-postcss, gulp-postcss, postcss-loader or postcss-cli.
You should give a install instructions in this way:
postcss-cli
postcss-cli
postcss-cli
topostcss-debug
in you scrips.gulp-postcss
gulp-postcss
The text was updated successfully, but these errors were encountered: