Editor weekly office hours for April 5th

It’s spring, it’s busy, and everyone is deep in work on the plugin. So we’re making a small change to the format. Instead of weekly meetings, we’re doing weekly office hours. That is, you’ll be guaranteed to find someone in chat, ready to discuss any topic you’d like to bring up.

The office hours start at 17:00 UTC, 19:00 CEST. Here’s a handy link: Wednesday April 5th 17:00 UTC. Yes, we’ve double-checked that.

Since last time:

  • Work is proceeding on the plugin. Follow it in Github, for example this link.
  • Feel free to leave a comment and we can discuss anything people want.

Remember, even if there are now office hours, the #core-editor channel in Slack is open 24/7! 💫

Some results from user testing the prototype Gutenberg Core Editor

During WordCamp London contributor day, Martin Lugton (@martinlugton), Johan Falk (@j-falk) and Lucijan Blagonic (@lucijanblagonic) created a user testing script to test the features of the Gutenberg editor. This is a guest post from them of their findings.

Issues observed:

  • When an image is aligned left or right just above the heading, the heading block encompasses the image block. Could probably be corrected with adding CSS to clear the floated element?
  • Adding links when no text is selected creates a link with no text. Maybe force the user to select something?
  • Dragging and dropping of blocks. In prototype 3, the user can drag and drop blocks. But this is only allowed if a user clicks on the left- or right-hand border of the block. Could we allow users to click and drag a block from its top or bottom border as well? Could we allow users to click and drag a block, just by clicking somewhere in its body?
  • Adding new block at the top of the page. Do we want to allow and facilitate this?
  • When adding new blocks, the user clicked on the HTML link instead of Paragraph.
    Could we rearrange the links in a more meaningful way? (Headings, Paragraphs, Images, Embed, Quote and HTML (last)).

Gutenberg Core Editor User Testing

This is a guest post by Martin Lugton (@martinlugton), Johan Falk (@j-falk) and Lucijan Blagonic (@lucijanblagonic).

During WordCamp London contributor day, we created a user testing script to test the features of the Gutenberg editor. The aim was to build a set of instructions so that people can easily carry out user testing, and quickly share the results.

We prepared 18 questions that cover the functionality of the prototype, and created a form for recording the results. This form populates a spreadsheet that gives an overview of each task and each test. This will allow us to identify which tasks are easy for users to complete, and which ones need some further design work.

We did one test run (with only a handful of questions) and one full run with a test subject (Thanks, @Jip). The whole interview is 24 minutes long and can be viewed here:

Part 1, Part 2 and Part 3.

Tammie Lister (@karmatosed) suggested we add another text field where the user can write down comments. We also added conditional formatting to the results spreadsheet so that tasks which were rated with 3 or lower (out of 5) are marked red. If you want to use this form you can or create your own based on it.

How to do the tests:

  • Open the interview form and resize to 1/3 of the width of the screen
  • Open Editor Prototype and resize to 2/3 the width of the screen
  • Use a screen recording app or the Chrome plugin Screencastify to record the whole screen. The free version of Screencastify version caps at 10 minutes, but you can record multiple videos.

Video showing how to test up the test environment:
https://drive.google.com/file/d/0B17jK6_GMrE5bzVObHgyLThhb1E/view

How you can get involved in user testing the new editor:

  • Test the prototype yourself:
    • Follow the above instructions (“How to do the tests”)
    • Post a comment on this post with your test videos, and highlighting any key problem areas.
  • Find some users to test the prototype
    • Send them the above instructions, so that they can fill out the form themselves
    • Watch the video of their session. Make a note of anything interesting.

Post a comment on this post linking to your test videos, noting any key insights.

This week’s design meeting agenda for March 30th

This week’s chat is happening Thursday March 30 20:00 UTC.

This weeks agenda is:

  • Open floor

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

See you in the #design channel in Slack

This week’s editor meeting agenda for March 29th

This week’s chat is happening Wednesday March 29 19:00 UTC. Edit: Due to an unfortunate typo by yours truly, this weeks meeting was kept very short. More details here.

The agenda is:

  • Work is proceeding fast on the editor plugin. Anyone have something to share or discuss?
  • Anyone have test results to share?
  • With DST here, is there a better time for the weekly meeting?
  • Anything else?

As a reminder, day to day work happens in the GitHub repository. 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-03-23

Well, the development of WordPress Gutenberg feature plugin has begun. Lots of activity, Slack fun meetings, GitHub issues you should check out. Here’s the meeting summary for this week’s editor team meeting (agenda here) in #core-editor Slack channel.

  • Testing: Lots of tests done at WC London. Summaries will be posted and referenced on GitHub.
  • Plugin Dev: Gutenberg Editor plugin development has begun. Starting with the API. 🎉 — Catch up on this GitHub project.
  • API Discussion: This PR around the API doc is a good start to see the pieces 1 & 2.
  • Better Developer Documentation: Need to work on better dev documentation so the barrier to contribution gets lowered.
  • TinyMCE link boundary feature trucks on. Has some accessibility challenges, but those could be used for good (link).
  • Accessibility recommendations: A good ticket with accessibility recommendations we should keep in the back of our mind.

That’s about it, happy hacking! 🚀

Design meeting time change

From next week we are changing our weekly meeting to be Thursday March 30th 20:00 UTC.

Some people will never be able to make the meetings because timezones are hard. Lets try this and see if we can get some people there who haven’t been able to make the earlier time. All chats will take place in Slack, so there is an archive.

Lets also take this opportunity to see if anyone wants to take notes – reply in comments if you are up for that important task (we can rotate it more than one).

This week’s design meeting agenda for March 23rd

This week’s chat is happening Thursday March 23 17:00 UTC.

This weeks agenda is:

  • Should we change our time of meeting?
  • Anything else?

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

See you in the #design channel in Slack

This week’s editor meeting agenda for March 22nd

This week’s chat is happening Wednesday March 22 19:00 UTC.

The agenda is:

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-03-16

We’re getting closer to having a new WordPress editing experience. Lots of activity, Slack fun meetings, GitHub issues are filled with discussion, you’ll love to read. Here’s the meeting summary for this week’s editor team meeting (agenda here) in #core-editor Slack channel.

  • Main Focus is moving away from the prototypes, feature plugin starting soon.
  • API & Data Structures: At this stage, we also need to focus on defining the APIs and data structure we’ll be working with.
  • Columns Mockups: @georgeolaru Built incredible mockups for exploring columns-based blocks.
  • Pros & Cons of the third prototype will be revisited.
  • Feature Plugin: As we move on to feature plugins, important to think long and hard about the pros and cons of each, compare the essence of the single and multi-instance approaches.
  • Let’s Work Together: Important we all work together, and review each others work in pull requests, and chat in #core-editor Slack channel.

That’s about it, happy hacking! 🚀