numpy / numpy/numpy.org

"Ecosystem" and "Case Studies" are easily lost

Open
#238 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Ecosystem and Case Studies are strikingly original and attractive content -- and I'm concerned that because they're below the fold users will never see them.

I have suggestions to tighten the top of the page to pull at least one of them above the fold.

  1. It's clear to readers that the boxes at the top are key features; the Key Features headline eats up space without adding content.

  2. It's not crucial that the supporting text in those boxes always be displayed. The boxes can be turned into links, or if we're fancy can expand into boxes when clicked.

  3. Finally, Try NumPy is a tour-de-force -- but it's competing with other content for visibility, and we have to ask the hard question of how much we benefit from having it on page one. It can't show NumPy's single most important feature -- speed; though we've worked hard to dress it up, it's not graphically powerful; and it has no payoff unless the user stops reading to play with it, and we're not talking about pressing a button and watching. On a learning page -- it's killer. It's a beast. It needs the right home. On the home page, it can't add as much as Ecosystem and Case Studies do.

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

Start by reviewing the NumPy home page and the above-the-fold layout described in the issue. Compare the visibility of Ecosystem, Case Studies, the key-feature boxes, and Try NumPy; done means agreeing on and implementing a clearer content hierarchy.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
content, design, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.