As we approach 3.6 final, we need to start thinking about the About page for the release. What should go on it? Shout out your ideas.
Tagged: 3.6 Toggle Comment Threads | Keyboard Shortcuts
Hey! Remember that WordPress 3.6 release we were working on? Yeah… we’re still at it. But there’s hope! Post Formats UI has been extracted, and Revisions has gotten an intense refactoring that makes it scale up to hundreds of revisions without killing your server or your browser. A backlog of many hundreds of tickets has been whittled down. As of this writing, we’re below 40 tickets for 3.6, and they’re actively being committed and punted as appropriate.
The plan is to keep on those tickets and get to RC by Friday. Help is appreciated! A bunch of people have been “pinged” regarding tickets on report/6, so please scan through those and log on to IRC to check for messages.
We’re getting very close.
This week focusing on RTL again, especially concerning
:afterand 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.
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.
Post Formats UI is looking like this right now:
This seems confusing, because it looks like they are icons to insert something (Image, Gallery, Link, Video, etc), but instead of launching a popup to insert a link or an image, the screen changes and the navigation that was just used to choose disappears completely. (Note: If Standard had some indication of being the default/current selection it wouldn’t be as confusing)
Clicking on one — say Link — makes the UI change, the big icon row go away, and a format switcher link drops below the title rather than keeping its visual hierarchy above the post stuff, and it’s generally disorienting.
If the user thinks, “Whoa, what happened, I better change format again,” and they click on the “Change format’ link under the title field and next to the “Enter URL” instruction, the screens morphs again to this:
Where the icon strip is back, but the link field has disappeared and the icon next to Add New Post is still a link. This is super confusing. Does it still think it is a link bc they didn’t actively choose to return to standard, they just chose to see the options? If that’s so, why did the url field disappear?
Looking at the release schedule:
We launched Beta 1 on April 4, and it’s been almost 3 weeks without a follow-up beta 2.
…I am wondering if the post formats ui is really prime time ready, or if it should be one of the very first thing sto land in a 3.7 branch so we can get the things that are completely ready into the hands of users sooner rather than later?
Since I’m outside the core dev group now, I’ve been on both sides of the deadline delay dance. I know how hard it is to let go of something that feels like it is thisclose to done. And I know that just about everyone on the core team will be thinking right about now that I should shut up (and I’m okay with that, because it used to be my first response to deadline questions to core, too). But we have this philosophy posted on wordpress.org:
Deadlines Are Not Arbitrary
Deadlines are not arbitrary, they’re a promise we make to ourselves and our users that helps us rein in the endless possibilities of things that could be a part of every release. We aspire to release three major versions a year because through trial and error we’ve found that to be a good balance between getting cool stuff in each release and not so much that we end up breaking more than we add.
Good deadlines almost always make you trim something from a release. This is not a bad thing, it’s what they’re supposed to do.
The route of delaying a release for that one-more-feature is, literally, a rabbit hole. We did that for over a year once, and it wasn’t pleasant for anybody.
The more frequent and regular releases are, the less important it is for any particular feature to be in this release. If it doesn’t make it for this one, it’ll just be a few months before the next one. When releases become unpredictable or few and far between, there’s more pressure to try and squeeze in that one more thing because it’s going to be so long before the next one. Delay begets delay.
I’m not trying to be a troublemaker or imply that anyone isn’t doing everything they can — I know for a fact that people are working themselves into the ground on this release. Nor am looking to incite a debate about deadlines or all the explanations of how we fell behind this time (I’ve been following along, everything is really pretty normal). But would it be better to not try to squeeze it all in, get out what we can ship now (including the awesome 2013 theme that regular people still don’t have access to), and take a quick breath to relax before diving back in on a new cycle? Shipping is a feature, too. 😉
He started contributing more than three years ago, and his contributions, which number well into the hundreds, are always top-notch. If you’ve had a chance to work with him, you probably noticed at least two things: calm judgment and biting sarcasm. I’ve found that the beta period is his bread-and-butter — he goes around polishing and fixing everything he can get his hands on. He’s also taken one for the team more than once on things like fixing RTL, getting IE to behave, and synchronizing color schemes.
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).
- 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
- Ask Joen to do another design audit, checking versus his design vision for things like spacing, colors, and post formats.
We’ll get back to office hours in #wordpress-dev IRC over the next few weeks, Tue and Thu at 17 UTC.
Our focus right now is on post formats integration, both structured (formats with post meta) and “normal” output for the other formats.
- Work with Post Formats team to get
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.
- 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.
- 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)
- 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_widthto 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
blockquotecorrectly 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_widthto 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
- Work with Post Formats team to get
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
- HTML5 improvements to comment list, comment form, and search form (yay!) #22005, #23702, and #23701
- More gallery visual fixes: #23773 and #23769
Here is a link to open tickets.
Twenty Thirteen Not Backwards Compatible? - WP Daily, Lance Willett, Myatu, and 3 others are discussing. Toggle Comments
As noted in The Road to 3.6 Beta 1, we’ve got quite a bit going on for post formats. Many of the tickets are in need of testing (including unit tests) and then a commit. As always, there are a few different fronts: UI/administration, data, and parsing. Here’s where we are with each, and what needs to get done. There’s a large variety of tasks here, and we are seeking contributors to help