-
Notifications
You must be signed in to change notification settings - Fork 14
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
create targeted tutorials on yargs website #26
Comments
Hey @bcoe! That sounds fantastic. I'm on board. ✨ |
@Charlotteis I was thinking as a stop gap, until we can write some content, putting a link to a Gitter chat on the website would be good, and in the yargs README.md; various folks have requested this. |
hey folks! I've had ideas to do this forever and literally never got around to it. Ideally I would like to see it as a set of tutorials set up as levels: i.e. first you want to get your options, then you want to have options with aliases, then you want to use a command builder. Basically you level-up. I think as a first thing, I want to compile a list of exact tutorials, and then start building them one by one. Maybe even release one weekly, like a newsletter \o/ ? I also think they should be relevant to what people normally do, so I ran a twitter quetionnaire, so I can hopefully get some data. I know I've written a bunch of tests with marsupial examples, but I think we should have these as IRL stuff. |
In fact, so I give myself some deadlines, I'll start with option parsing this week and actually get it done. |
I am biased toward Slack, but that sounds like a good idea as any :)
I love this. Too many times do I get tutorials that are "HERE ARE ALL THE THINGS, BYE!!!!" |
@Charlotteis would you like to join the yargs maintainer slack? if so what email should I send an invite to? |
like the approach we're starting to take with http://istanbul.js.org/, I'd love to see us split our very long yargs README document into various targeted tutorials. e.g.,
What do you think? also looping in @maxrimue @Charlotteis.
The text was updated successfully, but these errors were encountered: