nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community Menu Structure

Ryan_Gilmore

As part of a performance review, it was determined that speed improvements could be made by removing the JMP.com header and footer from the Community design.

The most selected menu items in the header (for the past 30 days) are

Learn JMP (764)
Software (542)
Support (319)
JMP Public (243)
JMP in Action (223)
Events (168)
About Us (90)

Of the callout links, these most selected are

JMP (under Software) [198]
Getting Started with JMP (under Learn JMP) [163]
Mastering JMP (under Learn JMP) [113]
Statistical Thinking Course (under Learn JMP) [59]
JMP Pro (under Software) [46]
Featured Content (under JMP Public) [35]

Note: Numbers given above represent the total event count

While the JMP.com header does bring some consistency between the two sites (jmp.com and community.jmp.com), I do not think either the header or footer is a strong enough presence to warrant the need to keep. The JMP branding (logos, colors, etc.) should be enough to provide a connection between the two.

However, I do think it is important to maintain the ability to provide links to more popular ones selected from the header. (We do not have data on the footer.)

With that, I think we should revisit the structure of the Community header. We previously attempted to have a single menu, indicated by a "hamburger" icon. That was not well received.

Here are some of thoughts,

Learn JMP should be prominently displayed in the main menu with links to each of the sections.
Have the JMP Blogs menu item provide links to each of the different blogs
The Microsoft Power BI Community has a single menu labelled Go To. Similar to what we tried before but I think it states the intent better than the hamburger icon,
I like the Alteryx categories - Participate, Learn, Support, Groups. Most of our spaces would fit into one of those categories.
I like the term Resources in the NetApp menu
I've seen the term Explore used. I like that as well.

Accepted answers

All comments

maria_astals

Hi @Ryan_Gilmore, the numbers mentioned are totals, right?

Is it possible to distinguish how many links came from JMP employees and how many from externals?

Ryan_Gilmore

Hi @maria_astals , these totals should be for externals only. The data is from Google Analytics.

Ryan_Gilmore

So, what's the purpose of the re-structuring?

Performance. Removing the JMP.com header/footer will increase our performance score. Because there is some value in the items we will be removing, we should insert these items in the menu bar.
Better Organization. There is lots of great content but knowing where to find the information you need may not be obvious. Improved menu items may make it more clear. Also, some of the important items, e.g. Learn JMP, are not prominent.
Future Growth. As we add more content/sections, we need to be able to accommodate the additional navigation.

Ryan_Gilmore

Suggestion 1

Participate
- Ask a question (Discussions)
- Suggest an idea (JMP Wish List)
- Share code (JSL Snippets)
- Groups
  - Regional
  - Private Support List (this would show the company name)
  - Private Group (this would show the group name)
- Private Spaces/List (Name
Learn
- Getting Started
- Tutorials
- Activities
- Learning Paths
Events
- Discovery Summit
- JMP on Air
Blogs
- JMPer Cable
- JMP Blog
- JMP Challenge
Support & Resources
- JMP Notes
- Technical Support
- JMP Software Administrators
- File Exchange

SAS Employees (only)

JMP logo (?)
- InsideJMP
- Private Groups
- Private Support List

Ryan_Gilmore

Suggestion 2

Go To
- Learn JMP
- Discussions
- Blogs
- File Exchange
- JSL Snippets
- JMP Wish List
- JMP Groups
- Support
- InsideJMP (SAS only)

The idea with this suggestion is that we only provide links to the landing pages (categories in Khoros speak). From the landing page, a user would navigate to an individual library or discussion. Exceptions are the Discussions and JMP Wish List boards. Some re-organization of groups and a new Support section would need to occur.

Ryan_Gilmore

Suggestion 3

Use the same menu structure as JMP.com

Software (these would be links to the product page showing posts associated with that product)
- JMP
- JMP Live
- JMP Pro
- JMP Clinical
- JMP Genomics
JMP in Action
- Discussions
- Blogs
- JSL Snippets
- File Exchange
Events
- JMP on Air
- Discovery Summit
- User Groups (? - this exists in the JMP.com menu but not intuitive to me)
Learn JMP
- Tutorials
- Getting Started
- Short Videos
- Activities
- Learning Paths
Support
- JMP Notes
- User Groups
- Discussions

SAS Employees (only)

JMP logo (?)
- InsideJMP
- Private Groups
- Private Support List

Ryan_Gilmore

All of these suggestions omit the About the Community category so will need to determine a way to include that area.

IanAtJMP

I would be more inclined to have the four menu headers like Altyrex has -- but of course we'd need to find our own headers so it's not exactly like theirs.

The current menu script and css supports flyout second-level menu items, which gives us some extra flexibillity. Screen Shot 2021-04-30 at 1.51.21 PM.png

smencia

I like the idea of reorganizing the menu structure and given the examples I too think the Altyrex is the best inspiration to go off of.

Jeff_Perkinson

I wonder if the tag line for the Community could be some inspiration here:

Share. Ask. Learn. Connect.

Those could make nice top level menus.

Ryan_Gilmore

Suggestion 4

Share
- Answer a question
- Share code
- Suggest an idea
- Share data
Ask
- Ask a question
- Technical support
Learn
- Getting Started
- Tutorials
- Activities
- Learning Paths
- JMPer Cable
Connect
- Regional JMP User Groups
- Private Support List (this would show the company name)
- Private Group (this would show the group name)
- Discovery Summit
- JMP Challenge

We need to add a menu item for SAS Employees. I like the idea of an icon rather than SAS Employees but can be convinced otherwise. Items to include would be:

InsideJMP
Private Support List
Private Groups