WordPress.org

Make WordPress Core

Updates from August, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Tammie 2:51 pm on August 25, 2015 Permalink |
    Tags: , , twenty-sixteen   

    Introducing Twenty Sixteen 

    WordPress 4.4 will see a brand new default theme; that’s right, today is time to meet Twenty Sixteen! The process of selecting the Twenty Sixteen theme was a long one, taking several months. Lots of themes were considered, eventually settling on the one you see below. It’s a perfect fit!

    00.twentysixteen

    Twenty Sixteen features a new, never-released design that has some really unique touches on a traditional blog layout. It adapts well to different devices and is a joy to use.

    Twenty Sixteen is a modernised approach of an ever-popular layout — a horizontal masthead and an optional right sidebar that works well with both blogs and websites. It has custom color options that allow you to make your own Twenty Sixteen. The theme was designed on a harmonious fluid grid with a mobile first approach. This means it looks great on any device.
    @iamtakashi

    Let’s take a look at more!

    We have the pleasure of welcoming back Takashi Irie as the designer of Twenty Sixteen. This year, the core team developing our new default theme will be myself and @iamtakashi — and you! We hope you can join us in getting Twenty Sixteen out to the world. Along with us, @iandstewart and @samuelsidler will be making sure the ship stays on course and giving us their wisdom as we charter the default theme seas.

    How can you get involved?

    There will be weekly meetings every Monday and Friday 16:00 UTC in #core-themes for half an hour. These weekly meetings will start once the theme has initially landed in core. If you are interested in contributing, subscribe to this blog (if you haven’t already), and leave your name in the comments. Once we’re ready, we will give everyone a ping and we’ll let you know on this blog too.

    Want to know more about default themes?

    There are some great links where you can find out more about past default themes.

    The road to releasing a new default theme is long, but we’re already well on our way! The next step is to commit the initial code to core. From there, we will begin testing and patching. We hope you join in the adventure of releasing Twenty Sixteen.

     
    • Nikhil Vimal 2:54 pm on August 25, 2015 Permalink | Log in to Reply

      I would be interested in helping!

    • Frankie Jarrett 2:57 pm on August 25, 2015 Permalink | Log in to Reply

      Pretty :-)

    • Drew Jaynes 3:05 pm on August 25, 2015 Permalink | Log in to Reply

      Congrats all around!

    • Ciprian 3:11 pm on August 25, 2015 Permalink | Log in to Reply

      I still think it looks a bit outdated. The default themes should be more modern, more 2016ish.

      • Mattias Tengblad 3:38 pm on August 25, 2015 Permalink | Log in to Reply

        +1

      • Paal Joachim Romdahl 4:55 pm on August 25, 2015 Permalink | Log in to Reply

        Agreed.

      • Arnan de Gans 6:21 pm on August 25, 2015 Permalink | Log in to Reply

        Yep, this looks like a 1998 html page :(

      • WTech 6:29 pm on August 25, 2015 Permalink | Log in to Reply

        +2 (imho 2014 is better)

      • Matt Mullenweg 11:52 pm on August 25, 2015 Permalink | Log in to Reply

        For the folks who think it looks old, definitely share some links to themes you think are more modern, it could be a good inspiration for twenty-seventeen (which is just around the corner).

        • waltson 5:37 am on August 26, 2015 Permalink | Log in to Reply

          Hi Matt .Really thanks for giving a chance to interact with you .I like wordpress, and i am working on it from few months .I like the 2016 theme. But please see the below points

          (1)Could you please add some more functions that assist in working with forms.

          (2)Captcha support by default

          (3)Could you please add some more permalink structure tags like %taxonomy%,%sub-taxonomy%,%sub-category% and way to arrange them

          (4) great pain is trying to make WP work with Angular.js or similar for building web apps.

          The most important ting is that please give some importance to https://wordpress.org/ideas/view/latest , because we only have this place to express our ideas . It would be very happy if we get correct reply and concentration from the wordpress team .

          I am looking forward to your reply.

          Thank you .

          • Paal Joachim Romdahl 8:12 am on August 26, 2015 Permalink | Log in to Reply

            Hi Waltson. A better place to post what you wrote would be in the “WordPress 4.4: What’s on your wishlist?” thread further down this page.

            • Sam wc 9:08 am on August 26, 2015 Permalink

              But Paal , these are some good ideas .Why we waiting for implement this in WordPress 4.4 . If these ideas make sense and it is important it can be implemented int he very next WordPress update.

            • Aparna123 9:25 am on August 26, 2015 Permalink

              Waltson is right

            • Sam wc 3:04 pm on August 27, 2015 Permalink

              WordPress team not looking at Frame work such as laravel,Yii,cakephp etc.Please make it very powerful such as this frame work. Because we love wordpress never wan’t to down when compare with these frameworks .

          • Aparna123 9:23 am on August 26, 2015 Permalink | Log in to Reply

            Good things Waltson.Generally there is lack of form handling and validating function in WordPress.Captcha is also important .

        • Adrian Pop 1:08 pm on August 26, 2015 Permalink | Log in to Reply

          I also think is kind of an oldish design – forget about sidebars! I really like Satellite (https://wordpress.org/themes/satellite/) and Ryu (https://wordpress.org/themes/ryu/) is one of my all-time favorite – Thaks Mr. Takashi :)

        • Sam wc 3:03 pm on August 27, 2015 Permalink | Log in to Reply

          WordPress team not looking at Framework such as laravel,Yii,cakephp etc.Please make it very powerful such as this frame work. Because we love wordpress never wan’t to down when compare with these frameworks .

        • transl8or 5:11 pm on August 27, 2015 Permalink | Log in to Reply

          I don’t think it looks old.
          It’s very very classical, kinda puristic und could be quite elegant with good pictures.

          Nevertheless I have two concerns about this theme:

          • The Frame; especially when it’s black, the site could somehow look like a newspaper obiatury.

          So I hope the customizer options will support a checkbox or simular to switch the frame on or off.
          Or maybe even have it only left & right vs. top & bottom.
          Or just choose the frame color individually so that it will be the same as the background color.

          • The Primary Menu; especially in the desktop version.

          I’m often very unhappy with lot’s of menus within WordPress Themes because they seldom look kinda “design consitent” for the whole site nor for bigger websites with lots of pages (not blogs, with mainly posts and infinite scroll).
          The later comes mostly with horizontal menu.

          — —

          As a suggestion for this theme, I could imagine a “sidebar integrated” menu, like you can see it in the Ascetic theme see here:
          http://demo.alienwp.com/ascetica/
          Could be a challenge with a full-width page, or pages with full-width header-image though.

          Or a menu like the Materialist Theme uses, see here:
          https://wordpress.org/themes/materialist/
          But on the upper right side.

          I like simplicity of the menu in the Libre Theme and the Theme in general;
          but it still has the issue of going “white over white, or even over content” when you create a site with a menu that has loads of items and levels.

          — — —

          Talking about the Materialist Theme brings me to the next topic.

          A more modern design approach for Twenty Seventeen?!?

          How about Material Design, Semi Flat Design, more colorful options and/or a “lighter, thinner, more playful & transparent look” for the menu/navigation, input-form elements and fonts.
          Oh, and I’d like to see an option in the Customizer for the primary menu to either be a “fixed navigation bar” or not more often.

          Examples:

          http://www.nuabikes.com/

          http://www.brindisatapaskitchens.com/

          http://revelator.com/

          http://www.wonderfullywild.co.uk/

          https://niice.co/

          http://branding.cards/

          http://simplehonestwork.com/

          http://evandorlot.com/portfolio/naaataa-fashion-branding/

          Google Resources on “Material Design”:

          https://www.google.com/design/spec/material-design/introduction.html

          :)

      • chrishoward 5:50 am on August 26, 2015 Permalink | Log in to Reply

        Yes. Reminds me of 2012.

        I think the main prob is the sidebar. That sort of stuff is all in footers in modern designs.

      • stuk 3:22 pm on August 26, 2015 Permalink | Log in to Reply

        +1

    • Lara Littlefield 3:16 pm on August 25, 2015 Permalink | Log in to Reply

      I’m so excited to have photos displayed in such a unique way like this in a default WordPress theme. 2016 is beautiful!!

    • Helen Hou-Sandi 3:18 pm on August 25, 2015 Permalink | Log in to Reply

      Woohoo! I’ve still got that musician bias – like Twenty Fifteen, this looks like it can serve as a really solid base for portfolio sites, especially with some creative thinking around colors and content.

    • web2033 3:23 pm on August 25, 2015 Permalink | Log in to Reply

      Happy new 2016 ^_^

    • Mel Choyce 3:24 pm on August 25, 2015 Permalink | Log in to Reply

      <3

    • Matthew 3:26 pm on August 25, 2015 Permalink | Log in to Reply

      awesome stuff

    • Philip Arthur Moore 3:27 pm on August 25, 2015 Permalink | Log in to Reply

      Happy to help do some theme breaking. Can’t wait to see this land. Takashi’s designs…are they ever not amazing? Another hit; cannot wait to see this on millions of sites. Great work gang.

    • Ihor Vorotnov 3:35 pm on August 25, 2015 Permalink | Log in to Reply

      One more blog theme with a font that looks ok only with latin characters? Looks nice, but… Come on guys, there’s life outside US. There are other languages out there. WordPress is not only for blogs anymore.

    • Ajay 3:40 pm on August 25, 2015 Permalink | Log in to Reply

      This is definitely looking very clean. Twenty Fifteen was OK look wise, but this definitely looks like a worthy base for any new site.

    • Nick Halsey 3:48 pm on August 25, 2015 Permalink | Log in to Reply

      I’m honestly not a fan based on the screenshots, but that’s okay – even a default theme shouldn’t try to satisfy everyone. Something feels off with it for me.

      Based on the way the colors seem to work, again based on the screenshots, we should probably explore making the text colors auto-generate to light or dark based on the selected background color, for simplicity and to minimize contrast issues. The Fourteen Colors plugin for Twenty Fourteen does something similar.

    • Chrisdc1 3:51 pm on August 25, 2015 Permalink | Log in to Reply

      Looks good, I’d be interested in helping as well,

    • Ahmad Awais 4:02 pm on August 25, 2015 Permalink | Log in to Reply

      I’d love to contribute.

    • Sakin Shrestha 4:03 pm on August 25, 2015 Permalink | Log in to Reply

      Looks really nice and clean. Would love to contribute… Thanks

    • Donna Fontenot 4:18 pm on August 25, 2015 Permalink | Log in to Reply

      This is exactly what WordPress does NOT need. Another boring, snoozefest old-school blog layout. Wake me when WP joins the rest of the world in 2015 and beyond. (BTW, I tried really hard to come up with a nice way to say that, and I just couldn’t, so here is the comment in all its straight-forwardness.)

    • MRWweb 4:25 pm on August 25, 2015 Permalink | Log in to Reply

      Let’s get some alt text in that image gallery! #a11y

      There are some really nice touches in the screenshots. I like the pull quote a lot (though wonder how it will be applied with the editor).

      At some point, I’d love to hear the core team be a little clearer on how the new theme is selected and why there have been two blog themes in a row. (It also might not be too late to add an interesting static front page option to Twenty Sixteen to make it more versatile!) I tend to follow this stuff and had no clue this process was happening. I certainly understand the need for fewer cooks in the kitchen, but at least letting some more people suggest ideas for priorities might be nice. Maybe even a poll or two.

      I’ve heard for years now many people clamoring for a “new Twenty Twelve” and still hope to see another “CMS” theme as a default soon. (It’s remained quite popular: https://docs.google.com/spreadsheets/d/1UV4UGFCdTdNhK8v7l9s6J0uI5Y-QMRocSET63NO3CVc/edit?usp=sharing)

      • Nick Halsey 7:11 pm on August 25, 2015 Permalink | Log in to Reply

        You’re not missing anything – there is a complete lack of transparency in the default theme process prior to the “announcement” posts. Even frequent contributors have heard absolutely nothing about it prior to today.

        My biggest complaint is that we have now had the same designer do the last three default themes. Takashi’s work is amazing, but it’s definitely time to give someone else an opportunity to fill this role as has been done in the past. Since the extremely outside-the-box Twenty Thirteen, we’ve gone back to progressively less and less compelling designs with each default theme.

        • MRWweb 8:59 pm on August 25, 2015 Permalink | Log in to Reply

          > Takashi’s work is amazing, but it’s definitely time to give someone else an opportunity to fill this role as has been done in the past.

          I agree. Even if Twenty Fifteen—which I like quite a bit—were by the objectively best designer in the world (that is not a thing, but for the sake of argument…) the core team should be doing more to promote and diversify the designers who show what WordPress can do and be. The idea that there aren’t other designs who can do this—and wouldn’t drop all sorts of other commitments if given the chance!—just doesn’t make sense.

          I hate being negative in what is an otherwise worthwhile celebratory post and call-to-action, but I really hope this can stop being so untransparent and homogenous.

    • Felix Arntz 4:26 pm on August 25, 2015 Permalink | Log in to Reply

      Plain and simple – and great. Looking forward to replace Twenty Fifteen on my blog :)

    • Emil Uzelac 4:30 pm on August 25, 2015 Permalink | Log in to Reply

      So Fresh, So Clean!

    • Nilambar Sharma 4:31 pm on August 25, 2015 Permalink | Log in to Reply

      Simple and nice. I am willing to contribute… :-)

    • voldemortensen 4:48 pm on August 25, 2015 Permalink | Log in to Reply

      Is there a way to get involved with this *before* it lands in core? I am a frequent core contributor and I have Slack open all day. I’ve heard nothing about this until literally a few minutes ago.

    • Shapeshifter 3 5:12 pm on August 25, 2015 Permalink | Log in to Reply

      “The theme was designed on a harmonious fluid grid with a mobile first approach. This means it looks great on any device.”
      @iamtakashi

      I like the concept !

      Is there any way to download the current alpha version of this, so I can upload it to my own website to preview it with my own personal content?

      I’m interested to know what the current Theme Customizer currently offers in Content (width) and Layout options.

    • Orangedrop 5:16 pm on August 25, 2015 Permalink | Log in to Reply

      For once purely based on screens I don’t know if I’m down this ! That said you can’t please everybody all of the time :) I would love to get my grubby mitts on it and break it a few times so please count me in ! Thanks guys and as always keep up the awesome work.

    • Brent Jett 5:39 pm on August 25, 2015 Permalink | Log in to Reply

      I’d like to know more about how this theme will be implemented in terms of customizer fields, editor styles, custom widgets/shortcodes etc… I’m a big believer in designing themes for the WP user as much as the reader. Where are these discussions currently being had? Is this project on github somewhere?

    • dannybrown 5:54 pm on August 25, 2015 Permalink | Log in to Reply

      Yawn. Sorry, but this design (as far as looks goes) is so 2012.

    • dshanske 6:15 pm on August 25, 2015 Permalink | Log in to Reply

      I would be interested in ensuring that the theme is microformats compliant.

    • Gaurav Tiwari 6:20 pm on August 25, 2015 Permalink | Log in to Reply

      Make it look like commercial themes. If WP is no longer blogging focused CMS why should the default themes be?

    • LittleBigThings 6:36 pm on August 25, 2015 Permalink | Log in to Reply

      Cool and clean, a bit Twenty Twelve-like. Hope to see some unique features in the Customizer. I would love to follow it up and help out testing.

    • Tomas Mackevicius 6:41 pm on August 25, 2015 Permalink | Log in to Reply

      Looks great! Can we see live demo?

    • Karthikeyan KC 6:44 pm on August 25, 2015 Permalink | Log in to Reply

      To be honest, twentyfourteen looks better than twentysixteen. Anyways, it’s good for the default one. :)

    • Tomas Mackevicius 6:52 pm on August 25, 2015 Permalink | Log in to Reply

      But 2014 was not built on _s, I hope 2016 is.

    • WebMan Design | Oliver Juhas 7:07 pm on August 25, 2015 Permalink | Log in to Reply

      Looks great, very clean! I’d like to contribute too :)

    • SanjayaBhai 7:10 pm on August 25, 2015 Permalink | Log in to Reply

      Twenty sixteen.. Hope it will be great…. But please make this themes more modern/Beautiful … It’s seems classic .

    • Alex Mills (Viper007Bond) 7:25 pm on August 25, 2015 Permalink | Log in to Reply

      It’s been a long time since I’ve run a default theme but I’ll be switching for this one!

    • George Stephanis 7:28 pm on August 25, 2015 Permalink | Log in to Reply

      I’m pulling for twentyseventeen to be Kubrick redone responsively. :)

      • Ryan Hellyer 9:42 am on August 26, 2015 Permalink | Log in to Reply

        I’ve been toying with forking Kubrick like that for many years now, but never gotten around to it.

      • Drew Jaynes 8:41 pm on August 26, 2015 Permalink | Log in to Reply

        FWIW, I already did it. I created a child theme for Twenty Twelve called Nubrick, that created a responsive version of Kubrick. The header used CSS gradients and everything else was matched to a tee with some obvious improvements. Might have it laying around here somewhere, have to look.

    • Tarik Cayir 7:59 pm on August 25, 2015 Permalink | Log in to Reply

      That’s sweet and incredible!

    • Morten Rand-Hendriksen 8:14 pm on August 25, 2015 Permalink | Log in to Reply

      Sign me up. I’ve done a lot of work with pull-images of the kind proposed here and know some of the pitfalls. I’ll contribute what I can and where it helps.

    • Valeriu Tihai 12:14 am on August 26, 2015 Permalink | Log in to Reply

      Happy to help

    • WP Sites - Brad Dalton 1:37 am on August 26, 2015 Permalink | Log in to Reply

      How about a widgetized page template which can be used as the front page. Widgets in columns are popular and so are full width sections. The genesis sample child theme is hugely popular because you can easily add custom functionality unlike any of the default themes.

    • Matt (Thomas) Miklic 2:03 am on August 26, 2015 Permalink | Log in to Reply

      This is a beautiful theme and I can’t wait to use it myself.

    • Aaron Brazell 2:13 am on August 26, 2015 Permalink | Log in to Reply

      I like the image offset a lot and I want a one-column option, so glad to see that in there. Agree with previous commenters saying it looks a bit dated, but I also don’t think that’s twntysixteen per se… I think the “blog layout”, which is a guiding principal, is a bit dated. I’d love to see twentyseventeen place less emphasis on text content, top down, left-right, sidebar, header and more of a focus on rich media. Photographs, videos, etc… with natural integrations (no external APIs) with social content (and not just FB and Twitter)… it’s such a rich internet, but the blog approach to the project might be influencing the frontend a bit much and not keeping up. :)

    • nick6352683 2:38 am on August 26, 2015 Permalink | Log in to Reply

      Anything, and I mean anything would be better than 2013, 2014, and 2015. I prefer 2012 over those, and 2016 seems more or less in line with 2012. The whole discussion is pretty much mute for me, as I always opt to use “premium” type themes, with tons of bells and whistles, but I’m very biased as I develop my own themes, with extra functions and shortcodes.

    • webdevmattcrom 3:33 am on August 26, 2015 Permalink | Log in to Reply

      Definitely interested in contributing, sign me up!

      I love that this does feel like it’s heading back toward a cleaner Twenty Twelve feeling. I like that the sidebar is on the right by default, but especially considering RTL it would be nice to have a Customizer option to put the sidebar on either side. In that vein, since the Customizer is getting more and more prominence it would be great to see this theme really flaunt some great aspects of the Customizer as a strong example of “Decisions not Options” while still providing flexibility in look and feel.

      Looking forward to seeing this come to life.

    • Amit Kvint 6:32 am on August 26, 2015 Permalink | Log in to Reply

      Definitely interested in contributing, sign me up too!

    • Brian Krogsgard 7:12 am on August 26, 2015 Permalink | Log in to Reply

      Is Ian Stewart the default theme lead?

      There is obviously a lot of decision making going on in regard to default theme design that nobody really knows about, and it is really confusing. It is so different than the rest of WordPress development.

      So, how would someone go about getting involved earlier in the process (at the design level!), short of going to Matt Mullenweg? I might add that going to Matt on how to get involved (though he appears the primary gatekeeper on default theme design) is likely quite intimidating for most folks.

      A lot of talented designers would probably like to get involved in this process but don’t know it’s possible or how to start. Some information and light on the process itself would be most welcome, I’m sure.

    • Philip Arthur Moore 8:55 am on August 26, 2015 Permalink | Log in to Reply

      The fact that there are so many passionate responses here is pretty cool.

      History time:

      Default themes won’t be for everyone, and ultimately I share Brian’s thoughts above. I think it’d be GREAT for 10000% transparency around the default theme making, designing, and proposal stages before posts like this are made. (Honestly it makes no difference to me personally but the community seems to benefit quite well from feeling like we have a chance to contribute to such a public and front-facing piece of WordPress.)

      But that aside, however the theme came to be, I think the first drafts shared are quite nice and absolutely cannot wait to help break things once it lands into Core. I’ve no doubt that there are some pretty serious design and development challenges that will come out of these drafts, and it’s going to be exciting to take part in that.

    • Subharanjan 9:04 am on August 26, 2015 Permalink | Log in to Reply

      Clean and Simple !! Looks awesome :)

    • Fotis 9:20 am on August 26, 2015 Permalink | Log in to Reply

      Perfect.

    • Ryan Hellyer 9:46 am on August 26, 2015 Permalink | Log in to Reply

      I like this new design. Simple, yet elegant.

    • stuk 10:24 am on August 26, 2015 Permalink | Log in to Reply

      To me it seems quite outdated and useless as any default theme, is it not?
      Quite clear that their intention is not to add extra features to WordPress, and indeed the basic theme can support only a maximum basic options.

      But also simply bad design. If it’s the preview we let people install with the system, so it seems bad.
      Nothing to do with new design trends.
      Despite the WordPress developers insist that the system is already more than a blogging system infrastructure, they continue to release static templates without AJAX and without REST, and yet the basic theme is a theme of a blog, not a website.

      In one word: shame.

    • David Bennett 11:42 am on August 26, 2015 Permalink | Log in to Reply

      It reminds me of Linen from TheThemeFoundry, and it has the open, airy look of themes from ElmaStudio. I like it. The only thing I wonder about are the horizontal dividers in the sidebar. The Daily Dish theme from StudioPress has black sidebar dividers overpower the theme somewhat. The dividers in The Daily Dish are thicker but if a blogger has a lot of widgets it can start to look like the i Ching.

    • Elisa 12:19 pm on August 26, 2015 Permalink | Log in to Reply

      I like it :)

    • CYBERsprout 1:28 pm on August 26, 2015 Permalink | Log in to Reply

      Looks great! A very modern design.

    • ldbaldwin 2:43 pm on August 26, 2015 Permalink | Log in to Reply

      I would be interested in contributing on some leve, (testing, documentation, etc.). Thanks!

    • cramdesign 2:47 pm on August 26, 2015 Permalink | Log in to Reply

      I think it looks great. The structure is a traditional setup but I think that the overall design, typography and image handling is very current. I agree that the dividers in the sidebar might be a little too heavy but, then again, that is easily changed with css and let’s be bold every now and again.

    • firewatch 3:34 pm on August 26, 2015 Permalink | Log in to Reply

      I’m interested in contributing, thanks!

    • djsteveb 9:20 pm on August 26, 2015 Permalink | Log in to Reply

      Wish all the like and dislike comments could be removed here. Give specifics or save the screen space.

      Sorry ya’ll but the default theme does not need to be any one person’s idea of pretty or modern, it’s default and certainly not the only option for anyone running wp.

      What the default themes have been lacking since 2012(?) is documentation, transparency, and support.

      All that fancy responsiveness is fine if you like things as is. Simply trying to move the left sidebar to the right with 2015 is a nightmare – I miss the days of simply change float left to float right.

      Yes I know, “modern design” is beyond that – I have learned how to move things around with bootstrap, and foundation… moving things with 2014 / 15 is a joke. No documentation, no support – no transparency with updates.

      Either given backend option for the most common changes, or make it easier for people to change things with code. Having to make edits and then change screen sizes and search for ways to change rules for each media query is a joke, with no docs, and no warnings about updates.

      Given that the default theme is the only thing we can count on that will get any kind of support from buddypress, rtmedia and other plugins – many are indeed stuck with the default theme base – pretty or not – those things can be adjusted if the options are understood, documented, supported.

      My comment on takshi’s site still waiting moderation (August 25, 2015 at 12:37 am ) – maybe it’s akismet limbo. Support on the wp repo is total confusion – even other professional sites that created right sidebar child theme break with basic background color change – is it them? Is it the theme? Was it working then an update fixed something and broke others?

      I am happy to contribute what I can (20% through my php course!) – I was planning to make a video tutorial from the text how-to for making themes at themeshaper.com – however it states it’s outdated. I stumbled across a trello that has documentation for theming in the works – but that may be finished in 2017?

      Given that the default theme has total power over so many things WP – I prefer no java, nothing complex, basic – make it easy to mod it so people can make it prettier and modern on their own. Not left in limbo choosing no support, no docs with wp plugins that work (and look basic) – or get a theme that looks better is modifiable – but then does not work with plugins and gets no love or support from plugin systems.

      Frankly the older default themes were much easier to make better. Anything default that is complex is just going to shrink the amount of WP users that can actually mod something on their own without a degree in javascript and php. You might as well force us to use sass and less and bower. Really shrink the amount of people that can enhance a basic default theme.

      Maybe pull all the extra stuff out and make it an option plugin like some do with “jetpack features” – I just want BP to work with something that can be modded – either with lots of backend theme options (colors, sidebar on, sidebar off, move to footer – basic stuff really, or easy css that the average person can figure out or get basic support from the community to figure out. (please take out all third party bloat, eg- google fonts, gravatar, emoji and put them as optional plugins, pretty please!)

      Or convince BP and rtmedia (and others) to work with / provide support themes based on bootstrap and or foundation – then the default theme can be whatever it wants to be and we can peruse the documentation for those frameworks, and make adjustments easily.

      Sorry to long rant, (and I started with ‘save the screen space – seriously sorry, very frustrated with all this!) I want to see WP, and things associated with it continue to succeed, however I concur that many of the past two years’ not-so-transparent decisions have not made this easy for most of the average users IMHO.

    • Marcus Tibesar 11:26 pm on August 26, 2015 Permalink | Log in to Reply

      IMO there is too much white horizontal space between the gravatars and the content.

    • Marcus 9:44 am on August 27, 2015 Permalink | Log in to Reply

      I would love to help out

    • weblizar 11:38 am on August 27, 2015 Permalink | Log in to Reply

      Hi,Like to contribute.

    • abe_charles 12:43 pm on August 27, 2015 Permalink | Log in to Reply

      Have to say that Twenty Sixteen default theme is very weak. It deserves to be placed on life support because it looks like something created in 2010. It’s plain black and white by default with options for different colour options but still quite stale.

      I thought Twenty Fifteen was poor but looking at Twenty Sixteen it’s as if WordPress is taking two steps backward by presenting this piece of crap. You have a disgruntled blogger in me and this theme ain’t gonna fly. At least you have a few more months before the year 2016 so get back to the drawing board and change the direction of this theme. It’s too late for April Fools.

      Repeal, repeal and stop making the images fall off the page. That’s frustrating. Come with a better theme.

    • Mel Choyce 8:22 pm on August 27, 2015 Permalink | Log in to Reply

      I think it’s important for people to remember that this theme was made by a real, live person. Disparaging contributors and their work is inappropriate and not welcome in this community.

      You are welcome to your opinion, but if you want to give feedback, please keep that feedback respectful and constructive. Critiquing the design and the default theme building process is fine. Calling this theme “crap” or “useless,” however, is not constructive feedback and not appropriate for these contributor blogs. As Matt Miklic mentioned, that kind of feedback is abusive and unhelpful.

      Here’s how to structure good design feedback:

      • Empathize. Remember that behind every design is a person. If you wouldn’t say it to this person’s face, don’t say it here.
      • Start with “I think…” and finish with “because…”
      • Comment on particular elements that don’t work in the design, like the typography, colors, hierarchy, and composition. Try to be as specific as possible.
      • Stick to goal-oriented feedback: “This theme can become a better default theme for more users if it did [x], [y], and [z].”
      • Frame feedback as suggestions, not mandates. “What if you…” and “How about if you tried…” are great ways to present alternate ideas to a designer.

      Thanks for helping us keep WordPress a positive place to contribute.

  • Konstantin Obenland 5:20 pm on July 7, 2015 Permalink |
    Tags: ,   

    Dev Chat Agenda for July 8 

    Here’s the agenda for tomorrow’s Dev Chat in the #core channel on Slack.

    Time/Date: July 8 2015 20:00 UTC:

    1. Beta Notes
    2. Feature Updates
      1. Admin UI – @helen
      2. Menu Customizer – @westonruter
      3. Passwords – @markjaquith
      4. Site Icon – @obenland
    3. Feature Plugin Chat Next Week@samuelsidler
    4. Component Updates
    5. Open Floor

    Feature Leads: Let’s review last weeks goals and set new ones for next week.

     
  • Daniel Bachhuber 7:46 pm on June 29, 2015 Permalink |
    Tags: , ,   

    Shortcake (Shortcode UI) chat summary – June 29th, 2015 

    Present: @danielbachhuber, @samuelsidler, @matth_eu

    • Sam shared with us the possibility of getting Shortcake committed to WordPress core. While he can’t make any guarantees, this is the direction he suggested:

      • Better first-run experience with the plugin so people can evaluate it better. He recommends adding a few “example” shortcodes, and mention that they’re examples / not to be included in core. Pull quote and PDF could be a good start.
      • Decide on the appropriate UX for inserting new shortcodes. The experience is currently tucked away under “Add Media”. We’ve been exploring a “Add Post Element” button alongside “Add Media”, or dedicated buttons in the editor for some post elements.
      • Inline editing would be really nice. We should see if we can make it the default experience for most shortcodes, and all existing core shortcodes. We should also experiment with content blocks, and see what other editors are doing.
    • Matt lost his internet, so we didn’t talk about any code things.

    Logs: https://wordpress.slack.com/archives/feature-shortcode/p1435604506000006

    Next chat: same time and place

    Next release: v0.5.0 – Tuesday, August 4th

     
    • webdevmattcrom 5:56 pm on July 3, 2015 Permalink | Log in to Reply

      Love the idea of adding a “Add Post Element” button. While I’m not a fan of adding more clutter to the editor in general, the current Shortcake experience is anything but intuitive for the average end-user. We build plugins that utilize shortcodes and that is the only thing that has kept us from using Shortcake to date.

  • Daniel Bachhuber 8:27 pm on June 22, 2015 Permalink |
    Tags: , ,   

    Shortcake (Shortcode UI) chat summary – June 22nd, 2015 

    Present: @danielbachhuber, @goldenapples, @davisshaver

    Logs: https://wordpress.slack.com/archives/feature-shortcode/p1434999676000006

    Next chat: same time and place

     
  • Morgan Estes 12:43 pm on April 19, 2015 Permalink
    Tags: ,   

    WordPress Core Weekly 

    Howdy! Sorry, I dropped the ball last week so this week’s Weekly Roundup is a double issue — it covers April 4, 2015 [32003] to April 18, 2015 [32140].

    This week marks the release of RC1, which is the first release that many plugin authors and beta testers will test heavily. If you don’t already, now is a good time to check out the Alpha/Beta forums for any issues that crop up during this testing cycle.

    We’re only days away from the release of 4.2; let’s finish strong! 🏃👏 Here’s the rundown of recent changes:

    TinyMCE

    • Update to 4.1.9+. Changes:
      • Fixed bug where extra empty paragraphs would get deleted in WebKit/Blink due to recent Quriks fix.
      • Fixed bug where the editor wouldn’t work properly on IE 12 due to some required browser sniffing.
      • Fixed bug where formatting shortcut keys where interfering with Mac OS X screenshot keys. [32058] #31895
    • Disable the wp-autoresize plugin in iOS. All iframes there are already expanded to the height of the content document. [32095] #31937
    • Update the “Keyboard Shortcuts” modal. [32060] #29558
    • Fix our shortcuts on Mac, use Ctrl + Opt + letter. [32059] #29558
    • Use window.twemoji directly in the wpemoji plugin. Gives a chance to the browser to lazy load twemoji.js when reloading the page. [32142] #31901
    • Remove the empty paragraph that sometimes is left over after adding an image caption. [32141] #32003

    wpView

    • Remove selected views when inserting content but not when loading all content, and remove the ref. to the selected view node on resetting the views. [32140] #31998
    • Resize sandbox iframes on load. [32056] #31480
    • Empty the content in the timeout, so it doesn’t render iframes twice. [32022] #31669

    Build/Test Tools

    • During PHPUnit tests, don’t autodetect permalink structure during WP installation. [32139] #31994
    • Move the built media JS files up a directory to their previous location and naming convention. [32125] #31912 (see [31373])
    • Don’t reference underscore.js source map. [32065] #31477

    General/Misc.

    • WordPress 4.2-RC1 [32137] [32138]
    • Use HTTPS URLs for codex.wordpress.org. [32116] #27115
    • Explain all placeholders in translator comment, not just the first one. [32111] #31675
    • Ensure post title input is not shortened for non-public post types. [32071] #30968
    • Improve handling of incomplete From and Content-Type headers in wp_mail(). [32070] #30266
    • wpLink: always show the URL field at the top. [32017] #28206
    • Force default avatar for HiDPI avatars on Discussion Settings. [32129] #31972

    Translation and Strings

    • Merge strings that describe the same command. [32078] #31776
    • Update placeholder for FTP credentials. [32077] #31922
    • After [31941], use the decoupled strings from wp-admin/network/themes.php in wp-admin/network/site-themes.php as well. [32029] #28502
    • Correct grammar when referring to “a user” vs “an user” in several places. [32025] #31894

    Administration

    Emoji and Smilies

    • Tweak which smiley matches which emoji. [32105] [32107] #31709
    • Update our few remaining smilies to better align with Twemoji, and add frownie.png until Twemoji provides a build containing it. [32104] #31709
    • The emoji JS files should be run through the script_loader_src filter, as they would be if they were registered scripts. [32097] #31938
    • Tidy up the wp_encode_emoji() regex, and clarify the function comment on Unicode 8 support. [32096]
    • Remove an errant / in Twemoji URLs. [32024] #31893
    • Remove executable bit from smilies. [32109] #31709

    Themes

    • Twenty Fourteen: update editor styles to better account for adaptive images in small screens. [32094] #31934
    • Twenty Fifteen: update editor styles to better account for adaptive images in small screens. [32090] #31934
    • Theme Compat: Make string translatable and add translator comments. Added in [31941]. [32084] #28502, #31921
    • Move initialization of $customizeSidebar to api.ThemesSection.initialize() to prevent cases where the result can be undefined. [32119] #31793
    • Translator comment should just reference placeholder numbers, not the actual placeholders. [32112] #31675
    • Tell developers how to correctly silence register_sidebar() notices. [32110] #31675

    Customizer

    Theme Switcher

    • Fix some esoteric breakage in iOS Safari. [32103] #31794
    • Don’t deactivate section on empty search results. [32083] #31889
    • Remove “Add New” reference from customize-controls.js. [32004] #31837
    • Use text input for the search field to prevent double tap issues for Preview and Customize buttons on iOS. [32127] #31794
    • Don’t re-render a theme control if it has already been rendered.
    • Lazy load theme screenshots. [32088] #31793
    • Fix tabbing order if section is open. [32087] #31289
    • Fix preview URL for subfolder installs. [32086] #31896

    Shiny Updates

    • Disable shiny updates from modal based on parent window [32082] #31739
    • Fix logic for details based shiny updates. [32080] #31739
    • Disable modal initiated shiny updates on wp-admin/update-core.php. [32067] #31739
    • Use dashes instead of dots as separator for jQuery events in shiny updates . is used for namespaces, so better to use dashes. [32063] #31819
    • Trigger events upon the completion of a shiny update. [32061] #31819
    • Remove Shiny Bulk Updates. Bulk updates don’t need to be ajaxified so let’s revert. [32053] #31770, #29820
    • Conditionally add AYS to leaving shiny updates. [32052] #31769
    • Enable users to initiate a shiny update from plugin detail modal. [32062] #31739

    Media

    • Don’t allow whitespace-only image captions from the Media modal. [32079] #21848
    • Fix focus and selected state for the selected attachments set. [32072] #31898
    • Rename get_media_embedded_in_content_allowed filter tomedia_embedded_in_content_allowed_types. [32113] #26675
    • Bring back spinners, now without bouncing select elements. [32101] #22839, #30725
    • Fix the media modal Insert into post button on narrow screens by limiting the width of .media-toolbar-primary and .media-toolbar-secondary only inside .attachments-browser (the top toolbar). [32121] #31908
    • Insert from URL: Make sure the link text is actually used. [32055] #29476
    • Make sure the spinner in the media modal is visible on narrow screens (without affecting the media grid). [32120] #30725

    Build Tools

    • Don’t override minified libraries included in core. [32066] #31477

    Docs

    • Remove unnecessary inline @see tags from a variety of parameter and return descriptions in wp-includes/wp-db.php. [32050] #31888
    • Remove unnecessary inline @see tags from the wpdb::process_field_charsets()DocBlock. [32049] #31888
    • Add a missing return description for has_header_image(). [32048] #31888
    • Fix a variety of inline documentation syntactical issues in wp-includes/taxonomy.php. [32047] #31888
    • Add a missing @access tag to the DocBlock for the WP_Meta_Query->$clauses property. Also adds a missing return description for WP_Meta_Query::get_clauses(). [32044] #31888
    • Add a variety of missing descriptions and fix syntax for wp_scripts(),_wp_scripts_maybe_doing_it_wrong(), and wp_script_add_data(). [32040] #31888
    • Remove an unnecessary inline @see tag and document the $wpdb global in two WP_Comment_Query methods. [32038] #31888
    • Add missing parameter and return descriptions to WP_Customize_Widgets->filter_customize_dynamic_setting_args(). [32036] #31888
    • Add parameter and return descriptions for WP_Customize_Widgets->get_setting_type(). [32035] #31888
    • Add missing @access tags to two DocBlocks in WP_Customize_Setting. [32034] #31888
    • Document the $theme property in WP_Customize_Themes_Section. Also adds a missing@access tag to the DocBlock for WP_Customize_Themes_Section->render(). [32033] #31888
    • Cleanup DocBlock syntax, add a missing parameter description for WP_Customize_Manager->set_post_value(). [32031] #31888
    • Add inline doc syntax fixes for WP_Customize_Manager->doing_ajax(). Also adds a return description. [32030] #31888
    • Add documentation for the $type and $theme properties in WP_Customize_Theme_Control. Also add some missing @access tags to various DocBlocks. [32028] #31888
    • Fix description alignment for the category_css_class filter docs. [32026] #31888
    • Add documentation for the $type, $mime_type, and $button_labels properties in WP_Customize_Media_Control. [32023] #31888
    • Clarify the DocBlock summary and parameter description forwp_edit_attachments_query_vars(). [32019] #31888
    • Add proper descriptions for the @global and @param tags in the wp_media_attach_action() DocBlock. [32018] #31888
    • Clarify the DocBlock description for wp_print_request_filesystem_credentials_modal(). [32016] #31888
    • Clarify 4.2.0 changelog entry, add global description to the DocBlock for WP_Users_List_Table->single_row(). [32015] #31888
    • Add missing @since versions from a variety of methods in WP_Press_This. [32014] #31888
    • Add missing DocBlocks for the _limit_array(), _limit_string(), _limit_url(),_limit_img(), _limit_embed(), and _process_meta_entry() utility methods in WP_Press_This. [32013] #31888
    • Add a return description to the DocBlock for WP_Posts_List_Table->is_base_request(). [32009] #31888
    • Add an @see mention for Plugin_Upgrader, plus spacing to the wp_ajax_update_plugin()delcaration. [32006] #31888
    • Add a more descriptive function summary for options_discussion_add_js(). [32005] #31888
    • Fix Docblock syntax for the taxonomy_parent_dropdown_args filter. [32003] #31888
    • Add a missing return description for wp_styles(). [32041] #31888
    • wp_install_maybe_enable_pretty_permalinks() should have a consistent @return value. [32027] #6481, #31888

    Help/About

    • All strings are available for translation. [32132] [32135] [32136] #31929
    • Change the subhead strings on credits.php and freedoms.php to match about.php.
    • Link the Emoji Codex article in the emoji blurb.
    • Add a second sentence to the JavaScript Accessibility blurb.
    • Switch positions for the JavaScript Accessibility and Complex Query Ordering sections for balance. [32131] #31929
    • Update about page for 4.2. [32118] [32123] [32130] #31929

    Upgrade/Install

    • Move wp-plugin-update-success event to after lock is released [32133] #31978, #31819
    • Use named function instead of anonymous function, making it testable and replaceable. [32126] #31964
    • When dbDelta() is checking whether an index is defined in a CREATE TABLE statement, don’t worry if MySQL has a subpart defined on an index, but the CREATE TABLE doesn’t. [32108] #31869

    Script Loader

    Press This

    • Do not show the bookmarklet upgrade notice when accessing directly press-this.php. [32122] #31968
    • Add mb_strlen() compatibility function. Works the same way as the existing mb_substr() compatibility function. [32114] #31951
    • Check the bookmarklet version and add the update notice from PHP. [32106] #31942
    • Add ARIA attributes to the alerts container. [32102] #31942
    • Fix focusing the Standard Editor link after saving draft, if the user has not focused another element. [32098] #31923
    • Change the link text to Standard Editor. [32093] #31923
    • When saving a draft change the text of the Save Draft button to “Saving…” [32092] #31923
    • Update documentation for press_this_save_redirect filter after [31992]. [32143] #31996

    Taxonomy

    • wp_update_term() should check if get_term() returned null. [32117] #31954
    • Avoid an unexpected object error when syncing global terms. Pass the expected single value, rather than object, when recursively calling global_terms(). [32064] #31914, #31149

    Editor

    Thanks to @adamsilverstein, @afercia, @awbauer, @azaozz, @boonebgorges, @DavidAnderson, @dimadin, @dlh, @DrewAPicture, @ericlewis, @hauvong, @helen, @hugobaeta, @iseulde, @jamescollins, @jeremyfelt, @joemcgill, @joen, @johnbillion, @jorbin, @kraftbj, @lancewillett, @markjaquith, @mattheu, @Michael-Arestad, @mindrun, @morganestes, @nacin, @nitkr, @obenland, @ocean90, @pavelevap, @pento, @peterwilsoncc, @samuelsidler, @SergeyBiryukov, @siobhan, @sirbrillig, @slobodanmanic, @swissspidy, @tmatsuur, @Tmeiste, @tyxla, @valendesigns, @westonruter, and @wonderboymusic for their contributions!

     
  • Daniel Bachhuber 11:23 pm on February 2, 2015 Permalink
    Tags: ,   

    Shortcode UI Chat Summary, February 2nd 

    Attendees: @jdgrimes @danielbachhuber @samuelsidler @matth_eu @bobbingwide @michaelarestad

    Full conversation: https://wordpress.slack.com/archives/core/p1422914584001521

    tl;dr:

    • Background: Fusion (a media company using WordPress) is using shortcodes increasingly to embed content within other content. Given the historically bad UX for shortcodes, we thought we’d invest a bit of development effort. The primary pain points for shortcodes we’re solving are discoverability (what shortcodes are there), and usability (what arguments do I need for this shortcode). @matth_eu (from Human Made) has done a substantial amount of development, along with other contributors.
    • We discussed whether, for pragmatic purposes, shortcodes are content blocks. Answer: Kind of, to a limited degree. We’d need to determine which types of shortcodes are safe to deal with.
    • Everyone agreed inline editing would be nice for the shortcodes that support it well, and take Shortcode UI from good to great. @michaelarestad offered to do some wireframes.
    • @bobbingwide opened a number of Github issues this morning that largely represent useful enhancements.
    • Because Shortcake makes use of JavaScript templates, @kaiser mentioned it would be nice to declare the templates as dependencies of specific scripts. @danielbachhuber agreed, and suggested opening a core ticket.

    Next chat: February 16, 2015 22:00 UTC (two weeks from now)

     
  • John Blackbourn 9:30 am on January 13, 2015 Permalink
    Tags:   

    Feature plugins in 4.2 and beyond 

    Feature plugins for WordPress 4.2 and beyond need to be planned. Let’s get some suggestions together along with their status and who’s working on them.

    For each feature plugin that you would like to see considered, either for 4.2 or for a future version, please leave a comment with the following details:

    • Current status (eg. idea, planning, early/late development, testing, stable)
    • Who’s responsible
    • Link to GitHub repo or w.org page, if appropriate
    • Whether you’d like the plugin to be considered for 4.2

    It’s become apparent that feature plugins need to be at a much more mature stage before they are considered for merge into core. After all, the point of a feature plugin is to build a feature as a plugin and if the plugin never gets merged into core then we’re still left with a fully workable standalone plugin. Any feature plugins which are to be considered for 4.2 need to be at a very mature stage already.

     
    • Hugh Lashbrooke 9:41 am on January 13, 2015 Permalink | Log in to Reply

      Not sure what kind of things you’re looking for here exactly, but I built this plugin to improve the export tool: https://wordpress.org/plugins/export-plus/ because the patch I submitted doesn’t look like it’s going to be merged anytime soon: https://core.trac.wordpress.org/ticket/27048.

      The plugin is fully functional and there aren’t any bugs that I’m aware of. The only thing it really needs before merge is unit testing, which is a problem because the core unit test library for the export tool was rewritten for a separate patch that also hasn’t been merged (https://core.trac.wordpress.org/ticket/22435), so we would need to revert the core unit test repo for this side of things. Anyway – just thought I’d throw this out there because I think it’s a very useful filler until the export API is properly rewritten like that other patch is doing.

    • Rami Yushuvaev 11:56 am on January 13, 2015 Permalink | Log in to Reply

      Currently, the wp.mce.views API is still experimental (https://core.trac.wordpress.org/browser/tags/4.1/src/wp-includes/js/mce-view.js). It would be nice if WordPress 4.2. will Introduce the full API.

    • Eric Mann 2:59 pm on January 13, 2015 Permalink | Log in to Reply

      I’d been working on Secure XML-RPC for consideration as a feature plugin, and would like to see it revisited.
      Current Status: Late development (on hold as the JSON API was supposed to be in core already, but since it’s not, let’s take some time to revisit this for security sake)
      Who’s Responsible: Me, at the moment. More than happy to have other collaborators.
      Github: https://github.com/ericmann/secure-xmlrpc
      Consider for 4.2: Yes please

      The plugin currently sub-classes the XML-RPC server to provide the secure authentication method as an alternative to sending username/password in plain text. If/When rolled into core, this subclass would be replaced by actually updating the core server implementation. Everything is still backwards compatible (original auth still works, it just sends an X-Deprecated header), so concerns about this breaking existing libraries are minimal.

      • Dave Navarro, Jr. 6:41 pm on January 14, 2015 Permalink | Log in to Reply

        Does anyone know the status of the JSON API? Are they ever gonna finish it?

        • Adam Silverstein 9:43 pm on January 14, 2015 Permalink | Log in to Reply

          Development is ongoing, version 1.1 was recently released and is avaialable for your use: https://wordpress.org/plugins/json-rest-api/

        • Eric Mann 12:09 am on January 15, 2015 Permalink | Log in to Reply

          v1.1 is live. When it’s eventually rolled into core, we’ll increment the version to v2.x. Unfortunately, the “when” for rolling into core is a moving target. Every time we get close, something else comes up to delay it. I was expecting it in 4.0. Then 4.1. Now we’re hoping it might make it into 4.2, but still no promises.

          I’m still really looking forward to the JSON API making it into core. It’s going to be a huge step forward to what WordPress can do. That said, XML-RPC isn’t going to disappear, even when the new API ships. So we should do what we can to make sure that the existing remote interaction API works and is secure.

          • Dave Navarro, Jr. 10:22 pm on January 15, 2015 Permalink | Log in to Reply

            Okay, great! So 1.1 is ready for production sites?

          • dshanske 12:05 am on January 17, 2015 Permalink | Log in to Reply

            I was hoping for a gradual sunsetting of XML-RPC after JSON came into core, although I know that is less likely to happen.

            Of course, it may merely be my annoyance of it being probed by so many outside sources.

    • Mike Hansen 4:02 pm on January 13, 2015 Permalink | Log in to Reply

      I have been exploring starting a project for the registration flow for new users. This would include the signup, login, email, etc.
      Current Status : Idea/Planning
      I would like to lead this project. I would like to have it ready for consideration in 4.3.

      Looking for others interested as well.

      • Travis Northcutt 4:53 pm on January 13, 2015 Permalink | Log in to Reply

        Mike, would this potentially include an option for something like “send this user a link to set their password” when creating a new user in wp-admin? Basically, a way to avoid setting passwords for users, and to avoid transmitting passwords via email.

        Feel free to ping me on twitter (tnorthcutt), I may be interested in helping out.

        • Mike Hansen 5:03 pm on January 13, 2015 Permalink | Log in to Reply

          Yea, plain text passwords in email is one thing on the list.

          • Ihor Vorotnov 10:03 pm on January 21, 2015 Permalink | Log in to Reply

            If this includes possible improvements to the whole registration process, I may be interested as well. Working on a several large projects based on WP, created 2 different versions of custom registration / activation / login process. Have some interesting experience, fails and mistakes, wins and tweaks.

    • Scott Kingsley Clark 4:17 pm on January 13, 2015 Permalink | Log in to Reply

      We’re still working on getting a proposal together for a new Metadata API for registering contextual custom field data (type of data, label text for forms) along with UI (show custom fields in a post edit screen with their corresponding field type inputs).

      It’s not ready, and we’re currently in the process of rebooting our efforts geared towards everything as a result of a discussion with core dev @helen

      We’ll be starting up discussion and status posts in the coming month.

      Though, not exactly a normal feature plugin, we’re hoping to develop it in such a way that it could be used and tested via a plugin for proof of concept.

      • Nick Halsey 4:33 pm on January 13, 2015 Permalink | Log in to Reply

        I’d love to see this, especially if it takes inspiration from (or actually uses, which could be a possibility) the Customizer API. The ease with which devs can spin up, for example, a media control with previewing with that API, as well as being able to easily create custom controls (and custom sections and panels) by subclassing in PHP and JS would be great for post meta.

      • Ihor Vorotnov 10:05 pm on January 21, 2015 Permalink | Log in to Reply

        That might be yet another bottleneck for multilingual sites until WP core becomes multilingual. Just saying :)

    • Siobhan 5:02 pm on January 13, 2015 Permalink | Log in to Reply

      Feature Plugin – Image Flow
      Better image uploading, management, and editing, on every device.

    • Nick Halsey 5:17 pm on January 13, 2015 Permalink | Log in to Reply

      Menu Customizer

      Current status: late development/iterations
      Who’s responsible: me (Nick Halsey, @celloexpressions), with help from @westonruter, @voldemortensen, and others so far
      Links: https://wordpress.org/plugins/menu-customizer/, https://github.com/voldemortensen/menu-customizer, continuous discussion in #core-customize on Slack
      Whether you’d like the plugin to be considered for 4.2: depends on 4.2 timeline and how the next couple weeks go. It’s fairly stable and usable, but there are a few things that need refactoring, and we’re also working on improving core APIs to make things less hacky. The UI is essentially the same as the Widget Customizer UI, so while there’s potential room for improvement there, I don’t foresee needing significant design work before the initial version goes into core (and no one has done much work there yet).

      • Paal Joachim Romdahl 4:05 pm on January 14, 2015 Permalink | Log in to Reply

        What about adding features from kirki?:
        https://github.com/presscodes/kirki

        • Nick Halsey 9:03 pm on January 14, 2015 Permalink | Log in to Reply

          That could probably be done in the form of core tickets/patches if anyone’s interested. The only potential thing that could add would be more custom controls.

      • Samuel Sidler 7:34 pm on January 14, 2015 Permalink | Log in to Reply

        I’d like to see some user testing before it goes into core. Has the accessibilty team reviewed it?

        • Nick Halsey 8:59 pm on January 14, 2015 Permalink | Log in to Reply

          I’ve done some informal in-person user testing and not run into issues. But if someone has the ability to do better user testing that we can iterate from, that would obviously be better (maybe @designsimply?).

          It would be good if the accessibility team started reviewing it. I’ve done basic keyboard-only tests and retained things from the menus admin and the widget Customizer API, but I have only limited knowledge there.

    • Daniel Bachhuber 5:33 pm on January 13, 2015 Permalink | Log in to Reply

      Shortcake (Shortcode UI)

      • Current status: Early to mid development
      • Who’s responsible: Matt H-Y from Human Made and a few of us from Fusion.
      • Link: https://github.com/fusioneng/Shortcake
      • Whether you’d like the plugin to be considered for 4.2: Could, if there’s interest. We have it in production, and it’s available on WordPress.com VIP. Currently it’s more of a developer API than user-facing feature because it requires code-level configuration. At the least, it would be good to get some core opinions on it.
      • Hugh Lashbrooke 7:09 pm on January 13, 2015 Permalink | Log in to Reply

        This sounds interesting – I’d be keen to get involved here. Will check out the repo.

      • Scott Kingsley Clark 9:47 pm on January 13, 2015 Permalink | Log in to Reply

        Would be a good idea to be sure we’re aligned in approach and what we’re doing between the Metadata project and Shortcake, could share some lessons learned and come up with a solution that has even greater reach.

    • petermolnar 9:00 am on January 14, 2015 Permalink | Log in to Reply

      Filter Post Formats
      If the site supports post formats, we should be able to filter by them on the posts admin.

      ImageMagick Sharpen Resized Images
      Simple Image Sizes
      WP Resized Image Quality
      For those who use WordPress as a portfolio, the default image quality is disappointing. Please let us have the option to change those.

      Thin Out Revisions
      Revisions are nice – unless you have hundreds of them.

      Unattach and Re-attach Media Attachments
      Instead of re-uploading everything, this would be useful.

      WP-Paginate
      The default pagination is way too simple.

      Webmention
      Semantic-Linkbacks
      Pingbacks are dead, long live webmentions.

      • John Blackbourn 10:01 pm on January 14, 2015 Permalink | Log in to Reply

        Can you provide some more info like I asked for? Would you like these plugins considered for 4.2 or later releases? What’s the current status of each?

        • dshanske 1:47 am on January 15, 2015 Permalink | Log in to Reply

          Webmention
          Who’s Responsible: The plugin was developed by Matthias Pfefferle, but I’m not sure if he’s prepared to lead a project on it.
          Current Status: Webmention is fairly mature
          Links – https://wordpress.org/plugins/webmention/ and the Github version https://github.com/pfefferle/wordpress-webmention

          It is basic plumbing for a better alternative to Pingbacks and Trackbacks. Both of those have become so much of a problem that people often disable them. It is time to start building better solutions than disabling them. That comes with a better foundation on which to base enhancements.

          Semantic Linkbacks
          Who’s Responsible: The plugin was developed by Matthias Pfefferle, but I’m not sure if he’s prepared to lead a project on it.
          Current Status: Also mature
          Links – https://wordpress.org/plugins/semantic-linkbacks/ and the Github is https://github.com/pfefferle/wordpress-semantic-linkbacks

          Semantic Linkbacks endeavors to generate richer trackbacks, pingbacks, and ‘webmentions'(see above) by parsing the source URL for microformats, but could also add other types of markup.

          Back to the issue of linkbacks of all types becoming useless…this, combined with webmention, is the start of making linking to other sites a more meaningful thing once more.

        • petermolnar 3:45 pm on January 15, 2015 Permalink | Log in to Reply

          I’m sorry for not being more detailed; I should have been in the first place.
          Thanks for dshanske for stepping in for the webmentions/semantic linkbacks plugin.

          For the rest:

          Thin Out Revisions
          ————————–
          Current status
          Mature and actively maintained.

          Who’s responsible
          blogger323 user.

          Plugin to be considered for 4.2?
          The provided functionality helps cleaning up and maintaining revisions in a nice and user-friendly way; yes, it should be considered might even for 4.2

          WP-Paginate
          ——————
          Current status
          Mature and old project, under active development.

          Who’s responsible
          Eric Martin and StudioFuel users.

          Plugin to be considered for 4.2?
          Not neccessarily for 4.2, but since it provides sophisticated and detailed settings for pagination, including labels, range, etc., therefore it could be considered.

          ImageMagick Sharpen Resized Images
          —————————————————–
          Current status
          Relatively new plugin but actively maintained.

          Who’s responsible

          HansVanEijsden
          and niwreg users.

          Plugin to be considered for 4.2?
          For one of the following versions where the Media Library receives significant updates.

          WP Resized Image Quality
          ————————————
          Current status
          It have not received an update in a long time and seems to be unmaintained.
          The functionality it provides is very useful though, especially for image-heavy portfolio sites.

          Plugin to be considered for 4.2?
          For one of the following versions where the Media Library receives significant updates.

          Unattach and Re-attach Media Attachments
          ———————————————————–
          Current status
          Seem to be abandoned, but the idea it represents should be considered as a feature.

          Plugin to be considered for 4.2?
          For one of the following versions where the Media Library receives significant updates.

    • Dan Nisbet 2:37 pm on January 14, 2015 Permalink | Log in to Reply

      It’s not anything gigantic or groundbreaking, but I created a plugin called Home & Blog Label: https://wordpress.org/plugins/home-blog-label/

      It simply adds a label next to the pages that are set to display blog posts or on the front page when a user sets them under Settings > Reading.

      I’ve been using it on some client websites and people love being able to quickly scan through the list of pages to find the blog or home page when it needs editing. I’d love to see it as part of core.

    • FolioVision 4:05 pm on January 14, 2015 Permalink | Log in to Reply

      Hi John,

      This is a great idea. We’ve always found the comment moderation/management a bit weak (no wonder so many people are using the Disqus crutch). Our plugin Thoughtful Comments supercharges comment moderation by moving it into the front end (i.e. in context). It also allows banning by IP, email address or domain.

      Unlike many comment plugins, Thoughtful Comments works hand in hand with Akismet, feeding all the information into Akismet as well as the existing WordPress whitelist and blacklist features.

      What’s cool about Thoughtful Comments is that you can add it to a WordPress site with no changes to existing comment moderation tables and you can remove it from a WordPress site with no loss of core functionality. I.e. I think Thoughtful Comments could be integrated into core with a minimum amount of pain. Thoughtful Comments works with all current Subscribe to Comment plugins as well. As we use all core functions and tables, Thoughtful Comments works with all current Subscribe to Comment plugins as well.

      Thoughtful Comments is the most powerful and useful code we’ve ever written (we have four very popular plugins). It’s integration into core would save many, many site owners the pain of Disqus.

      1. Thoughtful Comments is entirely stable and active on some of the most heavily commented political and lifestyle sites in the world.
      2. Foliovision is responsible.
      3. https://wordpress.org/plugins/thoughtful-comments/developers/
      4. We’d love to be considered for 4.2.

      I know Automattic has a horse in the ring (Intense Debate) but improving the core comment moderation would be such a great fix. Upcoming: we have additional invisible caching coming for heavily commented posts (so that if there are hundreds of older comments, they get saved as flat html, lightening PHP load and speeding up busy sites significantly.

      Cordial regards,

      Alec Kinnear
      Creative Director, Foliovision

    • aneeskA 5:21 pm on January 14, 2015 Permalink | Log in to Reply

      Current status : stable
      Who’s responsible : aneeskA
      Link to GitHub repo or w.org page, if appropriate : https://wordpress.org/plugins/downml/
      Whether you’d like the plugin to be considered for 4.2 : YES

    • Adam Silverstein 6:12 pm on January 14, 2015 Permalink | Log in to Reply

      Post Meta Revisioning

      Status: In development.
      Who’s responsible: Me, inviting contributors.
      Status: I’ve been working on Post Meta Revisioning (its a feature!) and a handful of related tickets in the Revisions component. I would love to see this considered for 4.2.

      I took the last patch from #20564 and, with the inclusion of two hooks added in 4.1, turned ‘Revisioning of Post Meta’ into a plugin:

      On wordpress.org: https://wordpress.org/plugins/wp-post-meta-revisions/

      Development taking place on github: https://github.com/adamsilverstein/wp-post-meta-revisions/

      I would appreciate any help with testing, patches, review, etc.

      Tickets related to and relying on this plugin:

      #29276
      – Ability to edit and preview any revision, not just autosaves
      https://core.trac.wordpress.org/ticket/29276

      #23314
      – Allow published posts to be revised without being updated immediately
      https://core.trac.wordpress.org/ticket/23314

      #20299
      – Preview changes on a published post makes all post meta “live”
      https://core.trac.wordpress.org/ticket/20299

      #27244
      – ‘Restore This Autosave’ immediately updates a published post
      https://core.trac.wordpress.org/ticket/27244

    • jtarrier 3:46 am on January 15, 2015 Permalink | Log in to Reply

      Improved Media Library with user-defined subfolders, taxonomies, categories, “where used” etc.

      The current media library only allows us the choice of uploading into year/month folders or into the “uploads” dumping ground. This is severely limiting and has been in dire need of an overhaul for years.

      The following is a list of plugins which provide much of the desired functionality. The main item of functionality not in the plugins (as far as I have found) is the ability to move media between subfolders and having the database links updated automatically.

      WordPress › Media Library Assistant « WordPress Plugins
      https://wordpress.org/plugins/media-library-assistant/

      WordPress › Support » FANTASTIC app for arranging media library in folders
      https://wordpress.org/support/topic/fantastic-app-for-arranging-media-library-in-folders?replies=1

      WordPress › Media File Manager « WordPress Plugins
      https://wordpress.org/plugins/media-file-manager/

      WordPress › Media Category Library « WordPress Plugins
      https://wordpress.org/plugins/media-category-library/

      WordPress › Enhanced Media Library « WordPress Plugins
      https://wordpress.org/plugins/enhanced-media-library/

    • Weston Ruter 5:09 am on January 15, 2015 Permalink | Log in to Reply

      Customize Partial Refresh

      GitHub: https://github.com/xwp/wp-customize-partial-refresh
      w.org: https://wordpress.org/plugins/customize-partial-refresh/
      Contributors: westonruter
      Status: in development, currently adding partial refresh support for widgets
      Milestone: not concerned to get it into 4.2

      This feature plugin is for implementing what is needed for #27355. As of now it resurrects the partial-refresh functionality from the Widget Customizer plugin and makes it available for Customizer management of Widgets as they exist in Core now. The problem being solved is eliminating the painfully slow Customizer preview update times when a setting transport=refresh. Ideally 100% of changes requiring PHP would be implemented using partial refresh as opposed to a full-page refresh, and this would allow us to do cool things like have Customizer controls appear inline on the frontend without even having to “go into” the Customizer to make changes. Partial refresh is closely related to the work being done on transactions: #30937.

    • Pascal Birchler 9:23 am on January 15, 2015 Permalink | Log in to Reply

      this would allow us to do cool things like have Customizer controls appear inline on the frontend without even having to “go into” the Customizer to make changes

      Ohh this sounds great! Just think of all the use cases for this…

    • Dave Navarro, Jr. 10:25 pm on January 15, 2015 Permalink | Log in to Reply

      I’d really like to see “title” supported with the audio player. It’s supported in jPlayer, but I don’t know how much jPlayer was modified for WordPress as I haven’t been able to find the support code in the WP version.

    • Cătălin Dogaru 10:14 am on January 16, 2015 Permalink | Log in to Reply

      Avatar Manager
      Plugin for storing avatars locally. Started as a core ticket (#16020) some time ago.

      • Current status: Pretty stable, feedback/peer review wanted.
      • Who’s responsible: Me and anyone interested.
      • Links: GitHub, WordPress.
      • Whether you’d like the plugin to be considered for 4.2: Not necessary, depending on your interest. At least, it would be great to set a resolution on it.
      • Dave Navarro, Jr. 8:48 pm on January 16, 2015 Permalink | Log in to Reply

        +1 on this, I really would like to see Gravatar removed from core and left in Jetpack and native avatars used instead.

        • dshanske 11:48 pm on January 16, 2015 Permalink | Log in to Reply

          The agument is that gravatar is an industry standard. Nothing ever seems to leave core though.

          Local storage of information should always be the primary option over polling a third-party site, at least for local accounts.

          Although I’d like to find a good solution for also polling the URL provided by a commenter to get their local avatars also.

      • Cătălin Dogaru 8:49 pm on January 20, 2015 Permalink | Log in to Reply

        Thanks @dnavarrojr and @dshanske for getting involved! Just to be clear, this doesn’t remove Gravatar support. Gravatar is nice; if you’re using it you’re all set! I just want to make it easier for anyone to update (like GitHub did).

        • dshanske 4:40 am on January 21, 2015 Permalink | Log in to Reply

          The counterargument is that gravatar support should be secondary. WordPress is self-hosted, yet has a dependency on a third-party service. I’m not advocating removing gravatar support…It’s been there too long, and too many things depend on it. But I think that infrastructure should be local first, remote second.

          I should be able to tell my install to only rely on local. If you can’t find a local image, use a local default. It should be a choice.

      • Cătălin Dogaru 1:43 am on February 1, 2015 Permalink | Log in to Reply

        For anyone interested, I’ve posted an update on the original ticket. It would be great to see more opinions on this, whether you think it’s suitable for core or not.

    • Merv Barrett 6:33 pm on January 17, 2015 Permalink | Log in to Reply

      Not sure if this is the right place to submit a request for an enhancement to get_template_part() I’ve searched but have not found a request for a core change.

      What would make plugin development much easier for plugins adding custom post types is a filter that would enable filtering of get_template_part() function.

      For example for a post type “property” we would be able to override the get_template_part if the post is being viewed.

      Is this possible to add to the core or are we requiring users to create their own single-property.php and archive-property.php.

      Having a filter would allow plugin developers to replace that with their own function and allow for greater control and compatibility with the thousands of themes. In my case adding to the_content is not sufficient as I would like complete control over the contents of the single and archive pages. Doing this also allows the plugin to inject customised content into the theme design withouth breaking the theme layout. (Every theme is so different in CSS and container elements)

      An example would be

      My plugin creates its own template eg:

      Function epl_single_content() {
      // address
      // bedrooms bathrooms price
      // featured image
      // content
      // features
      // map
      // more stuff
      }
      add_filter( ‘get_template_part’ , ‘$post_type’ , ‘epl_single_content’ );

      This would allow WordPress to be able to deal with custom post types and user skills much easier?

      Thanks

    • Nick Halsey 7:49 am on January 19, 2015 Permalink | Log in to Reply

      Customizer Theme Switcher

      Current status: stable, seeking feedback
      Who’s responsible: me (@celloexpressions)
      Link: https://wordpress.org/plugins/customizer-theme-switcher/
      Whether you’d like the plugin to be considered for 4.2: definitely 4.2 material. Although I only started working on it a few days ago, it’s pretty complete thanks to re-using a lot of code and UI from themes.php. Almost could have been done as a core patch, but this makes testing & iteration easier. Additionally, while a couple minor core patches would help, it’s entirely built on the 4.1 Customizer API. Accessibility should be covered, but it wouldn’t hurt for the team to do an audit. See also #26890.

      I have class during the meeting unfortunately, but if this and Menu Customizer could be discussed in my absence that would be great (I’ll read the archives).

      • Nick Halsey 1:10 am on January 20, 2015 Permalink | Log in to Reply

        Also, a clarification: the plugin simply provides the UI and is functional with the current way that theme previewing in the Customizer works. @westonruter also has some ideas for improving the internals, along with the proposed Customizer transactions API. That’s not a requirement but would be nice to have and will likely end up in 4.2 anyway.

    • Måns Jonasson 10:29 am on January 19, 2015 Permalink | Log in to Reply

      Enable Media Replace

      The plug allows users to replace uploaded media, which is perfect for switching out images or files without having to update URL:s on pages.

      Current status: stable
      Who’s responsible: me (@mungobbq)
      Link to w.org: https://wordpress.org/support/plugin/enable-media-replace
      Link to Github: https://github.com/mansj/enable-media-replace

      I think this functionality should be in core.

      • dshanske 4:36 am on January 21, 2015 Permalink | Log in to Reply

        If it is being looked at to replace uploaded media, is there anything we can do to deduplicate media concurrently? I’ve seen people try to upload the same picture multiple times.

      • enailor 7:56 pm on April 7, 2015 Permalink | Log in to Reply

        Just added this plugin as an idea as well.. did not realize it was already mentioned. I use this awesome plugin for every project I do. Thanks to Måns for this great feature!

    • Helen Hou-Sandi 8:24 pm on January 19, 2015 Permalink | Log in to Reply

      RICG Responsive Images

      Current status: Initial release
      Who’s responsible: Primarily @tevko and @wilto
      Link to .org: https://wordpress.org/plugins/ricg-responsive-images/
      Link to GitHub: https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images

    • Ihor Vorotnov 10:30 pm on January 21, 2015 Permalink | Log in to Reply

      Multilingual core, please. Years are passing and WP is still a single-language platform. I understand, that making core truly multilingual will kick WPML out of business. But hey, it’s a core feature in all platforms. It has to be in core.

      Polylang plugin is the best out there, better than WPML (and compatible with WPML API btw)

      Current status: stable, used by many people on many sites, pretty well maintained
      Who’s responsible: https://profiles.wordpress.org/chouby/
      Link to repo: https://wordpress.org/plugins/polylang/
      Whether you’d like the plugin to be considered for 4.2 – I understand that doing it right will require a lot of work and I suppose it has to be done in small steps. Last year I was talking to plugin author about making some significant and useful changes but we faced lots of limitations of the core. Once these limitations are solved, we will do the rest. So, basically, we just need some core architecture changes that will make it possible to turn Polylang into truly multilingual plugin, flexible and solid. I can describe those changes if there’s interest in at least planning to make it happen.

      • Paal Joachim Romdahl 3:37 pm on February 18, 2015 Permalink | Log in to Reply

        Regarding limitations. What about creating (finding existing) trac tickets to solve the limitations?

        The plugin seems really interesting. I hope you will bring this up again sometime in the future.
        I have added it to my to do list of language plugins to take a closer look at.

    • enailor 7:55 pm on April 7, 2015 Permalink | Log in to Reply

      Sorry I am late to this party, but a plugin that I think is very useful and appropriate is Enable Media Replace. I use this on every project I do and recommend it to anyone.

      WP.org link: https://wordpress.org/plugins/enable-media-replace/

      Måns Jonasson is the author https://profiles.wordpress.org/mungobbq/

      I know its too late for 4.2, but it should be added soon. So many added features around the media uploader and management of media, I am surprised this has not yet been added as a default feature.

      Enable Media Replace allows a user to simply replace an image with a new version, preventing the unnecessary uploading of newer versions of an image in addition to older versions that are no longer needed. Most users, in my experience, do not remove old images from the media library, so the library and hosting account can become bloated with images that are no longer used. being able to simply replace an image with a new one, but keep the original file names, also allows a user to update images without having to find every location of that image on their site. Big advantage if the image has been used on several blog posts.

  • Samuel Sidler 8:13 pm on September 16, 2014 Permalink
    Tags: ,   

    Feature Plugin Chat on September 23 

    Last week we mentioned holding a feature plugin chat today, but that didn’t happen. Let’s have it next week on September 23 2014 20:00 UTC.

    We’ve done this before, but just to recap…

    If you have an idea for a new feature, this will be a great opportunity to bring it up and find others interested in helping out.

    Please leave one comment per feature idea with the following information:

    • A brief (one paragraph) overview of your feature plugin proposal.
    • Current plugin status (idea stage, planning stage, under development, existing feature plugin, prior work, etc).
    • A list of those involved or already interested in your feature plugin (including you!)
    • What you’d like help with (scoping, planning, wireframing, development, design, etc).

    This post and the accompanying chat are for posting ideas that you’d be interested in working on. It is not for posting every feature idea you have for WordPress.

    Current feature plugin leads: Please post an update for your plugin here, along with the information above.

    See you all at the chat!

     
    • Nikola Nikolov 10:08 pm on September 16, 2014 Permalink | Log in to Reply

      The meeting is going to be held in #wordpress-dev channel right? I’m adding the time & date to my calendar :)

    • Caspar 5:35 am on September 17, 2014 Permalink | Log in to Reply

      Added to calendar, thx!

    • Peter Luit 7:35 am on September 17, 2014 Permalink | Log in to Reply

      In general the installation of plugins will have to be done on a site-by-site base. It would be very nice to have the possibility to have pre-defined sets of plugins for certain applications. Now we can just ‘favorite’ a plugin at wordpress.org, in others words ‘you make one set’. Would it be a nice idea to be able to make more sets?

      It could be done in wordpress.org, but it would also be great to have one plugin-installer (as a plugin) in which you can choose one of your own pre-defined sets and then download them all…..

      I am sure the WordPress community would love such a feature.

      Kind Regards,

      Peter Luit
      The Netherlands

    • Siobhan 1:13 pm on September 17, 2014 Permalink | Log in to Reply

      Image Flow is a project focused on improving the the image editing experience in WordPress.

      Current status: UX and wireframes
      Already involved: siobhan, @mor10, @sonjanyc, @markoheijnen, @dh-shredder, @pablo-perea, @edwerd, @klosi, @teamadesign (also less active ppl in the chat room and lots of feedback from people on the UI blog – apologies if I’ve missed anyone).
      What we’d like help with: development (particularly JS), ui design, research, labelling, testing

      • Ryan Boren 12:59 pm on September 18, 2014 Permalink | Log in to Reply

        You know how desperately I want to improve media flow. I’ll be around for research and testing, particularly on mobile.

        Usability as a feature. A featured flow for each release. Each screen of that flow and every tap and click gets attention, on all devices and across all interfaces. 4.1: Starting on your blog’s home page, create and publish a captioned gallery of edited images.

      • Andy Mercer 1:24 pm on September 22, 2014 Permalink | Log in to Reply

        Given that we have Featured Images, would anyone else be interested in the concept of Featured Galleries? Being a metabox, like the Featured Img metabox, which would allowed a user to select multiple images, and be called in a theme template the same way?

    • Nick Halsey 5:08 am on September 18, 2014 Permalink | Log in to Reply

      I have a class during the meeting, so I won’t be there. But I’d like to officially introduce the Menu Customizer as a feature-plugin seeking contributors.

      Menu Customizer is my GSoC Project that I’d now like to build out as a feature-plugin with the help of anyone else who’s interested. The goal is to merge navigation menus into the Customizer. Ideally, this should be done in a feature-complete and backwards-compatible way that allows the mess that is nav-menus.php to go away entirely for users who have access to the Customizer. In addition to leveraging the live-previewing framework that the Customizer provides, this project seeks to improve the user experience of menus as well as fixing several significant technical issues with the current implementation (particularly, scaling). The project is similar to the Widget Customizer project that landed in 3.9 in many ways.

      Current plugin status: development. The plugin is mostly functional, implementing the entire menu-management experience in a Customizer panel and allowing menus to be live-previewed. However, significant work remains to make things scale even better, improve the add-menu-item experience, improve the handling of sub-menus, and make menu-addition and deletion work more smoothly. Many improvements to WordPress core have already come out of this project, including the panels API, and those will need to continue before the plugin is ready to be merged (in particular, for 4.1, #29572 and #28709).

      To date, I’m the only developer working on the project, per GSoC regulations. But the project is now officially open to contributions. I’m in the process of getting set up on plugins trac with @samuelsidler and will be scheduling weekly meetings soon. @ethitter and @obenland are also familiar with the project, as they were my GSoC mentors.

      We need help with the following: development, particularly some JS-heavy components, but also on the PHP side. UI/UX, workflow research, and user testing. Changing the relationships between pages/posts and menus is not in scope, but for the first iteration we’d like to offer a much-improved UI/UX that fixes many issues with the current workflow. This particular project requires significant dev work regardless, which is why formal UI/UX work is happening mid-development. If you’re interested in helping out in any way, please leave a comment here or say something at the meeting (I’ll read the logs), and we can try to schedule the weekly meetings at a time that works for everyone.

    • Aaron Jorbin 9:17 pm on September 22, 2014 Permalink | Log in to Reply

      WP Session manager is a UI around user sessions. We aim to provide users with controls on the user profile screen and user editing screen for managing logged-in sessions.

      Current Status: Under development at https://github.com/johnbillion/wp-session-manager

      Current Team: @johnbillion, @DrewAPicture, @nacin, @jorbin

      What we want help with: Development, design (our UI/UX is currently functional and inline with core, but can always be improved)

    • M. Gage Morgan 11:38 pm on September 23, 2014 Permalink | Log in to Reply

      I think we should bring the post formats UI back again, this time with the new steps added to the process (3.6 “Oscar”).

      Current Status: Needs extracted from the old core files, we’d need somebody to do that. Still in the technical “idea stage.”

      Current Team: Myself, as a student, plus anyone who would be willing to volunteer.

      What I Need Help With: Porting the old files to WP 4.0.(Plus plugin development, I’m new here.)

      • Samuel Sidler 11:40 pm on September 23, 2014 Permalink | Log in to Reply

        There was some interest in this previously, but I’m not sure there’s enough to get it off the ground. If you’re willing to work on it, feel free. Things will have to be quite a bit different for it to be incorporated into core, so keep that in mind. I’d recommend starting from scratch design-wise, going through the steps that the Image Flow team is doing.

    • M. Gage Morgan 12:34 am on September 24, 2014 Permalink | Log in to Reply

      I would think it’s more than possible to do, but it would likely not be ready by 4.1, rather 4.2 or 4.3. I’ll try to work when I can, but scheduling is complicated.

      • Samuel Sidler 12:36 am on September 24, 2014 Permalink | Log in to Reply

        Keep in mind that feature plugins aren’t targeted at specific releases. Inherently they’re flexible and can ship when they’re ready. It’s also possible that a feature plugin never gets into core. That’s fine too. Experimentation is good.

    • Daniel Bachhuber 10:20 pm on September 29, 2014 Permalink | Log in to Reply

      A pretty consistent problem I run into is shortcode UX. Specifically:

      1. Remembering what shortcodes are available to a given site.
      2. Remembering what attributes each shortcode supports.
      3. Preview disconnect (shortcode ain’t WSYWIG)

      It would be neat to have UX in WordPress for selecting from available shortcodes, filling out required vs. optional attributes, and TinyMCE preview framework for registering a display callback for a shortcode.

      I’d be interested in working on this. I’d be best supported with UX help. And I’m pretty curious as to why this problem hasn’t been solved yet (e.g. what big gotchas we’re going to run into).

  • Samuel Sidler 4:40 pm on February 27, 2014 Permalink
    Tags:   

    Feature Plugin Chat on March 4 

    As mentioned at this week’s and last week’s meeting, we’re going to be holding a feature plugin chat on March 4 2014 21:00 UTC. If you have an idea for a new feature, this will be a great opportunity to bring it up and find others interested in helping out. In fact, just like we’ve done before, post your feature ideas here.

    Please leave one comment per feature idea with the following information:

    • A brief (one paragraph) overview of your feature plugin proposal.
    • Current plugin status (idea stage, planning stage, under development, existing feature plugin, prior work, etc).
    • A list of those involved or already interested in your feature plugin (including you!)
    • What you’d like help with (scoping, planning, wireframing, development, design, etc).

    This post and the accompanying chat is for posting ideas that you’d be interested in working on. It is not for posting every feature idea you have for WordPress.

    Current feature plugin leads: Please post an update for your plugin here, along with the information above.

    See you all at the chat!

     
    • scotthack 4:52 pm on February 27, 2014 Permalink | Log in to Reply

      I’d like to see a plugin built that will accept an XML file to import custom post types and taxonomies. That way theme authors can just provide an XML file with their themes. Then the end user can use the import file to create custom post types and taxonomies and it would be imported independent of the theme.

      This is in the idea stage. My coding skills are very basic, so I’d be of little to no help in the coding department. It would need to be picked up by a competent programmer to actually see it through. I’m only able to help with testing, feedback, and idea conception.

    • UaMV 5:33 pm on February 27, 2014 Permalink | Log in to Reply

      Extend proper author/contributor support when defining custom post types. Currently, when a CPT is registered with support for ‘author’, the metabox returns a list of users with the author role (even if those users don’t have ‘edit_posts’ capability for the CPT. Even in the standard post editor, the author metabox includes only users with an author role, not necessarily those who can contribute (or have edit_posts capability). I believe this metabox should return any user that has the ‘edit_posts’ capability for the specific post type in which the author metabox is being supported.

      There is currently a plugin, Authors Autocomplete Meta Box, in the repository that extends this functionality.

      Rachel Carden (aka bamadesigner) is the author of this plugin (commissioned by ereleases.com). I have, as of yet, had no contact with her regarding the plugin, but find it of great use on my site with multiple CPTs and multiple custom roles.

      Not sure at the moment how I might assist.

    • Avryl 6:36 pm on February 27, 2014 Permalink | Log in to Reply

      The Front-end Editor is a plugin that allows posts to be edited on the front-end (so it’s really WYSIWYG) and aims to have all the features available that the back-end editor has.

      It’s currently in development on GitHub and updates a posted weekly on the UI blog.

      I’m the project lead (@avryl) and those who are involved or have shown interest are @azaozz, @brainstormforce, @bravokeyl, @gcorne, @helen, @henrywright, @hugobaeta, @joen‎, @kraftbj, @markjaquith, @melchoyce, @mrahmadawais, @obenland, @protechig‎, @rafaelxt, @rhurling‎, @roundhill, @samuelsidler, @shaunandrews, @tillkruess, @ubernaut, @wholegraindigital and others.

      If you’re interested, take a look on GitHub and join our Skype chat. The next meeting will be Tuesday, 4 March 2014, 17:00 UTC in #wordpress-ui.

    • Chris Reynolds 12:46 am on February 28, 2014 Permalink | Log in to Reply

      AH-O2 (aka Admin Help) is venturing to reimagine the help system in the WordPress admin.

      It’s currently in development is on GitHub with updates being pushed weekly to the WordPress plugin repository. Updates are posted to the Docs and UI P2s.

      I’m the project lead (@jazzs3quence) and other contributors and folks who’ve been involved one way or another are:
      @brainfork, @trishasalas, @jdgrimes, @ubernaut, @zoerooney, @ninnypants, @mdbitz, @clorith, @nikv, and @veraxus

      We need help with:

      1. Documentation — new tooltips are being added to every admin page. Coders (the folks adding them) != writers, so many of these need to be (or will need to be) reviewed, fixed, updated or written. Also, it’s been pointed out that the help overviews we’re building — which replace the help tabs — may not be best suited for the existing documentation in the help tab (which we’re currently pulling from). So help documentation for those areas may need to be edited/changed/added/removed/etc.
      2. Coders — tooltips are added with javascript (and a little php, just to add the translatable string) but fear not! It’s really easy and repetitive. With about 10 minutes of guidance I think I can walk just about anyone through the process of adding a tooltip.
      3. Testers — please break our stuff (and create tickets)! https://github.com/jazzsequence/WordPress-Admin-Help/issues
      Also, extra brownie points to anyone who can test existing, open tickets to confirm/deny a behvior that has an open ticket.

      We meet weekly in #wordpress-sfd on Monday 18:30UTC.

    • Greg Ross 7:50 pm on March 4, 2014 Permalink | Log in to Reply

      The Admin Theme Experience is an update to the existing admin theme system to try and match the site theme user interface. It has two primary goals; simplify the creation of admin color themes and bring the Site Theme Experience to admin themes.

      Current plugin status: under development

      A list of those involved or already interested in your feature plugin: Me!

      What you’d like help with: Anyone with knowledge of the current site theme code would be helpful.

  • Eric Andrew Lewis 6:50 pm on December 18, 2013 Permalink
    Tags:   

    The group formerly known as Metamorphosis Update 

    Yesterday we held our last round of presentations of post meta library authors. Here’s Daniel Quinn on WP Extend, Tom Auger on Zeitguys’ Meta Tool, and Joey Kudish on Custom Metadata Manager.

    RIP Metamorphosis

    Our current project is not a feature-as-a-plugin. Features are big, user-facing elements that would probably get slapped onto a WP version’s About page. We are a bit more under-the-hood. We’re officially now working as the Metadata component group, working on our current task of creating an API for a metadata UI . Although this doesn’t really change our focus, I do think it’s a less pointed perspective to bring to the table, which is good.

    Organizational Changes

    We’ve been operating out of a big ol’ Google doc since day one. That’s been fun, but we’re going to get a bit more organized. I’ve created a project overview page for the Post Meta UI API project Github repo (Updated 1/11/14), which should serve as a portal to all related content.

     
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