-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Conversation
There was a problem hiding this 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:
- Remove the white space above the “Key Features”. This is how it shows now:
- Remove the “Key Features” title and “Learn More” below.
- Remove the “NumPy Shell” title.
|
Clearing the cache fixed it. Thank you for the tip!
I’m not certain if the CTA is really needed there. @MarsBarLee @rgommers what do you think? |
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. |
I'll submit a prototype/s with the new layout for you to make the final decision. |
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. |
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.
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). |
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. |
Stretching out the bar would work. And if we leave out the “Learn more” button, I would not miss it.;)
Correct. @joelachance @rgommers I understand that not everyone is comfortable editing .svg. Do you think using |
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. |
Great! I think we have consensus here.
I see. It makes sense. @joelachance Please go ahead and make changes to the code. |
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! |
… to generate the same
* 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
@InessaPawson @rgommers @MarsBarLee ready for another review |
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. |
agreed-- im not quite sure where that came from, or what it is. i can help remove it if everything else looks good! |
Thanks! Yes, the rest of the changes look good to me. |
@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 Also, I suggest changing the color of the These changes should make the top of the homepage look like this: |
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? |
Oops, yes that fixes it - thank you both |
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? |
Rebased and merged in gh-228, with follow-up items noted in the PR description there. Thanks all! |
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. |
Opened gh-229 to track the "remove a logo" todo. Thanks Inessa. |
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 -- I'm wondering how we can get it higher without losing impact. Thoughts:
|
@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. |
@InessaPawson, I'm a +1 on removing the Key Features title. I'll roll that into existing work here (assuming @rgommers agrees). |
Sounds like you all agree, it seems fine with me too, the tiles will work standalone too - please go for it! |
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