Document generic ride information (ratings, admission price, popularity, maintenance)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
There should be some ride-agnostic documentation related to ride ratings, admission price, popularity, and maintenance costs - what the actual numbers are, how they affect pricing, how to manage them.
Individual ride types would get their own information if they need to expand on these things (roller coasters can control their stats much more than something like bumper cars can, for example).
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the existing ride documentation and identify where generic information about ratings, admission price, popularity, and maintenance belongs. Document the actual numbers, how they affect pricing, and how to manage them, while leaving ride-specific expansions to individual ride-type documentation.
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