Live data from Hacker News

Explore Wikipedia's New Look

wikimediafoundation.org

261–270 of 288 posts

Re: Explore Wikipedia's New Look

#261

Details on the design process: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improveme... - On Wikipedia, and any MediaWiki installation, you can add the useskin query parameter to the URL to change skins on a page, even when not logged in. Current (vector-2022): https://en.wikipedia.org/wiki/59th_Academy_Awards?useskin=ve... Previous (vector): https://en.wikipedia.org/wiki/59th_Academy_Awards?useskin=ve... Olde…

Thanks, used this in conjunction with a url editing add-on [0]

    Description: Wikipedia Vector Skin
    Example URL: https://en.wikipedia.org/wiki/Joseph_campbell
    Include pattern: https://en.wikipedia.org/wiki/*
    Redirect to: https://en.wikipedia.org/wiki/$1?useskin=vector
    Pattern Description: Auto Redirects to vector skin version
    Advanced Options: 
        Exclude pattern: https://en.wikipedia.org/wiki/*?*
Feel free to toss a better way or an improvement for this if you end up doing the same. I'm sure the include and exclude patterns can be tuned, the add-on supports regex, otherwise you'll want a second rule for searches and such, but this should get a person started.

[0] https://addons.mozilla.org/en-US/firefox/addon/redirector/

Re: Explore Wikipedia's New Look

#262

Earlier quoted context omitted.

Could you share what font editor you used, and whether you're using ligatures?

FontForge, despite its antiquated interface, and liberal use of ligatures: https://cloudflare-ipfs.com/ipfs/QmVMS6LFUEqJJdnXDVuVZWRDSHT... The biggest challenge has been keeping it legible while dense. Ultimately I’d like to give it aesthetics similar to a roman serif, but for now still experimenting with the basic construction.

I just noticed that "L" and "R" are left and right arrows respectively. That's delightful.

Re: Explore Wikipedia's New Look

#263
post #163

Earlier quoted context omitted.

For whatever reason, especially with a bigger screen, I find that wider text becomes uncomfortable and somewhat exhausting to read. I'm not sure what the right portions/ratio are, but with a 27in screen it's definitely noticeable.

This has been studied a lot in design. Most people prefer line lengths in the 50-60 character region. Some studies show lengths up to 75 to be appropriate, but that’s about the limit. Past that people have a hard time keeping track of where they are and find reading to take more effort.

Isn't it because people are used to read pocket books?

Re: Explore Wikipedia's New Look

#264
post #263
post #163

Earlier quoted context omitted.

This has been studied a lot in design. Most people prefer line lengths in the 50-60 character region. Some studies show lengths up to 75 to be appropriate, but that’s about the limit. Past that people have a hard time keeping track of where they are and find reading to take more effort.

Isn't it because people are used to read pocket books?

Anecdotally, I'd say it has no relevance.

Re: Explore Wikipedia's New Look

#265

Earlier quoted context omitted.

Not always, but it often is. Zoomed to 200% the new design is fine though. Content fills the entire screen and the floating table of contents disappears. Works for me at least.

That suggests to me that you're either not sitting the correct distance away from your display, and/or your display's DPI settings are wrong.

I don't know if there's a "correct" distance, but I do have the monitor set fairly far back. Text is still perfectly readable at 100% it just doesn't fill the screen.

Re: Explore Wikipedia's New Look

#266

Earlier quoted context omitted.

Not always, but it often is. Zoomed to 200% the new design is fine though. Content fills the entire screen and the floating table of contents disappears. Works for me at least.

And now the text is huge . Sounds like you either are sitting too far away from your monitor, or need to have your eyes tested if that actually feels comfortable.

The text is huge, but it at least fits with screen. I do have the monitor set back, but not so far that text at 100% is unreadable.

Re: Explore Wikipedia's New Look

#267

> Research has shown that limiting the width of longform text leads to a more comfortable reading experience, and better retention of the content itself. Is this actually true? I'm curious if anybody has sources for this and if it's a common UX practice. I tend to use wider windows than traditional 8:9 half-screens and this max-width practice drives me nuts.

I guess it depends on the person. I'm happy to accept that I'm strange, but I'd much rather read lines that mostly fill my screen with normal margins on each side than short lines in a long narrow column surrounded by an ocean of empty whitespace. I can't be the only one who feels this way. I have yet to buy a book where 90% of each page is blank and there's just a tiny column of words down the middle of the page.

Thanks for the reply. I guess I am also strange, but I share your perspective.

At the very least, I feel like responsive options to toggle some of the various max-width CSS settings as an opt-in feature is worthwhile at least for reading-heavy sites like getpocket.com and news websites. I end up toggling these in Firefox / Chrome debugger and wish I could install extensions to apply custom code automatically but my employer does not allow this.

Re: Explore Wikipedia's New Look

#268

> Research has shown that limiting the width of longform text leads to a more comfortable reading experience, and better retention of the content itself. Is this actually true? I'm curious if anybody has sources for this and if it's a common UX practice. I tend to use wider windows than traditional 8:9 half-screens and this max-width practice drives me nuts.

It's a common accessibility requirement. For example, WCAG suggests limiting the max width of blocks of text to ~80 characters (40 for CJK). https://www.w3.org/TR/WCAG22/#visual-presentation

Aha, I was aware of the 80-character line limit for source code files, but wasn't aware it was a general accessibility recommendation. Thanks for the link!

Re: Explore Wikipedia's New Look

#269
post #195

Earlier quoted context omitted.

> I think if you really want full-width text, you could write a little custom CSS to make it work how you want it. How? Seriously, if you have a way to do this that works for pages in general I'll be extremely grateful. I tried using a user stylesheet that said * { max-width: 100% !important } for a while, but that breaks too many non-root elements on all sorts of sites. Whereas making the page narrow when it doesn't…

I use the Stylus extension for Chrome (also available on Firefox) to write user styles for sites, mostly to improve the legibility of text, but for sites like HN and Reddit that I browse a lot I've customised their look and feel extensively to match my tastes. Creating a custom style for a site just requires you to click the Stylus button in the toolbar, click on the site name at the bottom of the menu to create a ne…

> I use the Stylus extension for Chrome (also available on Firefox) to write user styles for sites, mostly to improve the legibility of text, but for sites like HN and Reddit that I browse a lot I've customised their look and feel extensively to match my tastes. Creating a custom style for a site just requires you to click the Stylus button in the toolbar, click on the site name at the bottom of the menu to create a new style and open the editor in a new tab and then add your CSS and hit save.

Yes, I'm talking about that kind of thing. It's trivial for people who want narrow sites to put a max-width on the root element that way. As someone who wants wide sites, how do I do undo all these designers' narrow widths without having to figure out manually what each individual site has done?

Post reply on HN