Skip to content
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

Homepage: add code snippet and link to tutorial #4187

Closed
wants to merge 1 commit into from

Conversation

iosonofabio
Copy link

The current matplotlib homepage is missing any reference to the tutorial and any example code for newbies.

I propose to add those in this PR.

@WeatherGod

@iosonofabio
Copy link
Author

Here a screenshot: http://picpaste.com/kTbywhbt.png

@tacaswell tacaswell added this to the next point release milestone Mar 4, 2015
@WeatherGod
Copy link
Member

Those buttons seem very out of place, especially since we don't have such buttons anywhere else. Plus, three of the four buttons are for the same links that are available at the top. Why not add a Tutorial link to that list? I also wonder if the font size for those links are too small, making them easy to ignore.

@tacaswell
Copy link
Member

This conflicts with #3350 (which should be revived)

@iosonofabio
Copy link
Author

@ben: "out of place" sounds a lot like "visible". That stands in
contrast with the current links which are, I think, not visible at all.
But they look ugly, agreed. Then I'd suggest to make the top menu a lot
bigger and more contrasted (orange on white??). Again, see golang for an
example.

@thomas: #3350 is closed and I can't find an image to what it looks
like. What is your concrete suggestion here?

From what I can tell from the code, #3350 is complementary to my proposal:

  • what I do: tune top part of the page only, adding a link and a snippet
  • what 3350 does: reorganized the rest of the page, adding sections and
    subsections and lists and questions and so on. Very text-heavy, not
    suitable for the "impact" first sight of the home, IMHO.

F

On 03/04/2015 04:02 PM, Thomas A Caswell wrote:

This conflicts with #3350
#3350 (which should be
revived)


Reply to this email directly or view it on GitHub
#4187 (comment).

@WeatherGod
Copy link
Member

Yeah, I see them as complementary. This is meant to give a better "first
impression", while the other was meant to help keep users from getting
mired down.

And yes, orange on white has been a thorn in my side (especially since I
wear tinted glasses). The links definitely need to be more prominent. Look
at just about every single other project page out there, and their
top-level menus are huge. Heck, look at just about every single other major
website! I would say that I would like to see it be twice as tall as it is
now, if not even turning it into a more button-like interface at the top.

On Wed, Mar 4, 2015 at 10:14 AM, Fabio Zanini notifications@github.com
wrote:

@ben: "out of place" sounds a lot like "visible". That stands in
contrast with the current links which are, I think, not visible at all.
But they look ugly, agreed. Then I'd suggest to make the top menu a lot
bigger and more contrasted (orange on white??). Again, see golang for an
example.

@thomas: #3350 is closed and I can't find an image to what it looks
like. What is your concrete suggestion here?

From what I can tell from the code, #3350 is complementary to my proposal:

  • what I do: tune top part of the page only, adding a link and a snippet
  • what 3350 does: reorganized the rest of the page, adding sections and
    subsections and lists and questions and so on. Very text-heavy, not
    suitable for the "impact" first sight of the home, IMHO.

F

On 03/04/2015 04:02 PM, Thomas A Caswell wrote:

This conflicts with #3350
#3350 (which should be
revived)


Reply to this email directly or view it on GitHub
<
https://github.com/matplotlib/matplotlib/pull/4187#issuecomment-77173085>.


Reply to this email directly or view it on GitHub
#4187 (comment)
.

@tacaswell tacaswell modified the milestones: proposed next point release, next point release Jun 18, 2015
@tacaswell
Copy link
Member

This has had no traffic for 2 years and has rebase conflicts, closing.

@iosonofabio Thank you for you work and sorry it did not get merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants