Last modified: 2014-09-24 22:52:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45170, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43170 - Sidebar toolbox is too crowded (tracking)
Sidebar toolbox is too crowded (tracking)
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.21.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: design, tracking
Depends on: 3575 22256 38863 51520 64312 64314 64329 41239 44594 64315
Blocks: tracking
  Show dependency treegraph
 
Reported: 2012-12-16 13:08 UTC by Niklas Laxström
Modified: 2014-09-24 22:52 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Niklas Laxström 2012-12-16 13:08:55 UTC
1. What links here
2. Related changes
3. Upload file
4. Special pages
5. Printable version
6. Permanent link
7. Page information
--
8. Browse properties
9. Short URL

A rule of thumb is that more than seven +/- 2 units makes a menu harder to use. In this case 7 links already come from core, leaving little to none space for extensions to add their own.

There are two items that are not related to the current page (upload a file and special pages) mixed between items that pertain to the current page.

Some ideas:
1) Upload a file could be integrated to page editors and removed from the sidebar.

2) What links here and Related changes could be integrated to Page information

3) Browser properties could also be integrated to Page information (via hooks, since it is an extension)

4) Permanent link and Short URL are kind of related, but perhaps they could be accessible from somewhere else then the toolbox. Same for printable version.
Comment 1 Nemo 2012-12-16 13:20:23 UTC
1) "What links here" must be in the sidebar, it's a crucial feature for navigation.
2) Related changes is related to history (but not in categories).
5-6) Permalink, print version and ShortURL are related and should stay together, as well as they're related to Collection's links; see also<https://www.mediawiki.org/wiki/Collection_Extension_2#Wireframe_Layout_for_placing_the_print_and_Collection_extension_buttons>
Comment 2 Nemo 2012-12-16 19:53:43 UTC
(In reply to comment #0)
> 2) What links here and Related changes could be integrated to Page
> information
> 
> 3) Browser properties could also be integrated to Page information (via
> hooks,
> since it is an extension)

Note: this was actually meant as a proposal to collate all "tools" about the (status of the) current wiki page in a single (special?) page/location which would then be linked from the sidebar or equivalent. I guess this would need some ideas on how to present all this mass of information, and a way to make it discoverable (starting from a way to call it); which is what I meant with point (1) above.
Comment 3 Quim Gil 2013-03-16 06:55:40 UTC
How popular "What links here" would be if it wouldn't be hidden inside the Toolbox? Once you know it you can't stop using it! It's not only useful for editors, for readers as well. Has there been any discussion about finding a better place for it?


"Printable version", "Permanent link" and "Short URL" could be placed at the end of the content area, right above the footer. It is a usual location for this functionality in blogs.
Comment 4 MZMcBride 2013-03-16 07:00:43 UTC
(In reply to comment #3)
> How popular "What links here" would be if it wouldn't be hidden inside the
> Toolbox? Once you know it you can't stop using it! It's not only useful for
> editors, for readers as well. Has there been any discussion about finding a
> better place for it?

Special:WhatLinksHere doesn't filter by namespace by default from the toolbox link. The results can be a lot of internal pages if you (as a reader) don't know how to filter to (for example) the article namespace. If this page/feature became more prominent or reader-focused, considerations like this would need to be made. Feel free to clone this bug, if you'd like.
Comment 5 Quim Gil 2013-04-02 18:51:22 UTC
Yes, there are many issues open related to WhatLinksHere. So many that it would even deserve a focused bug day to see what is actually going on there. If I'm not the only one thinking this feature should be more promoted in the navigation, that is.
Comment 6 MZMcBride 2013-04-03 02:20:15 UTC
(In reply to comment #5)
> Yes, there are many issues open related to WhatLinksHere. So many that it
> would even deserve a focused bug day to see what is actually going on there.
> If I'm not the only one thinking this feature should be more promoted in the
> navigation, that is.

Feel free to clone this bug, if you'd like.
Comment 7 Quim Gil 2013-07-17 10:33:30 UTC
(In reply to comment #6)
> Feel free to clone this bug, if you'd like.

See Bug 51520 - Morph "What links here" into a "Context" tab next to "Talk"
Comment 8 MZMcBride 2013-10-06 22:46:58 UTC
Is this a tracking bug?
Comment 9 Nemo 2013-10-07 08:00:50 UTC
(In reply to comment #8)
> Is this a tracking bug?

Not necessarily. There are some specific proposals above which could be done without too much problems.
Comment 10 John McClure 2014-09-24 22:52:17 UTC
(In reply to Nemo from comment #1)
> 1) "What links here" must be in the sidebar, it's a crucial feature for
> navigation.
> 2) Related changes is related to history (but not in categories).
> 5-6) Permalink, print version and ShortURL are related and should stay
> together, as well as they're related to Collection's links; see
> also<https://www.mediawiki.org/wiki/
> Collection_Extension_2#Wireframe_Layout_for_placing_the_print_and_Collection_
> extension_buttons>

agreed it's crucial so much so i suggest what links here can be a button next to a page's title, showing a list in a gadget thus displayed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links