Woo Design team joins X/Twitter — share your feedback

Brian Coords Avatar
Brian Coords

•

The Woo design team is now on X/Twitter and ready to hear from you! 👋

As we work to improve the core WooCommerce experience, we’re committed to building with the community, not just for it. That’s why our design team is opening up their process and actively seeking feedback from developers, agencies, and store managers who use WooCommerce every day.

What kind of feedback are we looking for?

The team will be sharing design concepts and early ideas for various parts of the WooCommerce experience.

For example, they’re currently exploring:

🎨 Product Variations — How can we make managing variable products faster and more intuitive? What friction points do you hit most often?

📦 Order Pages — What information do you need at a glance? Where does the current order management flow slow you down?

You’ll be able to test prototypes, see early designs, and share your feedback before these changes ship.

Your input matters

Whether you’re building extensions, managing client sites, or running your own store, your real-world experience is invaluable to creating solutions that actually work.

Follow @designatwoo on Twitter to:

  • See early concepts and prototypes
  • Share feedback that directly influences design decisions
  • Stay updated on upcoming changes before they ship
  • Connect with the team building WooCommerce’s future

We’re looking forward to building better experiences together. Follow along and make your voice heard!

One response to “Woo Design team joins X/Twitter — share your feedback”

  1. Diego Avatar
    Diego

    My comment, which I already shared with J. Kemp, is that any interface must provide an EASY way to extend it, for example to add sections and fields to it, as well as validate the input. Like many other developers, I maintain sites where 3rd party plugins add sections to the product editor, e.g. to allow entering country- and currency-specific prices.

    The prototype editor tested a while ago was difficult to extend, and the proposed solutions didn’t work too well. With the existing editor, a couple of add_action() and add_filter() calls, together with a well made HTML, do the trick. If the new editor will use complex scripts (of which I’m notoriously not a fan 😄), then clear, detailed integration steps (preferably on the PHP side, leaving the rendering to the core libraries) will be essential to allow a smooth and robust integration.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *