We’re getting very close This week focusing on…

We’re getting very close.

This week focusing on RTL again, especially concerning :before and :after and Genericon placement, see #24287. Turns out we’ll need flipped versions of lots of the glyphs—which Joen is now working on. After Joen completes the Genericons font updates are ready we’ll sync them into Twenty Thirteen.

Next is another quick pass at editor styles, including RTL support there.

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

Twenty Thirteen project update, April 23, 2013

The focus for Twenty Thirteen right now test, test, and test. Polish, polish, and polish. The IEs, RTL, testing with lots of popular plugins. Getting things working smoothly with the new core post formats functionality.

Priorities

  • Launch on WordPress.com: currently blocked by the pending final version of the post formats UI.
  • With core team: make a decision on how “structured-post-formats” should be used and declared (if at all) by the theme.
  • With core team: make a decision on fixed navbar—”stay or go.”
  • With Joen, making Quote style improvements.

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

We love testers We’d love more people to…

We love testers

We’d love more people to install Twenty Thirteen, with special emphasis on trying out all the new Post Format features.

Also, if you have access to Windows with various versions of Internet Explorer we especially need help testing out some IE8 and IE10 issues (see Trac list link below).

Priorities

  • Address open tickets in Trac, fix bugs and make improvements
  • More browser, device, RTL, and i18n testing
  • Post formats testing. For example, looking at the output from post_formats_compat(), making suggestions like Image should use wp_get_attachment_image() there for filters and correct core class attribute values in the resulting HTML.
  • Review and possibly refactor the js/functions.js JavaScript file, going to all procedural/functional or moving to a new architecture—the key is to be consistent with it within the file. We can also look at namespacing the events.
  • Ask Joen to do another design audit, checking versus his design vision for things like spacing, colors, and post formats.

Office hours

We’ll get back to office hours in #wordpress-dev IRC over the next few weeks, Tue and Thu at 17 UTC.

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

Twenty Thirteen project update, March 26, 2013

Our focus right now is on post formats integration, both structured (formats with post meta) and “normal” output for the other formats.

Priorities

  1. Work with Post Formats team to get the_video(), the_audio(), and the_image() functions into core, so we can avoid a ton of extra logic in Twenty Thirteen’s functions.php file to grab the first asset for a format. Making it easier for *any* theme to get the same data back and keep their template files simpler. Themes should not have to parse shortcodes or try to make something run through oEmded before display.
  2. Work with Post Formats team on post_formats_compat() functionality, improving Quote markup and filling in the gaps for other formats. Obenland is going to work on a patch for this.
  3. Image: we need clarification from 3.6 leads and Post Formats team on whether it is going to be structured or not (post meta) and it needs more work for the post-media functions (see 1 and 2 priorities above)
  4. Finalize each post format in Twenty Thirteen: what template HTML or PHP it needs, what it needs from core functionality to work correctly

By post format

Here’s a breakdown per format, per today’s discussion (IRC log).

  • Standard: good to go
  • Aside: we remove the title from the PHP template, added styling; non-structured
  • Chat: IHNIWIGOWTPF (see IRC log, hehe); non-structured
  • Gallery: we use a bit of PHP to remove default gallery styles, and we use a filter to change the image size to large on index view, then add a bit of CSS fanciness to change the first image to “bigger” size, 300×300 (single view is not changed other than to align the columns); non-structured
  • Link: structured, we use get_the_url() wrapped in our own fallback to output permalink if no URL is found
  • Image: right now it works OK without any changes, but the design calls for the image to be above the title, which means we need a way to pull out the first image, and have the_content() be output without that image; also filter content_width to 724 for this format (small issue with that reported in #23863). Seems like the best approach here is to use a custom image size to grab an exact 724 px wide image (unless it’s smaller that 724, in which case we grab the largest available). Ideal: a user uploads an image, adds it to the post content at exactly 724 from the Media editor, then the_image() outputs the exact HTML img tag + attributes.
  • Quote: structured; currently we rely on people using blockquote correctly in the editor, and style it with CSS; after Obenland’s patch to Quote markup (noted above in priority 2) we’ll add CSS support for the structured HTML markup, and leave in the basic styles in case someone uses post content anyway
  • Status: similar to Aside
  • Video: structured; we filter content_width to 724 to allow the video to be wider than the rest of the content area; needs the_video() to return the HTML output of first video and remove the same from the post content
  • Audio: structured, we’re leaning towards using the post format compat output instead of a custom structure in the theme; needs more testing but seems to be working OK as-is right now

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

Twenty Thirteen project update, March 19, 2013

We’re in great shape to get to beta. Here is what we’re working on right now.

Blocking older installs

Tracked in #23819 — since Twenty Thirteen is 3.6+ only, older installs could see errors. We’d like to come up with a graceful way to not allow older versions of WordPress to install and run Twenty Thirteen.

Maybe a nag function in the theme that puts up a warning? Forcing a change the previously activated theme upon activation? What are your thoughts?

Relates to #13780 also.

Post formats integration

See #23619, #23620, and #23621 — we are waiting on the core functionality to be committed before we can change the theme code (images, videos, galleries, links).

Recently completed

  • HTML5 improvements to comment list, comment form, and search form (yay!) #22005, #23702, and #23701
  • Solidify footer positioning when no JavaScript or no Masonry script available: #23771
  • More gallery visual fixes: #23773 and #23769

Open issues

Here is a link to open tickets.

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

Twenty Thirteen project update, March 12 2013

This week we are closing as many open issues as possible to prepare for code freeze.

Blockers

Here are the current blockers to getting to a code freeze tomorrow, as scheduled:

  • Post formats: #23619 #23620 #23621 — waiting on the core functionality to be committed before we can change the theme code (images, videos, galleries, links)
  • #15080: Comment form HTML5 input types — just needs a commit
  • #20088: Improve wp_list_comments() markup — needs a code review from core team dev, then commit

Recently finished

  • Several passes at RTL, editor, and print styles
  • Sidebar & footer clearing: #23557
  • Gallery visual fixes: #23742 #23649 #23584
  • Color contrast for accessibility: #23513

Open issues

Here is a link to all remaining open tickets.

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

Twenty Thirteen project update, March 4 2013

What we worked on last week

Lots of fixes and improvements went in — thanks to everyone who reported and patched and tested.

Bigger items discussed:

1. Fixing the sidebar (including discussion of dropping it completely). We decided to just swap primary and secondary sidebars for now. See #23644.
2. Remove fixed navbar for mobile — yes, let’s remove it. See #23647.
3. Keep fixed navbar for desktop for now, but next step is to switch site title to menu there, try that out.

IRC logs: Tue Feb 26 2013 | Thu Feb 28 2013

What we’re doing this week

More work on open tickets.

Big items to tackle next:

  • Post format support: #23619 #23620 #23621
  • Sidebar / footer clearing, still no perfect CSS-only solution. JS techniques are next. See #23557.
  • Gallery styles: portrait sized images, #23649 — and caption styles, #23584.

Non-theme tickets that affect Twenty Thirteen’s progress:

  • #15080: Comment Form Should use HTML5 input types for better accessibility
  • #15081: Search Form should use type=’search’
  • #20088: Improve wp_list_comments() comment markup

Want to get involved?

View open tickets.

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

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

It was pointed out that when using the…

It was pointed out that when using the WordPress Beta Tester plugin, Twenty Thirteen wasn’t being updated. As of r23529, that’s now fixed. If you update twice (once to get r23529, again to update the theme), you should be all set to test and contribute.

#bundled-theme, #twentythirteen

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 WP.org 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.

Continue reading

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

A first draft of the Twenty Thirteen theme…

Screen Shot 2013-02-18 at 5.15.50 PM

A first draft of the Twenty Thirteen theme is now in core, for your inspection and iteration. See: r23452

A demo site is available for you to browse.

@matt set the goals for this theme: a focus on blogging, and great support for post formats (which are getting attention on the backend in 3.6 as well). Under Matt’s guidance, @joen explored the artistic possibilities and was joined by @obenland and @lancewillett in bringing it to fruition.

What you’ll notice first is the colors. Way more use of color than a bundled WordPress theme has had before. Each post format has its own color, so each is distinct, yet they are all complimentary. The bold colors encourage authors to try out all the different formats. This color extends the full width of the window, which breaks your blog up into a lush, segmented timeline. This effect is even more pronounced on mobile browsers, where the screen can be dominated by one or two posts at a time, in all of their chromatic fullness.

On closer inspection, you’ll notice details, like the font-based icons (“Genericons”, by @joen) that scale up to any resolution or zoom level and can be easily recolored using CSS.

You may notice some playful details, like the size-offset pagination arrows:

Screen Shot 2013-02-18 at 4.52.23 PM

Or the 404 page (which I’ll leave to you to find).

One of the goals of having a new theme every year was to give ourself room to experiment. That hasn’t really happened. We’ve been far too conservative, trying to make themes that work reasonably well for everyone, but don’t push boundaries too much. That changes with Twenty Thirteen. It’s hard not to have a strong feeling about the theme, one way or another. It defies you to give it a shrug or a kurt nod. Some of you will hate it. And that’s okay. We’ll still be shipping Twenty Twelve, which is an excellent base theme and a canvas on which you can build anything from a blog to a static content site. But with Twenty Thirteen we’re taking a bold stance: this theme was meant for blogging, and it’s not a blank canvas. It comes pre-marinated with playfulness and warmth and opinions.

Twenty Thirteen really prefers a single column layout. Widgets live best in the footer, where jQuery Masonry bricks them together (but it supports a sidebar, if you really insist). Header images have a fixed width and height, and will be cropped at smaller resolutions, so the best choice is an artistic header where not 100% needs to be shown all the time (it ships with three).

Now that we have a first draft of Twenty Thirteen in core, it’s time to start iterating and sanding off some of the rough edges. Accessibility is still important, even when making bold artistic statements, and I’d be surprised if we didn’t have work to do there. We’ll need testing on lots of different browsers and platforms, and with lots of different plugins. @helen‘s Post Format UI team will need to give feedback on upgrading Twenty Thirteen to use the new post format API functions that are available.

@lancewillett and @obenland will be holding Twenty Thirteen office hours on Tuesdays and Thursdays at 1700 UTC. Interested parties should make an effort to attend and help us get this beauty ready for beta!

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