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

MySam plugins catalog #4

Open
ythecombinator opened this issue Oct 23, 2015 · 7 comments
Open

MySam plugins catalog #4

ythecombinator opened this issue Oct 23, 2015 · 7 comments

Comments

@ythecombinator
Copy link
Contributor

Given some facts like:

  • The great number of possibilities that MySan can achieve by plugins
  • The ease of creating new plugins and publishing them to npm
  • The growing popularity of this project

I'd bet that the number of MySam plugins will grow very fast. Maybe it would be cool to have a place to centralize them.

@thebergamo proposed in #3 the creation of a file or a section in the README and I think that this would be also important - but only for official (core-team developed) plugins - that's why I opened another issue instead of just commenting the other one.

Many tools in the node.js world have their own extensions catalog; e.g: automation tools, like gulp's plugins registry, preprocessors, like elm's catalog and so on.

Maybe now it's not a needing, but who knows in a near feature? If you don't have time to create one, I'd suggest, for now, include in the plugins creation guidelines instructions to any MySam plugin have a tag like mysam-plugin; e.g:

{
  "name": "mysam-myplugin",
  "main": "server",
  "mysam": {
    "client": "frontend",
    "styles": "styles.css"
  },
  "keywords": [
    "my-keyword-1",
    "my-keyword-2",
    "my-keyword-3",
    "mysam-plugin"
  ]
}

In short time it would at least allow you doing something like broccolijs does - which is linking to a npm seach-by-keyword result. In this case you would have a https://www.npmjs.com/browse/keyword/mysam-plugin link in the project's homepage.

In the long-term, you can use the idea of a special keyword in the package.json to create - or fork - something like Custom Elements - which would search for published packages with the mysam-plugin keyword and gather them in a beautiful and easy-to-publish registry.

BTW, I loved the project ❤️

@thebergamo
Copy link

@mabrasil I think this is the right way! This project is awesome and will grown fast =D

@igorantun
Copy link

+1, that sounds great.

@daffl
Copy link
Member

daffl commented Oct 23, 2015

This is great feedback. A website is definitely in the works and it will have a list of plugins based on the NPM tag. I'm also looking into creating a Yeoman generator for new plugins that initialize everything similar to what is described in the readme so that we can hopefully just do mysam create plugin.

Can someone add the suggested link to https://www.npmjs.com/browse/keyword/mysam-plugin to the Readme and submit a pull request? I'll re-publish the weather plugin (currently the only one I am aware of) with the keyword and once I am done with the todos list there will at least be two showing up already :)

@ythecombinator
Copy link
Contributor Author

Hey, it's great to know that you've been plannign this!

I'm also looking into creating a Yeoman generator for new plugins that initialize everything similar to what is described in the readme so that we can hopefully just do mysam create plugin.

That one would be my next issue. I think that issues are a very good way of organizing the project's TODOs. And I think it's worth opening one to discuss this generator.

Another good issue would be one to purpose a logo to this project.

If you agree, I may open both of them.

Can someone add the suggested link to https://www.npmjs.com/browse/keyword/mysam-plugin to the Readme and submit a pull request?

I've done this and also included some small docs suggestions in #6. Hope you like it 😃

@KarimJedda
Copy link

I love this thing, here's a logo proposal, hope you like it http://imgur.com/RLnDOf2, i can work on the resolution/sharpness if you want :)

@daffl
Copy link
Member

daffl commented Oct 25, 2015

@mabrasil Thanks for the pull request. It is merged and looking good.
@KarimJedda awesome! I would hold off a little so that we can plan what the next steps in regards to design and homepage should be but I'll definitely keep you in the loop.

@JawsomeJason
Copy link

This is fantastic! Whatever you do, do /not/ sell the rights to this property!!

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

6 participants