441–450 of 529 posts
Earlier quoted context omitted.
I'm writing a custom skin (CSS) to turn New Reddit into Old Reddit for when they inevitably, sadly, turn off old.reddit.com
Is all of the data even available? Posts don't show the author name on the front page and many comments are hidden under links on the new UX from the comment page.
Earlier quoted context omitted.
> Functionality that has been carefully designed so you won't find it The button is labeled 文A, which is quite common for translation service, and is just under an article title so it’s literally the most visible UI element. It’s difficult to make it more accessible than that...
I only learned about it when somebody pointed it out to me in an HN thread a couple of years ago, like the parent. The button is small and I think since I don't speak Chinese or Japanese my brain tends to skip Chinese characters as I assume that whatever they convey is not aimed at me. It's also alone on the left-hand side, with no decoration or styling showing that it's interactive. A flag icon or simply some more e…
If someone asked me to critique the UX of Wikipedia, the first two things I’d point out would be that I almost never use the left hand side bar (and I have a feel almost no one does) and that when paragraphs are that wide they become harder to read (especially when they snake around floated images). Not changing for 10 years, watching as some trends fade and others become law-of-the-land, and then making two changes…
> I almost never use the left hand side bar (and I have a feel almost no one does) The left sidebar has two killer features for me: 1. Finding canonical translations for technical terms. You need to know what the standard way to translate "hardware acceleration" or "differentiable manifold" is in French? Go to the wikipedia page and hover over the language switcher link in the left sidebar. Done. This has become one…
Sounds like they're going to repeat that mistake again.
If someone asked me to critique the UX of Wikipedia, the first two things I’d point out would be that I almost never use the left hand side bar (and I have a feel almost no one does) and that when paragraphs are that wide they become harder to read (especially when they snake around floated images). Not changing for 10 years, watching as some trends fade and others become law-of-the-land, and then making two changes…
The sole critique of the UX of Wikipedia that I have is that the normal version of Wikipedia redirects you to the mobile version when using a mobile device, and changes the URL while doing so. This is why we end up with all these m.wikipedia links. The mobile version, however, does not redirect you to the normal page when using a normal computer. So people like myself constantly have to edit the "m." from wikipedia l…
Mobile has higher latency and a small screen, so its important that I not need to make lots of request and its important that I can search inside documents. Both of which are broken by wikipedia's mobile interface.
If someone asked me to critique the UX of Wikipedia, the first two things I’d point out would be that I almost never use the left hand side bar (and I have a feel almost no one does) and that when paragraphs are that wide they become harder to read (especially when they snake around floated images). Not changing for 10 years, watching as some trends fade and others become law-of-the-land, and then making two changes…
> I almost never use the left hand side bar (and I have a feel almost no one does) The left sidebar has two killer features for me: 1. Finding canonical translations for technical terms. You need to know what the standard way to translate "hardware acceleration" or "differentiable manifold" is in French? Go to the wikipedia page and hover over the language switcher link in the left sidebar. Done. This has become one…
So much so that I've made a dedicated tool for this: https://wikitranslator.github.io/
It uses Wikipedia's APIs to "click the language links" for you. It also displays short summaries of both languages' articles, so the translation can be verified. I know I'm a small sample, but I end up using it reasonably often.
If someone asked me to critique the UX of Wikipedia, the first two things I’d point out would be that I almost never use the left hand side bar (and I have a feel almost no one does) and that when paragraphs are that wide they become harder to read (especially when they snake around floated images). Not changing for 10 years, watching as some trends fade and others become law-of-the-land, and then making two changes…
Please, since someone from wikipedia is probably reading this: Keep the JavaScript to a minimum. The plans aren't clear to me, but given what sites like reddit/etc have done during their "updates" the new UI's are terrible on anything that isn't a top of the line device with a screaming fast internet connection. Wikipedia (and a few other "older" sites) is such a pleasure to use as is, don't ruin it. AKA round-trippi…
They can embellish things with JS, but that has to be optional. Things like the article summary popup when you hover over a link. That can be deferred and left out completely.
They have the opportunity to do great things with design and typography for clarity, I hope they take it.
If someone asked me to critique the UX of Wikipedia, the first two things I’d point out would be that I almost never use the left hand side bar (and I have a feel almost no one does) and that when paragraphs are that wide they become harder to read (especially when they snake around floated images). Not changing for 10 years, watching as some trends fade and others become law-of-the-land, and then making two changes…
> I almost never use the left hand side bar (and I have a feel almost no one does) The left sidebar has two killer features for me: 1. Finding canonical translations for technical terms. You need to know what the standard way to translate "hardware acceleration" or "differentiable manifold" is in French? Go to the wikipedia page and hover over the language switcher link in the left sidebar. Done. This has become one…
I use this so often, that I've thought to turn this into a full-blown tool on several occassions. A simple "translate" webapp that opens wikipedia (API) in the background, looks for the inserted term and then returns the translated articles (with links to the article!) for that term.