 | newtonsongbird on Suggestions |
 | Kim Parsell on Core Contributor Handbook |
 | Lance Willett on We’re getting very close… |
 | Muhammad Abdi on Core Contributor Handbook |
 | Maor Chasen on We’re getting very close… |
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.
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
We’re going to go ahead with 2013 on WP.com without waiting for post formats, since the homepage / toolbar poster (instapost) already supports formats.
#24176 for the Quote post format styles.
#24184 for removing the fixed navbar.
It’s alive on WordPress.com now. Huzzah! http://en.blog.wordpress.com/2013/04/25/twenty-thirteen/
https://twitter.com/wordpressdotcom/status/327220917895843842
I added a bunch of thoughts and notes on the structured post formats issue here: http://core.trac.wordpress.org/ticket/24109#comment:18
Disqus isn’t working properly… it may be a plugin issue, rather then a wordpress twenty thirteen issue. Example: http://antigonishhpa.ca/2013/04/26/date-of-first-public-interest-session-announced/#respond
How about the mobile version? This theme is responsive but not entirely. For example, the YouTube video breaks the Home Page vertical layout.
Hi, could you report the exact issue in core Trac, please? Screenshots are helpful for us to repeat and fix. https://core.trac.wordpress.org/
I wonder if it’s related to this: http://core.trac.wordpress.org/ticket/24134
Just to inform that in GlotPress the sub-folder for 2013 is not the theme domain twentythirteen as other official theme (2010… 2012)
but an annoying ‘-’ is inside
http://translate.wordpress.org/projects/wp/dev/twenty-thirteen
Please erase this ‘-’, it’s facilitate automatic downloading updated .mo according theme domain
Hope you will find the good contact…
@nacin ping … ^^
Fixed. That’s particularly important because our own scripts are trying to import things into the “twentythirteen” project… Should start to live-update shortly.
Thank you.
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
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.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.Office hours
We’ll get back to office hours in #wordpress-dev IRC over the next few weeks, Tue and Thu at 17 UTC.
Can’t make it to the office hours, but want to point out a couple more IE 8 issues that may or may not be ticket-worthy. The headings are displaying in Georgia font, but Bitter should work for IE 8. It’s fine on 9 and 10.
Also, the header image is zoomed in in IE 8. See both issues in these screenshots (emulating 8/9 with 10): http://celloexpressions.com/nh/twenty-thirteen-fonts-ie8.png, http://celloexpressions.com/nh/twenty-thirteen-fonts-ie9.png.
By the way, is IE 7 supposed to be supported/should it be tested?
Here’s a WP 3.6 with (slightly altered – just colors) Twenty Thirteen. Working great so far!
Thanks for the link—cool color scheme! I’m seeing a few bugs in the comment form layout, though. Will need to debug and fix soon.
Love the brave new look of TwentyThirteen– I’m working on a child theme for my personal blog… (It’s live but on the QT so I’m not too worried about glitches at this point).
A few issues I’ve seen… with the fixed navbar, the header image I hacked/inserted into the masthead overlays and hangs below the bar. I know I can turn this behavior off by commenting out the JS but it may be an example of a use case that your more dive-into-the-code users will encounter. (I wanted that image to scale, which is why I inserted it as I have…)
Other notes: I couldn’t get the JetPack carousel to work with the gallery post format as it does on the demo. Not sure if I just missed a step or if it’s not hooked into the theme correctly.
The Status post format looks odd with an image floated left on the post… I nixed the background dotted line, but the Genericon (or whatever is producing the horizontal bar glyph in place of the title) is kind of distracting, too.
Here’s the link: http://lisafirke.com/blog
Looking forward to rolling out the finished version with much fanfare…
Hi there, and thanks for your notes. The fixed navbar + inserted HTML image isn’t a bug we’ll fix in the core theme—that’s a great example of child themes adjusting and changing how the core theme works.
We’ll investigate Jetpack Carousel and the Status post format left-aligned image a bit more.
Lisa: can you give more info on the Jetpack Carousel issues you had? I couldn’t repeat—seems to be working normally with all the various “types” of galleries in Jetpack.
See my notes below. I think it’s a jquery/Jetpack glitch of some kind, because others are reporting similar issues with Jetpack.
The main thing is, with Jetpack enabled, I’m still not seeing any formatting options for the carousel–I only have the ability to toggle from slideshow to grid on a gallery post.
You’re probably right. We know of some conflicts between jQuery 1.9.1 and Jetpack Carousel, and we”ll get this fixed before 3.6 ships.
See this ticket for more details about the conflict.
Hi again Lisa, to get rid of the horizontal bar glyph for Status posts, look for:
.format-status .entry-content p:first-child:before
And either change or comment it out in your child theme.
lisa was there a specific browser that you were having trouble with the JetPack carousel?
I’ve got 3.6 beta on my blog and loaded up a carousel post with JetPack slideshow ok.
I only tested in Safari–see my notes below…
I’m using Safari and the latest beta build. I fixed a javascript error that was preventing the slideshow from running, but I don’t see any way to enable a full-screen slideshow. Here’s my test post: http://lisafirke.com/blog/2013/carousel-test/
I’m thinking the problem lies with Jetpack and not with TwentyThirteen?
I disabled my test, so don’t bother clicking through. Only the background color and exif field data items are getting displayed as configuration options–and in the media ui no choice of carousels or any other configurables beyond “slideshow” versus “grid”.
There are posts in Alpha/Beta about 2013 – http://wordpress.org/support/forum/alphabeta
(look for the ones that aren’t resolved)
Thanks, triaged 3 of the unresolved ones (1 was not related to Thirteen specifically).
Shirley 
Is there a good way to report them or flag them for you? I don’t know enough about what is and isn’t a theme decision (seriously, I hate debugging themes!) to feel comfortable raising tickets.
Also if you’re not a forum mod, I’ll make you one so you can resolve those posts too 
To flag, please use tag twentythirteen and I’ll follow that tag feed.
(I am a forum mod already.)
twentythirteen it is! (and yay! Any time you hit a post with an accepted trac ticket, go ahead and resolve it in Alpha/Beta. Keeps it clean… er)
Will do, thank you.
As discussed yesterday during office hours, I tested 2013 against Jetpack Trunk, and found 2 issues, that we will have to fix in Jetpack before 2013 is released.
Infinite Scroll seems to work fine, whether you use footer widgets or not. All widgets seem to be displayed properly, although I haven’t tested in IE.
No problems with post formats either. There were some conflicts between Jetpack Shortcodes and the new Audio shortcode, but it was fixed in r696694-plugins.
Auto-linking fail. The 2 trac tickets are here:
Our focus right now is on post formats integration, both structured (formats with post meta) and “normal” output for the other formats.
Priorities
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.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.By post format
Here’s a breakdown per format, per today’s discussion (IRC log).
get_the_url() wrapped in our own fallback to output permalink if no URL is foundthe_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.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 anywaycontent_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 #23852 for the Quote post format markup
#23869 for Chat post format support and styling
I’m going to jack up my nice 2013 theme with a relative side bar, I’m not looking forward to the result, however, I decided to use a 2013 child theme on an actual project. Maybe some nice person will create a tutorial on how to do this once it’s released and get lots of hits. – the Nav at bar in the top is a big hit…
seams _the_image: functions doesn´t work I get a **Fatal error** in content-image.php line 13. I´m testing with wp 3.6 beta 1
Already fixed, see #23942.
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
Open issues
Here is a link to open tickets.
Great work lance.
But regarding to search forms, seems like you didn’t addressed the old discussions on tickets #14581, #19321, and #19579.
Thanks for pointing those out, I hadn’t seen them before.
I think putting up a nag function that can only be seen by a user with admin permissions is a great idea. As a matter of fact only a user with admin permissions should be able to see errors related to the administration of the website. It creates a better user experience.
Plugins can deactivated themselves if they know their requirements aren’t met. There needs to be a precedent set for how theme’s who requirements haven’t been met can ‘deactivate’ themselves.
I think that the result of a theme ‘deactivating’ itself should cause the same result as if the theme suddenly was removed. I believe right now it defaults to the default theme in WordPress. I would argue doing anything different then that creates an inconsistent error scheme.
If there was a way to track which theme it switched from (active before trying to activate this theme), then one could simply revert the action. That would be the safest method, as it does not alter the website in any way (ie., theme specific customizations, etc).
Having that said… Why not include this sanity check within the WP core itself, for both plugins and themes. Just give add two extra meta headers to the plugins/themes for the minimum WP and PHP versions, and add a little extra code that checks against these prior to activation. That would be a useful feature that could benefit many. #thinkingoutloud
See #13780 for the WordPress version requirement support.
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:
oelja, and 1 other are discussing. 
wp_list_comments() markup — needs a code review from core team dev, then commitRecently finished
Open issues
Here is a link to all remaining open tickets.
Oh my… I don’t think I have ever seen the default gallery so uber cool as I have in Twenty Thirteen…
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:
Non-theme tickets that affect Twenty Thirteen’s progress:
View open tickets.
Join us in IRC during office hours and we can get you started on a ticket or task.
if a comment author is the post author his authorlink has “rel external and nofollow”,
but his link is to the author page of the site, why rel external and why nofollow, no internal links should be nofollow,
I ask this myself all the years
Hi Monika—this topic is not related to this update on Twenty Thirteen, and I’m pretty sure the output you’re talking about is not theme-specific.
Related discussion here: http://core.trac.wordpress.org/ticket/18547#comment:11 and probably a bunch of other tickets.
I will try to get to the IRC during office hours… I just downloaded Twenty Thirteen Yesterday to my dev build. I am not a fan of the fixed nav bar… I understand I could make a child them to alter this… But it just looks odd… Take for example a 17in monitor without widgets. http://cl.ly/image/3K303B150131 I know I am late to the game… I know this has been previously discussed… Not asking to rehash something again… but just to give my “2cents” even if abet a bit late…
If you can join us in IRC, that’d be great—otherwise thank you for your comment and feedback.
Ha! The GIF on #23647 is a killer!
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.
(These are WP.org usernames.)
Many other folks already contributed patches and tickets, thank you.
Tuesday we started by dividing things up a bit:
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.
How can I help with Standard Theme Hooks? Related to the Theme Review Team, I have a vested interest in seeing standard Theme hooks ironed out, integrated into Twenty Thirteen, and then backported to Twenty Twelve and Twenty Eleven (and Twenty Ten?).
Hi Chip—I’d say start by testing the latest patch on the ticket — and leave comments there in Trac if you see need for improvements.
I’ve been running the “latest patch” in Oenology for many months. It looks like that ticket needs final decisions/consensus in order to move forward. I would be happy to submit a patch for Twenty Thirteen, but it would be somewhat counterproductive to do so before we’ve got those final decisions/consensus.
Looking at that ticket, it appears that the status is “everyone agrees in principle, but there are minor disagreements on the finer points of implementation.” I’m happy to submit any patches necessary, but who makes the “where do we go from here” decision?
It’d be cool if you drove it forward.
In case anyone else is wondering (as I was) what the ticket is for Standard Theme Hooks, it’s http://core.trac.wordpress.org/ticket/21506
It is also linked up in my post.
And what about http://core.trac.wordpress.org/ticket/21256 ?
The status of the 3.6+ requirement can be found in #13780
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:
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!
First impression: WOW
Holy color!
Nice Mark!
First thing I notice is that although the search bar sticks to the top with the Twenty Thirteen branding while you scroll, the main navigation is not up there with it on both large desktop screens and small device screens. Was there a reason for this or can this be changed by the user? And of course I\’m wondering if the user will be able to change those colors for each post format.
It’s a known issue, and something I’d like rectified. The dropdown menu that you get on small screens would be great up there. And colors could be overridden by a child theme — probably a lot of option overload if we exposed that.
WOW, instant love! The colors are bold but harmonious, the type is GREAT, and it’s got such a fabulous funky retro futurist feel. Thumbs up!
Pretty good for the first draft!
Wow indeed! I too was getting a feeling that the “clear white” theme spirit could feel overplayed if 2013 had it. I for one am very glad that the team is making such a bold move in a creative direction. I trust there will be enough theme option and color schemes so that users can make it their own in a few clicks.
Great work!
Love the colors, love the flow. Nice to see creativity unleashed on the default theme!
Nice! Just … Amazingly nice. I’m gonna have to find a site to use that on. Maybe my own!
Can’t wait to try it out..
I find that to be just delightful!
So excited to have this in. It really is great!
http://genericons.com/ seems to be behind a WP.com password.
The genericon site isn’t up yet. I think you can see the icons here for now: http://moc.co/a8c/genericons/example.html
Yep – got it!
Many thanks Aaron.
@Aaron, the theme and genericons look great! Are there plans to create icons for SoundCloud, IMDb, Vimeo, and YouTube?
Vimeo and and a minimal YouTube icon have been added already! We might be able to add SoundCloud and IMDb in the future at some point too. I expect the font to grow.
You guys probably have noticed by now that http://genericons.com/ is live. I just added a post to themeshaper.com about them too, if you’re interested.
http://themeshaper.com/2013/02/27/genericons-icon-font/
I love icon fonts!
Looking forward to the post format specific layouts and metadata.
Would be nice if the video, once ‘fetched’, would autopopulate the title.
Very Nice! Shades of BuddyPress
…beautiful, you’ve managed to stick with the mimimal yet spice it up with jazzy colors. Instant LOVE <3
The theme demo looks great. Like the direction it heading in.
Looking forward to testing the formats. Now to get home and uptade core.
Just finished testing Twenty Thirteen with the new post formats scheme. Sweet. : )
Looks great! Also nice to see some post formats love
Except for the header trick … sorry, it’s just not doing anything for me.
What if it had menu access like the mobile menu?
It’s lookin’ great so far! Well done to all involved!
It’s counterintuitive because this is a visually much more aesthetically opinionated base than we’ve had probably since Kubrick, but I think we’ll see a lot more customization and variations on Twenty Thirteen than Eleven or Twelve. It’s a delightful canvas to play on.
I agree, it does seem like it can be a great starting point for future themes and child themes.
While the CSS is pretty opinionated, as you call it, the theme’s markup is clean and streamlined. I believe this is a canvas just as good as any other core bundled theme.
Well, in that spirit, I made a blue version.
Nice work all around! I couldn’t help myself: http://jtsternberg.com/
This one will be the great example to show that without choosing white color can also make clean and beautiful theme. Love the way designer play the colors.
Thanks to all contributors. Its really Fantastic ! Can’t wait to see it out in my themes directory.
Love the new direction, looking versatile and fluid, +1
And here I was thinking that WordPress default themes need to be bland and white.
Wow. Bold move, I love it.
I’d make the main navigation sticky though, together with the search bar and the site name.
And it would be great to have some color palettes to choose from as visually color is the first thing you experience with this theme.
Default WordPress themes have always been great, but they’ve needed to be versatile and cater to the majority, and in doing so have had to be more conservative. This puts the fun back into WordPress, and definitely brings a smile to my face. I do agree that the collapsed mobile menu should be placed in the fixed header when scrolling though.
This. Looks. Awesome.
Excellent work! I love the post formats styles
there was a theme in tumblr directory by peter vidani, which used the colors for post types!
it looks like Windows8 colorful and dizzying.
Nice and different direction. With this new bold approach, I’d like to see the base font size increased a bit more. Chrome is telling me it’s 16px, and with Source Sans Pro 16px looks more like 14px. It looks good and is easier to read at 18 or even 20px.
Absolutely beautiful. Good work!
Sponsored by Ubuntu I see…
It’s really a beautiful theme , but I don’t think It’s good to be a default theme ,It’s too colourful … Yes it’s different direction but many of WP users like the default themes because they are simple and have a less colours , I was thinking if you can make the colours system is optional in the theme control panel ….
As I am seeing now , Its seems to be hard to use it as a framework , the default theme should be simple , clean , easy to customize and express WordPress main features !
Twenty Twelve will still be packaged with WordPress too. I do however think this theme will actually be pretty easy to extend.
This is actually going to be a perfect default Theme and honestly, very easy to customize as well.
Colors are post formats and they can be changed or removed
Is there a reason why the fixed navbar replaces the navigation menu with the site title? Doesn’t that pretty much defeat the purpose of the fixed navbar to provide better accessibility to the site’s navigation? Why would I need a static bar with just a link to the front page?
ooooooooo, ahhhhhh – very awesome indeed! The long scrolling homepage, ever-adaptive elements, and I’m sure much more will be realized with a test drive. Thanks!! BTW – why the persistent header with banner on all pages? Am I alone in wondering why is the banner needed on pages other the homepage?
Surprised to still see ‘Links’ in there as a post type…
Love at first sight.
Bold And Beautiful! A total change in direction from previous “Default” themes – this will make an awesome parent theme for developers to tinker with.
Would like to chime in on the menu though….the sticky menu “bar” minus the menu is not doing it for me – I would like to see the menus as I scroll the page instead of a blank “bar”.
Further more, since its bold in terms of color scheme – I would like to see the options to adjust the various sections incorporated in the Customizer’s Color section and not having to rely on changing them via child themes. As it is the child theme option would work for developer but not for the novice end user.
But all in all, I’m totally loving what I see so far – now its time to go break it apart and see what I can conjure up
What is up with the breaking of words in titles and in text? It was there in Twenty Twelve and is still around. Any insight on the word-breaking thingy would be great
Strange unanimity… I’m a guy who likes color and bold, though I’m more for minimal. I don’t understand this theme and can’t picture it as a default WordPress theme. Maybe the focus here is on blogs, I get it, and giving the author a panoplia of customization options. I get it too. Nevertheless, I fail to realise how one goes from twentytwelve to this twentythirteen. Sure, it’s a cut, but I don’t see it as a step forward, something new, more like something else.
(I could be wrong, though… me and Nashwan Doaqan up there…)
cool, love it!
Amazing theme. I like it and have a good feeling when I see it at first. It’s great when you can push the boundaries so far. It’s time to show people that WordPress is easy to customize.
Its like it or not based on my readers feedback. Personally i love it but also know you guys could seriously blow the socks off any premium theme out there. Built in hooks and conditional tags is where its headed i think. WordPress theme users are smarter now and want more. They understand the basics of coding. Extend further.
The bold colors and bold theme. Bravo. It’s going to be a good one.
Wow… really, really good. It”d be nice to get the default theme out early this year. (I;ve always thought that the annual themes should be released at the start of the year, not the end
Gorgeous and playful. Bravo!
Great!
I can’t wait to make a new theme for my blog based on Twentythirteen.
love the full width. Agree with comments about fixed nav bar. Look forward to seeing what people do with it. Thanks v much.
What I have seen is very promising. Can’t wait the release
One of the topics discussed at the core team meetup was next year’s default theme. It was determined that the default theme will be Matt’s project for 3.4. Matt will be overseeing a theme designer (via Lance) to ensure a theme that is “kind of different from before, generally palatable, and that Matt likes.” Once Matt chooses a design, a directory will be started and the core team will supervise the code from the start, hopefully with review cycles involving the theme review team.
Some notes about what we want in a new default theme:
To-do: Reverse engineer from 3.4 timeline to create a schedule of deadlines for theme design and development.
I would like to suggest incorporating an adaptive framework (like Skeleton) into the next default theme, such that a mobile site doesn’t have to be designed separately.
It would have been more accurate for that line item to say “looks good on mobile” rather than “mobile version,” much as Twenty Eleven does.
@Evan Twenty Eleven does have Responsive Design since I believe day one, so no it doesn’t need to be designed separately because it works and looks the same on all* devices!
@Jane is this something beyond Responsive Design?
Thanks,
Emil
Responsive design does not mean looking the same on all devices, it means dynamically rearranging and/or resizing things so they will look good and make sense regardless of size.
Yes I know and you’re right, for some reason I was under the impression that “elements” do resize in Twenty Eleven. What does not is video embeds a/ka/a (Post Format Test: Video) but that can be changed with i.e. object, embed, video, { max-width:100%;}.
Thanks for an additional input,
Emil
or using FitVid.js
I tried, FitVid.js works like charm
I’d like to contribute to Twenty Twelve theme. Let’s hope so.
Exciting! Would love it if the sidebar is an option to turn on or off on a permalink / single post page (instead of automatically off as in Twenty Eleven)
I believe it already is in Twenty Eleven. It just depends on what you choose as default layout on Theme Options, doesn’t it?
No, on TwentyEleven there’s no option to turn the sidebar ON for posts/pages. You can turn it on or off for the front page/archives, but not the posts. IIRC that was to showcase the content of the post, and not detract with ‘happy sidebar fluff!’
@Mika: I must have blocked that out. There were a number of things I didn’t like about Twenty Eleven.
Let’s please make sure that this time, the default theme properly calls The Loop, on all templates! It’s not very cool when the default theme doesn’t even follow the WP standard (as the case with Twenty Ten and Twenty Eleven).
the new theme could have 4 layout options. “content”, “sidebar-content”, “content-sidebar”, “sidebar-content-sidebar”. It would be wonderful.
default to static front page (will need a function in core to auto-choose)
Hot-diggity-dog, yes.
This one had me head-scratching a little bit, so I’m curious to see how it gets implemented.
If we wanted to set the standard for how social sharing icons are added to individual posts/pages, this would be the perfect opportunity to demonstrate and establish a best practice. Maybe with a theme-specific hook. Maybe with `get_template_part( ‘post_footer’ )`. In any case, setting the standard with the release of Twenty Twelve and 3.4 would convince a lot of developers to follow suit.
There’s a ticket for something like that on trac, from when I offered to make cookies for whoever solved it first.
Bingo (https://core.trac.wordpress.org/ticket/18561). It’s just that a few people seemed persuaded that this should be theme-specific and not in core. So if it’s not going to be in core, I think Twenty Twelve would be a great way to demonstrate how it should be done in themes. Either way, I figured *now* would be the best time to start a discussion as it pertains to 3.4/Twenty Twelve …
In any case, setting the standard with the release of Twenty Twelve and 3.4 would convince a lot of developers to follow suit.
+1
Post extras! It was #18561.
Ha! I was just working on a theme for my personal blog, and adding in some hooks…. Logged on here to suggest the very same thing!
… hopefully with review cycles involving the theme review team.
We would be greatly interested in being involved with this … I’m sure it will be easily arranged.
I hope you start with 2010 as the building block, personally I have never used 2011 as there was nothing about it i liked. Way more users are using 2010 and way more children of 2010 have been developed.
Can we have a 2012 theme where there’s only one H1 on each page? I’m told by my expert friends having more than one – like 2011 – is hurting my site with Google search.
Multiple H1s are actually semantically OK in HTML5.
Thanks Evan, that’s helpful to know. And ammunition to keep the nay-sayers quiet.
For some fun reading related to this topic, see #17611.
Good one Lance! I failed not to mention that ticket here That was fun indeed!
An optional sidebar on single post pages would be amazing!!!
Mobile version would be a great feature. Hope it has a option to set left or right side bar, since many users still prefer left side bar.
Make it as good as Twenty Ten is in Print, Please.
A default WorPress theme with no default header image? That’s something to look forward to.
Bryan Petty, 
Jorge, 
Lance Willett 8:11 pm on May 9, 2013 Permalink | Log in to Reply
Turns out we don’t need flipped versions of the glyphs—as several folks reminded me we can use the CSS
transformproperty instead.Ipstenu (Mika Epstein) 11:02 pm on May 9, 2013 Permalink | Log in to Reply
Serendipitous
George Stephanis 2:26 pm on May 10, 2013 Permalink | Log in to Reply
And we’re okay with them not flipping in older browsers that don’t support
transforms?Lance Willett 3:52 pm on May 10, 2013 Permalink | Log in to Reply
Your answer is in the code.
George Stephanis 5:59 pm on May 10, 2013 Permalink | Log in to Reply
Rightio! Will actually read that, then.
Lance Willett 6:06 pm on May 10, 2013 Permalink
The IE stylesheet has the older
FlipHfilter support in place. IE9 has-msprefix—the rest “just work.”Maor Chasen 1:11 pm on May 11, 2013 Permalink | Log in to Reply
Going to weigh in and help out with this. There are some more (mostly minor) RTL issues, I’ve started working on a patch. Will post real soon!
Lance Willett 4:44 pm on May 13, 2013 Permalink | Log in to Reply
Thank you!