Community Summit 2017

The Community Summit is coming up on 13-14th June in Paris, linked to WordCamp Europe. It’s a small, discussion-based event where face-to-face conversations take place about subjects and issues, sometimes difficult to discuss online. This is not a Contribution day. Those involved also have a duty to feedback to the rest of the team, you won’t miss out if not there.

The Design Team at the summit

We will be sending a team to the summit like other teams around WordPress. This will be a small group of people, no more than 10. Nominations will be finally decided by the team reps: Mel Choyce, Michael Arestad, Joen Asmussen and myself. The selection will include a range of factors including: diversity of opinions, diversity of people, inclusion, activity of that person within the team, speciality in a topic we’re discussing and also the benefit of their voice to an area being discussed.

Someone from team helping the summit

The team organising have asked for people from each team to step up to help them. Unless anyone has objections, after chatting with other reps that will be myself. The idea is by having members from each team we can ensure our team has a voice and increase the diversity of those organising the summit.

A suggested list of topics

A while ago, we asked for topics and as a result of that and some sorting, we now have a list of suggested topics. We will be using these to nominate people to come to the summit. So what are they? They loosely split into sections like this:

Onboarding

  • Contribution days: how can we have a format that works for even when a designers isn’t there (this relates to onboarding)
  • How do we make onboarding easier for designers? Pattern libraries, interactive Codepens?

Retention

  • Retention of designers: why do we have such a low rate and what can we do about it?

Outreach

  • Diversity: how do we reflect the diversity of our users in those designing.
  • How do we make space for all designers? Design is a wide subject with many roles. How can we make space for UX, UI and beyond?
  • How do we recruit beyond our community? To thrive we need to connect more and reach outside.
  • Outreach inside WordPress: how can we find and also send designers easily to all areas of WordPress. If we are the design team for all of the community, we need to address this and outreach.
  • Design Philosophy – what is it? Are we expressing it publicly in ways that attract other designers?

Process

  • Pattern library: the need for this is getting more, how can we make it happen
  • How do we establish a proper design process across the entire project of WordPress?
  • How do we establish a culture of productive design critiques?
  • How do we make research part of our process?

Role

  • How can we, as a team, best support the design needs of core, and the design needs of the community?
  • What does it look like for WordPress to be design-led, and how can we as a team lead that effort?
  • How is the Design Team, or WordPress is general, impacting design in the world? What are we planning to do proactively?

What next?

It is good to give feedback on the topics. Anything missing we should be discussing? We can chat about this in this week’s meeting which will be at a different date this week:

Friday 17:00 UTC in #design.

We have to respond to the summit post by Friday, March 3rd – so we will be making a decision as team reps from the comments here and discussion in this week’s chat.

This week’s editor meeting agenda for February 22

This week’s chat is happening today, Wednesday February 22 19:00 UTC.

The agenda is:

  • The UI prototype received a number of updates based on feedback from the week before, let’s discuss.
  • Mockups were updated, and collected on Github, thoughts?
  • Some more thoughts on <IE11+ support and how to proceed.
  • Anything else?

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🚀

Core Editor Meeting Notes 2017-02-15

WordPress community has been actively participating to help make the new editor for WordPress. There’s lots of activity both in Slack and at GitHub. It’s an incredible time to contribute.

Here’s the meeting summary for this week’s editor team meeting (agenda here) in #core-editor Slack channel.

MEETING NOTES:

Let’s keep working on the UI prototype — Gutenberg UI prototype. Some ideas for improvements discussed in the meeting are mentioned below:

Toolbars

  • Five of them: I (@mrahmadawais) suggested that we should try to consolidate the multiple toolbars, so there aren’t five.
  • Text vs. Block: Mel (@melchoyce) also felt that Gutenberg UI prototype does feel heavier, she also suggested that the text shouldn’t feel like a block.
  • Blocks Or Not: I tend to agree with her considering it’s hard to think about aligning text across multiple blocks — maybe it’s the block feeling. That said, Weston (@westonruter) said that the different toolbars can be contextual to the block being edited.
  • Selection: @aduth pointed out that selecting all isn’t doable at the moment.
  • Accessibility: @iseulde suggested the docked contextual toolbars make more sense from the accessibility point of view.

Colors

  • Survey: @androb ran a survey — People found the Editor with light colored toolbars to be easy to use.
  • Accessibility:@afercia pointed out that about accessibility standards — contrast ratio should be at least 4.5:1.

Ease of Use

  • Copy/Paste: @dave_navarro noted that Gutenberg UI prototype isn’t an intuitive UI when taking data from multiple sources (newswire, press releases, etc..) especially with a lot of cutting, copying, pasting involved.
  • Safety Net: A few folks suggested that simple fall back editor should be there as a safety net.
  • Rich Content: @joen pointed out that one goal of the project is to make it easy to write posts and help people write truly rich posts with ease; which doesn’t mandate inline toolbars or heavy block outlines on hover.
  • UX Question: Do we need every paragraph and every image to be its own block?
  • The power of Blocks: @sirbrillig suggest that the power of blocks actually comes up in dealing with complicated block type things which previously had to be shortcodes.
  • Text Block: Consider having a growing “text” block, instead of multiple small paragraph blocks.
  • Word Count: Looks like many folks would love the “word count” to still be visible somewhere on the screen. — suggested by @androb

Eliminate the Preview

  • No Preview: @dave_navarro said that the step of hitting preview and switching to another tab to see what it looks like is what he would like to eliminate.
  • Ella’s approach for outlines: Let’s that is, have none, or very faint ones that fade out super fast.

Editor Mode + Layout Mode

  • Two Modes: I (@mrahmadawais) think, perhaps there can be two modes of the new Editor A) For Writing B) For layout.
  • Use Case Specific: @sirbrillig agreed that in the case of long-form writing an editor mode would probably be more appropriate than a full-page preview of the layout. But it depends on the use-case.
  • Full-bleed Images: How would you do a “full-blood image with peephole scrolling” with a theme layout? — Joen (@joen)
  • Multi-Modes: That option might be worth exploring only after we’ve exhausted the current “block-first UI” approach — @joen

Apart from all this, flexbox is being considered for the front end design, but there’s a good deal of discussion about IE compatibility and stuff.

Joen (@joen) pointed out that some great work has been done by @chopinbach, @johnpixle, and @annaharrison 👏

Let’s test Andrews great new prototype!  — show it to your neighbor, use it yourself, take it through its paces. Take notes, and let’s reconvene!

P.S. If I missed anything, let me know in the comments.

This week’s editor meeting agenda for February 15

This week’s chat is happening today, Wednesday February 15 19:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🚀

Initial Editor Blocks prototype editor testing

@iseulde linked another prototype for people to discover in #editor on Slack. It’s a work in progress so very much at this stage discovery and feedback is useful.

How to test?
You can test in any way you want. You can test yourself and also test others. You can take images, audio or video. If you do create a video don’t forget to pull out those bugs, action points and do a summary. Cutting smaller videos out is also really useful.

Questions you can ask:

  • (on first look) Can you explain in words what each section does?
  • Can you re-order? How does it feel? What are your thoughts?

If you find a bug please report it in this repo.
You can also leave results from your testing either as a comment here, or you can link to a blog post.

Initial Gutenberg prototype editor testing

There is a UI prototype now for testing, this is a call for people to start that. If you want to test you can find Gutenberg here.

How to test?
You can test in any way you want. You can test yourself and also test others. You can take images, audio or video. If you do create a video don’t forget to pull out those bugs, action points and do a summary. Cutting smaller videos out is also really useful.

Questions you can ask:

  • (on first look) Can you explain in words what each section does?
  • Can you write a paragraph of text? How does it feel? What are your thoughts?
  • Can you add an image? How does it feel? What are your thoughts?

Reporting:

  • If you find a bug please report it in this repo.
  • You can also leave results from your user testing either as a comment here, or you can link to a blog post.

As specific things need testing, further posts like this can be made.

Thanks to @folletto and @joen for helping with this post.

Edit: as mentioned by @grappleulrich, this is very much in the early stages as a prototype. If you find an issue though please report it on the repo and also focus on how the flows work at this point.

Short guide to testing prototypes

The process for the editor is moving to prototyping and that means an opportunity for testing and getting some feedback. What does that mean? What feedback is useful? How should you do those tests?

From now on, when there is a prototype or something that needs testing exactly, a post on make.blog will be made. The idea there is to also give a place for feedback (one today is coming for the latest prototype).

Beyond that, here are some basic more general suggestions:

  • When testing focus on tasks. Ask people to do specific things.
  • Record somehow the test, be that images, audio or video.
  • Try and test with a range of people and abilities if you can. Meetups are great for that, also look at both users with different levels of experience.

Format wise, how is it best to report?

  • If the prototype has a blog post calling for specific testing, then add as a comment there.
  • If something has bugs, pull out those bugs and report them into the repo for example for the latest prototype.
  • If you record videos, make sure to take notes and also pull out action points.
  • Split the user problem from the user (or yours) advice and solution. A user suggesting a UI change is referring to a deeper problem, and the user isn’t in the position of evaluating all the needs and whys of a change.

Thanks to @folletto and @joen for helping me with this post.

Agenda for February 8 Editor Chat

In past mockups we sketched out how inserting blocks in a block-based editor might work. For the #core-editor chat today, let’s talk about a couple more ingredients: block controls, and changing block types.

It could work like this — click a block to surface block level controls, select text to surface inline controls:

Click the block type indicator to switch to a different, compatible, block:

For the chat, let’s talk about this approach. Questions, comments, ideas? Feel free to bring them up, you can start with commenting here.

Let’s also discuss this wonderful post by Reid Peifer about the editor content creation. What are the best pieces we can learn from?

It all goes down today, Wednesday, 8 February 2017, 19:00 CET! 🎉

This week’s design meeting agenda for February 2

This week’s chat is happening Thursday February 2 17:00 UTC.

This weeks agenda is:

  • An open floor
  • Anything else?

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack

What are you using the Customizer for?

As work continues on improving the Customizer, and the overall Customization flow in WordPress, it would be great to hear how a diverse variety of people within the community use it in their day-to-day workflows.

It would be really useful, if you could answer the following questions:

  • How often do you use the Customizer on your existing sites?
  • What do you use the Customizer for?
  • Have you downloaded and plugins that add new functionality to the Customizer? What for?
  • Do you use themes that add new functionality to the Customizer? What kinds of features do they add?
  • Is there anything in the Customizer you can’t live without?
    Is there anything in the Customizer you never use?
    Is there anything else about the Customizer you’d like to share?

If you’d prefer to answer this anonymously, please use this survey link. It would be great to get this link shared around, so please do.

Thanks for your input!

(Thanks to @melchoyce for working on the questions and draft)