WordPress.org

Ready to get started?Download WordPress

Review WordPress Themes

Tagged: default-theme Toggle Comment Threads | Keyboard Shortcuts

  • Lance Willett 11:48 pm on February 18, 2013 Permalink
    Tags: , default-theme, 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

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

      Emil

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

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

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

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

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

      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

        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

      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

        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

      Remove hyphens from body.

    • shadow_catcher 2:35 am on December 10, 2013 Permalink

      I second Bjornsennbrink – at least give everyone the option of hyphenating text.

      I can’t begin to tell you how much I HATE the illiterate look of the way WP hyphenates.

  • Lance Willett 10:38 pm on September 18, 2012 Permalink | Log in to leave a Comment
    Tags: default-theme, history, kubrick,   

    Why Default Themes Change Each Year 

    Since Twenty Twelve is coming very soon to the Extend directory, I wanted to share a bit of background on default themes and why they change from year to year.

    In 2005 Kubrick launched as the new default theme, then didn’t change for five years. It became a punchline for the project. With Twenty Ten a new pattern started, with every single year having a new theme, naming it by the year. Twenty ___. This gives the theme an expiration date and it doesn’t have the pressure to be the end-all theme for the ages, because it’ll be replaced in the next year rather than in five years.

    In the time between Kubrick and Twenty Ten the default theme efforts didn’t work too well as there were too many conflicting things. The efforts tried to please everyone: show off everything that’s possible in core, fully educational in every aspect, super nice-looking, and try to solve all the problems a theme can solve.

    Big shoes to fill, as it turns out. Even if one theme can’t do it all, though, the default theme can still strive to be as simple as possible while still sticking to important principles. For example, default themes are coded to be fully internationalized and ready for translation. Even though this effort makes the code more complicated, it’s an important principle in an increasingly globalized world where many people don’t interact with WordPress in English.

    The default theme should show off the latest and greatest features, be flexible enough to gracefully support child themes and encourage customization, work well for a blog or a website, and sport a design that is aesthetically pleasing and a bit different from the last design. Under the hood it should represent the best in coding practices and technical excellence. That said, the default theme isn’t trying to be an end-all-be-all theme. It won’t please everyone.

    To get an idea of how Twenty Twelve is intended to differ from its predecessors, here’s the the core team’s post on which key features they want to see implemented: Core Team Meetup Recap: Default Theme “Twenty Twelve”. Note things like the header image off by default, promoting a static front page, and no featured image in the header. A new look by a different theme designer.

    I think a lot of people are going to really like Twenty Twelve. And Twenty Thirteen. And Fourteen. And … you get the idea.

     
    • Emil Uzelac 10:42 pm on September 18, 2012 Permalink | Log in to Reply

      Good stuff Lance!

    • Brent Leavitt 3:55 am on September 19, 2012 Permalink | Log in to Reply

      Thank you for taking to time to walk though this. I appreciate the shift to promote the static page as a home page. I’ve been using WordPress as a full blown CMS for custom website builds. That’s one of the basic switches i do with every theme that I setup. Does this theme set the static page option by default?

    • Noumaan Yaqoob 9:56 am on September 19, 2012 Permalink | Log in to Reply

      I loved 2011 and it is one of my most favorite WordPress themes of all time. Not just because it is visually pleasent with good typography and easy readibility, but mainly because it is so easy to customize and build child themes upon it. I believe that the default themes are the perfect way to learn WordPress theme development. Can’t wait for 2012, which I think is a bit late, its already september when it will be released?

    • Kim Parsell 10:08 am on September 19, 2012 Permalink | Log in to Reply

      Really looking forward to working with Twenty Twelve. :)

    • jaredatch 8:20 pm on September 19, 2012 Permalink | Log in to Reply

      Well said Lance. You guys have been doing a great job.

      • Lance Willett 10:04 pm on September 20, 2012 Permalink | Log in to Reply

        Thanks Jared—it’s been amazing to see it come together, many hands — especially at WCSF hack day; I was blown away at the contributions and couldn’t keep up with them, heh.

    • kathy@lasvegasinfocenter.com 9:26 am on September 25, 2012 Permalink | Log in to Reply

      Very informative, Thank you. It is difficult to find a theme that will do everything the web author envisions. But it must be even more difficult to try and accommodate everyone with a default theme.

    • Bachsau 7:01 pm on September 29, 2012 Permalink | Log in to Reply

      For non technical users, a huge problem arises when updates to one of the default themes are released (twentyten, twentyeleven, twentytwelve). People without FTP access and knowledge are stuck a with an english frontend even on localized versions of WordPress. Please include the locals in themes packages, so autoupdate of themes work correctly.

    • Freddy K. 4:27 pm on October 2, 2012 Permalink | Log in to Reply

      Would like to see a working menu in IE8, it only shows a “Menu” button on top and then a list of all menu-entries of the complete menu. As my menus have about 30-40 items, this is not usable on desktop.

      • Lance Willett 9:32 pm on October 29, 2012 Permalink | Log in to Reply

        You can follow along with the theme’s development and improvements over on Trac. We’ve addressed this (and many more fixes) recently.

    • LatestBlogPostsCom 12:59 am on October 20, 2012 Permalink | Log in to Reply

      Hey Lance, good article on default themes. Twenty Twelve seems to have it all for the basic WordPress user, but I like learning about all the hooks and template tags to take the basics of Twenty Twelve and twist it into something totally or even slightly different, while using it as a starting point. I do that on AssortedProducts.com.

      Also, Twenty Twelve was the one entity about anything related to web design that got me into HTML 5!

      Bruce

    • richardpd 12:27 pm on February 23, 2013 Permalink | Log in to Reply

      Hi Lance
      Interesting post. It is a tall order to showcase all new WordPress features in a new theme every year. I personally though would prefer the default theme design to stay the same for a longer period e.g. 5 years and have the new code within that year on year. Kubrick was and still is a classic WordPress theme and did a great job for 5 years. 2010 was a great change of direction but to change design every year for 2011/12/13 etc is a bit too frequent for me. I think WordPress should design a classic flagship theme that can stand the test of time for a 5 year period & that can showcase the new code year on year. I think theme design is more of a personal issue in comparison to code dependent theme function and there are benefits to keeping these seperate elements. Mais, chaque un a sans gout! Tres bonne…Best wishes

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