Download & Extend
@font-your-face » Issues

[META] Simplify/reduce which functionality is available on which screens

Posted by sreynen on April 24, 2012 at 3:15am
Project:@font-your-face
Version:8.x-3.x-dev
Component:User interface
Category:task
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

Having something to add? Edit this!

Current functionality distribution:

Configuration screen

  • Add provider account info (username, keys, etc.)
  • Import fonts
  • Change logging options

Browse screen

  • Search fonts
  • Limited font preview
  • "Enable" fonts

Edit screen

  • Read font details (license, designer, etc.)
  • Full font preview
  • Set CSS selector
  • "Enable" fonts
  • See enabled fonts

Apply screen

  • See enabled fonts
  • Set CSS selector
  • See font family for theme CSS
  • See theme .info loading code

Better functionality distribution:

Configuration screen

Browse screen

  • Search fonts
  • Limited font preview
  • "Enable" fonts
  • Add provider account info (username, keys, etc.)
  • Import fonts
  • Change logging options
  • See theme .info loading code
  • See enabled fonts

Edit screen

  • Read font details (license, designer, etc.)
  • Full font preview
  • Set CSS selector
  • "Enable" fonts
  • See font family for theme CSS

Apply screen

Login or register to post comments

Comments

#1

Posted by sreynen on April 24, 2012 at 3:19am

As a first guess at how this should work, I removed both the apply screen and the configuration screen, and moved the functionality to the other 2 screens. This would make the browse interface more complicated, and I haven't even started thinking about what that would look like. I'd like to see some alternatives first.

#2

Posted by BTMash on April 24, 2012 at 3:39am

@sreynen, while I haven't thought this through, I was working on the FOUT issue to see what fonts.com does and found http://webfonts.fonts.com/en-us/videotutorial which, if you jump to ~ the 1:30 mark, you can see how webfont.font.com lays out their screens (and selectors). It might be worth looking at for ideas.

#3

Posted by Drave Robber on July 19, 2012 at 8:47am

Not exactly reduction or simplification, but still related: #1692468: Improve UI for local fonts to reduce confusion

#4

Posted by sreynen on July 29, 2012 at 11:25pm

While thinking about #1692468: Improve UI for local fonts to reduce confusion, I had some more thoughts on this, which I added to a new issue: #1704820: Remove "Browse all fonts" tab and move each provider tab up a level

#5

Posted by BarisW on October 4, 2012 at 9:43pm

I spoke with Bojhan about the FYF module and he did a quick review of it. These are his most important remarks:

  • Merge appearance/fontyourface and admin/appearance/fontyourface/browse/*
  • Showing an error message just after you've enabled the module is not so nice. Better is adding an 'add fonts' link in the table which brings you to the import page.
  • Sort the fonts on enabled first, so you see immediately which fonts are enabled.
  • He wasn't able to enable a font without my help (auch).
  • Remove some of the unneeded fieldset in the configuration interface.
  • Shorten the buttons texts (Save, Cancel, Delete)
  • We might improve the initial experience by just enabling something out-of-the-box (eg a Google Font).
  • I miss an All tab on the fonts overview

Lots of info, but summarized this is what he think is most important:

  1. Move the interface to /config (not Appearance)
  2. Make the Browse pages a lot cleaner
  3. Improve the out-of-the-box workflow, so enabling the first font is as easy as possible.
  4. Clean the individual config screens.

#6

Posted by sreynen on December 8, 2012 at 9:30pm
Version:7.x-2.x-dev» 8.x-3.x-dev

I'm moving this to D8, where the interface doesn't exist at all yet. Starting from scratch should make it easier to make big changes, and then we can backport them to D7.

#7

Posted by Drave Robber on December 9, 2012 at 4:27am

What would it mean for minor issues like #1692468: Improve UI for local fonts to reduce confusion - postponed until there's something to backport?

#8

Posted by sreynen on December 11, 2012 at 2:51am

What would it mean for minor issues ...

Hmm, good question. I think we should take that on a case-by-case basis. If it seems simple enough to implement in D7 we can go ahead and do it, but any more substantial revisions should probably happen first in D8. #1692468: Improve UI for local fonts to reduce confusion started simple, but then I made it more complicated. Now that we have a D8 version started, I think we should probably just do the simple fix for D7, so I moved it to RTBC.