3 ms·
Honeslty I was never a fan of sticky headers and this one [1] is no exception. Is it really worth cluttering the reading space when you can reach search in y
by wraptile 6y ago
Honeslty I was never a fan of sticky headers and this one [1] is no exception.
Is it really worth cluttering the reading space when you can reach search in your browser's bar or just pressing the home button to scroll up instead?
Generally pop-ups are bad design for power users. If there's free space why not have it expanded? Instead add distraction-free-mode when clicking certain keyboard button or shortcut the article is expanded and all of the clutter hidden.
My general wikipedia workflows heavily rely on search, with proposed pop-up redesigns for languages and ToC now I have to do numerous clicks rather than just searching for "Français" and clicking enter if I want the french article.
Finally the article mentioned that there should be width limit and it was always sore thumb of mine - how can something that has 200 characters per line be read efficiently? There should be configurable limit with a more sane default.
1 - https://www.mediawiki.org/wiki/File:Search_prototype_for_the_Desktop_improvements_project.gif https://www.mediawiki.org/wiki/File:Search_prototype_for_the...
- ROARosen 6y agoTry the Wikipedia mobile site https://en.m.wikipedia.org/wiki/ https://en.m.wikipedia.org/wiki/ which basically solves most of your issues including the sidebar and wide paragraphs.
- wraptile 6y agoTIL, thanks! Though I'm fine with the current design, the proposed one is what bothers me.