Make WordPress Themes

Tagged: core Toggle Comment Threads | Keyboard Shortcuts

  • Lance Willett 11:48 pm on February 18, 2013 Permalink | Reply
    Tags: core, , twentythirteen   

    Twenty Thirteen Draft Now in Core 

    Hi theme reviewers,

    Twenty Thirteen is ready for feedback and testing in core: http://make.wordpress.org/core/2013/02/18/introducing-twenty-thirteen/

    Our goal is to have it ready along with the rest of 3.6 for an April launch. Would love your eyes on it for testing, performance, tying in with core features, all that good stuff.

    Also noting several theme-related core tickets, if anyone wants to jump in with comments, patches, and testing:

    We’ll have open office hours Tue/Thu throughout the cycle (see http://make.wordpress.org/core/ sidebar for times), so hope to talk with you soon.

     

    • Emil Uzelac 11:50 pm on February 18, 2013 Permalink | Reply

      Will do for sure and Twenty Thirteen looks mighty fine :)

      Emil

    • @mercime 1:06 am on February 19, 2013 Permalink | Reply

      Congratulations @matt @lancewillett @obenland @joen and team.

    • Daniel 6:53 am on February 19, 2013 Permalink | Reply

      Can we please add the ticket about styling the post comment button?

    • Sallie Goetsch 11:55 pm on February 19, 2013 Permalink | Reply

      I like the typography (except the menu font, which is microscopic–PLEASE bear in mind that not everyone using WP is under 25) and the color. It’s pretty and fun. Can’t imagine using the theme in a million years, though, because the sites I build aren’t blogs and do need to be customized to the user. Where does the theme customizer fit in with something that has such distinctive colors?

      I’m also wondering how to fit Twenty Thirteen into my intro WordPress class for May, because I’m not at all sure it will suit my students half as well as either Twenty Eleven or Twenty Twelve.

      • Lance Willett 3:15 am on February 20, 2013 Permalink | Reply

        I wish I were 25. :)

        Could you share a screenshot of tiny menu font size? That sounds like a bug.

    • Nathan Reynolds 6:11 am on February 20, 2013 Permalink | Reply

      I am wondering if there is a reason that when I post under the link or quote format the .entry-content is empty so it’s just showing the post-meta.

      I am using the built in boxes for URL in link, and quote/source in quote. I just test to see if the post body will show up and it does, just none of the other boxes I filled out.

      • Lance Willett 4:07 pm on February 20, 2013 Permalink | Reply

        Hi Nathan, are you using trunk 3.6 bleeding edge? That code is brand new, and doesn’t work with Twenty Thirteen yet.

    • bjornsennbrink 7:40 am on February 25, 2013 Permalink | Reply

      Remove hyphens from body.

  • Lance Willett 6:47 pm on July 18, 2012 Permalink | Reply
    Tags: core, tags   

    I’d love your thoughts on adding two new tags to allowed theme tags: see http://core.trac.wordpress.org/ticket/21065.

     

    • Amy Hendrix (sabreuse) 6:54 pm on July 18, 2012 Permalink | Reply

      +1 to both. There’s some ongoing discussion about what the review standards should be for responsive themes, but I see that as a separate issue to the question of having a tag — tags are about the fact that end users want to search for certain features, and responsive design isn’t a concept that’s going away any time soon. And flexible headers is an easy win.

    • Nicholas Weaver 7:25 pm on July 18, 2012 Permalink | Reply

      I think this is a great idea, not only because its a feature on WordPress.com already but because I often want to change the size dimensions (height more so then width) in twenty ten and twenty eleven as I use those themes for almost everything I do with WordPress.

      Adding the ‘flexible-header’ tag & allowing 3.4 compatible themes the ability to use the custom header feature is a must as far as I am concerned.

      Adding the ‘responsive-width’ tag isn’t a bad idea. I think as people’s expectations of themes, to be responsive, increases, this will be a patch you will have to make down the road, if you decide against it now. Definitely a step in the right direction.

      I appreciate you reaching out to me for my thoughts and I’d love to help out more in whatever way I can!

      side note: :) I apologize for the lack of Weekly Theme Shows as of late, we are really trying to get the right fit and structure down for the show to make it worthwhile to everyone who listens.

      • Amy Hendrix (sabreuse) 7:30 pm on July 18, 2012 Permalink | Reply

        Note that the features are up for grabs and any theme developer to use, and flex headers in particular are already in both Twenty Ten and Twenty Eleven — the question here is about adding the tags to the filtered search so users can specifically search for themes that include them.

        • Nicholas Weaver 7:36 pm on July 18, 2012 Permalink | Reply

          Ah, gotcha. Yeah i read trough that track ticket a little to quickly.

          Themes with those abilities are something I actively look for when dealing with clients, hence the heavy usage of twenty ten and twenty eleven. Being able to do a filtered search for themes with these features would be extremely beneficial, save time, and help to better qualify themes for selection/download, in my opinion.

    • Emil Uzelac 9:28 pm on July 18, 2012 Permalink | Reply

      There’s no doubt that this isn’t needed, both are definitive (yay).

      To check if Theme is using RWD and how much of that’s true will take as much as time as the standard review. No point really going there, unless there are some obvious issues.

      RWD is not just the layout, it’s everything else around it, such as images, videos, typography etc.

      If an author says that their design is layout super, we can take their word for it. If it’s not it will be classified as false “advertisement” (Theme Description).

      Emil

    • Konstantin Kovshenin 8:30 am on July 19, 2012 Permalink | Reply

      I like both feature tags, though I wouldn’t use “responsive-width” for several reasons:

      • it’s not clear (for the end users) how responsive-width differs from flexible-width
      • media queries can contain max-height too
      • separate stylesheets (and even markup) based on user agent strings (without media queries) achieve the same goals, except that we don’t get that funky effect we all love, when resizing our browser windows :)

      I think the feature should be called mobile-friendly, device-friendly or okay, maybe responsive-layout, but it should not fall under the width column in the tag filter: http://wordpress.org/extend/themes/tag-filter/

      Just my two cents :) I’d like to hear your opinion.

      • Lance Willett 1:42 am on July 20, 2012 Permalink | Reply

        Those are good points, it could be hard to explain “responsive-width” from “flexible-width” as you said, but I think it still stands on its own.

        I do think it’s better to add to the width category rather than not adding it at all—themes need to be able to be categorized by having responsive design.

        Should we update the width category to something new? Like “Layout” and change it to fixed, responsive, and fluid? (Flexible is ambiguous—I prefer fluid for themes with a liquid, fluid layout.)

        • Konstantin Kovshenin 2:50 pm on August 2, 2012 Permalink | Reply

          Hi, sorry never subscribed to this thread after posting.

          After discussion on Make Themes, I think a better approach is to rename
          “Widths” terms to “Layout” and change the three allowed values to “Fixed,
          Fluid, Resonsive”.

          Yes please! :)

    • Lance Willett 1:44 am on July 20, 2012 Permalink | Reply

      By the way—if anyone wants a fun read—we’ve developed a much broader taxonomy for categorizing themes including new terms for Subject and Style: https://wpcom-themes.svn.automattic.com/demo/theme-taxonomy.txt.

      It’s in use heavily on http://theme.wordpress.com/themes/ and has been well-received by people looking for themes fitting a certain look or style.

      Someday I’d like to rework the core list to include this, if possible.

    • Lance Willett 5:55 pm on August 1, 2012 Permalink | Reply

      Update: I split out the “flexible-header” and the proposed changes to width -> layout into a new ticket.

      See http://core.trac.wordpress.org/ticket/21442 for the proposal and http://core.trac.wordpress.org/ticket/21065 for just the flexible-header change.

    • Lance Willett 11:53 pm on August 24, 2012 Permalink | Reply

      The flexible-header tag is now in core with r21604.

  • Andrew Nacin 7:19 pm on September 26, 2011 Permalink
    Tags: core   

    Feedback requested on Core Trac #18548: Add a better option for <title> tags.

     

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