Skip to content

Cut widgets from nav #497

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

Merged
merged 2 commits into from
Dec 26, 2021
Merged

Cut widgets from nav #497

merged 2 commits into from
Dec 26, 2021

Conversation

palewire
Copy link
Collaborator

As we continue to hone the homepage as a result of the discussion in #433, I propose this edit.

In my view, the nav, which has very limited space to work with, should be restricted to highest level metadata about the project. In my view, the widgets pages is not at the top level of the hierarchy. So I suggest removing it from this position.

@krassowski
Copy link
Member

What if we had a dropdown with "More" instead of removing bits and pieces? I think that placement in the navbar facilitates discoverability - if it is not there many users won't see it. I really think that having "More" would be useful.

@palewire
Copy link
Collaborator Author

Something like that could be a good future addition. Good to remember that, right now, widgets is in the nav but the /binder and /conduct pages are not. Hard to justify having this one up there and not those. And there clearly isn't space to include them all.

My feeling is that trimming it is a good incremental practice before building it back up, which is why I am submitting this small edit alone.

@choldgraf
Copy link
Collaborator

If we remove widgets is there any other place where people can get to that page?

I think it's OK to remove them now, and I agree that something like a projects dropdown is the right way to do it. As long as we collect a list of the projects that will need to be there so that we don't lose track, I'm +1 on it

@palewire
Copy link
Collaborator Author

It is not listed anywhere else. Though, neither are the /conduct and the /binder pages, which have long been orphans.

My take is we should continue to prune this nav down to a strong foundation, then look to build it back up after we've settled on what won't make the top line cut.

@choldgraf
Copy link
Collaborator

+1 from me - I just wanna make sure keep track of the orphans somewhere, so that it doesn't become an information silo!

@palewire
Copy link
Collaborator Author

@choldgraf, I made up a ticket where I tried to record the scope of the problem and open room for discussion. #529

@palewire palewire added this to the Streamline the site milestone Dec 24, 2021
@SylvainCorlay
Copy link
Member

No problem making it a temporary orphan as long as we come up with another easy way to find this content eventually. Let's improve navigation.

Copy link
Collaborator

@choldgraf choldgraf left a comment

Choose a reason for hiding this comment

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

Ok we have a few approves, a plan for how to add this content back in, and an issue to track it. This LGTM !

@choldgraf choldgraf merged commit f831f6b into master Dec 26, 2021
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.

4 participants