Use tags for content info?
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 673
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Description
At the very least, I would suggest using tags such as "Beginner", "Intermediate" or "Advanced". I'm not sure those are descriptive enough, or if we should group content in some other way. Thoughts?
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
No implementation files, tests, or entry points are identified. Start by reviewing how tutorial content is currently organized, then seek a decision on whether tags such as Beginner, Intermediate, and Advanced are descriptive enough or whether another grouping is needed; done requires an agreed content-labeling approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100