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
Although the driver is already mature and stable to use, seems like the documentation is the main friction point to early adopters. In fact, the open issues #394#391#389 and #383 are questions in the form "How do I do x thing on gorethink" .
I think that we should either bring more examples inside the documentation in the code or to create a site that mimics the ease of usage and friendliness that the official drivers provide (the ideal on my mind is to fork the official documentation repo ) or through a brand-new site.
I'm opening this issue to hear the thoughts of you, and together follow the best approach for the community.
The text was updated successfully, but these errors were encountered:
Perhaps there's a way for us to get the gorethink implementation added to the existing rethinkdb docs through a pull request? If not I think the fork idea is solid!
Personally I think that we can work in-house with the documentation in the Gorethink organtization, and submit a pull request when our documentation is good enough to the official rethinkdb docs.
Although the driver is already mature and stable to use, seems like the documentation is the main friction point to early adopters. In fact, the open issues #394 #391 #389 and #383 are questions in the form "How do I do x thing on gorethink" .
I think that we should either bring more examples inside the documentation in the code or to create a site that mimics the ease of usage and friendliness that the official drivers provide (the ideal on my mind is to fork the official documentation repo ) or through a brand-new site.
I'm opening this issue to hear the thoughts of you, and together follow the best approach for the community.
The text was updated successfully, but these errors were encountered: