"Ecosystem" and "Case Studies" are easily lost
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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.
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.
-
It's clear to readers that the boxes at the top are key features; the Key Features headline eats up space without adding content.
-
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.
-
Finally,
Try NumPyis 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.
- 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
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
agent-research-recommend agent-review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jordansmall/spindrift#3714 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conda-forge/python-feedstock#934 ·