OpenRefine / OpenRefine/openrefine.org
Create a getting started page in the documentation that we can easily reference.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
This issue follows the Heuristic Analysis done by asengupta on the forum
Create a getting started page in the documentation that we can easily reference. That page will contain the same information as the updated post-download page (see #371) and can be used by trainers or support personnel as an entry point for new users.
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
Review the updated post-download page referenced by #371 and the linked heuristic analysis on the forum. Create a documentation getting-started page with the same information, and consider it done when trainers and support personnel can use it as a clear entry point for new users.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100