#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: |
Description (last modified by )
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:
- #24863: Add a Contributors page template to highlight authors (see http://www.aeonmagazine.com/contributors/ for example).
- #24857: Easy-to-manage featured content (as a plugin first).
- #24856: Add support for an Authors widget to highlight authors: (as a plugin first).
Attachments (5)
Change History (59)
#28
in reply to:
↑ description
@
11 years ago
- Cc cyberchimps added
#31
in reply to:
↑ description
@
11 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:
- #24863: Add a Contributors page template to highlight authors (see http://www.aeonmagazine.com/contributors/ for example).
- #24857: Easy-to-manage featured content (as a plugin first).
- #24856: Add support for an Authors widget to highlight authors: (as a plugin first).
#36
in reply to:
↑ 8
@
11 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:
↓ 38
@
11 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
@
11 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
@
11 years ago
Thanks for the details :)
Can we get an official word on browser-compatibility, or it's too early for that?
#40
@
11 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/
#45
@
11 years ago
@emiluzelac and @taupecat Please make a new Trac ticket for IE7 discussion and changes.
#47
@
11 years ago
- Resolution set to fixed
- Status changed from new to closed
Let's open new tickets for new issues. Closing this one.
#50
follow-up:
↓ 52
@
11 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.
#52
in reply to:
↑ 50
@
11 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
@
11 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.
Noting a few things that will need work right away.
These will need new tickets: