design

Clone

#565 Redesign top menu for new wiki theme
Closed: Invalid 6 years ago Opened 6 years ago by mattdm.

Closed: Invalid
Reopen Issue

This is more a UX design request than a visual design one — the visual design is fine, but the menu entries don't seem ideal.

Right now, the top level categories are:

  • wiki
  • Navigation
  • sub-projects

where:

  • "wiki" is a random list of wiki pages that seem of general interest like News and Features — but which happen to be outdated pages.
  • "Navigation" is a list of non-wiki pages: fedoraproject.org, get.fedoraproject.org, and join.fedoraproject.org. Except currently the first two go to the same place, and the last one redirects back into the wiki
  • "sub-projects" is basically okay, although the "all projects" list page itself needs work, which doesn't lead to a great experience. Also, we generally say subprojects, without a hyphen. Merriam-Webster confirms to me that this is fine. :)

What should these menu items be? I'm not sold on these three categories as top menu items at all, so the sky's the limit.

In my thinking, there's basically two audiences for the navigation bar, and probably they should be visually distinct.

First, people who landed on the wiki but really should go elsewhere. That's kind of what we just (thanks, @duffy!) just did with the front page. I don't know if it's useful to duplicate that in the menu, really.

Second, there are people who are using the wiki as a collaboration space. I think the subprojects menu is a good start. I think there should either be a search box or a link to the search page, too. What else? I'm not sure! It may also be that we should focus on the subgroups that use the wiki most heavily — Packaging, Ambassadors, QA, I think — and not make subprojects the navigation focus. (For example, with Pagure, I don't think Design really uses the Wiki much at all, and Magazine just has some short intro docs that would probably be better on the new docs site, not the wiki.)

I mean, really we need an information architect. But failing that, let's work on the menus. :)

There are some pages like

https://fedoraproject.org/wiki/Releases

which are kind of... logistics and program management, rather than a subproject per se. And groups like Release Engineering which aren't on the current menu.

Just some background on this, these are the exact links that were in the
sidebar on the old theme:

https://web.archive.org/web/20171101211715/https://fedoraproject.org/wiki/F=
edora_Project_Wiki

And these are pulled directly out of this page:
https://fedoraproject.org/wiki/MediaWiki:Sidebar

So I=E2=80=99m pretty sure if we edit that page, the toolbar will update

Cheers,
Ryanlerch

On Tue, 28 Nov 2017 at 7:26 am, Matthew Miller pagure@pagure.io wrote:

mattdm added a new comment to an issue you are following:
``
I mean, really we need an information architect. But failing that, let's
work on the menus. :)

There are some pages like

https://fedoraproject.org/wiki/Releases

which are kind of... logistics and program management, rather than a
subproject per se. And groups like Release Engineering which aren't on th=
e
current menu.
``

To reply, visit the link below or just reply to this email
https://pagure.io/design/issue/565

Yeah, I figured that's where it came from. It wasn't great before, but it was lost in the noise, and now it's much more prominent. Also, since they were expanded before, meaningless headers like "wiki" and "navigation" were harmless, but now with the non-expanded drop-downs...

Hmmm — I'm not so sure it's coming "live" from that page, though, because Navigation is capitalized in the menus and not in the sidebar page.

Divided into projects?
I do not think it's even better,.
But by category (development, design, media, graphics) and technologies (ARM, docker, etc.) will be ok.
I don't know even the design page is a little tired and lifeless , maybe more blue theme and in the style of drawing with some effects.
Also, I saw something very good at https://codepen.io/alaricweb/post/single-path-morph-svg
But I don't think use Greensock for free.
Good work anyway.

Hello guys,
My name is Vikram and I am new to this group so please excuse if I make any gaffes. I am a UX design and one of my skills is Information Architecture. I saw the links and I believe I can help not just with the header but also in improving the front page further. Personally I believe the navigation bar issues is connected to the overall IA of the Wiki and its design.

However, to begin with I will require some details, about the exact nature of the Wiki and its purpose, to get started. I can do a huristics evaluation of the Wiki site if that would get the discussion started.

Let me know how to proceed.

Please also have a little attention to advanced users ;)
I would like to see a link to special pages and to "what links here".

Usecase for special page: I noticed a broken link on L10N page: https://fedoraproject.org/w/index.php?title=L10N&type=revision&diff=507268&oldid=501101
This sounds weird, it may be a migration issue, I wonder how many pages have similar broken links and search the special page link, can't find it..

Usecase for what links here: our headers looks ugly with the new design https://pagure.io/design/issue/567
I don't know why, only L10N has an extension, I wanted to have a look how many L10N pages where using this headers.

I agree, please I try to upload a picture right now and I dont find the damn link for the upload anymore

I agree, please I try to upload a picture right now and I dont find the damn link for the upload anymore

Even though there's no obvious link to it, you can go to: https://fedoraproject.org/wiki/Special:Upload

@vikrams Let's start with a heuristic review and see how it goes? Once you've done the review I think you'll be in a better position to ask the kinds of questions where we can fill you in more on the usage patterns?

Metadata Update from @duffy:
- Issue assigned to vikrams
- Issue tagged with: triaged
6 years ago

So, not counting /wiki/Infrastructure/Fedorahosted-retirement, and leaving out all of user-focused documentation want moved to the docs site, these are the pages that have over 10,000 hits so far in 2017. I'd also like the Packaging and Legal stuff to move to the docs site, but we aren't even ready to have the conversations with those teams yet so that's getting a little ahead of things. So (in order):

/wiki/EPEL
/wiki/Releases/26/Schedule
/wiki/Common_F25_bugs
/wiki/Releases/27/Schedule
/wiki/How_to_create_an_RPM_package
/wiki/Join
/wiki/EPEL/FAQ
/wiki/Communicating_and_getting_help
/wiki/Legal:Main
/wiki/Releases/26/ChangeSet
/wiki/Special:Search
/wiki/SIGs
/wiki/KDE
/wiki/Releases
/wiki/Common_F26_bugs
/wiki/Releases/Rawhide
/wiki/Packaging:Guidelines
/wiki/Architectures/ARM
/wiki/Packaging:Scriptlets
/wiki/EPEL/ja
/wiki/Releases/27/ChangeSet
/wiki/Distribution/OnlineVendors
/wiki/Distribution/Download
/wiki/Docs_Project
/wiki/EPEL/zh-cn
/wiki/DocsProject
/wiki/Packaging:RPMMacros
/wiki/Fedora_Release_Life_Cycle
/wiki/Category:Package_Maintainers
/wiki/Infrastructure/Mirroring
/wiki/Legal:Trademark_guidelines
/wiki/Wallpapers
/wiki/Category:SIGs
/wiki/Packaging/RPMMacros
/wiki/Licensing:Main
/wiki/Fedora_27_Final_Release_Criteria
/wiki/Forbidden_items
/wiki/Changes/WaylandByDefault
/wiki/Releases/25/Schedule
/wiki/Magazine
/wiki/FedoraProject:Translating
/wiki/Websites
/wiki/Xfce
/wiki/Features
/wiki/End_of_life
/wiki/FWN
/wiki/Wayland_features
/wiki/Fedora_26_Final_Release_Criteria
/wiki/PackageMaintainers
/wiki/QA/Join
/wiki/Features/TeXLive
/wiki/Infrastructure
/wiki/Infrastructure/WhatHappenedToPkgdb
/wiki/EPEL/es
/wiki/Schedule
/wiki/Architectures/ARM/F25/Installation
/wiki/Common_kernel_problems
/wiki/Changes/CryptoPolicy
/wiki/Packaging:Naming
/wiki/Ambassadors
/wiki/QA:Updates_Testing
/wiki/LXDE
/wiki/Using_Mock_to_test_package_builds
/wiki/Bugs/Common
/wiki/Account_System
/wiki/Join_the_package_collection_maintainers
/wiki/Packaging:Python
/wiki/Design
/wiki/Remix
/wiki/List_of_Fedora_remixes
/wiki/Packaging:Systemd
/wiki/Special:RecentChanges
/wiki/Licensing
/wiki/Packaging:NamingGuidelines
/wiki/Projects
/wiki/Subprojects
/wiki/Games
/wiki/CommOps
/wiki/Statistics
/wiki/Events
/wiki/L10N
/wiki/Features/DNF

If the goal is to be a contribution tool, why do we think visits instead of activity ?

We can think whatever we like :) -- that's just some extra information I thought might be helpful. We can probably get edit information from datagrepper...

@vikrams Let's start with a heuristic review and see how it goes? Once you've done the review I think you'll be in a better position to ask the kinds of questions where we can fill you in more on the usage patterns?

I'll do heuristics based on layman assumptions and then we can sync our understanding. Hope to get back in a couple of days.

Summarizing and adding some missings in the new wiki theme:
- Search
- Uploads
- Classification in the top menu

Something that I realizes is that now tables need to have class="wikitable" or even specific css features to draw tables. That's ok if we think in new, but our wiki is kind of big and I had to modify by hand a lot of pages and even some templates because for some reason tables were redifined.

I'm probably ones of the few that want to keep and maintain the wiki (almost everyone hates it :sob: ), so I will track this issue and add a lot of things while going.

One of the new features that is bothering me a lot is the integration with FAS. I mean, it's really cool that it now uses the FAS authentication page, but now it doesn't remember the login, and I have to login each time I close the browser.

While we are fixing these, the design is displaying poorly on mobile. The wiki menu is off screen and the login button is hidden under a non-obvious icon. Screenshots:

here is the best place to file new issues with the theme.

https://pagure.io/fedora-mediawikitheme/issues

The login / avatar issue is now fixed in master over there FWIW too.

On Sun, Dec 24, 2017 at 8:54 PM, Brian Exelbierd pagure@pagure.io wrote:

bex added a new comment to an issue you are following:
While we are fixing these, the design is displaying poorly on mobile. The wiki menu is off screen and the login button is hidden under a non-obvious icon. Screenshots:

To reply, visit the link below or just reply to this email
https://pagure.io/design/issue/565

im closing this out since it's not the right queue and it seems some of the issues have already been fixed.

Metadata Update from @duffy:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
6 years ago

Hey design team: any further thoughts on this?

Login to comment on this ticket.

Metadata

triaged

None
None
None
None
Attachments 1
18708D03-7745-46E7-9115-7927F7DBAB0C.png
Attached 6 years ago View Comment
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.