WordPress.org

Make WordPress Core

Tagged: twentytwelve Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 5:12 pm on September 20, 2012 Permalink
    Tags: , , , twentytwelve   

    Timeline for Twenty Twelve 1.0 — final testing window 

    During the dev chat yesterday (logs), it was determined that the timeline for Twenty Twelve’s release to the WordPress.org theme directory will be next week.

    That means if you have any bugs to report against Twenty Twelve, please do so now! It’s time for final reviews. Once 1.0 is released, it will be very tough for us to make style or code changes, as we will then need to avoid breaking child themes (both code wise, and stylistically).

    So, if you haven’t looked at Twenty Twelve yet, now’s the time. Here’s the demo site: http://twentytwelvedemo.wordpress.com. Also, if you’re using the Beta Tester plugin instead of a checkout from Subversion, you may not have Twenty Twelve installed and up to date. In that case, here’s a direct link to download a ZIP.

    (@westi, @dd32, we should adjust how beta theme installs are handled…)

     
  • Andrew Nacin 6:40 pm on March 20, 2012 Permalink
    Tags: , , twentytwelve   

    As Twenty Twelve is punted to 3.5, it is being removed from core. It can be found here for now, and will be brought back in for 3.5.

     
    • Cais 7:13 pm on March 20, 2012 Permalink | Log in to Reply

      I’m looking forward to its return, there looks to be a great deal of potential with the theme.

    • arena 2:59 am on March 21, 2012 Permalink | Log in to Reply

      Hope it will be released before Dec 21 ….

    • John Blackbourn 3:08 pm on March 21, 2012 Permalink | Log in to Reply

      I thought the plan was TwentyTwelve would be the headline feature of 3.4 that 3.3 lacked. Now that it won’t be, what will?

    • RozaniGhani 12:51 pm on March 22, 2012 Permalink | Log in to Reply

      It too bad to wait twenty twelve theme until the end of year 2012. It should be renamed as twenty thirteen because almost 2013 in that moment.
      So far, twenty twelve theme is far more better than toolbox theme.

      • Mert Yazicioglu 10:12 pm on March 23, 2012 Permalink | Log in to Reply

        Agreed. 3.3 was the best release to call it Twenty Twelve and 3.4 would still be nice but 3.5 sounds a bit too late. On the other hand, assuming that 3.5 will be released by the end of the summer or beginning of the fall, it would be too early to call it Twenty Thirteen.

        Doesn’t really matter what it’s called though, it’s a great theme and I’m sure people will love it :)

  • Lance Willett 6:51 am on February 28, 2012 Permalink
    Tags: , , twentytwelve   

    We’re digging in full bore to get things done by freeze. #19978 is the primary ticket.

    Tasks that need to happen by Wed Feb 29:

    • Finish the styling (Drew)
    • CSS file cleanup (Lance)
    • RTL stylesheet
    • Editor stylesheet

    The last big missing piece for styling is post formats.

    Update Wed Feb 29: see my comment below.

     
    • Lance Willett 5:41 am on February 29, 2012 Permalink | Log in to Reply

      Update: Twenty Twelve is not going to make the cut for 3.4.

      The design isn’t quite finished, and we risk a rushed, incomplete product by forcing it in.

      We’ll continue working on it so it’ll be ready at the start of the 3.5 development cycle, and do a longer report soon on why it was delayed so we can prevent it from happening again.

  • Lance Willett 10:00 pm on February 20, 2012 Permalink
    Tags: , , twentytwelve   

    Team Update: Twenty Twelve 

    We are still plugging away at theme styles and related code changes. See the task list on our last update for the exact things we’re working on and who’s working on what.

    I’ll keep that list updated as we continue to crank on the theme. You can also follow along in the main Trac ticket: #19978.

    One thing that came up this week is a minor revamp to the default comment markup, see #20088 for notes and a patch. If those changes are approved we can delete a big chunk of code from Twenty Twelve’s functions file.

     
  • Lance Willett 4:20 am on February 14, 2012 Permalink
    Tags: , , twentytwelve   

    Team Update: Twenty Twelve 

    We are currently plugging away at fixing up missing styles around the new theme.

    r19915 brings in several of these style fixes and related template changes (see #19978).

    Next up is more of the same, including styling comments, handling the main navigation gracefully in small screens, styling all the default widgets, and styling the basic post formats (aside, link, image, quote).

    If anyone wants to help out a bit, we could use eyes on #19627 — the “default to static front page” behavior.

     
    • Lance Willett 11:18 pm on February 16, 2012 Permalink | Log in to Reply

      Nacin and Jane both asked me to be a bit more open about what we’re actually working on.

      So… hands off the code for a few minutes to keep everyone in the loop.

      Here are the big, open tasks, what we’re doing right now.

      Current tasks

      There is a big blocker to moving any further than that list, and that is:

      Blocker

      We need to wait until after the main styles are “stable”, and all the CSS styling is in. Meaning Drew says he’s done styling all the basic theme elements.

      Then we can move on to the next big tasks:

      Big tasks, part 2

      Who’s doing what?

      Drew: Design concepts, CSS, images, minor HTML changes, a new eye on the well-worn pattern of blog design

      Lance: PHP code, enabling WP core features, testing, CSS cleanup, ensuring WP code standards on everything, i18n, approving any major departures from previous Twenty Something themes in terms of code, making sure this theme owns up to the awesome lineage of WP themes.

      Matt: Art direction and overall taste tester, meaning he has the final say on the design and functionality; testing it out for us in each stage and giving feedback on everything; sending us cool music to listen to while coding. :)

  • Lance Willett 12:17 am on February 7, 2012 Permalink
    Tags: , , twentytwelve   

    Team Update: Twenty Twelve 

    We are the team formerly known as “Twenty Twelve Two”—now three strong with Drew Strojny joining up for the 3.4 release cycle as the theme designer. Welcome Drew!

    What we’re calling our “first cycle” ends today with Drew delivering us the first working prototype with the basic layout in place. Matt committed it with r19842. (See also #19978.)

    Consider this version 0.5

    This is not yet a fully working theme—we’ll be adding in more features and lots of missing styles over the next 3–4 weeks. Including post formats, comments, archives and page templates, more in-post styling, and a nav menu rework so the main content comes ahead of the navigation.

    Our goal for the next cylcle is to finish up all the missing visual styles from Drew, with Lance making relevant code changes as needed. Deliverable is a finished theme that everyone can start using and testing in earnest.

    Schedule notes

    1. Due to schedule conflicts we need to be going slowly over the next week or two, picking it up again in earnest Feb 20–Feb 29.
    2. Office hours will probably be on Mondays, I’ll post the actual times soon.

    Update: We’ll end our cycle on Feb 29th.

     
  • Jen 3:26 am on December 20, 2011 Permalink
    Tags: , , twentytwelve   

    Core Team Meetup Recap: Default Theme “Twenty Twelve” 

    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:

    • single post/permalink view with post formats is needed
    • variable height header image
    • mobile version
    • default to static front page (will need a function in core to auto-choose)
    • editor styles the same as front end.
    • avoid clever things that aren’t super-useful (like ephemera widget)
    • start with 2011 as base for code (or 2010, which has gotten more updates and had more eyes on it)
    • no featured image in header
    • by default – no header image

    To-do: Reverse engineer from 3.4 timeline to create a schedule of deadlines for theme design and development.

     
    • Evan Jacobs 3:30 am on December 20, 2011 Permalink | Log in to Reply

      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.

      • Jane Wells 3:45 am on December 20, 2011 Permalink | Log in to Reply

        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.

      • Emil 4:01 am on December 20, 2011 Permalink | Log in to Reply

        @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

        • Jane Wells 4:12 am on December 20, 2011 Permalink | Log in to Reply

          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.

        • Emil 8:36 pm on December 20, 2011 Permalink | Log in to Reply

          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

        • Rafael 3:41 am on December 21, 2011 Permalink | Log in to Reply

          or using FitVid.js

        • Emil 5:59 am on December 21, 2011 Permalink | Log in to Reply

          I tried, FitVid.js works like charm :)

    • Banago 9:59 am on December 20, 2011 Permalink | Log in to Reply

      I’d like to contribute to Twenty Twelve theme. Let’s hope so.

    • Sara Rosso 11:12 am on December 20, 2011 Permalink | Log in to Reply

      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)

      • Jane Wells 1:35 pm on December 20, 2011 Permalink | Log in to Reply

        I believe it already is in Twenty Eleven. It just depends on what you choose as default layout on Theme Options, doesn’t it?

        • Mika Epstein (Ipstenu) 2:37 pm on December 20, 2011 Permalink | Log in to Reply

          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!’

        • Jane Wells 3:37 pm on December 20, 2011 Permalink | Log in to Reply

          @Mika: I must have blocked that out. There were a number of things I didn’t like about Twenty Eleven.

    • Jeff Farthing 1:56 pm on December 20, 2011 Permalink | Log in to Reply

      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).

    • Jorge 2:52 pm on December 20, 2011 Permalink | Log in to Reply

      the new theme could have 4 layout options. “content”, “sidebar-content”, “content-sidebar”, “sidebar-content-sidebar”. It would be wonderful.

      • Rami 10:21 pm on December 22, 2011 Permalink | Log in to Reply

        +1 !!!
        3 column theme would be great!

        • BGR 6:27 pm on February 21, 2012 Permalink | Log in to Reply

          two side bars with flexibility on placement is ideal.

          • Jorge 5:10 pm on February 23, 2012 Permalink | Log in to Reply

            Great! your comment makes three of us. It would be excellent that more and more people joined this petition and the development team listen us.

    • Ian Stewart 3:24 pm on December 20, 2011 Permalink | Log in to Reply

      default to static front page (will need a function in core to auto-choose)

      Hot-diggity-dog, yes. :)

    • Eric Mann 3:37 pm on December 20, 2011 Permalink | Log in to Reply

      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.

      • Jane Wells 3:43 pm on December 20, 2011 Permalink | Log in to Reply

        There’s a ticket for something like that on trac, from when I offered to make cookies for whoever solved it first.

        • Eric Mann 4:38 pm on December 20, 2011 Permalink | Log in to Reply

          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 …

      • Helen Hou-Sandi 4:15 pm on December 20, 2011 Permalink | Log in to Reply

        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.

      • Rev. Voodoo 5:59 pm on December 20, 2011 Permalink | Log in to Reply

        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!

    • Cais 4:29 pm on December 20, 2011 Permalink | Log in to Reply

      … 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.

    • bobbi 5:39 pm on December 20, 2011 Permalink | Log in to Reply

      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.

    • billbennettnz 1:25 am on December 21, 2011 Permalink | Log in to Reply

      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.

    • Tim 3:59 pm on December 22, 2011 Permalink | Log in to Reply

      An optional sidebar on single post pages would be amazing!!!

    • Worli 12:24 am on December 23, 2011 Permalink | Log in to Reply

      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.

    • Gaurav Tiwari 1:14 pm on December 24, 2011 Permalink | Log in to Reply

      Make it as good as Twenty Ten is in Print, Please.

    • Jhay 5:45 am on December 25, 2011 Permalink | Log in to Reply

      A default WorPress theme with no default header image? That’s something to look forward to.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar