Use tags for content info?

Open
#7 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
numpy
Domain
content, documentation

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.

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?

Dominant language
No language data
Stars
673
Forks
229
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from numpy/numpy-tutorials

All issues in numpy/numpy-tutorials

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.