Page MenuHomePhabricator

Make Refreshed less-specific to Brickimedia: Custom font for skin should be definable on wiki instead of the repo
Open, Needs TriagePublic


Currently, Lato is being pulled from Google Font's server, and in Refreshed/refreshed/main.css - This should be defined instead in MediaWiki:Refreshed.css or MediaWiki:Refreshed-font (but preferrably the former)

Event Timeline

Restricted Application added a subscriber: MacFan4000. · View Herald TranscriptAug 4 2016, 11:56 PM
SamanthaNguyen moved this task from Backlog to Refreshed on the Brickimedia board.Aug 5 2016, 2:02 AM
SamanthaNguyen added a project: Refreshed.
SamanthaNguyen moved this task from Backlog to Feedback / Suggestions on the Refreshed board.
MtMNC added a subscriber: MtMNC.Aug 18 2016, 1:16 AM

I support this. Should the default header font-family be the same as the current body scheme ("Helvetica Neue","Helvetica","Arial",sans-serif) or should it match Vector's header ("Linux Libertine",Georgia,Times,serif)?

SamanthaNguyen added a comment.EditedAug 18 2016, 4:50 AM

I personally disagree with the order of the font stacking, but I'd go with a sans-serif font stack. Here's a little comparison for these based on websafe compatibility across operating systems:

font-family: Arial, "Helvetica Neue", "Helvetica", sans-serif;

How about this one above? :D

MtMNC added a comment.Sep 3 2016, 4:29 AM

Oh yeah that'd be fine. That stack was based on the one planned for the MediaWiki typography refresh, but in the end it wasn't used and plain old sans-serif was used instead.

SamanthaNguyen removed SamanthaNguyen as the assignee of this task.Jun 30 2018, 8:50 PM
SamanthaNguyen removed a subscriber: SamanthaNguyen.

Would it not make sense to ship the skin with a simple font-family: sans-serif and not worry about different font face compatibility across platforms? That leaves font choice entirely up to the end user which could be a good or a bad thing.