Graphic design for the Visualization tab under the Ecosystem section

[ghost]

This issue is raised in #342 by @InessaPawson.

I am just making a specific issue out of it so that people give attention to it.

Ecosystem section comes on the home page, and Science Tab appears even first when you visit the Ecosystem Section, but there are other Tabs too which have not been given enough attention like Data Science and Visualization.

@InessaPawson you want new images for the Visualization Tab or want to modify the existing ones ?

[InessaPawson]

I’d go with creating a set of icons to replace the current images. I’m open to other ideas as well.

[ghost]

@MarsBarLee what do u say ?

[ghost]

@InessaPawson If you observe the present difference between "Scientific Domains" and "Visualization" tabs - you will observe that the structure of both of them is different.

let me explain.

"Scientific Domain" Tab is organized in two vertical sections. (like two halves of a soccer field) - on the upper half is the content and in the lower half we have some categories of Scientific Domains and then within those categories we have provided an icon to represent those categories and related python libraries which use NumPy.

(It seems a lot of work has been done to organize the Tab in that way. LGTM)

Now let me explain the present "Visualization Tab"

Visualization Tab is organized into two horizontally attached sections (like two train coaches are attached).

In left side we have got the images (which also redirect to certain other webpages which explain the use of python libraries that are used in area of Visualizing large datasets).

In the right side we have got a description which somehow lists the names of libraries which are used in the Visualization industry.

So much for the present structure.

Now the design issues, let me bring to notice a few milestones.

1. In order to create new icons, we must first of all divide the field of Visualization into subfields (which has been done in Scientific Domain)
2. Once we have found the subfields - we can then proceed towards representing them through icons.
3. Once icons are done, we can arrange the name of libraries below the icons (much in the same way as has been done in the Scientific Tab)
4. The issue of centering the icons will apply there too as it applies at present in the Scientific Domain Tab

Now my suggestions to keep things moving towards execution (instead of just keeping them stuck in the planning stage)

I think the core issue of underdevelopment of Visualization Tab is the lack of content in it at present - the right section which includes description is not at all very much informative, so the first milestone has to be expand that description.

What i suggest for that ? To create a separate page on the very NumPy website which explains the use of various libraries that are used in the field of Visualization (instead of redirecting the user to external websites by creating hyperlinks on the images provided in the left section).

Let me know the gaps, if any, in my own understanding of the whole issue.

[InessaPawson]

What i suggest for that ? To create a separate page on the very NumPy website which explains the use of various libraries that are used in the field of Visualization (instead of redirecting the user to external websites by creating hyperlinks on the images provided in the left section).

@new-vivek11 Thank you for sharing your thoughts. The current version of numpy.org was launched in May 2020. This was preceded by nearly 10 months of in-depth discussions within the NumPy team as well as the user and developer NumPy community on every aspect of the website redesign. We are not planning on any major changes to the content or UI/UX of the website in the nearest future beyond what is already filed in the issues.

[ghost]

@InessaPawson

What i suggested was not to remove the "Visualization" section, I suggested to add a page to the NumPy website which explains the related things in detail.

Which might ultimately lead to the better development of that Tab.

Do u think it is under-developed too ?

[MarsBarLee]

Hi @new-vivek11, thank you for taking the time to share your suggestions. As Inessa said, there won't be major overhauls. To elaborate, the NumPy website is maintained by a core team and welcome PRs from contributors. Big changes like you initially suggested require group discussion with the core team and wider community. Any changes on one page must be consistent with the aim and design of the website as a whole.

However, smaller changes are still possible, such as the recent icon recoloring, and can be done individually and then reviewed by the team.

In terms of workflow, you can make suggestions with issues and make changes with PRs. Discussion can happen in both Github forums and in our community calls. In a call, you can clarify your ideas so that we can better understand your ideas. You can link to your issue, an early draft of your code, a written example of your descriptions or any mock-ups that would explain your ideas.

Some upcoming calls you could join are the NumPy Newcomers Meetings (on Nov 4, 4pm UTC) or the NumPy Documentation team meetings (on Nov 8, 3pm UTC). You look at our Documentation meeting agenda to see our workflow and add yourself to the next meeting agenda.

You can find the Zoom links to these calls in the Numpy Community Calendar.

You can also connect or collaborate with others in the NumPy community by checking out the NumPy Community page.

[ghost]

@MarsBarLee Your input was very helpful as always. Thanks ... Will adjust my approach accordingly !

[InessaPawson]

@InessaPawson

What i suggested was not to remove the "Visualization" section, I suggested to add a page to the NumPy website which explains the related things in detail.

Which might ultimately lead to the better development of that Tab.

Do u think it is under-developed too ?

@new-vivek11 The objective of the Visualization tab was to underline the importance of NumPy in this space by showcasing some of the most popular and highly reputable visualization libraries that depend on NumPy. With that in mind, I think the amount of the existing content will suffice.

[rgommers]

With that in mind, I think the amount of the existing content will suffice.

I agree. We want to give a sketch of the ecosystem, but not explain everything in a lot of detail. That would be a ton of work, and would also give a lot more content to translate into a number of other languages. So while we can tweak things if needed, in general we're happy with the amount of content on the site right now, and the quality of it.

For visualization in more detail, please see https://pyviz.org/