WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 5 weeks ago

#24858 closed task (blessed) (fixed)

Twenty Fourteen

Reported by: lancewillett Owned by:
Milestone: 3.8 Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords:
Focuses: Cc:
PR Number:

Description (last modified by lancewillett)

New default theme for WordPress is a magazine theme with clean, responsive design that highlights featured content prominently on the home page.

Demo: http://twentyfourteendemo.wordpress.com/

This is slated for 3.8. Development will occur in trunk for the theme, and in plugins for the nice-to-have features.

Nice-to-have improvements include:

Attachments (5)

24858.diff (91.0 KB) - added by obenland 6 years ago.
First pass of updating templates to 2013 standards
24858.1.diff (30.6 KB) - added by obenland 6 years ago.
24858.2.diff (41.9 KB) - added by obenland 6 years ago.
24858.3.diff (41.3 KB) - added by obenland 6 years ago.
24858.4.diff (48.3 KB) - added by obenland 6 years ago.

Download all attachments as: .zip

Change History (59)

#1 @lancewillett
6 years ago

  • Description modified (diff)

#2 @ocean90
6 years ago

  • Cc ocean90 added

#3 @jjeaton
6 years ago

  • Cc jjeaton added

#4 @sabreuse
6 years ago

  • Cc sabreuse added

#5 @obenland
6 years ago

  • Cc obenland added

#6 @lancewillett
6 years ago

  • Description modified (diff)

#7 @markmcwilliams
6 years ago

  • Cc mark@… added

#8 follow-up: @lancewillett
6 years ago

Noting a few things that will need work right away.

These will need new tickets:

  • Post format queries need optimization on front page.
  • Change to just one footer widget area and use Masonry.
  • Update codebase to match Twenty Thirteen more (404 page, no content shouldn't be articles, permalinks on title, markup updates, other cleanup, etc).
  • Update comment template and search form to 3.6 compat.
  • Re-look at content filters.
  • Improve image.php a bit. Make it simpler.
  • Review "all the cool cats" categories functionality.

#9 @lancewillett
6 years ago

In 24832:

Importing the Further theme, first pass at the new default theme for 2014.

A magazine theme with clean, responsive design focused on highlighting featured content prominently on home page.

This is slated for 3.8. Development will occur in trunk for the theme, and in plugins for the nice-to-have features.

Nice-to-have improvements include:

  • Add a Contributors page template to highlight authors.
  • Easy-to-manage featured content.
  • Add support for an Authors widget to highlight authors.

Welcome, Twenty Fourteen né Further. Props iamtakashi, see #24858.

#10 @sumobi
6 years ago

  • Cc sumobi added

#11 @MikeHansenMe
6 years ago

  • Cc mdhansen@… added

#12 @chellycat
6 years ago

  • Cc chellycat added

#13 @Jayjdk
6 years ago

  • Cc kontakt@… added

#14 @philiparthurmoore
6 years ago

  • Cc philip@… added

#15 @sunnyratilal
6 years ago

  • Cc sunny@… added

#16 @rdall
6 years ago

  • Cc robert@… added

#17 @jeherve
6 years ago

  • Cc jeremy+wp@… added

#18 @Frank Klein
6 years ago

  • Cc contact@… added

#19 @celloexpressions
6 years ago

  • Cc info@… added

#20 @kwight
6 years ago

  • Cc kwight@… added

#21 @alex-ye
6 years ago

  • Cc nashwan.doaqan@… added

#22 @colorful tones
6 years ago

  • Cc damonacook@… added

#23 @wonderboymusic
6 years ago

  • Type changed from defect (bug) to task (blessed)

#24 @melchoyce
6 years ago

  • Cc melissachoyce@… added

#25 @DrewAPicture
6 years ago

  • Cc xoodrew@… added

#26 @iamtakashi
6 years ago

  • Cc takashi@… added

#27 @emiluzelac
6 years ago

  • Cc emil@… added

#28 in reply to: ↑ description @cyberchimps
6 years ago

  • Cc cyberchimps added

@obenland
6 years ago

First pass of updating templates to 2013 standards

#29 @taupecat
6 years ago

  • Cc tracy@… added

#30 @jazzs3quence
6 years ago

  • Cc jazzs3quence added

#31 in reply to: ↑ description @valeriosza
6 years ago

It would be interesting to have a control system for news of home, a way to drag and position the place.

Replying to lancewillett:

New default theme for WordPress is a magazine theme with clean, responsive design that highlights featured content prominently on the home page.

This is slated for 3.8. Development will occur in trunk.

Nice to have features:

#32 @valeriosza
6 years ago

  • Cc valeriosza@… added

#33 @lancewillett
6 years ago

  • Description modified (diff)

#34 @paolal
6 years ago

  • Cc paolo@… added

#35 @swissspidy
6 years ago

  • Cc hello@… added

#36 in reply to: ↑ 8 @wpfo
6 years ago

Replying to lancewillett:

  • Change to just one footer widget area and use Masonry.

Please don't do that.
Very often it is desired that you know in which column comes which widget.
Or you can achieve this with Masonry?

#37 follow-up: @emiluzelac
6 years ago

Should we remove all IE7 stuff from style.css, since the Theme isn't working on IE7 anyways? not sure if that's the plan and if it is all * hacks are no longer needed as well as:

{clip: rect(1px 1px 1px 1px); /* IE6, IE7 */}

Also, will the Theme support IE8 or this will be IE9+. Just asking what to test for that's all. Currently the Theme does not behave properly in IE7 nor IE8 :)

Last question (more info only) Twenty Twelve uses rem, Twenty Thirteen does not and rem is back in for Twenty Fourteen, can someone shed some light please.

Thanks!

#38 in reply to: ↑ 37 @taupecat
6 years ago

Replying to emiluzelac:

Should we remove all IE7 stuff from style.css, since the Theme isn't working on IE7 anyways? not sure if that's the plan and if it is all * hacks are no longer needed as well as:

{clip: rect(1px 1px 1px 1px); /* IE6, IE7 */}

Also, will the Theme support IE8 or this will be IE9+. Just asking what to test for that's all. Currently the Theme does not behave properly in IE7 nor IE8 :)

Last question (more info only) Twenty Twelve uses rem, Twenty Thirteen does not and rem is back in for Twenty Fourteen, can someone shed some light please.

Thanks!

I had a convo with @nacin on #wordpress-dev last week about IE7 support. His theory was so long as it didn't return a blank page, then it was fine. As a themer, I don't think I necessarily agree with that opinion. But if WordPress itself aims to continue supporting IE7, then I think the theme should too.

On the flip side, @nacin said that IE7 fixes constituted about an hour per release cycle. Theming is a totally different animal. The effort that goes into making a theme IE7 compatible (not necessarily the same, mind you, but at least compatible) is considerably more than an hour.

I think we need Lance's decision on whether Twenty Fourteen is going to support IE7 and by how much. IE8, however, I think should be as fully supported as possible, since there are still a large number of Windows installations throughout the world limited to IE8 based on the fact that Windows XP still commands a high market share.

Of course, by support, that could mean serving IE<9 users a simple print stylesheet. ;-)

As for the rems issue, where to use rems vs. ems is a lot more subtle a distinction than I think most people give its full due. There's a place for both in a theme. However, if we're going to pick one OR the other, I'd say go with rems since in a large project, they provide the least guesswork as to what basis the font is being measured against. But again, you have IE issues, and wherever you use a rem you need to have a pixel fallback in order to support IE<9.

That's done easily enough via the use of a CSS preprocessor and mixins, but that's a whole other comment! :-D

#39 @emiluzelac
6 years ago

Thanks for the details :)

Can we get an official word on browser-compatibility, or it's too early for that?

#40 @Jayjdk
6 years ago

There's office hours for Twenty Fourteen on Tuesday at 17 UTC. http://make.wordpress.org/core/2013/08/09/2014-theme-project/

#42 @jcastaneda
6 years ago

  • Cc jomcastaneda@… added

#43 @karmatosed
6 years ago

  • Cc karmatosed@… added

#44 @cainm
6 years ago

  • Cc cainm added

#45 @lancewillett
6 years ago

@emiluzelac and @taupecat Please make a new Trac ticket for IE7 discussion and changes.

#46 @lancewillett
6 years ago

In 25021:

Twenty Fourteen: first pass at matching code standards achieved with Twenty Thirteen development. See #24858, props obenland.

#47 @lancewillett
6 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Let's open new tickets for new issues. Closing this one.

@obenland
6 years ago

@obenland
6 years ago

@obenland
6 years ago

#48 @lancewillett
6 years ago

In 25023:

Twenty Fourteen: second pass at matching code standards achieved with Twenty Thirteen development. See #24858, props obenland.

@obenland
6 years ago

#49 @lancewillett
6 years ago

In 25060:

Twenty Fourteen: change IDs to classes in markup and CSS selectors. Props obenland, see #24858.

#50 follow-up: @dfavor
6 years ago

Unsure where to place this request... so doing so here.

Testing Twenty Fourteen (theme part) is straight forward...

cd wp-content/themes/
svn co http://core.svn.wordpress.org/trunk/wp-content/themes/twentyfourteen/

And how to download + test all associated plugins is more challenging to understand.

If there is someplace all associated plugin names are gathered... plus an installation procedure for testers... pass along the link.

Thanks.

#51 @dfavor
6 years ago

  • Cc david@… added

#52 in reply to: ↑ 50 @SergeyBiryukov
6 years ago

Replying to dfavor:

And how to download + test all associated plugins is more challenging to understand.

Twenty Fourteen does not require any plugins, nor do any other of the bundled themes.

#53 @dfavor
6 years ago

I'm clear Twenty Fourteen "requires" no plugins.

Maybe a better way to say this is, "What's the best way to find all Twenty Fourteen related plugins?"

Maybe http://DavidFavor.com/twenty-fourteen-tickets is the best way.

This ticket was mentioned in Slack in #core by kraft. View the logs.


5 weeks ago

Note: See TracTickets for help on using tickets.