• Resolved irishetcher

    (@irishetcher)


    While I am starting to really get into using the block editor on projects there are some things that are really really irritating concerning documentation, support and what’s new.

    The plugin page for Gutenberg developers tab now only links to a GitHub for the changelog when it used to be available on that page, with all the versions going back to 0. While the gitHub links to the latest changes it’s a bit of a mystery on where to find the other latest releases in the event that one hasn’t checked in for a while to see what is going on.

    Strange, considering the new block editor was meant to get rid of the mystery meat, here everything to do with development is a mystery?

    It seems to be the form for much of Automattic software. I see the same archaic approach when you want to send feedback regarding features in WooCommerce. You come to a page like this and submit a suggestion or criticism and you are directed to post it on some GitHub page to be voted on, or rather to be lost in the ether.

    While I am guessing there is merit in using GitHub for developers, for day to day customer support and experience its a pretty drab experience and not very exciting.

    This is the one reason why I still rate Gutenberg in the 2.5 to 3 category. While the UI UX in using the block editor is improving dramatically, the other aspects of UX and CX are still lagging, like they did from the beginning.

    The obscure reasoning of implementation and transition, where you need to add Classic Editor plugin, suggesting the workings for this are in that plugin, when in fact it is just an additional switch in WordPress to suppress the block editor, still baffles me. It caused a lot of confusion and controversy when it needn’t of have had.

    • This topic was modified 4 years, 9 months ago by irishetcher.
    • This topic was modified 4 years, 9 months ago by irishetcher.
Viewing 1 replies (of 1 total)
  • Plugin Author Jorge Costa

    (@jorgefilipecosta)

    Hi there!

    I’m sorry removing the changelog from the plugin page and linking to the release page made it feel like transparency was being removed. That was never the idea, the change happened because of technical limitations related to how big the changelogs could be, and sometimes there were problems during the release because of passing this limit.
    We also publish a post with the changelog on each WordPress release on make.wordpress.core. On this link https://make.www.ads-software.com/core/tag/gutenberg-new/, it is possible to see all the changelog posts, so I hope this link may be useful to check changelogs of multiple releases.

    Regarding the classic editor, for now, it is mostly a switch like you referred. But the idea to have a plugin is that with time the plugin will grow, and functionality may be moved from core to the plugin. In the future, it may be something more than a switch.

    Thank you for sharing this feedback with us!

Viewing 1 replies (of 1 total)
  • The topic ‘A bit more transparency please’ is closed to new replies.