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

Official plugin registry #283

Open
Justineo opened this issue Jan 11, 2015 · 8 comments
Open

Official plugin registry #283

Justineo opened this issue Jan 11, 2015 · 8 comments

Comments

@Justineo
Copy link
Contributor

Hi all,

Since Less now supports plugins, I think it would be sweet if we have an "official (recommended) plugin registry/list". (We kind of have one in current docs but I think we may need a mechanism of publish/register/submit plugins from the community.) It can prevent similar functionalities from being implemented several times and save developers lots of efforts when looking for suitable plugins.

@matthew-dean
Copy link
Member

Like a package manager? What about using NPM?

@lukeapage
Copy link
Member

I think its overkill. The majority of the plugins are tiny post-process plugins. as Matthew says, you can search on npm and a PR to our docs isn't difficult. If we start getting 100's of plugins we can revisit.

@matthew-dean
Copy link
Member

Agreed. The docs can get pull requests from people if others want to add to the list. If we get a longer list it can break off into its own section first, and then if the list gets too long too manage, decide then if we want to do something different.

Having said that, I am interested in consuming a list of plugins in a data (JSON) format. @lukeapage are you tagging all plugins with "less plugins" as keywords in NPM? If so, maybe we could recommend that in docs, or some common way of tagging so it could be consumed with a search to: https://www.npmjs.com/browse/keyword/less%20plugins. Then it would be a kind of "unofficial-official" list in a package manager.

@bassjobsen
Copy link
Contributor

I recently post some question here less/less-meta#5. Not the right place or not interesting. In summary i wonder how to distribute client side plugins?

@Justineo
Copy link
Contributor Author

I noticed jQuery recently switched to NPM to host its plugins. An NPM blog post recommended to add jquery-plugin and ecosystem:jquery as keywords (they said "make sure to do it"). So what if we do the same way by adding less-plugin & ecosystem:less for Less plugins?

@bassjobsen
Copy link
Contributor

+1 i will add the keywords from now

@seven-phases-max
Copy link
Member

To not increase the entropy of the universe I'll be using less-plugin keyword only.

@Justineo
Copy link
Contributor Author

Justineo commented Apr 5, 2015

Do things according to specific rules help slow down entropy increment.

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

5 participants