Want to get involved? See the handbook and optionally drop into #design to chat. Most active design work happens in the block editor project, consider dropping into Needs design or Needs design feedback.
There’s a WordPress Component Library in Figma. Duplicate to edit, direct access is reserved for the design team.
Hi design folks! Thanks for all your hard work and contributions in 2015. Could you contribute few more minutes to fill in the 2015 contributor survey? It will help us establish some baselines around the contributor experience so that we can see how things change over time.
**This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.**
The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results by the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could knock it out right after you read this post! 🙂
There are two sections of the survey. The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).
The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.
The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks!
Heads up: I’m taking a leave of absence! See the post on wpdevel make/core for details.
Hi there. I’m starting to think the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Group should be rethought and split into more specific groups, since it has kind of wound up being a CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. and styling outpost of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor group, which wasn’t my original intention. Have been thinking about creating specific areas with less ambiguous goals: graphics, usability/interaction design, CSS/layout, etc.
Like accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), this is an area where there are aspects of design, code, testing, and documentation, and I think that’s part of why it’s been hard to focus momentum… so many possibilities and once a couple of people pick a direction it looks to newcomers like we don’t care about the other stuff. No decisions yet, but in the meantime, if you consider yourself a member of the UI Group (or you’ve expressed interest here and have been waiting for direction on how to participate) you can help determine what happens and how UI is represented at a potential wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ contributor summit by filling in this survey:
http://wordpressdotorg.polldaddy.com/s/ui-contributors
Thanks!
If you’ll be at SXSW this year, RSVP to come to the WordPress party on the 12th! Snacks, booze, WordPress people, what more could you ask for? No SXSW required, just an RSVP.
Also, if anyone wants to volunteer at the booth to help people with their sites/answer questions, get in touch with Rose, who is coordinating the booth.
In 2012, let’s gets things going here again. In 3.3, “UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Group” meant CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. development, which moved the focus in a direction that was unintentional. People can be both application UI designers and front-end developers, but to get this group active again and in the area it’s intended to be producing things, we should get back to improving WordPress admin screen design. We’re going to be shifting the way the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team approaches development timing and assignments in 3.4, and a similar shift should happen here. We should ID all the big and little UI redesign/touch-ups that need to be done and put them in prioritized order (with the things slotted for 3.4 officially coming in first). Then, when we start up again after Jan 1, we should figure out who’s able to work on what.
A fair number of UI involvement has been from people who are good with front-end development and like thinking about UI and/or web designers without much application design experience, vs experienced application designers. These are pretty distinct skillsets, and though it’s possible to be adept in all of them, almost no one is by nature, and experience is necessary to be that kind of crossover hit. We should be pairing people up so that the more experienced application designers can work with those who are still developing that particular skillset. (This is how core development work is going to be structured in 3.4, too.)
It’s been a while since original introductions, and people have come and gone since then anyway. I’m going to be making some changes to this site over the next few days to try and make it a little more conducive to ongoing discussions, comping, etc. In the meantime, maybe we could all re-introduce ourselves for the new year in the comments? Name, URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org, one-liner describing your experience level, note the kinds of UI design you particularly enjoy and/or think you’re good at (specify which), and ID anything in the WordPress UI that you’d particularly like to see addressed in the coming year (and if you have ideas for how to fix it already, say so). This will give us a better understanding of who’s in the mix when we get going on Jan. 3rd.
The core team meetup is over, and the 3.4 cycle will begin in earnest around the third week of January. Official hiatus until after New Year’s! Resume meetings etc then. Project: update http://dotorgstyleguide.wordpress.com/ to reflect any changes since 3.3 and add more sections. Who’s in?
We’ve gradually been updating the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. First the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. went lighter, then the whole thing got a facelift, and in 3.3 the admin bar + header = toolbar. What’s the next style up for grabs? Let’s talk about buttons. 
In 2008, man did we love those pill-shaped buttons. We were all Apple-cool. Primaries in dark blue with white text, secondaries in gray with black text. Is it time to push a little on the button design? It’s been 3 years, so I’m thinking… probably, yeah.
Over on the WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ home page, Andy Peatling introduced a new posting form, a la QuickPress, on the main page for logged in users. If you haven’t seen it yet, here’s the new form:
There’s a lot to like about this (post formats integration, single uploader access point), but the thing I want to point out here is the button styling. Different shape, different colors, different text. I’m not saying these should be transported wholesale into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but it gives us something to think about.
The secondary button (Add Tags) looks a little too much like a Windows desktop toolbar item for me b/c it blends into the background so much, but that primary button (Publish Post) grabbed me right away. In 2.7 we introduced colors in the Dashboard Right Now box — green, orange/yellow, and red — to indicate different statuses.* We always meant to integrate those colors into the rest of the wp-admin design, but never really got around to it beyond coloring delete links red and pending links yellow. ‘Green means go’ is a pretty universal metaphor, thanks to traffic lights around the world. This button is a little too subtle to stand out as the primary action on an action-packed screen like post-new.php, but maybe with bold text and an outline (or maybe an actual green button, or maybe something else) we could consider a shift to using green in the primary buttons.
We stuck with blue back in 2008 using the logic that the submit would take you to a new screen, similar to the way a link would. Since then, however, it’s been an uphill battle to get people to use buttons for submit actions and links for links. Maybe separating them by color would make the difference (subtly) more clear.
If anyone is interested in experimenting, post button comps in the comments. Probably won’t devote much attention to this until 3.3 is out, but if we have stuff in progress, maybe we could get it in early in 3.4.
As you know part of the scope for 3.3 was a revised admin bar that would reduce duplication in the admin headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. The first draft of it has been posted to TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
https://core.trac.wordpress.org/ticket/18197
It needs a color refresh, some optimization, some decisions about which links going where, etc, but is the starting point we are using. Would like to get it back toward the lighter gray we used in the header before, but with some border maybe so it doesn’t look like browser chrome. Fiddling with the links and stuff will happen on Trac, but if anyone wants to mock up some color variations, we have until Sunday.
https://core.trac.wordpress.org/ticket/17739
Need a better label for email field in default theme comment form so it doesn’t sound like it’s promising peace, justice, and respect for email address privacy by blog author/owner.
https://core.trac.wordpress.org/ticket/18301
Goal of this ticket is to make it faster and easier to activate themes in multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. installs. See my comment on the ticket. Looking at a) possible label change, b) adding a highlight state to the themes list table, and/or c) any UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. suggestion that would make this process easier. Let’s hash out early ideas and/or mockups here, and when we’ve got something solid, move over to tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
You must be logged in to post a comment.