Add theme support system for themes wanting to utilize Typecase

[chriswallace]

One of the major feature requests we have seen is the ability to register theme support for certain selectors as groups that can be modified with the Typecase.

Requirements for this feature:

1. When add_theme_support( 'typecase' ) exists, accept an array of selectors as the second argument. Need to decide on the structure for this array to implement a standard for theme developers.
2. On theme activation, save the font selections in the typecase option for fonts/selectors.
3. Within the Customizer, add settings for selector groups for each font and ability to search other fonts and swap them for certain selector groups.
4. Add a button to Typecase that allows the user to "reset fonts for current theme" in case they've modified or deleted things and want to restore.

[ataylorme]

@chriswallace pushed up https://github.com/UpThemes/Typecase/tree/issue-66 with initial theme support and Customizer integration

This does not address 2 or 4 yet - wanted to get your thoughts.

[ataylorme]

@chriswallace saw your update to display a message in Customizer if no fonts are in the Typecase collection.

I added some error checking so if a font is set for a theme location and the font gets removed from the Typecase collection it is reverted to the default.

I also consolidated up some duplicate code into class properties and cleaned up some formatting.

See commit 805a8d0 for details

[ataylorme]

@chriswallace per our discussion Friday I added theme support for the default themes:

• twentyten
• twentyeleven
• twentytwelve
• twentythirteen
• twentyfourteen

TwentyFifteen can't be activated until 4.1 is released, which is scheduled for 12/10/14. I will add support for twentyfifteen and test after the 4.1 release.

See commit a5557b2 for details

[calebsylvest]

I setup a clean install and tested Typecase with the default WordPress themes (minus TwentyFifteen). The good news is that they are all working just fine, so initially, we are good to go. However, I do have a number of thoughts and suggestions to improve the usability of Typecase and make it more useful. I'm going to go ahead and write out some of my thoughts here and we can chat about them later.

Problem: We can allow people to add custom fonts to the site, basically to design it how they like. But after choosing custom fonts the only area that is actually affected is the blog roll (everything in the green box) while everything else on the site is left in its original state. This is a good first start, but comes off as very disjointed.

Suggestion: We need a way to better style the full site with custom type, instead of one subset of the site. What I'm thinking is simplify the custom options, and apply to the body which will better style the full site.

Here's an example of what I mean, simplify the options initially, and provided an extended set of selectors. I'm also tweaking the names of the fields.

Body Copy. Apply to the body selector so the full site is affected by the custom font. This definitely works on the default WP themes. Could be trickier with other themes (to overwrite styles further down the line, unless we use !important).
Headings (H1-H6). Apply to all heading elements, not just inside of Articles. That way it will apply to the site title, widget titles, pages titles, etc.

Advanced options >. Have an expander to present more options for more minute control.
Article Title. Changing the name of this field to make more sense. But applies only to the title of a Post.
Block Quote. applies to block quote
List Items (Bulleted & Numbered). applies to list items.
Any other very specific options we want to add should be here.

[ataylorme]

@calebsylvest Please see commit de74f67

Here is what changed in a nutshell

• Added Twenty Fifteen Theme Support
• Updated all theme font locations to your suggestions
• Added checkbox for "Show Advanced Theme Font Locations" to customizer

If you can update locally and re-test I would appreciate it.

[ataylorme]

@chriswallace and @calebsylvest please see commit 523e9e5

I switched to using customizer panels to break the "advanced" fields into sub sections (content, sidebar, etc). for Twenty Fifteen and Twenty Fourteen.

The "simple" fields are body copy and headings (h1-h6). These apply site wide (not just content).

The "advanced" fields give more control to items like widget titles, site title, blockquote, etc.

Wanted to get your feedback and testing on the update.

[chriswallace]

Seems like a good use case for panels. I'm picking up my computer from
apple tomorrow and will try to test everything thoroughly then.

On Tuesday, December 16, 2014, Andrew Taylor notifications@github.com
wrote:

@chriswallace https://github.com/chriswallace and @calebsylvest
https://github.com/calebsylvest please see commit 084d098
084d098

I switched to using customizer panels to break the "advanced" fields into
sub sections (content, sidebar, etc). for Twenty Fifteen and Twenty
Fourteen.

The "simple" fields are body copy and headings (h1-h6). These apply site
wide (not just content).

[image: screen shot 2014-12-16 at 9 30 20 pm]
https://cloud.githubusercontent.com/assets/2133004/5466165/d7d3ad3a-856a-11e4-8291-34bed615bc08.png

The "advanced" fields give more control to items like widget titles, site
title, blockquote, etc.

[image: screen shot 2014-12-16 at 9 31 47 pm]
https://cloud.githubusercontent.com/assets/2133004/5466178/11f8359e-856b-11e4-9c59-bf2d9e05d5ef.png

Wanted to get your feedback and testing on the update.

—
Reply to this email directly or view it on GitHub
#66 (comment).

Chris Wallace
Principal Creative // Lift

mobile 314-406-9109
skype chriswallace7
email/gtalk chris@liftux.com

http://liftux.com

[ataylorme]

@chriswallace sounds good. I need to test with 4.0 (and older). I installed 4.1 RC to test Twenty Fifteen.

There are a lot of changes to customizer in 4.1

[ataylorme]

Cleaned up customizer.js in dfdeff8

Going to start testing < 4.1 now

[ataylorme]

Added 4.0 support to customizer in commit 3ef7bcf

[chriswallace]

Cool, feel free to push to wordpress.org, I added you as a committee to the
project.

On Wednesday, December 17, 2014, Andrew Taylor notifications@github.com
wrote:

Added 4.0 support to customizer in commit 3ef7bcf
3ef7bcf

—
Reply to this email directly or view it on GitHub
#66 (comment).

Chris Wallace
Principal Creative // Lift

mobile 314-406-9109
skype chriswallace7
email/gtalk chris@liftux.com

http://liftux.com

[ataylorme]

@chriswallace I would like to have someone else test if possible. I want to see what you guys think of the panels/layout.

If we are good to go I can add the new layout to the older default themes, Twenty Thirteen and below.

[ataylorme]

I've looked at about a dozen Google Font plugins and haven't been able to find anything with a decent interface - nothing comes close to the Google Fonts page itself

We can use some data from the API such as variants (font weights, "regular", "italic", etc) and category ("sans-serif", "serif", etc.) to help users narrow down font selection

There are also some sort options such as date added, popularity, etc. See the developer docs for details.

I am thinking we can add some of those filters in a row above the search box.

@chriswallace since we moved towards the customizer is the "Live Editor" feature still necessary?

[chriswallace]

I think it does work well as a bridge to a Customizer-based solution, but I don't know what that is going to look like just yet.