New theme for 3.next -- Twenty Eleven

[matt]

It's been a few years since we did this (#9015) but let's track the effort for the Twenty Eleven theme, hopefully making 3.2, here.

Main goals besides what we've already done in Twenty Ten:

• To be different from Twenty Ten, aesthetically.
• Is a good showcase of WP's headline features.
• Clean, fast to load, and with best-practice markup.

Nice to have, but optional, improvements:

• Ability to have random rotating headers. (Core improvement to custom header functionality, see #17240.)
• Color and layout options.
• More post formats. (Currently supports Asides, Links, and Galleries.)
• CMS-style slider home page option.

Some people will prefer the design of Twenty Ten, which is still excellent, over Twenty Eleven, but that's okay. We'll have something new next year.

Fix wrong html5.js path in header.php

Remove excessive whitespace

Remove excessive whitespace and standardise on \r\n

Make showcase.php query usage more efficient

Cross-referencing the commit:

matt in [17669]

Importing Duster theme, first pass at a candidate for twentyeleven theme.

Nice to have, but optional, improvements it'd be nice to have:

• Ability to have random rotating headers. (Core improvement to custom header functionality.)
• Color and layout options.
• More post formats. (Currently supporst Asides, Links, and Galleries.)
• CMS-style slider home page option.

Welcome, TwentyEleven n?\195?\169e Duster. :) Track at #17198.

Line endings should be svn:eol-style native, so \r\n or similar shouldn't matter. We should make the text files have Windows-style endings though, if they don't already.

(In [17670]) Set svn:eol-style on twentyeleven. See #17198

Replying to matt:

Line endings should be svn:eol-style native, so \r\n or similar shouldn't matter. We should make the text files have Windows-style endings though, if they don't already.

I set svn:eol-style on the files - I suspect you may want to change it from native on readme and license based on this comment?

(In [17671]) Fix html5 js link. See #17198 props Jayjdk

(In [17672]) Provide more arguments to the widgets on the 404 page so as to avoid notices. See #17198

I submitted this patch which has been picked up for 3.2 which should fix the notice issues in TwentyEleven: #16761

Replying to dd32:

Nice to have, but optional, improvements it'd be nice to have:

• CMS-style slider home page option.

What exactly are you looking for here? Something like on ​http://www.fiftyandfifty.org/ or like ​http://xavisys.com or ???

Additional conditional IDs for the html element

17672.html-id.diff adds conditional ids for IE6 and IE8 for users who will be using Twenty Eleven as a parent theme and may have use for those ids (an id for IE7 was already present in Duster).

showcase.php cleanup, 2nd pass

17198.showcase.2.diff adds full loop functionality back to the $featured query since we can't rely on sticky posts being available (may be trashed) and ensures all loop actions are fired correctly, while avoiding invoking it at all when no stickies are set.

Also makes better use of $feature_class and uses the native current post counter in the $recent query.

iandstewart, 3.2 wil drop IE6 support, I think 2011 should drop it too.

3.2 is marked as EOL for IE6 (for the admin), however themes (front end) should still support it so they have best compatibility. There are still people that are stuck in IE6. For them the admin would have limited functionality but the front end site should work.

Support for Status and Quote Formats

17672.status-quote-formats.diff adds support for Status and Quote format display, excludes those formats from the Showcase Recent Posts, and adds them to the posts included in the custom "Ephemera" widget. It also adds CSS section headers for each Format and the 404 styles in style.css.

Allows the /twentyeleven/ directory to be added, for anyone using the WordPress Beta Tester plugin, and updating nightly.

I was hoping the above patch would solve the /twentyeleven/ directory being included in any updates used from within your dashboard, if you used say the WordPress Beta Tester plugin. Turns out I already had the theme there, after I uploaded it myself. But I'm finding that /twentyeleven/ isn't included when I went from 3.1.1 to 3.2-bleeding, so I can't try it out online!

I was hoping the above patch would solve the /twentyeleven/ directory being included

I'll take care of that tomorrow

Replying to dd32:

I was hoping the above patch would solve the /twentyeleven/ directory being included

I'll take care of that tomorrow

Cool, thanks. Obviously a little more work needed than adding a line of code? ;)

Adding that line should've done it. However, it should be fine as '3.2', and it also needs to be set in the file -during- the 3.1.x -> 3.2 update, ie. within the update zip. There may be other things at play here though, so I'll check it during testing.

Minor style fixes (overflow) for international blogs and replacing em dash with the proper CSS value for the entity.

Replying to dd32:

• Ability to have random rotating headers. (Core improvement to custom header functionality.)

Added #17240 to track work on new random image rotation feature. This should be available to all themes (not just the new default theme).

Added #17242 to track work for allowing custom height for header images.

(In [17714]) Twenty Eleven: strip trailing spaces, props kawauso - see #17198

(In [17717]) Twenty Eleven: add support for Status and Quote formats, props iandstewart - see #17198

(In [17718]) Twenty Eleven: add additional conditional IDs for the html element, props iandstewart - see #17198

(In [17719]) Twenty Eleven: minor style fixes (overflow) for international blogs and replacing em dash with the proper CSS value for the entity. Props matveb, see #17198

(In [17720]) Twenty Eleven: move widgets.php into /inc - see #17198

(In [17721]) Twenty Eleven: functions.php cleanup and introduction of theme options; see #17198

• Cleanup functions.php, adding comments and function_exists() checks following Twenty Ten's example
• Theme option for choosing an alternate (dark) color scheme. It currently only loads a placeholder CSS file with dark styles to follow.
• Theme option for selecting a link color that loads an internal style block for resetting link colors. An updated style.css will follow to take advantage of this.
• Theme options for selecting an alternate layout. Adds a class to the body element. An updated style.css will follow to take advantage of this.

Can we set a default case for the switch statement in the twentyeleven_comment() function? It would be as simple as moving the first check down to the bottom and changing the case to:

default :

Currently, this function handles the comment, trackback, and pingback comment types. All other comment types are skipped. By default, WordPress core functionality handles custom comment types just fine.

This is also an issue in the TwentyTen theme and now many, many themes being submitted to the theme repository because so many theme authors just copy/paste code from the default WordPress theme.

Replying to greenshady:

Can we set a default case for the switch statement in the twentyeleven_comment() function?

Makes sense to me, plus it's a good practice in programming in general to have a default case for switch statements. Patch looks good, thanks Justin.

(In [17722]) Twenty Eleven: set default case for switch statement in the twentyeleven_comment(), props greenshady - see #17198

(In [17723]) Twenty Eleven: fix spacing and add a few missing esc_attr() calls in widgets.php - see #17198

Related to Twenty Eleven (but should work with any theme), I added a patch for #17240 that will load a random image from the theme's registered header images.

Note: Twenty Eleven only has one header image right now (more coming soon), so test it out with Twenty Ten.