You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we're to the point where it would be beneficial to have the npm readme to extoll the virtues of iter-tools. We should be telling people why they want to use it, and if we convince them then they can move on to an even more pleasant way of interacting with our documentation.
The text was updated successfully, but these errors were encountered:
Definitely!
As soon as I manage to clean up a few pending issues/PRs, I'd like to create a new ticket where we collaboratively set the goal for the new major release.
A website is sneaking higher and higher on my list of priorities. As you suggest @KSXGitHub I do think I'll move from central API docs in the README to jsdoc style comments at the top of a method's source which will be parsed by the website generator.
Let's make a doc website for iter-tools.
I think we're to the point where it would be beneficial to have the npm readme to extoll the virtues of iter-tools. We should be telling people why they want to use it, and if we convince them then they can move on to an even more pleasant way of interacting with our documentation.
The text was updated successfully, but these errors were encountered: