Twenty Fourteen: Add Site Logo Support

[celloexpressions]

After a bit of thought, I came up with what I think is a fairly elegant way to incorporate a site logo into Twenty Fourteen. This is much nicer than the current approach of shoving a logo into the header image option that I've seen in the wild.

This particular approach can work in addition to or in place of the site title and tagline. If the title and tagline aren't displayed, we may want to consider adding the title into the fixed header as the user scrolls down the page. There are of course other ways to do this, so we should consider some different options before coming to a final decision. The patch doesn't look at handling on mobile yet - it may need to be hidden.

[celloexpressions]

First pass.

[celloexpressions]

Example with logo without text and site title/tagline shown.

[celloexpressions]

Example logo with text and site title & tagline shown.

[celloexpressions]

Example with header text hidden.

[celloexpressions]

I attached some examples. Note that the USC ASCE logo is square and intentionally has top padding within the image.

[karmatosed]

@iamtakashi looping you in here to so we can get your feedback before this goes in.

[iamtakashi]

If this is up to me, I'd say not to add support to Twenty Fourteen. The theme obviously wasn't designed for a site logo at that time and there is no good place to add a logo in this theme.

Like Twenty Thirteen doesn't support background color, if the design doesn't make sense with the feature, we don't need to add it just for the sake of it.

[marioi]

I got the following error when applying your first pass:

Fatal error: Call to undefined function the_site_logo() in /home/labelwcp/public_html/wp-content/themes/twentyfourteen/sidebar.php on line 18

I like this initiative as most brands require logos on their websites. Twentyfourteen is a theme I'm considering implementing for a client, but if I can't get the logo in, I'll have to install another.

[celloexpressions]

I would say that Twenty Thirteen, for example, definitely wouldn't make sense for a logo. But for Twenty Fourteen, because it's designed to be used for more content-heavy sites, I think a lot of those sites would have logos. I also feel like the top of the left sidebar is an appropriate place for a logo, not sure about mobile. As I said before, a lot of sites are using the custom header for a logo, which doesn't work well at all. Can we give them a better option?

@marioi are you running the latest version of trunk? Sounds like your version might be missing the initial logos commit.

[marioi]

Hi @celloexpressions, I haven't done anything with trunk (as a WP dev newbie, I'll research a bit more into this), seems I missed something. It's just a standard WP 4.4.2 installation in which I've added the code (will be using a child theme going forward). I'm fairly new with WP dev but becoming ever more involved with going beyond to tweaking the PHP.

[iamtakashi]

Replying to celloexpressions:

In my opinion, the left sidebar isn't a good place for a logo. The sidebar won't be there until 1008px wide viewport and the fact makes a logo need to be hidden for small screens which is bad if you choose to hide your site title in favour of your logo. Of course, there are things to solve the issue with complicated logics but that would simply confuse users.

The only place, if we must to add, is the header where the site title is. If a logo is thin rectangle shape could work but I'd say that's too limiting when we offer an option like this. And it's worth to mention that the sticky header will stop work if the header is more than 48px tall.

I wouldn't argue if the type of sites that uses Twenty Fourteen would or wouldn't likely have a logo. But what I can say is that the theme wasn't designed to have a logo that can be all sorts of sizes and shapes. Therefore I'd suggest to not to add the support in this theme.

[kirasong]

Per conversation in dev meeting last week, the consensus was to let the original designer decide what themes are appropriate for Theme Logo Support.

As such, as this is @iamtakashi, and he's made clear his decision, suggesting wontfix here.

For context, see the discussion previously linked: ​https://wordpress.slack.com/archives/core/p1456953047003074

[ocean90]

Agreed.