-
Notifications
You must be signed in to change notification settings - Fork 34
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 coverage of node-api in Youtube #437
Comments
@nodejs/addon-api if you have thoughts on what videos would make sense to create or existing content that we should promote. |
1 to promote - https://www.youtube.com/watch?v=4cCSPw-I0GE |
Suggestion, walk through the existing examples in the examples repo in a video |
Another suggestion projections into other languages |
We discussed in the 24 June 2022 Node API meeting, that it would be beneficial to find some vloggers that are interested in developing addons using Node-API in order to promote the API usage. If there are people that have videos / other promotions using NAN or V8 APIs directly, we can contact them to see if they are interested in doing a similar one in Node-API. |
We discussed in the meeting this week and opened, nodejs/social-team#7 @NickNaso has volunteered to start working on some videos so we wanted to agree on where best to post them. |
|
|
From discussion in the meeting today, it would be good to add to this issue links to some existing presentations. Some include: https://www.youtube.com/watch?v=-Oniup60Afs |
We discussed in the 11 Nov Node API meeting of "where do we put links to videos". We believe the best approach would be something similar to what we plan for the Node bindings list, where we:
|
Kevin volunteered to |
Created PR in core to add link to Node-API main documentation: nodejs/node#46189 |
We agreed to close based on the pages being set up. We should still remember that there is more video content we could create. |
It was mentioned that a search on youtube shows videos which are still mostly non node-addon-api. We should work to improve that.
The text was updated successfully, but these errors were encountered: