• The new WordPress editor, “Gutenberg,” available for early beta testing!

    Super excited that Gutenberg, the new Editor for WordPress, is available for early beta testing in the WordPress.org plugin directory. I'm using it right now to type up this post!

    Gutenberg's going to need a lot of eyes on it over the next couple months so we can work out all the bugs. If you test it and find a bug, please open an issue on GitHub.

    Happy posting!

  • WordPress 4.8 “Evans” released!

    An Update with You in Mind! Gear up for a more intuitive WordPress! Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard


    Check it out: WordPress 4.8 “Evans”

    Super excited about this release! I’ve been pushing for an image widget for years now, so it’s super great to finally see it released. Give it, and the new widget updates, a spin :)

  • Consistency and Perseverance

    Consistency and perseverance is the difference between realising a dream and seeing it through, or it never materialising at all.

    – Nguyen Le, Consistency and perseverance is so underrated

    In his most recent article, Nguyen writes about the importance of consistency and perseverance, and what it means to just keep going despite failure and rejection. It’s good advice for pretty much everyone, but feels particularly important for me currently. I’ve taken on some new responsibilities this year and my fear of failure is pretty dang high. In order to make things work I need to keep showing up, keep working hard, and never stop trying. Something important to keep in mind when things get frustrating and I feel like nothing is moving forward fast enough.

    PS — Nguyen runs an awesome newsletter I read each week. You can sign up at his site. Want to know who else I follow? I wrote about designer newsletters I subscribe to.

  • Design and Exclusion Conference

    Later this month, Automattic is hosting a remote conference on design & exclusion:

    The products we build can perpetuate exclusion and marginalization, often despite our best intentions. On April 21, join a free, online conversation with design and technology leaders about the people and groups that we sometimes exclude, and the need to create products and services that welcome them. Tune in right here.

    I’m helping out with some of the web and design work, along with Kjell Reigstad.

    Keep an eye on https://x.design.blog/ for more info.

  • Open Source Design

    This upcoming weekend, I’m presenting at the Lesbians Who Tech Summit in San Francisco on The Untold Struggles of Open Source Design. My presentation is based on my experiences as a designer and contributor to WordPress, and goes into issues around attracting and retaining designers, process, and leadership.

    As I work on my presentation, I’m realizing more and more the need to cross-pollinate with other open source communities. WordPress is an older community, but we’ve seen a lot of turnover in the past twelve years. Some of our habits are engrained based on our long history. There’s a lot we can learn, both from more well-established projects and from newer projects.

    So, consider this my public commitment to learn from and share more with other open source design communities. I’ve started by asking around about what communities currently exist. I’ve received a number of replies I hope to look more into:

    https://twitter.com/eli_schiff/status/833430304811601922

    https://twitter.com/mairin/status/833441356836134912

    If you’re a design contributor to another open source project, let’s chat.

  • The Social Internet

    Typography, as Postman describes, is in essence much more capable of communicating complex messages that provoke thinking. This means we should write and read more, link more often, and watch less television and fewer videos—and spend less time on Facebook, Instagram, and YouTube.

    — Hossein Derakhshan, Social Media Is Killing Discourse Because It’s Too Much Like TV

    While I pulled out this specific quote about writing and typography referencing Neil Postman’s work because it resonated with me as a designer and someone who blogs, Derakhshan’s entire piece is a valuable critique of social media and the current state of the internet.

    Derakhshan’s online activism and his blog landed him in an Iranian prison for six years. A notable early blogger, he found the internet after his release a radically different place from the internet he knew before incarceration. He wrote about this (ironically) on Medium in 2014. I remember reading his post then and finding myself tentatively nodding along with with a lot of what he wrote. I’ve just reread it and I find it all the more relevant in a post-2016-election America. Take, for example:

    “Nearly every social network now treats a link as just the same as it treats any other object — the same as a photo, or a piece of text — instead of seeing it as a way to make that text richer. You’re encouraged to post one single hyperlink and expose it to a quasi-democratic process of liking and plussing and hearting: Adding several links to a piece of text is usually not allowed. Hyperlinks are objectivized, isolated, stripped of their powers.”

    Reading that reminds me of the Verge’s recent article, “Facebook and Google make lies as pretty as truth.” All embedded content, for good and increasingly for ill, is treated with the same amount of weight. It’s easy to game. It’s becoming increasingly harder to tell truth from lies, high from low quality, and ads from, for a lack of better words, real content. This is a design problem that as an industry we need to be cognizant of. We need to work towards some sort of solution.

    Reading both of these pieces again, it also reinforces the importance of owning your own content. Just look at Vine. As our freedoms start to wane, the open web becomes all the more important. Start your own blog rather than relying solely on someone else’s platform. Backup regularly. Write frequently.

    I’ll try to write more this year as well.

    H/T John Maeda for sharing.

  • Behind the Scenes of Twenty Seventeen

    It’s a wrap! After months of work and over 100 individual contributors, Twenty Seventeen, the new default theme for WordPress, shipped yesterday in WordPress 4.7 “Vaughan”:

    WordPress 4.7 “Vaughan”

    Twenty Seventeen was the first default WordPress theme I’ve had the pleasure of working on. I wanted to talk a little bit about the design and history of theme, and how we got to where it is now.

    The design that would eventually become Twenty Seventeen went through a couple iterations. At its earliest, it was a one-page restaurant theme that we didn’t feel comfortable tackling yet at Automattic. Once we figured out a good way to do multi-page homepages, I brought it back up and it was suggested I turn it into a business theme. This theme would eventually become Lodestar, a yet-to-be-launched theme on WordPress.com.

    Another couple rounds of iteration to introduce a more interesting grid, sharper typographic system, and the idea of video headers brought us to where Twenty Seventeen is today.

    The coolest part of Twenty Seventeen wasn’t just watching it come to life, it was also watching it work with WordPress core to introduce new features: video headers, starter content, and even edit shortcuts (another feature I worked on alongside the Customizer team). The theme worked well with the release, which was centered around the idea of “your site, your way.” 4.7 is one of the most exciting releases yet, and I’m happy Twenty Seventeen contributed to that.

    Of course, any good default theme also needs a strong team behind it. Working with Laurel Fulford and David Kennedy on the theme has been an absolute pleasure. Laurel coded my designs with accuracy and precision, and was ever patient and gracious in the face of my nitpicking. DK kept us on-track, and made the hard decisions that led us to success. You can read his writeup here:

    https://davidakennedy.com/2016/12/07/dear-twenty-seventeen-contributors/

    I’m thankful for all 103 contributors who helped create Twenty Seventeen:

    aaroncampbell, acmethemes, adammacias, afercia, ahortin, akshayvinchurkar, alex27, allancole, anilbasnet, b-07, binarymoon, bradyvercher, brainstormforce, caspie, celloexpressions, claudiosanches, clorith, davidakennedy, davidmosterd, delawski, dimadin, dineshc, doughamlin, electricfeet, enodekciw, fencer04, for, grapplerulrich, hardeepasrani, helen, hiddenpearls, idealien, imnok, implenton, implenton, initial, iv, joefusco, joemcgill, johnpgreen, jordesign, joshcummingsdesign, joyously, juanfra, karmatosed, laurelfulford, leobaiano, littlebigthing, lukecavanagh, mageshp, mahesh901122, manishsongirkar36, mapk, mattwiebe, mbelchev, metodiew, mor10, mrahmadawais, netweb, nikschavan, nnaimov, noplanman, nukaga, ocean90, odysseygate, patch, patilvikasj, peterwilsoncc, pratikchaskar, pressionate, presskopp, rabmalin, ranh, rianrietveld, ryelle, sami, samikeijonen, sandesh055, sgr33n, sirbrillig, sixhours, smyoon315, snacking, soean, sstoqnov, swapnilld, swisspidy, swissspidy, taggon, tg29359, themeshaper, transl8or, tsl143, tywayne, valeriutihai, voldemortensen, vrundakansara, westonruter, williampatton, yoavf, yogasukma, and zodiac1978.

    All you folks were a pleasure to work with. We made a pretty dang nice default theme, if I do say so myself.

  • Speaking at WordCamp US

    https://2016.us.wordcamp.org/2016/10/27/wcus-speakers-part-2/

    I’m happy to announce I’ll be speaking at WordCamp US this year!

    I’ll be giving a lightning talk this year, focused on new user experience (NUX). Come listen to me talk about the various improvements we’ve made to WordPress.com’s NUX in the past year or so, and what we’ve learned from A/B testing and iteration.

  • Comments

    It’s taken me a while and a lot of thought, but I’m finally throwing the switch and removing comments from my blog for good.

    — Goodbye to Comments – Ryan Markel

    My colleague Ryan Markel offers insights into why he’s removing comments from his blog. I agree with his reasoning, and to be honest, I’ve considered doing the same for my blogs — but receiving comments on my blog itself is rare enough that I’ve never bothered. If anything, most of my engagement happens through Facebook or Twitter.

    Maybe I’ll also turn off comments when I eventually launch the site redesign I’ve been working on. Who knows?

  • Design Feedback

    As some of you probably know, I’m a design contributor for WordPress. Lately, I’ve been working on Twenty Seventeen, the latest default theme. It’ll be released this December with WordPress 4.7.

    A topic I wanted to bring up early in the public process for making Twenty Seventeen was design feedback. Designers, either through art school (which I didn’t go to), or working with other designers on teams, or even open source contributing, need to learn how to give and receive feedback. Most other people don’t have to learn this skill to succeed at their jobs. However, anyone can learn how to give good design feedback, even if you aren’t a designer. In fact, I believe it’s a good skill for anyone working in product design to learn. If you’re an agency designer, it’s also a good skill to teach your clients.

    Here’s how I think good design feedback should be structured:

    • Empathize. Remember that behind every design is a person. If you wouldn’t say it to this person’s face, don’t say it on the internet.
    • 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.

    Twenty Seventeen’s been going swell and we’ve had a lot of great contributions and feedback from the community. Thanks to everyone who’s left a comment, or made a GitHub issue, and helped keep the process positive. :)