-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Plugin Search #17
Comments
Yep, that's one of my main qualifications I guess. Andrey had some suggestions for the plugin list which we should include, so I'll have a think about how to refactor postcss.parts in a more modular way! Same thing applies to the wizard, let's keep it simple for v1 and do a soft @ai thoughts? On Tue, 5 Jan 2016 18:27 Marcus Tisäter [email protected] wrote:
|
@mxstbr the Number 1 task is to use Also we should highlight most important plugins, as we did in README.md. I think this task should be done for v1, because they are really important. Without npmsearch.com we will have not full list of plugins. Without highlighted plugins we will create wrong PostCSS impression. |
Let's try make this feature happen for 1.0. |
You could get plugins from npm + whitelist some that you want to promote or make "approved by the community" |
@ai alright will do. @MoOx see this issue: mxstbr/postcss.parts#12 |
For reference, the Karma project just links to a npm keyword search http://karma-runner.github.io/0.13/config/plugins.html (see "existing plugins" link) |
Highly likely going to use npmsearch.com 👍 |
Hey @mxstbr - I think we need to talk a few things over before officially hacking away on this issue and milestone together, I have few ideas that I would like to talk over and some reorganizing to do when you have time to help me with that. I think we all deserve a small break from this project so we don't go crazy. 😅 |
We need a section for visitors to search & find PostCSS Plugins, similar to http://postcss.parts/ - Is it possible to integrate PostCSS Parts into this?
The text was updated successfully, but these errors were encountered: