[wp-meta] [Making WordPress.org] #334: Improve the Coming Soon design for new WordCamp sites

[Making WordPress.org]

#334: Improve the Coming Soon design for new WordCamp sites
-------------------------------------+----------------------
 Reporter:  iandunn                  |       Owner:  iandunn
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  fixed
 Keywords:  has-screenshots          |
-------------------------------------+----------------------

Comment (by melchoyce):

 Replying to [comment:23 iandunn]:
 > Doh, my bad. I replaced Open Sans with the new 4.6 font stack and missed
 the height/weight issues. We can definitely fix those, or maybe revert to
 Open Sans if you feel like that's best.
 >
 > The reason I switched was to avoid the external dependency and extra
 HTTP request, and also to avoid the potential for leaking sensitive
 information via referrer headers (and all the other issues with Open Sans:
 [https://core.trac.wordpress.org/ticket/26072 1],
 [https://make.wordpress.org/core/2013/11/11/open-sans-bundling-vs-linking/
 2]). Leaking info is admittedly unlikely in this context, but it still
 makes me leery when combined with everything else.
 >
 > It also sounds like the new stack has
 [https://make.wordpress.org/core/2016/07/07/native-fonts-in-4-6/ several
 advantages] over Open Sans, like instant loading, better language support,
 and consistency with the device's native UI.
 >
 > What are your thoughts on all that?

 I think in this case, the site is small enough that an extra HTTP request
 isn't going to be a big deal. Since already using Open Sans on
 WordPress.org, I'm not really worried about the security aspect. However,
 if you are worried, we can host the files internally rather than linking
 to Google's versions.

 The new core font stack was designed to address the needs of an
 application, not websites. We made the explicit decision to use the native
 stack for UI elements, and continue using serif fonts for content. Most of
 the fonts within the font stack were designed for things like labels,
 menus, etc., and don't work as well for the kind of content you'd find in
 websites themselves — large titles, paragraphs, etc. You can especially
 see this in OSX's San Francisco, which was designed with ample letter-
 spacing that makes it ideal for applications but difficult for reading
 longer lines of text.

 As far as I know, we haven't made a decision to stop using Open Sans for
 our community materials. If we do (and we have been talking about it), we
 will likely choose a different sans-serif webfont (not native UI font).
 However, until we make that decision, we should use Open Sans here to
 provide an easier to read, more consistent experience.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/334#comment:24>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org