numpy / numpy/numpy.org

Tracking issue for new functionality and design ideas

Open
#266 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content design enhancement next release
Dominant language
Shell
Stars
128
Forks
132
Avg merge
1d 18h
Merged PRs (30d)
3

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 (scipy-sphinx-theme-v2) (new Sphinx theme was done)
  • 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

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.

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.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.