Twenty Thirteen project update

The Twenty Thirteen team jumped into 3.6 with two two first office hours this week; things are off to a great start. We’re meeting in #wordpress-dev IRC on Tuesdays and Thursdays at 17 UTC.

Who we are

(These are usernames.)

  • Leads: lancewillett and obenland
  • Contributors joining us for office hours this week: johnbillion kwight clakeb karmatosed sabreuse taupecat jorbin bpetty MikeHansenMe georgestephanis jayjdk nacin

Many other folks already contributed patches and tickets, thank you.

What we’re working on

Tuesday we started by dividing things up a bit:

  • Color contrast and general accessibility (sabreuse and jorbin)
  • Mobile behavior, the navbar and menu need some work (obenland, johnbillion, and karmatosed)
  • Device testing (karmatosed)
  • General bug reporting and patches (everyone)

We also looked at open tickets for Twenty Thirteen.

Thursday we had a more open discussion style. Based on people grabbing tasks I’ve added a “point person” in bold after each — if you want to jump in look for “Unassigned” here and drop a comment or ping me in IRC.

  • Post Formats functionality: a game plan for tying Twenty Thirteen into new API, working with Helen and Post Formats team. (Point person: lancewillett)
  • Browser support: we’re going to focus on basic usability for IE8 and IE7, doesn’t need to be pixel perfect. Tasks include: remove IE6 hacks (notes) and move IE7 and IE8 hacks to ie.css. (Unassigned)
  • Auditing all our vendor prefixes: #23568 (Point person: jayjdk)
  • Back compat will be different for Twenty Thirteen. We’re going to be 3.6+ only for theme features. Goal for older versions is to be error-free, but they do not need to be feature complete. To make this work, we need fallbacks and checks in the API. (Point people: nacin, bpetty)
  • Checking multisite styles, per notes in #22179 (Point person: kwight)

Two bigger issues we discussed that need a bit more explanation.

Sidebar not clearing the footer: This was a big one that everyone has mentioned, see #23557. The layout looks broken when the sidebar is longer than the content area. The footer is below the content, but the sidebar keeps going and due to the CSS techniques to make the color bands 100% wide the footer can’t clear the content. The best idea we’ve had so far is to swap the two sidebars: putting footer sidebar as primary, and explaining why in the description. We’ll make the right-side sidebar secondary — and we’re also considering removing it entirely. (Point person: obenland)

Improving the fixed navbar: This was suggested as a change: include the menu in the fixed navbar for small screens instead of the title and search. Other suggestions included: 1) remove the fixed navbar completely (everywhere in the theme) 2) put the menu in the navbar for all screen sizes and 3) keep menu for small screens but remove search and title. We’ll need to discuss this more before taking action. (Point person: obenland)

Non-theme tickets that relate to Twenty Thirteen

  • HTML5 markup support in core: #20088 #15080 and #15081 (Point person: georgestephanis)
  • Standard theme hooks: #21506 (Unassigned)

Want to get involved?

Join us in IRC during office hours and we can get you started on a ticket or task.

IRC logs: Tue Feb 19 2013 | Thu Feb 21 2013

#3-6, #bundled-theme, #theme, #twentythirteen