WordCamp Tokyo 2019 – Keep, Burn & Add exercise

At WordCamp Tokyo 2019 we followed last year’s exercise from WCUS and ran a Keep / Burn / Add workshop interactive activity. The idea is to explore from a high-level perspective where WordPress is going for that part of the community and how it could be improved.

Note: these are individual opinions, and as such, it should be considered as first-level research to be read and interpreted, not as an absolute list.


❤️ Keep

  • Gutenberg: drag & drop blocks
  • Appearance ⇒ Customize: Live preview
  • Automated SEO
  • CMS allows posting articles without deep knowledge.
  • Autosave feature (version-revision and auto-save functionality)
  • Handy posting from WordPress mobile app
  • Preview on HTML on the editor
  • General Setting allows changing Site Address (URL)

🔥 Burn

  • Customizing themes (4 opinions): difficult to customize, hard to manage, and so on.
  • Too many configuration settings
  • Too many navigation menus
  • Tend to add too many customizations
  • Too many admin notices
  • Installation settings are difficult
  • Plugin management requires manual work on WP dashboard instead of https://wordpress.com/ page: auto-update is not working, version compatibility issues, risks, …

➕ Add

  • Multi-Language support with Multisite (2 opinions)
  • Collaboration with live editing
  • Pre-set essential plug-ins (light-weight)
  • Customizable user interface
  • More Graphical User Interface than text-based UI
  • Easier use on mobile
  • Easier to operate visually (like Adobe Illustrator)
  • Hard to understand the difference between “.com” and “.org” for newbies. While “.org” seem to have more information than “.com”, it will be nice to have in-between information page to fill the gap between “.com” and “.org”.
  • Have thumbnails column with titles on “All pages” and/or “All Posts”.
  • Enhance automated SEO settings
  • A better learning experience for Gutenberg

Thanks to @miekoyo for writing this recap.

Add yours

This is the perspective of the participants at WordCamp Tokyo 2019 Contributor Day Design Table. What’s your perspective?

#wctokyo #contribution-day #workshop

WCEU contribution day recap: design team

During WCEU the design team had a great showing of people wanting to contribute. As discussed before the event, our plan was to split into a team

General table

A table was formed for ‘other’ tasks, these included working on triage for Trac and ‘Block directory usability testing’. A test was written and also tickets triaged ready for 5.3, with a focus on a11y tickets for media. Some great conversations were had and collaborating between other teams flowed.

Figma table

One of the two dedicated focus tables was about Figma and lead by @tinkerbelly. Here is a brief recap of what happened:

  • On-boarded new contributors to Figma.
  • Started working with the components.
  • Compiled some feedback for improvements; most of which would be documentation/process.
  • Working on improving documentation, establishing procedures for working with and maintaining the library, and creating starter templates.
  • Also added a grid layout style and two new components.

Gutenberg table

The second focused table was lead by @mapk and involved a dive into Gutenberg design. There was a great discussion around the future of Gutenberg and how it’s changing WordPress in a good way. The designers were encouraged to comment on at least one issue in GitHub. A couple of people also worked on mockups. Issues commented on include:

If anyone worked on other tasks during the contributor day please leave a comment. Thanks to everyone that attended.


WCUS contribution day exercise: keep, set on fire, add

At WCUS contributors to the design team got together for a short interactive session of things within WordPress they wanted to keep, set on fire or add. Some interesting points came up so worth taking out of the workshop setting and writing up for everyone.

Note: these are not one opinion, they are the thoughts of everyone at the workshop.

❤️ Keep

  • Menus.
  • Customizer.
  • The installation process.
  • Multiple ways of getting to different parameters.
  • New wordpress.com logo.
  • Themes.
  • Block plugins.
  • Gutenberg * 2 votes.
  • Blocks * 3 votes.
  • Divi.
  • Add pages in navigation.
  • Amazing people.

🔥Set on fire

  • Page on front.
  • The current user-facing menu builder.
  • 10, 000, 000 meta boxes
  • Interface inconsistency.
  • When WordPress breaks.
  • Static list tables.
  • Split UI/ Blocks vs dash.
  • The automatic blogger style.
  • 2 color WordPress logo.
  • Widgets and Widget Areas (in their current form).
  • Clutter on dashboard.
  • Widgets.
  • Comments (native).
  • Vulnerable themes/plugins.
  • Older packaged themes.

➕ Add

  • WordPress.com home page. Add real people.
  • Domain search.
  • Designed for mobile.
  • Ease of creating unique layout transitions.
  • WordPress first context collaboration.
  • Blocks everywhere!
  • Cleaner media organization.
  • Design system for admin / plugins.
  • Direct manipulation.
  • Context editing.
  • Other shapes.
  • Static output and disconnect from database.
  • Better onboarding.
  • PWA (Progressive Web Apps).
  • An actual media manager with file replacement and better media managing.
  • Color palette.
  • Visual page template creation / selection.

So, what would you keep, set on fire or add?

#wcus #contribution-day #workshop

WordCamp US 2018 design contribution day summary

Last weekend at WCUS the design team ran a workshop based session. The focus was around blocks. @joshuawold was co-lead with myself leading and @melchoyce, @kjellr, @lessbloat also took groups to work with.

The day was loosely planned out as:

  • Introduction
  • Sketch yourself on post-it and share.
  • Get everyone on Slack.
  • Interactive session: ‘Keep, set on Fire and Add’. Pick up to 3 things for each section within WordPress.
  • Information about what the design team does shared in Slack.
  • “Thinking in blocks”: pick up to 3 existing sites and break into blocks. Add to InVision.
  • “Block focus”: pick a block to begin designing from ones identified before.
  • Choose your own adventure: after lunch we had a few options that people could do. Votes ended up falling on 2 options:
    • Triage: run in Slack for an hour to show how it happens, thank you to those that joined remote.
    • Continue designing blocks and thinking about them.

Follow along

During the day everyone’s work was put into various InVision boards and Figma:

You can also follow along the Slack archive of the day as lots of great discussion took place.

@joshuawold has a post coming up about the navigation block work done and there will also be one on the ‘Keep, set on Fire and Add’ session.

#contribution-day #wcus

Facilitating a contribution day for design handbook update

As previously discussed in Slack #design, @folletto and myself worked on a contribution day format suggestion. This was tested at WordCamp Tokyo and from there a document was created to iterate based on feedback.

There is now a new handbook page, this is just a suggestion but has a guide to help you facilitate a successful contribution day for design.