Tracking issue for new functionality and design ideas
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
- hugo, numpy
- Domain
- content, documentation, web-dev
Research direction
This is a broad tracking issue rather than a single implementation task. Start with one unchecked linked item, such as gh-55, gh-212, or gh-263, and read that issue for its scope and entry points; this tracking issue is done only when its selected item has a separately defined completion state.
Written by the indexing model from the issue text.
Description
Since we've got a ton of work and conversation going on, I think it's useful to have an overview of ideas we have that are not yet implemented. There's no way we can do all of this before launch; for many of these we can choose to either release them one by one, or do a second significant release:
- translations (gh-55)
- new logo (gh-37)
- install widget (gh-212)
- further install docs improvements (e.g. unify build from source)
- interactive shell improvements
-
better Hugo/Sphinx integration ((new Sphinx theme was done)scipy-sphinx-theme-v2) - search box (gh-263)
- adding more case studies
- What to do with "Get Started" (gh-233)
- adding back the array computing content in some form
- moving the Team gallery to a Hugo template
- further optimizing categories in the main navigation bar (gh-234)
- a page on how to report issues (gh-72)
- content to address some of the user stories we haven't fully taken care of (gh-42)
- email validation of Mailchimp form
- add content on NumPy performance (gh-370)
... and more
- Dominant language
- Shell
- Stars
- 128
- Forks
- 132
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
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.
More from numpy/numpy.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sustain-2026
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
sustain-2026 translations
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
translations
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pop-os/plymouth-theme#43 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hykilpikonna/hyfetch#545 ·
-
on hold T: core-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100