Add documentation on use cases for RethinkDB
Open
Nobody has claimed this yet.
enhancement
more
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Describing typical use cases for RethinkDB helps answer common questions like, "Is RethinkDB useful for tracking analytics?" or, "Can I use RethinkDB as an alternate data warehousing solution?"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing RethinkDB documentation to find the appropriate place for a use-cases section. Document typical use cases, including analytics tracking and alternate data warehousing, and consider the work done when those common questions are answered clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100