Skip to content
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

Open
ai opened this issue May 25, 2016 · 4 comments
Open

Better install instructions #4

ai opened this issue May 25, 2016 · 4 comments

Comments

@ai
Copy link

ai commented May 25, 2016

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

  1. If you have postcss-cli
  2. Install postcss-debug
  3. Replace postcss-cli to postcss-debug in you scrips.

gulp-postcss

  1. If you use Gulp with gulp-postcss
@andywer
Copy link
Owner

andywer commented May 31, 2016

@ai Would you say it's ok for now as it is?
(Added a little more documentation yesterday)

@ai
Copy link
Author

ai commented May 31, 2016

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).

@andywer
Copy link
Owner

andywer commented May 31, 2016

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.

@ai
Copy link
Author

ai commented May 31, 2016

Yeap, but we can provide diff for easy and popular cases and have API for other cases :)

@andywer andywer mentioned this issue Jun 1, 2016
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

No branches or pull requests

2 participants