Skip to content

Moves shell below key features #221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 20 commits into from
Closed

Conversation

joelachance
Copy link
Collaborator

I've added a Title to NumPy Shell here, and right now I'm indifferent about the result. It felt like something was missing when I moved it below Key Features, so please post thoughts and suggestions.

Resolves #220

Copy link
Member

@InessaPawson InessaPawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joelachance Let’s try the following and see how we like it then:

  1. Remove the white space above the “Key Features”. This is how it shows now:

numpyorg_221

  1. Remove the “Key Features” title and “Learn More” below.
  2. Remove the “NumPy Shell” title.

@joelachance
Copy link
Collaborator Author

@InessaPawson

  1. I did notice the whitespace and had removed it. You might have cached styles. I'll double check though!
  2. Without the 'Learn More', I don't think there's a CTA in that section.
  3. Will do!

@InessaPawson
Copy link
Member

  1. I did notice the whitespace and had removed it. You might have cached styles. I'll double check though!

Clearing the cache fixed it. Thank you for the tip!

  1. Without the 'Learn More', I don't think there's a CTA in that section.

I’m not certain if the CTA is really needed there. @MarsBarLee @rgommers what do you think?

@rgommers
Copy link
Member

It felt like something was missing when I moved it below Key Features

Yeah, it's hard to explain exactly what it is, but visually the page looks less appealing to me now. Perhaps because I'm already used to the original layout, but I'm not completely sure this is an improvement.

@InessaPawson
Copy link
Member

InessaPawson commented Apr 26, 2020

I'll submit a prototype/s with the new layout for you to make the final decision.

@InessaPawson
Copy link
Member

Here are four lo-fi prototypes for your consideration.

Version 1 Key features -> News -> Shell
numpy_h1
Version 2 Shell -> News -> Key features
numpy_h2
Version 3 News -> Shell -> Key features
numpy_h3
Version 4 News -> Key features -> Shell numpy_h4

@InessaPawson InessaPawson mentioned this pull request Apr 28, 2020
@joelachance
Copy link
Collaborator Author

One suggestion if we go with the banner-style news section: We could do the blue background in CSS and allow that to stretch across the screen 100%, and simply export the rest of the image as an svg. On that note, if we are just rendering text, it'll be a bit more performant to write it in HTML. On the flip side, this could be a pain if this section changes a lot.

My preference would be v3 or v4.

@InessaPawson InessaPawson mentioned this pull request Apr 30, 2020
@rgommers
Copy link
Member

I like v4 the best, and I think it will look even better with Joe's suggestion of stretching the news bar to 100% of site width. v4 has a nice symmetry to it somehow, and fixes the thing that felt a little off with the "key features" section right under the title.

and simply export the rest of the image as an svg. On that note, if we are just rendering text, it'll be a bit more performant to write it in HTML. On the flip side, this could be a pain if this section changes a lot.

The text of that news bar will change regularly I think. The text shouldn't be inside an svg image imho, that'd be too annoying to update (unless I'm missing what you are suggesting here).

@InessaPawson
Copy link
Member

For the record, I prefer Version One slightly more. I like the logic of it. First, there is an outline of the key features of the library, then an announcement (with a link) of the latest news about the project (in this example the latest stable release), then an opportunity to try out NumPy without the installation is offered.
Version Four would be my second choice.

@InessaPawson
Copy link
Member

I like v4 the best, and I think it will look even better with Joe's suggestion of stretching the news bar to 100% of site width. v4 has a nice symmetry to it somehow, and fixes the thing that felt a little off with the "key features" section right under the title.

Stretching out the bar would work. And if we leave out the “Learn more” button, I would not miss it.;)

The text of that news bar will change regularly I think.

Correct. @joelachance @rgommers I understand that not everyone is comfortable editing .svg. Do you think using news class would be a better option?

@InessaPawson
Copy link
Member

Here is Version 4 with updates.
numpy_h4_1

@joelachance
Copy link
Collaborator Author

I like your v4 update, @InessaPawson!

Why don't we put news content in the config file, and have it render in html? I think this might be much less of a chore for whomever needs to update the NumPy news.

@InessaPawson
Copy link
Member

I like your v4 update, @InessaPawson!

Great! I think we have consensus here.

Why don't we put news content in the config file, and have it render in html? I think this might be much less of a chore for whomever needs to update the NumPy news.

I see. It makes sense. @joelachance Please go ahead and make changes to the code.

@rossbar
Copy link
Contributor

rossbar commented May 4, 2020

I'm a bit late, but I just wanted to chime in and say I like v4 best too, esp. after the update!

@InessaPawson
Copy link
Member

I'm a bit late, but I just wanted to chime in and say I like v4 best too, esp. after the update!

Thank you for your feedback, @rossbar!

shaloo and others added 6 commits May 8, 2020 19:16
Cleanup of README, 80char line

Cleanup of README, 80char line
* DOC: Re-work EHT intro paragraph

 * Removed sentence about EHT sensing wavelength.
 * Updated wording surrounding VLBI
 * Switch to md reflink style for source readability

* Updates to Key Imaging Objectives

 * Renamed the section to 'Key Goals and Results' to better fit the content.
 * Updated first bullet point with context and accurate date.
 * Minor re-wording of remaining bullet points

* Modified the wording of a couple bullet points.

 * Made the reference to M87's black hole more explicit
 * Updated last bullet point of Challenges to give a higher-level overview
   of the imaging challeng.

* Re-wrote first paragraph of NumPy's role section

 * Attempting to focus specifically on image reconstruction,
   particularly eht-imaging, where the dependence on the scientific
   Python ecosystem is most relevant.
 * Trying to provide a little background on overall reconstruction
   task, and tie it into why NumPy/SciPy are so important.

* More reorganization of the NumPy Role section.

 * Moved eht-imaging up as it ties in with the theme and is the
   most prominent example of NumPy used in the eht analysis
 * Removed paragraph on CHIRP:
   - Trying to reduced redundancy given previous discussion on data
     processing
   - CHIRP is not available on GH - not sure to what extent NumPy is
     used for that particular pkg
 * Removed additional paragraph on regularized MLEM - want to avoid
   too much detail and focusing on algorithms

* Re-wording of the summary.
 * replaced vectors/matrices with n-dimensional array
 * Emphasize importance of discovery and role of collaboration.

* Final pass through for wording/grammatical edits.

* Added bolded titles to bulleted list in eht casestudy.

Addresses comments from review.
For corresponding change in the main repo, see
numpy/numpy#16201
Extra space removed

Extra space removed
@joelachance joelachance requested a review from InessaPawson May 12, 2020 02:05
@joelachance
Copy link
Collaborator Author

@InessaPawson @rgommers @MarsBarLee ready for another review

@joelachance
Copy link
Collaborator Author

Looks like some changes from master might have gotten merged in here, hopefully those don't make this PR too confusing.
I renamed section2 to keyfeatures here to keep things a bit more obvious.

@rgommers
Copy link
Member

Thanks for the update Joe. The colors and text look good. Could you make the text a link to an empty numpy.org/news (which can come from a news.md)?

There's a lot of whitespace for me and the bar is a bit on the wide side vertically:

image

@rgommers
Copy link
Member

Looks like some changes from master might have gotten merged in here, hopefully those don't make this PR too confusing.

Oh yeah that doesn't look too good. I think it's okay for testing for now, I can help do some surgery before merging if needed - I'd prefer not to merge it with this commit history as-is.

@joelachance
Copy link
Collaborator Author

agreed-- im not quite sure where that came from, or what it is. i can help remove it if everything else looks good!

@rgommers
Copy link
Member

Thanks! Yes, the rest of the changes look good to me.

@InessaPawson
Copy link
Member

Thanks for the update Joe. The colors and text look good. Could you make the text a link to an empty numpy.org/news (which can come from a news.md)?

There's a lot of whitespace for me and the bar is a bit on the wide side vertically:

@rgommers Clearing the cache should fix the whitespace issue. See Joe's tip above!;)

@joelachance The news bar is too wide indeed, let's try min-height: 45px;.

Also, I suggest changing the color of the hero-title font and the background color of the footer to Warm Black ( #013243) to match the rest of the dark elements. (Probably, needs a separate PR.)

These changes should make the top of the homepage look like this:
numpyorg_41

@InessaPawson
Copy link
Member

Every time I look at the homepage I can’t help but think that maybe two logos at the top one too many. @joelachance @rgommers @MarsBarLee @shaloo What do you think of removing the smaller logo just from the homepage?

@InessaPawson InessaPawson mentioned this pull request May 13, 2020
@rgommers
Copy link
Member

@rgommers Clearing the cache should fix the whitespace issue. See Joe's tip above!;)

Oops, yes that fixes it - thank you both

@rgommers
Copy link
Member

What do you think of removing the smaller logo just from the homepage?

Dynamically hiding a logo in the header seems a little elaborate. I agree having the double logo is a little odd (but who knows, maybe it looks better with the new logo!). Maybe easier to remove the bigger one?

@rgommers
Copy link
Member

Rebased and merged in gh-228, with follow-up items noted in the PR description there. Thanks all!

@rgommers rgommers closed this May 16, 2020
@InessaPawson
Copy link
Member

Maybe easier to remove the bigger one?

I do like the larger version of the logo next to the title NUMPY. However, if it is the only way to minimize the number of the logos on the homepage, I'm willing to sacrifice it.

@rgommers
Copy link
Member

Opened gh-229 to track the "remove a logo" todo. Thanks Inessa.

@bjnath
Copy link
Contributor

bjnath commented May 17, 2020

I've just seen the site, and it's breathtaking -- us at our best.

It's so good it has me worried. There's incredible content below the fold --
the ecosystem, the case studies -- and I'm concerned it will not get seen.

I'm wondering how we can get it higher without losing impact. Thoughts:

  1. Omit the KEY FEATURES heading.

  2. The features boxes can be shrunk to links -- or if we want to be fancy,
    boxes that expand on mouseover. We will not lose the supporting text; it
    will be there for those who want it.

  3. Try NumPy is a tour-de-force -- but we have to ask the hard question of
    how much we benefit from having it on page one. The single most important
    feature of NumPy is speed, and TryNumpy can't show that. The section is
    less pretty and demands active engagement. On a learning page -- it's killer.
    It's a beast. It just needs the right home.

@joelachance
Copy link
Collaborator Author

Rebased and merged in gh-228, with follow-up items noted in the PR description there. Thanks all!
@rgommers , thank you!

@InessaPawson
Copy link
Member

  1. Remove the “Key Features” title and “Learn More” below.

@rgommers @joelachance Based on #238 (comment), would you please give a second thought to the quoted suggestion? Keeping it is a waste of prime real estate indeed.

@joelachance
Copy link
Collaborator Author

@InessaPawson, I'm a +1 on removing the Key Features title. I'll roll that into existing work here (assuming @rgommers agrees).
I still think a CTA somewhere in the 'key features' section is a good thing (maybe that is the tiles being links to somewhere), but I seem to remember removing the 'learn more' already (it's probably in a branch in progress, if it's not in master). I'll do that as well, pending comments from @rgommers

@rgommers
Copy link
Member

Sounds like you all agree, it seems fine with me too, the tiles will work standalone too - please go for it!

@rgommers rgommers deleted the feature/220-move-shell branch August 30, 2020 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Revise the info architecture of the home page
6 participants