WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Updates from October, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Pascal Birchler 6:28 pm on October 15, 2014 Permalink
    Tags: ,   

    WordPress Core Weekly 

    Hi everyone!

    It’s time for WordPress Core Weekly (formerly known as Last Week in WordPress Core) again! There have been suggestions to change the name of these summary posts to stop confusions about being the last week of WordPress.

    This updates covers all commits since last week up to today, October 15th. There has been much progress this week with lots of improvements to the WP_*_Query classes, fixes in the admin and of course the introduction of the Twenty Fifteen theme! The complete summary:

    Admin

    • Add missing labels to category filter dropdowns. [29870] [29871] #29921
    • Differentiate between invalid and missing admin emails when adding a new site [29877] #17890
    • Multisite: Do not send a welcome notification when noconfirmation has been flagged [29880] #16235
    • Admin menu: [29898] #29806
      • Fix pinning after resizing the window.
      • Merge the two DOM ready callbacks in common.js
      • Fix the submenus position adjustment on focus.

    Editor

    • TinyMCE: fix the ‘wpgallery’ plugin to use a placeholder for galleries when either the ‘wpview’ plugin or wp.mce is not loaded. [29883] #28756
    • Quicktags: move focusing the editor after inserting content to the end of the code blocks. [29884] #29944
    • Editor-expand: reset the editor height after the window is resized. [29886] #29952

    Customizer

    • Change instances of “Theme Customizer” to just “Customizer”, as the Customizer isn’t necessarily theme-specific. [29903] #29947
    • Only POST dirty settings to preview to improve performance. [29905] #29983
    • Don’t trigger a change event if two unchanged object values are equal, second pass. [29907] #26061

    Bundled Themes

    • Add an alt attribute with the site title for header images linked to the home page. [29842] #15926

    Twenty Fifteen

    Comments

    External Scripts

    • Update jQuery UI to 1.11.1. [29847] #29833
      • Rename all files, remove the jquery.ui. prefix. Add old files to $_old_files.
      • Add and use non-minified files in /src.
      • Add grunt task to minify jQuery UI files.
      • (Non-minified files will not be shipped.)

    Language Packs

    • Language packs: Remove translations when deleting a theme or a plugin. [29856] #29860

    Internals

    • Handle deficiencies in PHP’s parse_url in older versions of PHP (<5.4.7) in WP_HTTP::make_absolute_url(). [29851] [29850] [29861] #28001, #29886
      • Correctly handle url’s containing url’s in WP_HTTP::make_absolute_url().
      • Correctly support Schemeless URLs in WP_HTTP::make_absolute_url() by respecting the ‘host’ field if present in the relative url.
    • New remove() method and some unit tests for the WP_Error class. @29854 #28092
    • Return an error when adding a term to a non-existent parent. [29867] #29614

    Queries

    Thanks to @rianrietveld, @tschutter, @netweb, @joedolson, @bramd, @Fab1en, @ocean90, @stephenharris, @boonebgorges, @georgestephanis, @jesin, @afercia, @miqrogroove, @avryl, @mboynes, @transom, @DrewAPicture, @johnrom, @matt, @iandstewart, @iamtakashi, @obenland, @cainm, @kristastevens, @karmatosed, @chellycat, @lancewillett, @kwight, @davidakennedy, @otto42, @jakub.tyrcha, @studionashvegas, @tareq1988, @westonruter for their core contributions!

    Revisions covered: [29842] to [29907]. For the complete list of commits to trunk, check out the log on Trac.

    Interested in joining in? Write or test a patch for 4.1.

     
  • Konstantin Obenland 11:57 pm on September 9, 2014 Permalink
    Tags: , ,   

    Twenty Fifteen 

    It’s that time of the year again, time to work on a new default theme!
    This year we’re back to creating a brand new design. Like Twenty Fourteen, this is being targeted for December and thus WordPress 4.1.

    @matt asked Takashi Irie to design Twenty Fifteen, and they are both closely collaborating with @iandstewart, who also worked on Twenty Ten and Twenty Eleven. The design is far from finished, but the following screenshots might give you an idea of what direction it is headed this year:

    Twenty Fifteen is a clean, blog-focused theme designed through simplicity. With careful attention to typography, the theme treats text as a major part of the user interface. It features Google’s Noto Serif and Sans – a font family designed to be visually harmonious across many of the world’s languages, and a perfect fit for the internationalization strides being made in WordPress core.

    The theme is also designed to maximize the impact of core’s customization tools – Custom Headers and Custom Backgrounds. These tools will allow any Twenty Fifteen blog to be easily personalized.

    Last but definitely not least, Twenty Fifteen uses a mobile first approach in its design, remaining attractive and focusing on an optimal browsing experience across a wide array of devices from mobile to widescreen desktops.

    All of these things come together to present content cleanly for any of Twenty Fifteen’s users – a simple default theme.

    —Takashi Irie

    Next steps will be to finish the design, create a working theme, commit that to core, and then break it and make sure it adheres to the high standards and expectations we all have for default themes.

    If you are interested in contributing, please subscribe to this blog (if you haven’t already), and leave your name in the comments. As soon as it’s ready for public breaking, testing, and patching, I’ll make sure you get a ping!

    Further reading:

     
    • Amy Hendrix (sabreuse) 11:58 pm on September 9, 2014 Permalink | Log in to Reply

      You had me at “Twenty…”

      • utahman1971 8:23 pm on December 18, 2014 Permalink | Log in to Reply

        They had me at none of the vertical menu themes. They are ugly. That navigation is old or is just set for one sided people. Kind of takes up the pages space too. Never really like the look either. I rather have something you don’t have to spend hours coding to add something to it, then use there default theme that makes you have to do extra coding. You would at least think for a CMS software that was built since 2005 would offer something free that is like a premium paid product. I guess people are right nothing is for free anymore, unless it is do all the work for something you would like on it.

        • Ipstenu (Mika Epstein) 6:11 am on December 19, 2014 Permalink | Log in to Reply

          The default theme is not something that will work for everyone. We know that. It’s an example of what you can do.

          If you want a different theme, we have over a thousand :) https://wordpress.org/themes/ All free.

        • leonp 1:57 pm on December 19, 2014 Permalink | Log in to Reply

          I rather like them. It’s easier to read down the page. “Ugly” is subjective…

          Also, a hamburger menu @ narrow screen that expands to a vertical menu @ widescreen is a pretty “modern” design pattern.

          There’s lots of space on a widescreen these days…

        • thoughtwell 3:30 pm on December 29, 2014 Permalink | Log in to Reply

          +1 for leonp’s comment—was sitting in a client meeting the other day and couldn’t help but notice how awkward large fields of negative space look on large screens and how the content just becomes so isolated looking as this happens… especially when a full-screen background image-cover is used and the photo crops strangely due to letterbox formatting… a vertical side menu would probably help even out the proportions a bit…

          Lager screens are becoming more commonplace as the price drops… and gaming consoles, televisions, htpcs, etc. have folks using browsers on their televisions (probably not a mass demo, but still considerable for some projects, depending on what is being developed… and projection screens are pretty common in company boardrooms… I guess it’s just another case of ‘the right tool for the right job.’

    • Mel Choyce 12:01 am on September 10, 2014 Permalink | Log in to Reply

      <3

    • Carbis 12:03 am on September 10, 2014 Permalink | Log in to Reply

      Very glad to see design inspiration come from twentyeleven and twentyten.

    • codel1417 12:07 am on September 10, 2014 Permalink | Log in to Reply

      Can we have a theme focused around color and design instead of something that matches an ios device. Color is good. white is boring and bland.

      • Robert Dall 12:12 am on September 10, 2014 Permalink | Log in to Reply

        This theme as it is being stated will allow users to completely customize their blog based on their customizer choices. You can see from the screenshots provided that white is just the starting point and the world is your oyster in terms of colour choice…

    • Robert Dall 12:09 am on September 10, 2014 Permalink | Log in to Reply

      Take me to your leader… Actually just direct me to his blog… Oh and seriously: Yes please let me break this theme for you…

    • Reza 12:10 am on September 10, 2014 Permalink | Log in to Reply

      Looks Good to me, at least not left align on bigger screen like 2014 :)

    • ericdaams 12:14 am on September 10, 2014 Permalink | Log in to Reply

      The link to Takashi Irie’s post about Twenty Fourteen is broken ;)

    • Eric 12:14 am on September 10, 2014 Permalink | Log in to Reply

      I’m already a fan. :)

    • bmoredrew 12:14 am on September 10, 2014 Permalink | Log in to Reply

      Awesome. Looks great!

    • Nikhil Vimal (NikV) 12:20 am on September 10, 2014 Permalink | Log in to Reply

      Howdy! I would definitely be interested in working on the next default theme!

    • Ipstenu (Mika Epstein) 12:21 am on September 10, 2014 Permalink | Log in to Reply

      Nice, I like this!

    • Ryan Cowles 12:21 am on September 10, 2014 Permalink | Log in to Reply

      Looking sharp! I’d be happy to help in whatever capacity I can.

    • Ben Lobaugh (blobaugh) 12:22 am on September 10, 2014 Permalink | Log in to Reply

      I have not been this excited about a new default theme in a few years!!!

    • Spencer Hill 12:28 am on September 10, 2014 Permalink | Log in to Reply

      Is this built using Bootstrap?

    • Josh Levinson 12:45 am on September 10, 2014 Permalink | Log in to Reply

      Can’t wait to see it made a reality! I’d love to help out in any way I can.

    • IgniteWoo 12:45 am on September 10, 2014 Permalink | Log in to Reply

      99% of the world reads left to right. Therefore, single sidebar on the left = distraction = poorer visitor experience.

      Lets hope 2015 is avoids the various design fiascos of 2014.

    • marsjaninzmarsa 12:53 am on September 10, 2014 Permalink | Log in to Reply

      Nice and clean and Material-like – I’like it! :D

    • webdevmattcrom 12:59 am on September 10, 2014 Permalink | Log in to Reply

      Looking forward to taking it for a spin and breaking stuff!

    • Michelle Langston 1:00 am on September 10, 2014 Permalink | Log in to Reply

      Love it! I’m interested in contributing however I can! :)

    • fikrirasyid 1:02 am on September 10, 2014 Permalink | Log in to Reply

      This looks really fantastic. Same here, I’m really interested in contributing :D

    • derekspringer 1:11 am on September 10, 2014 Permalink | Log in to Reply

      Almost looks like 2012 fancier, side-bar’d younger brother!

    • David A. Kennedy 1:44 am on September 10, 2014 Permalink | Log in to Reply

      Looks awesome! Ping me as well. I’ll contribute whatever code I can as well as coordinating with the Accessibility Team for testing. We’ll test for accessibility from the earliest build possible. I’d love for Twenty Fifteen to carry the accessibility-ready tag, just like Twenty Fourteen. :)

      • Graham Armfield 5:18 am on September 10, 2014 Permalink | Log in to Reply

        +1 David. accessibility-ready should be the default path from now on.

        • Olivier Nourry 9:33 am on September 23, 2014 Permalink | Log in to Reply

          I’d even go further: the default theme should be the top-of-its-class with regards to accessibility. And it should brag about it. It’s a unique and efficient way to spread knowledge about accessibility to people who usually do not care too much about it, and most of time never heard of it.

    • s.r. 1:49 am on September 10, 2014 Permalink | Log in to Reply

      Looks good! Simple and clean.
      However one thought crossed my mind why we always have “blog-focused” themes? WordPress stepped much further than just a blog CMS, so I believe WP could once in awhile make one for proper website to show how to it is done. :) Just saying

      • Graham Armfield 5:15 am on September 10, 2014 Permalink | Log in to Reply

        Totally agree with this. All of the WordPress websites I’ve created for people have been for small
        /medium sized businesses and charities. A good, modern, business-based default theme would be really useful.

      • Xavier Borderie 9:22 am on September 10, 2014 Permalink | Log in to Reply

        You mean, like the current theme, Twenty Fourteen, which is a magazine-like theme? ;)

      • Andrew Nacin 6:45 pm on September 10, 2014 Permalink | Log in to Reply

        And Twenty Twelve, which wasn’t designed to be blog-focused either.

        • Marcel Stephan 11:34 am on November 19, 2014 Permalink | Log in to Reply

          I’ve used Twenty Twelve a lot of times for small business and other, but it’s not responsive enough. So a theme based on a small business would be great.

      • faospark 7:38 am on September 26, 2014 Permalink | Log in to Reply

        I agree @ s.r. and graham. lets call things for what it is and probably do things that is current and useful. i thought sending out wodpress 2014 default theme into the wild was a huge statement from the core the were moving out from this blog type of themes like wordpress 2013 default and yeah maybe 2012 was designed not be blog focused but come’on sir Nacin. look at on how 2012 default theme looks like? it does not require one to be a rocket scientist to figure out that it was meant for a blog. I appreciate the work of the core but for this theme release im little bit not ease with it. i like the look of the theme but the fine print tells me that more likely its gonna downloaded by users but be kept unused.

      • Ian Stewart 8:26 pm on October 1, 2014 Permalink | Log in to Reply

        You should write a blog post about this with some visual examples — or even an example, working theme. It’d be great to see more ideas and discussion around default themes. You can have an impact here. Everyone can. And it doesn’t hurt to start thinking about Twenty Sixteen sooner rather than later.

    • Brent Logan 1:50 am on September 10, 2014 Permalink | Log in to Reply

      Beautiful already. Please ping me.

    • cramdesign 1:53 am on September 10, 2014 Permalink | Log in to Reply

      I’m in. Ping me.

      Where is the appropriate place to discuss the design? Here?

    • Philip Arthur Moore 2:47 am on September 10, 2014 Permalink | Log in to Reply

      > create a working theme

      What’s your game plan for the codebase? You had some awesome food for thought post-2014.

    • Philip Arthur Moore 2:48 am on September 10, 2014 Permalink | Log in to Reply

      Also, ping me. Always happy to help break this stuff. :)

    • Nick Halsey 3:02 am on September 10, 2014 Permalink | Log in to Reply

      I’ll help out again, as time allows with ongoing Customizer work I’m exploring.

      It’s good that Twenty Fifteen will emphasize headers and backgrounds to this extent, right as we re-imagine media in the Customizer (including a new Background Image control) and hopefully officially deprecate and (conditionally) redirect the standalone header/background screens in 4.1.

      Let’s make sure we leverage and showcase some of the new things that the Customizer can do in the code. I already see potential for a conditional-contextual control for header/sidebar color when there is no image, for example. Most importantly, we should show how simply the Customizer can be leveraged by themes by keeping the code side minimal. A versatile theme like this is made even more powerful by giving users the power to achieve a custom design without code (or too many options).

      Given the visual similarities to Twenty Twelve, are we planning on only shipping the three most recent themes with new installs, or will we be keeping Twelve in new installs still? The problem with dropping it is that it’s the only “CMS”-oriented theme of the last four bundled ones, whereas we would now have two blog themes. But given the visual similarities and the clear advantages to the newer one, I think Twelve should be dropped (and it’s easy enough to grab from the repo if wanted).

    • Japh 3:07 am on September 10, 2014 Permalink | Log in to Reply

      <3

    • doughamlin 3:36 am on September 10, 2014 Permalink | Log in to Reply

      Very interested in helping.

    • rilwis 4:08 am on September 10, 2014 Permalink | Log in to Reply

      I love the design, simple and beautiful. It’s very convenient to use for a personal blog.

    • Zulfikar Nore 4:18 am on September 10, 2014 Permalink | Log in to Reply

      Interested in helping and ready to start breaking when you are.

    • Zoe Rooney 4:22 am on September 10, 2014 Permalink | Log in to Reply

      I’d be happy to help as well!

    • Sujay 5:00 am on September 10, 2014 Permalink | Log in to Reply

      Would be happy to contribute!

    • Morten Rand-Hendriksen 6:05 am on September 10, 2014 Permalink | Log in to Reply

      I’m all in. Hit me up.

    • Chris Lema 6:28 am on September 10, 2014 Permalink | Log in to Reply

      Looks great. I’m in.

    • Sakin Shrestha 6:29 am on September 10, 2014 Permalink | Log in to Reply

      Nice and Clean Design. Simply Love it. Thanks and will check in more detail.

    • Slobodan Manic 6:36 am on September 10, 2014 Permalink | Log in to Reply

      Looks really nice. I’d be happy to contribute.

    • Tarık ÇAYIR 6:57 am on September 10, 2014 Permalink | Log in to Reply

      Simple and new modern design.

    • LittleBigThings 7:16 am on September 10, 2014 Permalink | Log in to Reply

      It looks very nice.
      I am happy to follow the development of a default theme for the first time.

    • Caspar 7:20 am on September 10, 2014 Permalink | Log in to Reply

      Looks nice, ping me when you need it broken.

    • blumenberg 7:49 am on September 10, 2014 Permalink | Log in to Reply

      I would be happy to help, count me in. (^_^)

    • Michel - xiligroup dev 8:02 am on September 10, 2014 Permalink | Log in to Reply

      As author of multilingual plugin named xili-language and child themes of bundled themes like twenty fourteen.
      As done previously in tracs, I am ready to contribute – by example – to add some filters at right place : this will avoid un-registering some widget to after clone it with including customisation of query… ( Don’t hesitate to question me.

    • zomidaily 9:34 am on September 10, 2014 Permalink | Log in to Reply

      Wow… can’t wait to see another great default WordPress theme.

    • Nashwan Doaqan 10:00 am on September 10, 2014 Permalink | Log in to Reply

      It looks really Nice!! .. waiting for it :)

    • fritoebola 10:25 am on September 10, 2014 Permalink | Log in to Reply

      December ???!!!!!!! But we want it NOW!!!!! 4.0 is live!!!! :'(

    • Jack Lenox 10:40 am on September 10, 2014 Permalink | Log in to Reply

      Woot!

    • Torsten Landsiedel 11:41 am on September 10, 2014 Permalink | Log in to Reply

      I’m in, too! And this comment section should be read by everyone who is participating. Great thoughts!
      http://konstantin.obenland.it/2013/12/19/twenty-fifteen/

    • Sharon Austin 12:37 pm on September 10, 2014 Permalink | Log in to Reply

      Definitely. Ping me.

    • Jose Castaneda 12:53 pm on September 10, 2014 Permalink | Log in to Reply

      I’m for any direction you choose in order to try and break this. Will this theme be a11y-ready?

    • Tracy Rotton 1:09 pm on September 10, 2014 Permalink | Log in to Reply

      ::hand raised::

      Looking forward to contributing on this!

    • WP Sites - Brad Dalton 1:48 pm on September 10, 2014 Permalink | Log in to Reply

      Ping me please when ready. Thanks

    • Tammie 2:30 pm on September 10, 2014 Permalink | Log in to Reply

      Looks great! I’m excited to see and poke this around. I’d love to help in any way.

    • Yojance 2:53 pm on September 10, 2014 Permalink | Log in to Reply

      This looks amazing. Can’t wait to try it on my site.

    • Tracy Levesque 3:47 pm on September 10, 2014 Permalink | Log in to Reply

      Yeah :-D

    • firewatch 5:46 pm on September 10, 2014 Permalink | Log in to Reply

      Ping me please. :)

    • Dave Clements 5:51 pm on September 10, 2014 Permalink | Log in to Reply

      Looks great guys, though I have to say, I think I was more excited to see a picture of what I believe to be the West Pier in Brighton (my hometown) featured so prominently.

    • Mary 6:07 pm on September 10, 2014 Permalink | Log in to Reply

      I’m really excited to see this! Please count me in for contributing wherever I can be helpful.

    • David Marichal 6:46 pm on September 10, 2014 Permalink | Log in to Reply

      Looking forward to contributing. Ping me.

    • Joan Artés 7:23 pm on September 10, 2014 Permalink | Log in to Reply

      It will be an honor to contribute. Ping me :)

    • Eduardo Reveles 9:40 pm on September 10, 2014 Permalink | Log in to Reply

      o/

    • Alex Vasquez 6:08 am on September 11, 2014 Permalink | Log in to Reply

      I guess it’s okay. If you’re into that kind of thing. =)

    • michaelaterndrup 1:53 pm on September 11, 2014 Permalink | Log in to Reply

      Looking forward to it I try to create my own theme but fail…

    • techjewel 5:32 pm on September 11, 2014 Permalink | Log in to Reply

      Awesome!

    • Jesper Johansen (jayjdk) 10:41 pm on September 11, 2014 Permalink | Log in to Reply

      Looks very nice. Ping me please :)

    • memuller 1:16 am on September 12, 2014 Permalink | Log in to Reply

      Nice and simple – I like it.
      Count/ping me in.

    • menkom 3:29 am on September 12, 2014 Permalink | Log in to Reply

      Hmmmmm… am i the only one that does not like it…. seems extremely bland and limited…. i guess i have to see the final result..

    • Gaurav Tiwari 2:23 pm on September 12, 2014 Permalink | Log in to Reply

      Simple and Trendy theme. And the best, it is ‘really’ readable.

    • Stephen Edgar 10:33 pm on September 12, 2014 Permalink | Log in to Reply

      Impressive, much like :)

    • chrissyrey 2:57 am on September 13, 2014 Permalink | Log in to Reply

      Count me in!

    • Ahmad Awais 4:52 am on September 13, 2014 Permalink | Log in to Reply

      Design is lovely. I am a big fan of Minimal Themes. Looking forward to build & contribute the frontend of this theme. Count me in.

    • Haseeb Ahmad Ayazi 3:19 pm on September 13, 2014 Permalink | Log in to Reply

      Nice theme actually. It will suits the WordPress 4.1 , try to make it more customizable. I am too much tired of using third party themes.

    • abe_charles 3:42 am on September 14, 2014 Permalink | Log in to Reply

      While I think that Twenty Fifteen looks promising, it is light years behind what it should be and I understand it’s still being worked on but it need excerpts as many great themes nowadays employ those features and not just pictures in the same rows as texts but videos as well.

      Twenty Fifteen needs to have more colours. The white thing is too plain as is. If it’s going to have a white background predominantly it needs some flavour to it.

      Plus the menu bar should be interactive with the ability to show images and a mega menu when the cursor hovers over it and if that is not in by default it should be in the theme’s options. All cards should be on the table or at least in the theme’s options.

      Those are my suggestions. Keep the screenshots coming. I am glad that things developed on this theme so quickly.

    • Eric Lewis 3:37 pm on September 14, 2014 Permalink | Log in to Reply

      I think we’re missing out on an opportunity to doing something Javascript-forward here. Aaron Jorbin proposed something similar for Twenty Fifteen, and I’d like to echo his thoughts.

      The WP API would benefit greatly were a default theme built on top of it. We have an API that needs real world usage – what’s more real world than a default theme that ships to 20% of the web?

      We can introduce non-trivial front-end Javascript to theme developers, which would be a great educational service for the community.

    • abe_charles 3:45 pm on September 14, 2014 Permalink | Log in to Reply

      Suggestion: Try to make the excerpts on this theme be set or defined by featured images without having the featured image eclipse the post on the main page like in the default Twenty Fourteen theme.

    • abe_charles 3:53 pm on September 14, 2014 Permalink | Log in to Reply

      Suggestion: Make items in a menu bar be of different colours by default or customizable, similar to the effect the “Fourteen Colors” plugin has on the Twenty Fourteen theme. But this should be a built in feature in the Twenty Fifteen theme and it would be great if when hovered over a menu item the set featured image associated with the posts or some of the traits of the posts or posts themselves be displayed for a particular menu item or category be displayed, like a modern menu.

    • abe_charles 1:12 am on September 15, 2014 Permalink | Log in to Reply

      Suggestion: It would also be great to have a slider with featured posts like the one in Woothemes’ “Headlines” theme and excerpts as i have been saying all this time is key and we need a theme with a decent type of font. No crappy fonts please. it takes away from the greatness of the theme.

    • ajay.khullar2 7:44 pm on September 22, 2014 Permalink | Log in to Reply

      The link to Takashi Irie’s post about Twenty Fourteen is broken again :)

    • Emil Uzelac 9:59 pm on September 22, 2014 Permalink | Log in to Reply

      Look nice on any device! <3

    • Patrick Rauland 2:14 pm on September 23, 2014 Permalink | Log in to Reply

      Always happy to help break things Obenland! :)

    • ThatChris 10:46 pm on September 23, 2014 Permalink | Log in to Reply

      I’m in! :)

    • Paal Joachim Romdahl 11:29 pm on September 23, 2014 Permalink | Log in to Reply

      What features could be added to Core that would also help make the theme even better/easier to use/etc? I am thinking that a subgroup who are working on the theme could also be working on improving aspects of Core at the same time.

    • Ahmad Awais 4:44 am on September 24, 2014 Permalink | Log in to Reply

      @konstantine any further news about how and when we are going to contribute?

    • activedirectory-faq 7:39 am on September 24, 2014 Permalink | Log in to Reply

      Looks nice and is much more my taste than twenty fourteen

    • iluchen 2:40 pm on September 25, 2014 Permalink | Log in to Reply

      wonderful!

    • Justin Kopepasah 12:46 am on September 28, 2014 Permalink | Log in to Reply

      Yet another awesome looking theme for core. Looking forward to digging in to it!

    • aglaonika 10:26 am on September 30, 2014 Permalink | Log in to Reply

      Great design. Would like to join if I didn’t miss the deadline.

    • vishal_chitnis 6:01 pm on October 6, 2014 Permalink | Log in to Reply

      Nice, looking forward to contributing

    • Siobhan Bamber (siobhyb) 10:00 pm on October 6, 2014 Permalink | Log in to Reply

      If you are interested in contributing, please subscribe to this blog (if you haven’t already), and leave your name in the comments. As soon as it’s ready for public breaking, testing, and patching, I’ll make sure you get a ping!

      I’d like to help test when it’s ready too!

    • Tony Ketteringham 3:25 am on October 8, 2014 Permalink | Log in to Reply

      Happy to help as well if you need any more.

    • ianarmstrong 10:50 pm on October 10, 2014 Permalink | Log in to Reply

      I have some concerns that the default layout isn’t keeping up with what we know about user experience. I would love to see a priority placed on purpose -> pitch -> call to action in terms of how the information is presented.

      One of the big trends in design right now is the use of subtle animations to help the user better understand [a] what they just did and [b] what they are supposed to do next. I’d like to see these types of animations callable by class, so that if we create a class called .t15_button it’ll automatically use the appropriate styles.

      While I’m happy to see the theme going back to a cleaner look, there is so much more that it can be. WordPress twentyX series dictates the course of design for all non-premium themes across tens of thousands of sites. I think it would be unfortunate if we stepped back to TwentyTwelve, updated for HTML5 flexbox support and schema.org compatibility.

    • gd6d 7:56 pm on October 11, 2014 Permalink | Log in to Reply

      Would be happy to contribute too!

      • gd6d 7:50 am on October 17, 2014 Permalink | Log in to Reply

        If no menu is activated, the pages title are not visible in the sidebar. If you delete the conditional “if has menu” line 12, sidebar.php, it works fine… Is it going to stay?

    • Maria Antonietta Perna 10:45 am on October 15, 2014 Permalink | Log in to Reply

      Nice clean look for this new theme. I’m always eager to update my knowledge of WP theme development and best practices through the latest default theme, therefore I hope the code is clear to understand and generously commented and that the features that WP offers are made use of, especially the Customizer. I look forward to seeing the proper ways of adding the customization options that most users expect in themes using the Customizer in the default theme, especially after the WP upgrade to v.4. My sincere thanks to this awesome community.

    • dariodev 12:52 am on November 12, 2014 Permalink | Log in to Reply

      Looks great! Ping me, please!

    • Avi_Lambert 10:57 pm on November 14, 2014 Permalink | Log in to Reply

      Woot! Looks like a mobile first theme.

    • Jincheng Shan 11:19 am on November 15, 2014 Permalink | Log in to Reply

      Why Twenty Fifteen didn’t include tag.php and category.php although in archives.php it says Twenty Fifteen has already included them?

    • Fabrizio Pivari 2:11 pm on November 15, 2014 Permalink | Log in to Reply

      Can you add in social menu 500px and tunblr icons?

    • sonisitez 9:34 am on November 16, 2014 Permalink | Log in to Reply

      Im waiting :)

    • divnull 9:17 am on November 17, 2014 Permalink | Log in to Reply

      Wow! Glad to see the spirit of 2011 and 2012 is back! Clear, crisp, simple. I’m happy to skip 2014. :-)
      Good job! :-)

    • wassem mansour 5:29 pm on November 17, 2014 Permalink | Log in to Reply

      Twenty Twelve Rules Forever :)

    • ncjcj 8:56 pm on November 17, 2014 Permalink | Log in to Reply

      I am going to update one the two volunteer sites I keep. It calls for the global nav to be horizontal at the top with drop-down menus.

      Can this be easily achieved with a child-theme (I write my own css) and does the core funtionality easily allow for drop-downs?

      I wanted to use the 2015 just because they get out of date so fast.

      Thanks

      Nancy

    • suzettefranck 11:30 pm on November 19, 2014 Permalink | Log in to Reply

      My blog theme is a child I made of Twenty Thirteen since Twenty Twelve. I think I will have to upgrade to Twenty Fifteen, can’t wait to see how it turns out. I use Twenty Fourteen on all my new blogs, but loved my girlie child theme.

    • David Favor 8:59 pm on November 20, 2014 Permalink | Log in to Reply

      Theme Check reports following (very minor) problems with Twenty Fifteen.

      REQUIRED: The theme needs to have a call to wp_title(), ideally in the header.php file.
      REQUIRED: The theme needs to have tags, ideally in the header.php file.<br /> REQUIRED: The theme doesn’t have post pagination code in it. Use posts_nav_link() or paginate_links() or next_posts_link() and previous_posts_link() to add post pagination.

    • Monika 9:12 am on November 25, 2014 Permalink | Log in to Reply

      hi my first feedback to Twenty Fifteen :-)
      I love the typographie and the elegance of this theme.

      I can’t understand:
      $content_width = 660;
      but the postthumbnail size is set to 825
      set_post_thumbnail_size( 825, 510, true );

      Why is the default thumb bigger than content width?

      This theme has one widget area.
      In source the widget area appears before the main content => this is a really strange design pattern

      If someone would like to have a very good position on search engines I can’t recommend to use this theme because the sidebar appears before the main content in source.

      And is it possible to decrease the http requests for styles and scripts? Everybody is loving a fast website :-)

      I know I can use a child-theme to create a second widget area under the content and use the first sidebar only for navigation, combine scripts and so on.

      Thanks

      Monika

    • Sunnyj 6:51 am on November 28, 2014 Permalink | Log in to Reply

      Noto Sans is a bad choice, very poor quality hinting on the digits 1234567890, especially at 14px or less they will get noticeably blurry. Better off sticking with Open Sans or something else imo.

    • gd6d 5:59 pm on November 30, 2014 Permalink | Log in to Reply

      I use this theme on my website. I have a problem with SEO plugin like Yoast or All in One. I can’t save any change on title or description fields… I had to change the theme, make my corrections, save, and return to Twentyfifteen…

    • Sami Niemi 12:17 pm on December 4, 2014 Permalink | Log in to Reply

      I need to have Twenty Fiveteen for my site :)

    • Edward R. Jenkins 8:47 pm on December 6, 2014 Permalink | Log in to Reply

      Interested in contributing and/or testing!

    • wholroyd 7:30 pm on December 10, 2014 Permalink | Log in to Reply

      Looks like the Flat theme from YoArts, but the article tail looks better and I hope you can put widgets in other places than just in the left menu column.

    • OlalaWeb 9:47 am on December 17, 2014 Permalink | Log in to Reply

      Hi all! Ping me as soon as Twenty Fifteen is released! We’d love to create a Child Theme :)

    • praveenrk 10:10 am on December 18, 2014 Permalink | Log in to Reply

      Great themes …..cool work

  • Helen Hou-Sandi 8:30 pm on May 6, 2014 Permalink
    Tags: ,   

    Summary of last week’s dev chat on 4/30 (IRC log):

    Announcements

    Features as plugins

    • Met on 4/29 (IRC log)
    • Current potential considerations seem to be WP API and media grid.
    • Press This is getting some attention from an early stages working group, which could also be a part of the 4.0 release.
    • Admin Help is poised to shift into more of a continuous testing and advisory group, which is awesome.
    • Front-end editor is making good progress, but has UX issues that are getting worked on, needs iteration and experimentation and probably won’t be ready by 4.0, but should continuously be worked on, as is the goal of features as plugins in the first place. Developers needed.

    Potential ideas and their suggesters:

    Summary: we have good things in mind about more media improvements, more editing experience improvements, more visual media grid and better plugin installer experience (following in the footsteps of themes), and behind the scenes wins in taxonomy, multisite, and post type and comment APIs.

    If you’re interested in any of the above or have other ideas, please sound off in the comments.

    Getting involved

    • We are always looking for more people to be involved with Trac gardening, patch review, patch writing, or some combination thereof.
    • Component pages are running well, and most could still use the caretaking of a component owner or somebody who’d like to become well-versed in a particular area of core. To get started, just sign up for component notifications at https://make.wordpress.org/core/notifications/. No need to be an expert now – learning and persistence is more important.To help with a specific plugin, join their weekly chats and/or follow along wherever they post. See the Features as Plugins page for more information.
    • A reminder from @matt to always be dogfooding the product – use WordPress every day.

    Bonus punnage, to the lead’s chagrin:

    > wonderboymusic will make a t-shirt for anyone who gets all 16 of those Cache tickets closed :)
    > sams: “Cache Master”?
    > wonderboymusic: Johnny Cache
    > jorbin: If you fix the Cache, you’ll get the Credit. That Checks out.
    > MarkJaquith: I’d put in a cache pun, but I don’t want to be sent to purgetory.
    > johnbillion: You would have to be a cache machine to fix all 16

     
  • Andrew Nacin 9:26 pm on December 31, 2013 Permalink
    Tags: ,   

    Commit announcements for 3.9 

    Lots of news to share! First: Helen Hou-Sandí has had guest commit for the past three release cycles. She’s been spending the last year reviewing contributions, mentoring contributors, and working on some of our larger UI projects. I’m proud to announce @helen is now a permanent committer to WordPress!

    We’ve invited John Blackbourn (@johnbillion) to be a committer for the 3.9 cycle. His strong, consistent contributions have been backed by excellent judgment and temperament.

    Matt Thomas, who led the dashboard redesign in 3.8 (and 3.2, and 2.7, etc.), will keep his commit to continue to maintain and improve WordPress UI. He’s been a great mentor to many contributing designers and his long-term impact is indelible.

    For the last few years, we’ve been granting commit access on per-cycle basis, sometimes for a particular component, feature, etc. Generally, after about a year, a guest committer can be considered for permanent commit access. Dominik Schilling, Sergey Biryukov, Drew Jaynes, and Scott Taylor have all had their commit extended for 3.9.

    Drew (@DrewAPicture) was given temporary commit for inline documentation starting with 3.7. He’s been heading up the long-running initiative to document every hook in WordPress. Scott (@wonderboymusic) also started committing during 3.7, and has a particular penchant for digging deep into the query and taxonomy APIs. And Sergey (@SergeyBiryukov) and Dominik (@ocean90), well, they are forces of nature.

    (@aaroncampbell was also given guest commit in 3.7, but he ended up not having much time to use it.)

    Here’s a full list of those with permanent commit: @markjaquith, @ryan, @westi, @matt, @azaozz, @dd32, @koopersmith, @duck_, @helen, and me (@nacin); @lancewillett for bundled themes; @iammattthomas for UI. You might have also seen commits before from @josephscott (XML-RPC), @nbachiyski (internationalization), and @mdawaffe (secret weapon for really tricky problems).

    Next weekly meeting is January 8. Happy new year, everyone. Here’s to a great 2014.

     
  • Matt (Thomas) Miklic 7:33 pm on November 11, 2013 Permalink
    Tags: , fonts, open sans   

    Open Sans, bundling vs. linking 

    In Wednesday’s 3.8 planning meeting we discussed hotlinking vs bundling Open Sans. MP6 followed Twenty Twelve’s example by linking to Google Webfonts, but the consensus from Wednesday’s chat was that bundling would be preferable.

    I began experimenting with this last week; first determining which font formats were necessary to include. I settled on WOFF and SVG as the two formats that would cover every browser we’re aiming to support. I left out TTF and EOT as they add only marginal browser support (IE8), but would add significant weight to the WordPress download. We do include TTF and EOT versions of Dashicons, since loading those icons is essential to usability in a way that loading Open Sans is not.

    The bundled Open Sans webfonts come from FontSquirrel. The Western Latin and Basic Latin subsets are small and include enough characters for English language support. Those subsets do not include a full set of glyphs for other languages, however (they’re available as separate downloads). There is a non-subsetted version of the font available which includes all necessary glyphs, but it’s 2x–2.5x the file size of the subsetted fonts, which add significant overhead to the pageload and can actually crash some mobile browsers. The Western Latin and Basic Latin subsets can cause missing characters (spaces or boxes) to appear in text using accented characters, which is a significant usability concern.

    Google Webfonts solves both the character set and the font format problems by intelligently loading the font format and the character subset that’s needed for a particular browser and a particular website, and nothing more. For us to bundle Open Sans with WordPress, we need a way to accomplish that without adding significant heft to the core WP download. I’m starting this P2 thread to open up the discussion on how we might do that.

     
    • Matt Mullenweg 7:43 pm on November 11, 2013 Permalink | Log in to Reply

      It’s also worth noting if we can solve this in a standalone way (the script not loading any of the rest of WP) we avoid licensing issues and also solve a general problem many people across the web have.

      Also keep in mind if this takes longer than a few days the right answer for 3.8 might be linking in core and releasing a plugin for people that bundles for people that don’t like Google.

      • Piet 4:28 am on November 12, 2013 Permalink | Log in to Reply

        I think it doesn’t have so much to do with liking or not liking Google. There are certain countries where Google is blocked and that includes loading their fonts. For all sites I built (I live in China), I bundle fonts, because only then I can be sure that these fonts load.
        That might be another argument pro-bundling :)

        • krembo99 6:03 am on December 22, 2013 Permalink | Log in to Reply

          I am with Piet – Have the same problems in china ( and elsewhere – granted – all totalitarian regimes, but still .. ). Google services work only sporadically . Fonts , jQuery CDN , Maps etc. Linking those resources makes the page time-out .

    • Doug Wollison 8:41 pm on November 11, 2013 Permalink | Log in to Reply

      Regarding the missing characters, don’t just about all browsers fallback to the next font in the font-family list for those characters?

    • mindctrl 8:46 pm on November 11, 2013 Permalink | Log in to Reply

      Relying on a third party for fonts in core doesn’t make me want to do cartwheels. It’s a backdoor analytics of sorts, and a privacy concern. The increased file size is the lesser of two evils. Neither option is ideal.

      I love Open Sans, but given the two options, I’d rather see Arial. *runs for cover*. I just tested swapping out Open Sans for Arial in trunk, and it’s really not that bad. Theming the WP admin/MP6 via plugins would be a great way for people to opt into hosted font solutions.

      • Doug Wollison 9:21 pm on November 11, 2013 Permalink | Log in to Reply

        Or, the better compromise; Helvetica (Neue if possible), finally falling back to Arial if things get desperate.

        • mindctrl 9:26 pm on November 11, 2013 Permalink | Log in to Reply

          I thought the same thing originally. Helvetica Neue isn’t that bad, but it’s also not standard on a number of platforms. Neither is Helvetica. This was news to me. I don’t know of a definitive list online, but this one from MailChimp is helpful, and the reason I said and tried Arial. http://templates.mailchimp.com/design/typography

          • mindctrl 9:27 pm on November 11, 2013 Permalink | Log in to Reply

            Sorry, actually standard Helvetica is.

            • jwarren 11:09 am on November 13, 2013 Permalink

              If we’re going with system fonts, it should probably just be standard ‘san-serif’, which will be Helvetica on OSX, Arial on Windows, and whatever has been deemed appropriate on the Linux distro of choice. It also allows people and browsers to override that easily for their own purposes – perhaps a different language, perhaps extra visual clarity, perhaps an unusual display technologo… who knows?

    • Robert Dall 9:41 pm on November 11, 2013 Permalink | Log in to Reply

      I have never really like relying on a third party service to do what could be done internally.

      Also what if you are developing locally without access to the internet?

      Regardless of who provides the free service. One day Google (or Adobe who just started there own free font embedding service) “could” turn around and say. “Ya were not going to do that free font thing anymore”

      Now it would be easy to swap it out but why rely on something like that anyways.

      • Matt Thomas 9:50 pm on November 11, 2013 Permalink | Log in to Reply

        To be clear, we’re talking about linking to Google Fonts for Open Sans just until we can solve this in a standalone way, as @matt mentioned above.

        If you’re working locally with no internet connection, the fonts will just fall back to the browser-defined “sans-serif” font (Helvetica on OS X, Arial on Windows by default).

    • Ryan Hellyer 10:04 pm on November 11, 2013 Permalink | Log in to Reply

      I suspect that bundling scripts into WordPress core will create privacy concerns for many people. The ability to perform analytics via them will disturb a small segment of the user-base.

      It may even be illegal in some countries. Germany springs to mind in regards to that. They’re already super ticked off about being spied on at the moment, so I think it might be best if WordPress doesn’t join the party too.

      And yes, you can install a plugin to force them to be self-hosted, but many people will just unwittingly hit the “update” button without ever realising that they’re opening themselves up to privacy issues.

      • Doug Wollison 10:10 pm on November 11, 2013 Permalink | Log in to Reply

        What if we take a progressive enhancement approach? By default, we wouldn’t actually load Open Sans from anywhere, and instead just falls back to whatever font it can. Then we offer plugins (or packaged right in the core) options for self hosted or google hosted.

      • daveshine (David Decker) 11:49 pm on November 11, 2013 Permalink | Log in to Reply

        Almost any modern theme loads Google Fonts already, including some of the default themes, plugins not counted…

        I have absolutely nothing against loading Open Sans from Google, and find it a rather good option to do so.

        Yes, there are lot of issues with privacy that should be done better – in my opinion this topic here falls not amongst them…. just my personal view.

        Thanks, Dave from Germany :)

    • Dion Hulse 11:14 pm on November 11, 2013 Permalink | Log in to Reply

      There is a non-subsetted version of the font available which includes all necessary glyphs, but it’s 2x–2.5x the file size of the subsetted fonts, which add significant overhead to the pageload and can actually crash some mobile browsers.

      If we actually want to use Open Sans for WordPress, this is unfortunately what we have to do.

      • Open Sans (WOFF+SVG for Italic, Regular, SemiBold, and SemIbold+Italic) weighs in at 576K uncompressed (92K WOFF, 484K SVG), 174K compressed.
      • Open Sans (WOFF+SVG for Italic, Regular, SemiBold, and SemIbold+Italic w/ full charset support ) weighs in at 4.5MB uncompressed (345K WOFF, 4.2MB SVG), 826K compressed.

      The SVG’s will compress well as they’re just text, WOFF is already compressed. We could have a light-weight PHP script that served compressed documents intelligently depending upon the client (selectively adding Charsets based on WPLANG / browser UA), but this has caching issues amongst other things.

      If we actually look at what the fonts are for though…

      • WOFF is the primary font, it’s supported by most browsers.
      • SVG is included for iOS 3.2-4.3 support, and for Android Browser 4.0-4.3.

      Given the significant size of SVG fonts, it makes me question if we should be using them at all, it doesn’t add much extra browser support.

      An alternative is shipping with WOFF+TTF fonts – that would add support for iOS 4.2-4.3 (iOS 3.2 misses out), and Android 2.2-4.3 (SVG only works for 4.0-4.3).

      • Open Sans (WOFF+TTF for Italic, Regular, SemiBold, and SemIbold+Italic w/ full charset support ) weighs in at 1,000K uncompressed (345K WOFF, 661KB TTF), 689K compressed.

      or.. just drop Open Sans for those mobile clients.. since it really doesn’t seem worth it.. WOFF supports most desktop browsers and modern mobile devices, and we should have a GOOD font fallback list for unsupported browsers (which we don’t currently have with MP6, but we did previously have in WP 3.6).

      • Dion Hulse 11:22 pm on November 11, 2013 Permalink | Log in to Reply

        I also missed that SVG is also for Mac Safari 3.2-5.0, not just for iOS. TTF is supported in Safari 3.1-5.0 as well.
        TTF/SVG is also needed for older Opera versions (desktop and mobile, and some gaming systems), but WOFF is supported for v11+ so that doesn’t seem like a deal breaker at all (coming from an Opera user..)

      • Matt Thomas 11:48 pm on November 11, 2013 Permalink | Log in to Reply

        I don’t recommend using the un-subsetted font for any solution because of the extra page weight that every user would incur. Intelligently loading the correct subset for the specified language is the best possible user experience, whether it’s linked to from Google fonts or we implement our own solution that accomplishes the same result. Just for comparison, this is the size difference for a single weight and style of Open Sans (we need four: regular, italic, semibold, and semibold italic).

        • English subset, WOFF: 13 KB
        • Czech subset, WOFF: 17 KB
        • Full charset, WOFF: 85 KB
        • English subset, SVG: 32 KB
        • Czech subset, SVG: 70 KB
        • Full charset, SVG: 1.1 MB
        • Dion Hulse 12:01 am on November 12, 2013 Permalink | Log in to Reply

          So yes, I’d never suggest SVG for this.. ever..

          WOFF however, we can get away with including the full set, the extra page load isn’t significant once it’s in the cache.

          Most web services will get away with only loading one subset as they know what the characters on the page are, WordPress doesn’t really know the answer to this, French accented characters can appear in an English post, etc.. so relying upon WPLANG is a rather bad idea for this.

          One method would be to have Javascript detect the characters on the page and load the english by default, and optionally load the larger CSS if it spots any of those characters..

          Even Google Fonts requires you to specify which subsets you want to load, it can’t automatically guess what’s on the page.. so it’ll have the same page load issues (except that you gain benefit from their extra-special browser compression and CDN).

    • davelab6 5:30 am on November 12, 2013 Permalink | Log in to Reply

      Disclaimer: I consult for Google, Adobe and other companies on web fonts and libre fonts issues, but I represent only myself. This is my own personal opinion.

      One day Google (or Adobe who just started there own free font embedding service) “could” turn around and say. “Ya were not going to do that free font thing anymore”

      Anyone can see that Google uses the Fonts API for its own web apps and web pages. Since the fonts are libre licensed, if that day ever comes, switching is possible.

      If you’re working locally with no internet connection, the fonts will just fall back to the browser-defined “sans-serif” font (Helvetica on OS X, Arial on Windows by default).

      If you’re working locally, you can install the fonts, and if the CSS includes them with ‘local’ (as the Google Fonts API css does) then they’ll load :)

      For WordPress to self host the fonts, in a way that matches the fonts served by Google’s Fonts API, you’ll want to subset them by language, and also have versions with the hinting removed to serve to browsers on platforms that don’t use hints, and perhaps also CFF versions for platforms with good CFF rendering. Since WordPress doesn’t have a dynamic font subsetter, you’ll need a set of language subsets and a set of hint subsets.

      WOFF, SVG, TTF, EOT is needed for full browser support, in descending order of importance. If you leave out formats, you will leave out users. Maybe that matters, maybe it doesn’t.

      By using the Google Fonts API you support all users on all platforms. The API doesn’t carry a cookie, so there aren’t the same privacy implications.

      • Matt Thomas 4:15 pm on November 18, 2013 Permalink | Log in to Reply

        Thanks Dave, this is good information to have. Aside from the font format issue — I think we could get by with WOFF and SVG or TTF, based on the browsers we have chosen to support (others would just fall back to browser-standard sans-serif as in 3.7). But hinting and internationalization are big issues that will be thorny to solve with a bundled solution.

    • jwarren 11:14 am on November 13, 2013 Permalink | Log in to Reply

      I would suggest that bundling would be ideal – who know what strange systems WordPress could be running on if/when Google eventually deprecates their fonts service? It also keeps the experience consistent for any isolated environments. Local development away from a consistent internet connection is not an infrequent occurrence, and the fewer 404s, the better.

    • toscho 3:17 am on November 17, 2013 Permalink | Log in to Reply

      MIME types for fonts are not always set up properly on the web server. I just had such a case recently, where the browser showed garbage on first load because of that. The second load took the fonts from cache, and the browser applied the correct glyphs.

    • Louy Alakkad 2:25 pm on November 17, 2013 Permalink | Log in to Reply

      How about using the ‘open-sans’ fonts by default and giving the user three options in theme settings, first is open-sans, second is google fonts and third is downloading a plugin that contains all the fonts needed?

    • Anderton 1:08 am on November 18, 2013 Permalink | Log in to Reply

      Also, Google is blocked in some countries (i could for example not use Google Fonts in China now and then). Now this is no issue with the bundling open san. But for reference: http://www.google.com/transparencyreport/traffic/disruptions/#expand=Y2013

    • Milan Dinić 4:50 pm on November 18, 2013 Permalink | Log in to Reply

      I vote for ditching Open Sans for reasons already mentioned in this thread:

      • Why would we all of sudden rely on external service for essential part of WordPress that is admin area? Then why don’t we also load jQuery from Google, at least that way there would be real benefit since it would save billions of request?
      • Why would we decide which subset to use based just on WPLANG? What with those that use admin in English even though content is in other language? What for multilanguage? Some browsers don’t do proper fallback and we’ll end with squares and other garbage. If Open Sans gets in, all subsets should be included, that’s the price of using nonstandard font.
      • Possible server issues.
    • mor10 7:41 pm on November 19, 2013 Permalink | Log in to Reply

      For the default theme any custom font needs to be bundled for a simple reason: Not every WordPress installation runs on a computer connected to the web. There are many scenarios in which the site is not connected to the web: It could be a standalone application entirely severed from any network, it could be a site hosted on a secure intranet, the list goes on. As an external font library would result in a non-standard experience for these use scenarios I would encourage the inclusion of any custom font in the package itself. And for those same scenarios the inclusion of TTF and EOT might well be necessary since many of these users (European hospital intranets is one example) are stuck behind old system architecture that doesn’t support IE9 and above. Keep in mind that IE9 requires Windows 7, an update not yet undertaken by large parts of government and large industry landscapes.

    • Milan Dinić 5:11 pm on November 28, 2013 Permalink | Log in to Reply

      I have coded a simple plugin that disables loading of Open Sans from Google’s servers. If you have any comments about it (including its name), please share and I’ll submit it to repository in a few days.

    • mighty_mt 7:34 pm on December 10, 2013 Permalink | Log in to Reply

      So what’s the status here? I see in 3.8-RC2 (and also in MP6 2.2.1) that Open Sans is still loaded from Google. And to be honest, I don’t like that.
      I also think that WordPress shouldn’t use web fonts for the admin at all (especially not ones loaded from third party servers). Even though the new admin looks very pretty with Open Sans.

    • Alex Nguyen 1:48 am on December 15, 2013 Permalink | Log in to Reply

      Is there any way to disable Open Sans in the new 3.8 update? My blog is in Vietnamese and Open Sans does not display Vietnamese characters properly.

    • Paul 8:36 pm on December 19, 2013 Permalink | Log in to Reply

      Would love to dequeue open sans, it was a lovely idea but on a unstable african ISP its making editing on a clients site an unbearable experience – and I’m fairly privileged – honestly a standard stack would suit me fine, or just ‘sans-serif as someone suggested above.’. I really don’t thing open sans looks that great to boot.

    • ElectricFeet 12:44 pm on February 19, 2014 Permalink | Log in to Reply

      If it must be linked and not bundled (and I defer to your expertise on that decision), the best option would be to have a simple checkbox in “Edit my profile”: Use Google fonts for admin area?

      Apart from privacy concerns, linking on local dev environments really slows things down.

      (I’m using Milan’s plugin for now. Thatnks Milan!)

    • owcv 4:23 pm on February 24, 2014 Permalink | Log in to Reply

      I’m not happy with this kind of integration of Google on my WordPress Website. I don’t want big brother to watch my site. Open Sans should be included in WordPress but not linked to Google. At least there should be an option to deactivate for users in countries with certain information privacy policies. In the EU for example this could be a violation of actual law!

  • George Stephanis 10:35 pm on November 4, 2013 Permalink
    Tags:   

    Upcoming Global Admin Search (née Omnisearch) Meeting 

    After the feedback in the merge chat today, it looks like we’ve got a bit more work to do on the global search spine.

    Based on a quick survey, it looks like Monday, November 11, 20:00 UTC (3pm EST) is likely to be the best time for the most people.

    As we’ve done before, we’ll meet in #wordpress-core-plugins on Freenode, and I’ll give a shout in advance on #wordpress-dev for anyone that may be lurking in there.

    Putting up the bat-signal:

    Other folks who spoke up during the merge chat that I’d love to have join us:

     
  • Andrew Nacin 7:14 pm on November 1, 2013 Permalink
    Tags: ,   

    @matt will be running a WordPress 3.8 feature planning/decisions meeting on Monday, November 4, 21:00 UTC. Now that Daylight Saving Time has ended for both Europe and the U.S., note that the weekly Wednesday meeting is now moved from 20:00 UTC to 21:00 UTC (4 p.m. EST, 1 p.m. PST). (Americans, change your clocks on Sunday.)

    I’d strongly encourage everyone to study, test, and weigh in on the four 3.8 proposals before the meeting. I believe the goal of the meeting will be to establish what exactly gets merged into 3.8.

    API enhancements, bug fixes, etc. can/will continue as usual — it would be awesome if we had a surge not unlike 3.7. But for now, 3.7.1 is out, so stare at the download counter sip some tea, and relax this the weekend. :)

     
  • Samuel Sidler 11:27 pm on October 22, 2013 Permalink
    Tags: ,   

    Preparing your feature for the 3.8 merge 

    Now that 3.7 RC has shipped – and the final release is coming soon – it’s time to talk a bit more about how merging to core will work for feature plugins. First, let’s talk about decisions.

    Decisions

    I’ve been asked a few times “who decides” what goes in core and variants of that question. There’s actually three decisions that need to get made. In order:

    1. Does the feature belong in core?
    2. Is the feature ready for core?
    3. Should the feature be in this release?

    Core contributors and members of the community are strongly encouraged to help inform and guide each of these decisions. You may even want to offer some of your feedback in the form of answers to these questions. Each question is ultimately answered by a different group.

    1. Project leaders determine if a feature belongs in core.
    2. Contributing developers determine if a feature is ready for core.
    3. The release lead – for 3.8, @matt – determines if a feature belongs in a particular release.

    We’re now at the point where these questions need to get answered. To do that, it’s time to present your feature plugins.

    Present Your Feature

    If you remember back when we first started the feature plugin process, each team had to present its feature idea and answer a few questions. We’re going to do that again, but with a bit more information. If your project thinks it’s ready for core – and specifically for 3.8 – your team lead should make a post to make/core with the following information:

    • A visual and written overview of your feature plugin, along with a link to your plugin.
    • What problem is your feature plugin trying to solve?
    • What brought you to this solution and what other potential solutions did you explore?
    • Have you done user testing of your feature plugin? If so, what were the results? What worked and what didn’t?

    In your post, be sure to include links to previous posts and even specific comments that have helped form your decisions.

    Be ready for feedback from across the WordPress community – especially UX and code quality  – and be ready to defend your decisions or change your mind if a better idea emerges. Everyone will be reviewing the make/core posts and feedback in their discussion threads to determine if the answers to the questions above are all “yes”. If so, the feature can land when the merge window opens.

     
  • Andrew Nacin 3:07 am on August 7, 2013 Permalink
    Tags: ,   

    WordPress 3.8 meeting Thursday, August 8 

    In his State of the Word keynote, @matt announced that WordPress 3.7 and 3.8 will be developed simultaneously. Trunk would represent 3.7, while for 3.8, potential new features would be developed first as plugins. (3.8 starts at 35:00 in the video.)

    This “features as plugins” method* will allow teams to conceptualize, design, and fully develop features before landing them in core. This removes a lot of the risk of a particular feature introducing uncertainty into a release (see also 3.6, 3.5, 3.4 …) and provides ample room for experimentation, testing, and failure. As we’ve seen with MP6, the autonomy given to a feature team can also allow for more rapid development. And in a way, 3.7 provides a bit of a buffer while we get this new process off the ground.

    As announced at WordCamp San Francisco, Matt is leading the 3.8 release. He identified MP6 as a likely candidate for 3.8, along with the Twenty Fourteen theme. WP 3.7 will be released in October, at which point we’ll begin short window (probably two to three weeks) for any features to be merged for 3.8. If a feature isn’t ready for release by this point in the development cycle, it doesn’t land in core and moves to the next release. The target for WordPress 3.8 is early December.

    On August 8 at 18:00 UTC, Matt will host a WordPress 3.8 meeting in #wordpress-dev on Freenode.

    Thursday’s meeting is a great time to propose features that you’re interested in working on, keeping in mind they may or may not make it into WordPress 3.8. But keep in mind an early December timeline sets up WordPress 3.9 to kick off no later than January. Bring your ideas and thoughts as 3.8 development begins!

    To recap this post and the previous 3.7 post:

    • Wednesday, August 7 at 20:00 UTC — WP 3.7 initial planning meeting, #wordpress-dev
    • Thursday, August 8 at 18:00 UTC — WP 3.8 initial planning meeting, #wordpress-dev

    * Yes, this is more or less “feature branches,” but our rich plugin architecture makes it an obvious choice to follow the plugin-based model set by MP6. We have built features in plugins before — distraction-free writing in 3.3, the customizer in 3.4, and media in 3.5 all started as plugins. But they were pegged to a specific development cycle and did not have full teams developed around them, two issues we are now trying to fix.

     
    • Andrew Nacin 3:16 am on August 7, 2013 Permalink | Log in to Reply

      Just a note: All future weekly development meetings (Wednesdays, 2000 UTC) will cover both 3.7 and 3.8 updates and discussion items. Individual 3.8 feature teams will likely schedule their own office hours and such, as well. I understand how 1800 UTC is a terrible time for our friends in Australia and we’ll try to keep them a little more sane without upsetting our friends in Eastern Europe. :-)

    • Gage Morgan 3:34 am on August 7, 2013 Permalink | Log in to Reply

      That’s a very inspirational AND smart idea – building plugins are like making a model piece by piece to demonstrate what the software should look like before actually making any promises that the software will make it into core – if it doesn’t look right, rebuild it or just take it out completely. This will make the design process faster. Indeed, very smart indeed.

      • Scott Kingsley Clark 5:14 am on August 7, 2013 Permalink | Log in to Reply

        Agreed, and building as a plugin should help keep things well abstracted so it can be coded well, or other developers can provide their own ‘take’ on it too.

    • Eric Andrew Lewis 4:04 am on August 8, 2013 Permalink | Log in to Reply

      So working on two versions simultaneously is a practice that won’t be continued, at least for 3.9?

  • Andrew Nacin 7:17 pm on August 6, 2013 Permalink
    Tags: ,   

    WordPress 3.7 meeting tomorrow, August 7 

    If you haven’t caught @matt‘s State of the Word keynote at WordCamp San Francisco last weekend, you should. It contains a lot of great insight into how WordPress is used (using data from the 2013 user survey) and what should be expected for WordPress 3.7 and 3.8. (Talk about 3.7 starts at around 33 minutes in.)

    Here’s what was announced: WordPress 3.7 will be released in two months — early October. (Wat.) Jon Cave (@duck_) and I will be leading the release. It will be a quick “platform-focused” release, with a focus on stability and security.

    There are three main things we’d like to get done — language packs, auto-updates for minor releases, and some enhancements to help strengthen user’s passwords. Beyond that, though, the major goal of 3.7 is to offer a bit of a “reset” — which includes a huge cleanup of Trac. We’re currently at 3,800 open tickets, and we’d like to whittle that down as well as make things more manageable for the future. That includes reorganizing our Trac components, making it easier to contribute to certain areas of core (rather than, say, drinking from a single Trac firehose), and trying to organize teams around these components.

    Outside of core, there will also be work on developer.wordpress.org, which will include a hosted code reference and developer handbooks. As part of this, there will be a lot of inline documentation cleanup in 3.7 — potentially including an inline documentation standard for actions and filters.

    Better development tools will also be a goal in 3.7 — see also the post on develop.svn.wordpress.org from earlier.

    This is just the beginning. Please join me on Wednesday, August 7, 20:00 UTC for our weekly developer meeting in #wordpress-dev on freenode.net. I expect 3.7 to be a bit crazy, with a high volume of commits (oh, the days of WordPress 3.0), but also with increasing organization that can help set the stage for future releases. Daily bug scrubs! Rapid development! High tempo! Yay! Who is with me? See you tomorrow.

     
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