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.
Part of the duties of a team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for each area of contributors is to be responsible for a weekly update on the group. At this moment, there is not an established 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. team rep, but as a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team representative, I’m happy to step in until new elections are done sometime in the near-ish future.
Part of our UI group discussion at the Community Summit was about how we can make these weekly updates both informational and effective, especially when it comes to attracting and retaining contributors. Here’s what we’re thinking:
Thoughts? Love it, hate it?
A summary of the Community Summit discussion on 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 has been published. Thanks to @sabreuse for her wonderful note-taking! Feel free to discuss the notes, and do hold us accountable for our action item. Weekly summaries will also begin very soon.
Note: meeting on 8/7 did not really happen, as many were traveling or otherwise out of commission post-WCSF.
Meeting was largely focused on status check of various items and really bearing down on assignments and breaking down tasks into what can be realistically accomplished within a given time period (the next week) so we can regularly check in. Setting the goal is not the maximum that can be achieved – only the minimum. Things finished early or with aplomb are highly encouraged 🙂
Reminder: devs should ideally be focused on one large item at any given moment. Working on your own pet projects and roaming around is always fine, but would prefer to stay away from overcommitment, especially for point people. This includes me 🙂
Logs: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2012-07-31&sort=asc#m49644
And finally, a reminder that open office hours are every weekday at 19:00 UTC (3PM EDT). #wordpress-ui is always open for discussions, but if you’re a little more nervous about just poking your head in or want to schedule something with a group, it’s a great time to do just that!
The current goal is to HiDPI/2x current assets, whether that’s through making new versions of various images/icons or converting to CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. solutions (pretty much gradients and perhaps comment bubbles). Longer-term we may end up using other solutions, but for the moment let’s focus on the task at hand.
I’ve left a long comment about things I’m seeing as still needed. No need to know how to do the CSS patching – a dev can jump in and do that part if you’re more comfortable with the graphics side. What we need is people helping out with creating 2x versions of things, sometimes in various colors. We may need to coordinate with @empireoflight (Ben) to make sure there’s no duplicate effort.
You’ll want to be uploading files to TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. for the most part – if you want to have somebody take a look first, feel free to post a comment here or talk about it in IRC (office hours are a great time for that). Note that uploading files to Trac does not trigger an email notification, so you’ll want to leave a comment noting what you’ve added so it’s not overlooked. Again, feel free to ask questions here or in IRC if you’re not sure what to do and we’ll try to get you sorted!
Scope meeting in #wordpress-dev tomorrow, July 11, at 20:00 UTC is an official go. Not being a developer-type doesn’t mean you shouldn’t be there, even if you just lurk. Discussion will be had about scheduling and planning features. See you there!
http://wpdevel.wordpress.com/2012/07/11/version-3-5-scope-session-on-wednesday-july-11/
Strong teams and good team members are those who know themselves well and can identify both their strengths and weaknesses. Consider the following:
Don’t feel pressured to write a novel. Just wanted to give everyone plenty of questions to consider and a chance to get to know each other a little better, at least virtually 🙂
What are some bigger ticket items that we’d like to see happen in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? What really needs to be made better/easier/prettier but takes some effort to achieve?
Again, one item per comment, and then discuss each (or add your +1) in replies to that comment. Talk about what you think effort might be, how it might be broken out into subtasks, and whether it’s something you see as a feature/enhancement for 3.5 or a longer-term project for another future release.
What can we identify as low hanging fruit from the user tests run thus far or other experiences? What existing features can we quickly iterate on and make better?
Let’s put one piece of fruit per comment, and then discuss each (or add your +1) in replies to that comment. Be as specific as possible – perhaps mention the item, what makes it not quite right, what can be better, and what we can do about it.
I would like to note here that we encourage plugins for proposals that involve UI changes because not all people (or realistically, the minority of people) know how to apply a patch or have an environment in which to do so. A pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, whether or not it’s actually in the .org repo, is a better way to get non-coding types to have a go at testing. I think this is sometimes not well communicated or understood and can come across as a brush-off, so I thought I would write it out here again.
