1 Comment

  1. Anne McCarthy
    · Reply

    Thanks so much for testing this, Sarah, and for doing a writeup! It genuinely made my week to see you jump in to test this so soon after I posted the call for testing. I hope it was even a tiny bit fun for you to go through despite the overall frustration.

    Right off the bat, you raise something I’ve both witnessed and felt confusion around: the navigation toggle. It’s why I linked to a screenshot as I didn’t trust that people would easily know what I was referring to. You can see some discussion here around the naming of this and how to make it more intuitive: https://github.com/WordPress/gutenberg/issues/29509

    In terms of deleting the template part, I agree. Check out this design that helps narrow in on specific template parts to make that experience a bit clearer: https://github.com/WordPress/gutenberg/issues/29148#issuecomment-789679709 I expect this kind of “zooming in” and “zooming out” aspect of editing a template vs a template part vs general content to be something that will continually be worked on to make it all more robust. Right now, it’s very easy for it all to blend together.

    I opened an issue around the template part name not updating: https://github.com/WordPress/gutenberg/issues/29844 Thanks for calling that out once more as when I was writing the test it was something I noticed but didn’t specifically dive into being a bug.

    With the saving experience, can you expand on what you imagine when you say “the interface could communicate this better”? For now, I’ve tried my best to get creative and capture some ideas/feedback in this issue: https://github.com/WordPress/gutenberg/issues/29846 Generally speaking, the saving flow is another area I’m keen to see iterated upon as it’s a key part of the experience to get right.

    I’m so bummed (yet also excited at the chance to figure out what’s broken) that you ran into issues with embeds and block styles. I jumped in and found a similar issue with the embed block: https://cloudup.com/c-I_B1EBe7Q but I couldn’t replicate the problem you had with the button block. Can you clarify if you added a link to the button block when this happened? For now, I commented on this previous issue related to allow resizing options with embeds as I think that’s the root issue here to create a WYSIWYG experience: https://github.com/WordPress/gutenberg/issues/14805#issuecomment-797808226 Separately, here’s hoping we can get a GIF block as a core block soon: https://github.com/WordPress/gutenberg/issues/13426

    Finally, your feedback around both wanting to see a preview and ultimately needing to is something that has come up repeatedly in both initial rounds for testing. I imagine it will continue to be a major piece of feedback and, for now, I recommend following this issue discussing exactly that: https://github.com/WordPress/gutenberg/issues/29398

    Thanks again! To anyone else reading this, I hope you join #fse-outreach-experiment in slack and join in on this call for testing to find more ways we can move this work forward.

    Report

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: