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

Updated README #4325

Merged
merged 1 commit into from
Nov 6, 2017
Merged

Updated README #4325

merged 1 commit into from
Nov 6, 2017

Conversation

Kira2
Copy link
Contributor

@Kira2 Kira2 commented Nov 6, 2017

Added a link to the new SendinBlue adapter for parse-server

Added a link to the new SendinBlue adapter for parse-server
@flovilmart
Copy link
Contributor

Hi @Kira2 ! Thanks for working on another adapter! That makes me think we need a better way for discovery of such adapters :) Any suggestions?

@flovilmart flovilmart merged commit d163269 into parse-community:master Nov 6, 2017
@Kira2 Kira2 deleted the Kira2-patch-readme branch November 6, 2017 07:45
@Kira2
Copy link
Contributor Author

Kira2 commented Nov 6, 2017

Hi! Glad if it can help. I need it for the project I'm working on, so it's normal to share it.
Don't have time to really think about a good and simple idea to discover adapters, but these are some suggestions.

I think that to be able to identify adapters, developers should share them and be able to let the community know about it easily, and by using the same way.

A section into the parse-server documentation, that could be called Adapters, could already introduce the principle to developers by explaining how to create an adapters, and how to publish them for the whole community. It might also encourage more people to write some, and make the ecosystem grow around parse-sever.

When creating node packages, it is possible to set keywords in order to find them on npmjs. It would also be possible into this new documentation to propose keywords to always put in the published packages, in order to find all the adapters created for parse-server easily. It can also be done by using a template for all packages' names. Example : parse-server-whatever-adapter.

Then, this documentation could contain a section with the best identified adapters, sorted by type (emails, images, notifications, files, etc.), and have direct links to them.

UnderratedDev pushed a commit to UnderratedDev/parse-server that referenced this pull request Mar 21, 2020
Added a link to the new SendinBlue adapter for parse-server
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

Successfully merging this pull request may close these issues.

None yet

2 participants